Customer Support Files

MAP-41 Software History

This is the software revision log for the MAP-41 software.

----------

Map41 v2.02 Release Notes 07/03/2024

1.0 INTRODUCTION

This release corrects the following:

SNMPv3 access violations were not being caught during mapping/unmapping operations.

SNMPv3 credential modifications would not take effect until Map34 was restarted.

Error reporting was updated to include additional details.

PuTTY release 0.77 was replaced with PuTTY release 0.81.

----------

Map41 v2.01 Release Notes 3/11/2024

1.0 INTRODUCTION

This release adds the following features.

The Endpoint Identifier feature, provided by Map41, was modified to mimic the Circuit ID naming feature found in the AM3440 CCB.

The CSV format for the map import/export feature was modified to include the Endpoint Identifiers and Endpoint Comments.

The CVS format for the map import/export feature was modified to compress a run of sequential mapping entries down to a single entry in the CSV file.

A navigation search feature was added to the user interface. It allows the user to search and navigate the cross-connect map using the Endpoint Identifier or the Customer Information text.

The version of PuTTY, included with Map41, was upgraded to a Release 0.77. This release is compatible with Wolf SSH, used by V4150 firmware v2.15.01 and later.

Support for IPv6 addresses.

Support for SFTP file transfers with external SFTP server.

Support for TFTP file transfers with an external TFTP server. Note: the internal TFTP server is still included in Map41.

The firmware upgrade feature was modified to provide more user feedback during the process.

The XCU and Card reset feature was modified to provide more control and to provide more user feedback during the process.

Several Old bug workarounds removed. These were bugs dating back to 2015 and corrected long ago. In several cases, the Map41 workarounds were causing errors.

The Map41 menus were reorganized. Mapping related functions were relocated from the “Tools” menu to the “Map” menu.

----------

Map41 v1.16 Release Notes 3/29/2022

1.0 INTRODUCTION

This release corrects the following:

Comment file locking, added in v1.14, prevented the user from creating a new comment file.

The DLL file required to support AES privacy protocol was missing from the installation package.

Note: There was no v1.15 release.

----------

Map41 v1.14 Release Notes 08/11/2021

1.0 INTRODUCTION

This release adds several features requested by customers:

A menu item was added under "Map" that will cause Map41 to read the full cross-connect map. Normally, Map41 reads small chunks of the cross-connect map as needed to show the current view.

The arrow and color of uni-directional cross-connects was changed to make them easy to distinguish from bi-direction cross-connects. The uni-directional cross-connects use a different color pattern and will have a "bar" on the arrow, similar to a diode symbol.

Support for encrypting the configuration (.lcf) file was added. The feature is configured from the "Edit Device" dialog. When selected, the configuration file is encrypted with AES-256 using the password to generate an encryption key. The password must be 8 to 39 characters long and contain at least 3 of the following 4 character types, upper-case, lower-case, digit, special character.

Comment file locking. This feature is intended to prevent unintended overwrite of the comment-file when running multiple instances of Map41 on the same device. The first instance of Map41 will obtain a file-lock that will prevent further instances of Map41 from modifying the cross-connect identifiers and comments. These subsequent instances of Map41 will be able to read the comment file and display the identifiers and comments.

Note: With regard to the comment file configuration, the user must configure the comment file in the device configuration before they will be allowed to add identifiers and comments. In the past, they could leave the comment file field blank. Once they added some comments, Map41 would prompt them to configure a file name.

Map41 now supports Privacy Protocol "AES" for SNMPv3.

----------

Map41 v1.13 Release Notes 11/07/2019

1.0 INTRODUCTION

This release removes PuTTYtel from the install package and replaces it with PuTTY.

Map41 was modified to include an "SSH Console" item under Tools menu, allowing the user to initiate an SSH session with the v4150.

----------

Map41 v1.12 Release Notes 11/05/2019

1.0 INTRODUCTION

This release concerns several issues with regard to the TFTP server integrated into Map41:

Support for TFTP block-size option. This improves the data transfer speed with the v4150.

There was a protocol bug in the TFTP server. Duplicate acknowledgments, received from the client device, would cause the server to unnecessarily resend a data that had already been acknowledged.

After Map41 uploads firmware to the v4150, it monitors the v4150 waiting for the v4150 to report that the operation has completed. This can take several minutes following the completion of the TFTP transfer. However, Map41 was prematurely reporting to the user that an operation had completed.

