----------

Map95v2 v2.30 Release Notes 4/16/2023

1.0 INTRODUCTION

This release adds the following feature:

A feature was added to enable/disable the SSH server on the target device. The feature is found under the Tools drop-down menu.

This release corrects the following:

Following a controller reset, Map95 will re-read the firmware version from the target device to determine if the firmware changed and to reevaluate which version of PuTTY is required to support the device.

----------

1.0 INTRODUCTION

This release corrects the following:

The new version of PuTTY, included in the v2.27 release, requires the Visual C++ 2019 Runtime libraries be installed on the system. While these libraries are usually already available on the system, there is no guarantee they are installed. The Map95 installer was modified to include the Visual C++ 2019 Runtime installer. The Visual C++ 2019 Runtime libraries need only be installed once. After that, Windows system update will automatically update the libraries. A checkbox in the Map95 installer will allow the user to choose whether to Launch the Visual C++ 2019 Runtime installer. If the libraries are already installed, the installation will fail and display a message indicating a new version of the library is already present on the system.

----------

1.0 INTRODUCTION

This release adds the following feature:

The Map95 package now includes two version of PuTTY, v0.77 (released in 2022) and an unlabeled version from 2014. Map95 will selectively launch PuTTY, for SSL connections, based on the primary controller’s firmware version. This is to address SSL compatibility as Loop migrates the SSL implementation to WolfSSL. Telnet and serial connections will utilize PuTTY v0.77 in all instances.

O9500-PTN v2.7.1 and later will utilize PuTTY v0.77 for SSL connections.

The O9500R, O9400R, O9400R-CC16, O9400-PTN and O9550R will continue to utilize the old PuTTY version for SSL connections.

----------

1.0 INTRODUCTION

This release corrects the following:

The 8GESW and ETH-SW cards do not support warm reset. Map95 was allowing the user to select a warm reset for these cards which would subsequently cause a cold reset. Map95 was modified to disable and grey-out the warm reset button for these cards.

----------

1.0 INTRODUCTION

This release corrects the following:

Map95 did not correctly reset the E&M, FXS, and FXO cards, following a firmware upgrade, when installed in the O9500. Instead, it was resetting the cards to default configuration.

Map95 was unable to retrieve the FAE package from the O9500-CC4 running firmware v3.18.01.

This release adds the following features:

Support for FPGA upgrade of tributary cards. “File – Transfer – Send Card Firmware”

Redesign of the firmware upgrade process for both the controller and tributary cards. The new process provides more user feedback and monitors the system through the controller or card reset required to switch firmware banks.

Ability to reset tributary cards from Map95 interface. “Tools – Reset Card”

----------

1.0 INTRODUCTION

This release corrects the following:

Map95 was not correctly reading the cross-connect type when reading the cross-connect table from the B2G5 card installed in the O9500ptn.

Map95 was not correctly reading the cross-connect type and the secondary source when reading the cross-connect table from the PTN card.

Note: If users have either of these cards installed in an O9500ptn and used Map95 to export the cross-connect table for backup, they should generate a new export file.

----------

1.0 INTRODUCTION

The user can view the “Active Alarm Summary Table” in the O9500ptn. The feature is found under the “view” menu.

When creating cross-connects, a warning will be displayed if the user attempts to create a loopback cross-connect.

----------

1.0 INTRODUCTION

PTN10G

63 Port E1/T1

FOM7

B155-622

This release adds the following feature:

The cross-connect display was modified to denote uni-directional cross-connects. A uni-directional cross-connect will have a bar-line in front of the arrow, similar to the electrical symbol for a diode.

----------

1.0 INTRODUCTION

O9500R-PTN, dry-contact card. Map95 did not display the cross-connects for this card.

----------

1.0 INTRODUCTION

----------

1.0 INTRODUCTION

O9500R-PTN support for the 8GESW - 622 card. .

----------

1.0 INTRODUCTION

O9550, O9500, and AM3440 support for the 6UDTEA card.

----------

1.0 INTRODUCTION

O9550 support for the ABRA card. Mode 1 only, as mode 2 does not appear to be supported by the controller.

Support for the O9550-D chassis.

----------

Map95v2 V2.07 Release Notes 10/02/2020

1.0 INTRODUCTION

Support for Support for ABRA card, mode 2 (Voice Protection).

----------

1.0 INTRODUCTION

A feature to pull FAE package was added. This appears under the "File - Transfer" menu.

This release corrects the following:

Corrected a TFTP protocol problem when sending files to the device. This only affected transfers where there was no TFTP option negotiation.

----------

1.0 INTRODUCTION

This release adds a ULSR Tool to Map95, to help with the tedium of mapping ULSR rings. This tools has the same look and feel as the ULSR Tool in Map34.

----------

1.0 INTRODUCTION

This release adds mapping support for the 1FOMB card on the O9500R-PTN. The O9500R-PTN firmware does not currently support reading or modifying the 1FOMB configuration via SNMP. For this software release, Map95 will assume the 1FOMB card is configured for framed mode.

A configuration file may be specified as a command-line argument to Map95.exe. This will be used as the default configuration file. The purpose of this is to allow users to create shortcuts that load a specific configuration file. The user must specify the full path to the configuration file. If there are any space characters in the full path name, the entire path must be enclosed in double quotes.

----------

1.0 INTRODUCTION

Map95 did not probe the HDE1 or HDT1 card to determine the number of installed ports. It assumed the cards had 32 ports. This only applied to the O9500 and O9500PTN.

Map95 did not probe the B155-622 card to determine the number of active ports. It assumed both ports were active, but depending on the mode, only one port may be active. This only applied to the O9500 and O9500PTN.

This release adds the following:

This release adds preliminary mapping support for the 8DBRA card to the O9500, O9500PTN, and O9550. However, at this time, the 8DBRA card is not fully supported by any of these platforms.

----------

1.0 INTRODUCTION

Correct the "phantom arrow" problem. After clearing a map, Map95 may still indicate a few non-existent cross-connects. However, once the user drills down on the path, the arrows disappear. This was due to a memory initialization problem.

----------

1.0 INTRODUCTION

This release adds support for the O9400R-CC4.
The following Trib cards are supported:

This release adds support for the E3/T3 card on the O9400R-CC16. This includes T3-M13 mode.

This release corrects a bug when manipulating granularity on the O9400R-CC16.When a user configures a cross-connect, Map95 needs to prevent the user from modifying the granularity that effects the cross-connected path. However, Map95 was incorrectly blocking the user from modifying granularity on adjacent paths that are not cross-connected.

Map95 does not correctly detect the 16 and 32 port versions of the E1/T1 card. This problem has been corrected for the O9400R-CC4 and O9400R-CC16, but not for the O9500.

Additional Feature:
Added a button to the "Select Device" dialog to launch a serial console. This is to allow easy access for initial configuration.

----------

1.0 INTRODUCTION

This release adds support for the O9400R, with CC16 controllers. It does not support the CC4 or PTN controllers.
The following Trib cards are supported:

• E1/T1 (mapping and configuration)
• B155/622 (mapping, granularity, configuration)
• TDMoG (mapping, granularity, time-slot related configuration)

Potential issues:
- Firmware upgrade for the controllers and cards have not been tested.

Map95 problem fix:
- This release corrects a problem with the "select device" dialog. If the user manually entered the configuration file name instead of using the file browser, it would not open correct file.

Additional Features:
- A larger font display option was added. Under the "View" Menu there is a click box for "Large Font". When checked, the Map display will use a larger font size making the map easier to see on a modern high-resolution screen. If combined with SNCP View, the Map95 view will be 1325 x 803, so the user will need a wide-screen monitor with a resolution greater than this.

----------

1.0 INTRODUCTION

This release adds support for the O9500PTN, with CCPA controllers. In addition, it adds support for the following cards installed in the O9500PTN:

High-speed

• PTN10G (mapping and granularity configuration)
• E1/T1 (mapping)

Low-speed

• 8-EM (mapping and configuration)
• Dry-contact (mapping)
• 8-OCU/DP (mapping and configuration)
• GSHDSL-2 (mapping)
• 6-UDTEA (mapping and configuration)
• 12-FXS (mapping and configuration)
• 12-FXO (mapping and configuration)
• 3-T1 (mapping and configuration)

Other high-speed and low-speed cards may work, but have not been tested.

Potential issues:

• If the 4GeSW card is installed, Map95 will display an "unsupport card" error. This error can be ignored.
• Firmware upgrade for the controllers and cards have not been tested.
• There seems to be an SNMP bug with the 12-FXS card. With SNMP, it is not possible to read or modify the OOS-Alarm port signal configuration. Map95 will display it as "????". The user can attempt to configure it, but the setting will be ignored.
• Mapping to the in-band channel may be flawed. This problem also existed with the O9500. The CLI exposes 13 in-band ports. However, if you attempt to map ports 2 through 13, the DS0 time-slots appear to overlay port 1. For this reason, in Map95 is only allowed to port 1.

----------

1.0 INTRODUCTION

This release adds support for the 1FOM card installed in an O9500. Both the FOMA and FOMB card function in the O9500 and identify as the same card.

----------

1.0 INTRODUCTION

This release corrects the following:

When a B155/622 card was configured for OC3 mode, Map95 did not display or allow mapping to port 2 on the card.

----------

1.0 INTRODUCTION

This release corrects the following:

Map59 could not handle a space character in the path or filename for the comment file.

----------

1.0 INTRODUCTION