During TFTP transfer operations, Map41 will now display the "percentage status" as reported by the v4150. This feature did not work correctly in older versions of the v4150, where the unit would only report 0% or 100% and nothing in between.

Firmware cannot be uploaded to a trib-card, that is part of a 1:1 protection pair and operating as the "standby" card. If a user attempts to upload firmware to a standby, Map41 will display an appropriate warning message.

The method for upgrading a pair of trib-cards configured for 1:1 protection is to upgrade the working card first, then copy the firmware from the working card to the standby card. Finally the cards need to be restarted. Map41 can be used to load the firmware to the working card. After that, the CLI must be used to copy the firmware from the working card to the standby card and to perform the reset. If Map41 is used to load firmware to a "working" card, upon completion, it will instruct the user to perform the final steps using the CLI.

The feature to load a configuration file to the v4150 was removed. Using SNMP to load the configuration is not reliable and was corrupting the v4150. Map41 can be used to to get the configuration file from the v4150. However, to load a configuration, the CLI must be used.

----------

Map41 v1.11 Release Notes 10/25/2019

1.0 INTRODUCTION

This release adds the following features:

A new display mode 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.

A configuration file may be specified as a command-line argument to Map41.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.

----------

Map41 v1.10 Release Notes 12/21/2018

1.0 INTRODUCTION

This release corrects the following:

Correct the "phantom arrow" problem. After clearing a map, Map41 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.

----------

Map41 v1.09 Release Notes 4/21/2017

1.0 INTRODUCTION

This release corrects the following:

When an E1/T1 card was configured for 1:N protection, Map41 would throw an error when the user tried to modify the Customer Info field for a DS1 on the E1/T1 card.

----------

Map41 v1.08 Release Notes 4/21/2017

1.0 INTRODUCTION

This release corrects the following:

Map41 could not handle a space character in the path and/or filename for the comment file.

----------

Map41 v1.07 Release Notes 4/17/2017

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.

----------

Map41 v1.06 Release Notes 2/28/2017

1.0 INTRODUCTION

This release adds support for the E1 and T1 cards configured for 1:N protection.

----------

Map41 v1.05 Release Notes 4/24/2015

1.0 INTRODUCTION

This release corrects the following:

Map41 would throw an SNMP error when reading the "Line Overhead Setup" on the OC3 card.

As noted in the v1.04 release, when reading a cross-connect to/from the inband channel, the HDLC port information was not being returned by the v4150. This release implements a workaround, suggested by Jack Miao, for obtaining the missing HDLC port information.

----------

Map41 v1.04 Release Notes 4/15/2015

1.0 INTRODUCTION

This release adds the following features:

Support for the B155 OC3/STM1 card.
Support for C-Bit-T1 and C-Bit-E1 modes added to the T3 card.
Support for in-band HDLC channels.

This release corrects the following:

Map41 did not display and could not cross-connect E1 ports configured for unframed mode. An unframed port will now have a single time-slot, TS-00, which can be mapped to any other TS-00. Framed E1 ports will display with TS-01 through TS-31.

The format of the .csv export file did not have enough fields in each record to represent B155 cross-connects. It was necessary to add two additional fields (columns) to each record in the file. When importing, Map41 will detect the file format and import both the old and new format.

Outstanding issues:

The v4150 does not return the HDLC port number when reading an HDLC cross-connect. Map41 will show HDLC cross-connects, but will show them as going to both HDLC port 1 and HDLC port 2. If a user exports the map to a .csv file, all HDLC related cross-connects will be to port 1. The user will need to manually correct the .csv file for any cross-connects to HDLC port 2.

When clearing a cross-connect entry from the B155 card, the v4150 will always return an error code, even though there was not an actual error and the operation succeeded. This version of Map41 will ignore the error code returned during a clear (unmap) operation.

----------

Map41 v1.03 Release Notes 2/18/2014

1.0 INTRODUCTION

This release adds the following feature:

The Loop v415-V1.07.01 firmware release added some additional cross-connect error codes to the SNMP mib. This release adds support for the new error codes.

----------

Map41 v1.02 Release Notes 1/15/2014

1.0 INTRODUCTION

This release adds the following feature:

A copy of PuTTYtel is included in the install package and will co-install with Map41. PuTTYtel is both a terminal emulator and a telnet client. Map41 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 v4150.

----------

Map41 v1.01 Release Notes 8/5/2013

1.0 INTRODUCTION

This is the initial public release of the Map41 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.