This release corrects the following:

When storing user-defined endpoints to the endpoint comment file, there was an error in the index field used to identify the controller card and also the in-band interface. This would cause the comments for these cards to get lost.

Endpoint comments would be lost if the user added/modified a comment, then performed a "Rescan Device" operation or "Select Device" operation.

This release adds the following modification:

Empty comments will be purged from the comment file. Previously, if a user added a comment, then later removed it, there would be an empty record left in the comment file. Now, the empty record will be removed.

----------

1.0 INTRODUCTION

This release adds the following features:

Support for time-limited enterprise keys. See internal documentation for details.

User-defined endpoint comments. The user may add comment information to endpoints. These comments are stored in a user specified file located on the user's PC.

----------

1.0 INTRODUCTION

This release adds the following feature:

This release modifies Map95v2 support for the o9550. At some point around the O-9550 v1.09.02 firmware release, Loop changed the way in-band channel cross-connects are reported. Map95v2 was modified to work with the new mechanism.

----------

1.0 INTRODUCTION

Loop's firmware release, v3.04.01 (0082) for the O-9500, changed the underlying SNMP mechanism for reading the low-speed card cross-connect map. As a result, Map95 and Map95v2 were not compatible with the O-9500 running v3.04.01 or later. This release modifies Map95v2 to support the new mechanism.

This software release supports the following low-speed cards on the o9500:

Q-T1 (tested - also supports right-click configuration)
8RT-B (tested)
8-EM (tested - also supports right-click configuration)
12FXS (tested - also supports right-click configuration)
12FXO (tested - also supports right-click configuration)
EIA530-A (tested)
RS232-8 (tested - also supports right-click configuration)
TDMoE (tested - also supports right-click configuration)
LS-Optical (tested - also supports right-click configuration)
V.35-A (not tested, but similar to EIA530-A)
V.21-A (not tested, but similar to EIA530-A)
V.36-A (not tested, but similar to EIA530-A)
Magneto (not tested, but similar to FXS)

This release drops support for the following cards on the o9500:
V.35 Q-E1
G.703
GSHDSL-2
GSHDSL-4
RS422-A
Dry-Contact
8DBRA

There was no change to the cards supported on the o9550.

Note: This Map95 version is not backward compatible with previous versions of the o9500 firmware.

----------

1.0 INTRODUCTION

This release corrects the following:

The Export Map function did not work.

The chassis view for the O9550 showed the O9500 chassis.

This release adds the following features:

O9500, added support for the Ethernet Card without L2 switch.

Added a feature allowing the user to force Map95 to read the entire cross-connect table. This feature is found in the "Map" drop-down menu.

Add the option of performing a "System Warm Reset", "System Cold Reset", "XCU Warm Reset", or "XCU Cold Reset" following XCU firmware upgrade.

----------

1.0 INTRODUCTION

This is the initial release of Map95 Version 2, which supports both the 9500 and the 9550. We are temporarily treating Map95v2 as a separate product from Map95 until we have more customer feedback. This is because Map95v2 works differently from Map95 and current 9500 customers may prefer to continue using Map95 Version 1. Both versions can be installed at the same time, and Map95v2 can use Map95 Version 1 configuration files.

----------

1.0 INTRODUCTION

This release adds the following feature:

A copy of PuTTYtel is included in the install package and will co-install with Map95. PuTTYtel is both a terminal emulator and a telnet client. Map95 has been modified to launch PuTTYtel directly from the tools menu, giving the user a quick and easy way to open a console session with the O9500.

----------

1.0 INTRODUCTION

This release corrects the following:

Reading the number of ports on an LS-Optical card, resulted in the 1-Port card showing 4 ports.

----------

1.0 INTRODUCTION

This release corrects the following:

There was a problem in the export feature when exporting only assigned time-slots or exporting only unassigned time-slots. Some timeslots would be missing from the export file.

This release adds the following features:

An integrated TFTP server was added to Map95 that allows the user to easily send and receive configuration files and to send firmware images to the O9500. Access to this feature can be found under the "File - Transfer" menu.

----------

1.0 INTRODUCTION

This release allows E&M cards to be mapped either as voice or data without regard to the "transmit only" setting.

----------

1.0 INTRODUCTION

This is the initial release of the Map95 Software.

----------

Data Comm for Business Inc. 2949 County Road 1000 E Dewey, Il 61840	Voice: 217-897-6600 Toll Free: 800-4-DCB-NET Toll Free: 800-432-2638	Email: Contact Page Web: www.dcbnet.com Fax: 217-897-8023
All DCB web pages copyright ©1995- Data Comm for Business, All rights reserved. EtherPath®, EtherSeries®, EtherPoll®, EtherBridge® and EtherModem® are Registered Trademarks of Data Comm for Business, Inc.