MultiCommManager +++++++++++++++++ This document contains information about the current release of the MultiCommManager. Please take the time to read it over. ---------------------------------------------------------------------- MultiCommManager Version 7.50 Feb 28, 2000 ---------------------------------------------------------------------- Contents: ------------- 1. Introduction 2. New Features 3. Known Problems 4. Problems Fixed 5. Controller changes 6. Additional Files on the Installation disks 7. Current Firmware Versions 8. Technical Support 9. New Controller Commands 10. Previous Releases 1. Introduction -------------------- This is a feature release of the MultiCommManager to add support for the Multi-VOIP, E1 cards, Emailing of faults and IP Query. 2. New Features ----------------------- Support has been added for the Multi-VOIP. Allowing you to remotely configure, update and monitor the Multi-VOIP. Setup and viewing of the Multi-Voip configuration and statistics can be done through the manager setup and view menu. Updating is done through the firmware menu. It should be noted that only 1 management interface can configure the VOIP at one time. All other management interfaces are limited to read only access to the configuration parameters. Whereby, the initial changing of a variable that has only Read access will get a error message stating "Request to change device information failed because device erred on the request." When the IP with Read/Write access quits, the next remote IP that accesses the VOIP will get Read/Write access. Support has been added to email any fault or faults to up to 5 email address's. This would allow a remote site to receive fault information from a controller via email. The SMTP capability gives the controller the ability to alert other users, that aren't managing the rack, of fault status problems through an email message. All faults may be emailed. Setup for Email is done by highlighting an IP and selecting the Email option from the Setup menu of the MCM or through the controller by using the smtpsetup command. Setting up the fault to send email is done by selecting the IP and choosing the Faults and Alarms option under the setup menu or through the controller by using the Setfaults command. Setting the fault to enable/disable email is simply another selection in the fault setup menu. Support has been added for E1 cards. This will allow you to remotely configure and monitor an E1 card. The E1 card can be setup and viewed using the manager setup and view menus. A feature has been added allowing users of the manager to get summary information about a CommPlete rack. The IP Query function can assign a query to an individual IP or a group of IP's. The results of the IP query are displayed next to the IP name in the explorer window. To use the IP Query feature, the user selects an IP (or set of IP's) and chooses the IP Query entry from the Setup menu. A IP Query dialog prompts the user of which query to run (presently there are two available IP Query "modules" in the MR9600). Once selected the results of the IP query are updated every 5 seconds. The term "modules," refers to software components that add capabilities to the controller while it is running. Firmware Version has been added to the dropdown list in the Explorer Window. Community strings may be set for proxy (Legacy) agents. 3. Current Limitations ---------------------------- The latest online help and documentation is available on our Web site. We recommend, when updating devices that traffic is kept to a minimum. We recommend updating devices at off peak hours, on an (ideally) idle system. We recommend the maximum number of modems that are to be updated at one time be limited to 24. We recommend updating one T1/E1/PRI device at a time. Only use the -BOOT option when it is necessary to update the boot code of a device. Earlier versions of the MT5634HD8 CommPlete modem cards have a boot code prom that was smaller than the current one. Please refer to the ftp site below to determine the boot code prom that you have. The statement "early versions of MT5634HD8" refers to cards that were manufactured prior to May of 1998. To determine the prom size for a MT5634HD8 refer to the following URL: ftp://ftp.multitech.com/CommPlete/Modem/Bootcode/current/bootcode.TXT or contact CommPlete Tech Support directly at 888-273-1610 M-F 8:30AM - 5PM CST. 4. Problems fixed (MCM): --------------------------------- The PRI calling party number did not show up in the Statistical reports, or in the MCM Supervisor Call Traffic window when an originate PRI call was made. After a T1 card is flashed, it is reset to make sure the T1 is correctly configured. The MCM manager is now able to accommodate more than two legacy racks daisy chained together. The Statistical Analyzer is now able to process all PRI events 5a. Controller Features (MR9600 and MR4800E): ------------------------------------------ The UPTIME and VER commands have been expanded to return information about devices. The -v(Version) and -u(uptime) options have been added to the GetDevice commands (GETDEVICES, GETMODEMS, GETRAS, GETT1,...). Type the option before the CSN. Ex. [1]A:\#getras -u 9b System up since -- 2/21/2000 10:14am -- 2 Days 0 Hours 57 Minutes 52 Seconds 9B RAS up for 002-00:57:27 [2]A:\#getdevices -v 10a 10A PRI MTPRI-HD23B 2.52.43/232 The help command (?) was expanded to list commands at a desirec starting point. ?# where '#' is the alpha character the desired command/s begins with. Ex. [1]A:\#?O OC ONLINE OS OOSSET OOSCLEAR OOSCLR The SMTPSend command is new. Where is some arbitrary message to be sent. It allows the testing of the SMTP setup. It will send the test string to the first recipient of the SMTPSetup parameters. The SMTPSetup command is new. It configures the controller's email information (email server IP, sender...). Allows the controller to send faults via email, based upon fault setup and email recipients. The GETCALLS command was modified to always display the last known call for each modem since the controller had been up and running. If the last call for a modem or modems occurred prior to the last 200 actual calls, the GETCALLS command will display the last number of calls in addition to the last known call for each modem. The change to the GETCALLS command will now let you know when the last call for all modems occurred. 5b. Controller Problems Fixed (MR9600 and MR4800E): ------------------------------------------ Internet Explorer 5.0 could lock up because the response to user authentication was incorrect from the controller. The MR9600 Controller could reboot when the supervisor opens the explorer window to the rack level. This was caused by PRI version 2.49 or later 7-27-99 PRI Release 2.49 7/9/99. 6. Additional files on the Installation Disks -------------------------------------------------------- The files listed here are files that provide additional information, or services other than the manager software. The files not described are required for installation, or are one of the four manager components. Wintftpc.exe Tftp client utility for the VOIP firmware upgrading. snmp.txt Information on installing Newt, SNMP, and the MultiCommManager MIB description. Inetwh32.dll Required by MCM online help for WEB Hot-link support. Inetwh16.dll setbrows.exe 7. Current Firmware Versions --------------------------------------- Current firmware for modems, and the MR4800E controller can be found on the Multi-Tech FTP site ftp://ftp.multitech.com Controller MR4800 All Revs 4.00 MR4800E All Revs 5.42 CC9600 All Revs 2.50 CC4800 Modems MT1432MR Rev D 8.08D MT1432MR Rev F 2.11B MT2834MR All Revs 1.14 MT2834MR-R All Revs 3.14b MT2834MR6 All Revs 6.04c Commplete Modems MT3334HD8 All Revs 8.03 MT5634HD8 All Revs 1.09E MT5634HD16 All Revs 2.09E MT5634HD16 boot code 2.05 MT5634HD8 boot code 2 meg 1.05 4 meg 2.05 Commplete RAS Card RAS96 All Revs RasExpress 5.50 Commplete T1 Card RAS96T1 All Revs 1.08 RAS96T1 boot code 1.06 Commplete E1 Card RAS96E1 All Revs 2.00D RAS96E1 boot code 1.06 Commplete PRI Card MTPRIHD23B All Revs 2.52.43 **** MTPRIHD23B boot code 2.32 Note! **** PRI ver 2.49.43 or higher requires MR9600 ver 2.42 or higher and RAS Express 5.40 or higher to operate. It is recommended that the MR9600 be updated to version 2.50 first. Then update the PRI to version 2.52.43 next. Then update the RAS to version 5.50 last. 8. Technical Support ------------------------------- Any problems or questions should be directed to Multi-Tech CommPlete Group at (612) 785-3500 or (800) 273-1610. Please send any suggestions or possible enhancements to: Multi-Tech Systems, Inc., 2205 Woodale Drive, Mounds View, Minnesota 55112, c/o "Software R&D -MultiCommManager" Internet Address http://www.multitech.com FTP Site ftp://ftp.multitech.com Fax us at (612) 785-9874. 9. New MR9600 Controller Commands COMMAND PARAMETER SECURITY LEVEL E1SETUP E1 Slot/Device Supervisor Def. E1SETUP is a Supervisor level command used to set up the E1 configuration parameters. Ex. [1] A:\ # E1SETUP 9b Use Settings from: 1. Use Active Settings (pre-configured card) 2. Use System Defaults (new card) 3. Use Stored Settings (swapping cards) Enter selection (q(uit), <1>): E1CFG E1 Slot,Device Operator Def. Sends the E1 configuration information to the E1 device. Ex. [1] A:\ # E1CFG 9b E1CHSTATUS, E1CHANNELSTATUS E1 Slot,Device Guest Def. This command will display the State of each E1 Channel and modem, and flag any channels that seem to be in an inconsistent state. It uses E1 Channel information reported to the controller by the E1. The interval at which the E1 reports the Channel status is controlled by the E1CHPOLL command. Ex. [2] A:\ # E1CHSTATUS 9B Channel CO Modem OOS Channel CO Modem OOS 1 On Hook On Hook 2 Off Hook Off Hook 3 Off Hook Off Hook 4 Off Hook Off Hook 5 On Hook On Hook OOS 6 On Hook On Hook OOS 7 On Hook On Hook OOS 8 On Hook On Hook OOS 9 On Hook On Hook OOS 10 On Hook On Hook OOS 11 On Hook On Hook OOS 12 Off Hook Off Hook 13 Off Hook Off Hook 14 Off Hook Off Hook 15 Off Hook Off Hook 16 Off Hook Off Hook 17 Off Hook Off Hook 18 Off Hook Off Hook 19 Off Hook Off Hook 20 Off Hook Off Hook 21 Off Hook Off Hook 22 Off Hook Off Hook 23 Off Hook Off Hook 24 On Hook On Hook CO - Central Office, * - Inconsistent State E1STATUS E1 Slot,Device Guest Def. This command will display the E1 configuration setup information. Ex. [2]A:\# E1STATUS 9B Channel Polling Interval (Sec): 30 Error Threshold: 5 Disconnect Timeout (sec): 11 Framing Format: CRC4 LineCoding:Alternate Mark Inversion (AMI) Signal Options: R2 Digital Line Buildout: 120 Ohm LED Information: Red Alarm, Yellow Alarm, Sync Loss, Test Mode Model:RAS9600-E1 Version:2.00c/1.06 GETE1 E1 Slot,Device Operator Def. This command will display the status of an E1. Ex. [2] A:\ # GETE1 9B 9B E1 Online E1CHPOLL Slot,Device Supervisor Def. E1CHPOLL is a Supervisor level command used to set up the polling interval and threshold for the E1CHANNELSTATUS command. The polling interval is the interval in seconds the E1 channel status information should be reported to the controller by the E1. The threshold is the number of times an inconsistant state is recognized, before the E1 channel (and modem) are reset. Three pieces of information are compared to determine if a channel is in an inconsistent state: the Central Office State; the E1 to Modem State; and the Controller Modem State. Note: The threshold (default 10) * polling interval (20 seconds) should be > 90 seconds, because the modem will not accept a call for 90 seconds after a reset to allow the E1 Channel to clear. Ex. [01] A:\ # E1CHPOLL 9b E1 9B Channel Poll Setup Polling Interval in Seconds:16 Error Threshold:6 Polling Interval in Seconds (<16>, -(previous), q(uit)): 20 Error Threshold (<6>, -(previous), q(uit)): E1 9B E1 Channel Polling Interval 20 (sec) Error Threshold 6 GETRAS Ras Slot,Device Operator Def. This command will display the status of a RAS. Ex. [2] A:\ # GETRAS 9A 9A RAS Up LISTMOD none Supervisor Def. This lists all currently loaded modules in the following format. Ex. [2] A:\ # LISTMOD Module Last Mod Date/Time Built-In NOCALL Yes VERSION Yes USAGE 1/27/00 10:20am No LOADMOD PathName Supervisor Def. This loads a module that adds capabilities to the controller while it is running. Currently the only capability supported by modules is to add additional IP Queries. The module file should be named [ModuleName].MLM where ModuleName is the name of the module (8 characters or less). The module should reside in the A:\MODULES directory Ex. [2] A:\ # LOADMOD VERSION Module loaded successfully RUNMOD PathName Supervisor Def. This loads (if the module is not loaded) and runs a given module. This has no use for IP Query modules but may be useful in the future to add further capabilities to the system. Ex. [2] A:\ # RUNMOD VERSION Module run successfully UNLOADMOD PathName Supervisor Def. This unloads a module that was previously loaded. It will return an error if the given module is not currently loaded. Ex. [2] A:\ # UNLOADMOD VERSION Module unloaded successfully SETRESETPING Length Supervisor Def. This command can be used to set the packet sizes of three, consecutive pings which will cause the controller to reboot. This mechanism for remotely resetting the controller, can be used as a last resort if the telnet or SNMP interfaces are not responsive. Ex. [2]A:\# SETRESETPING 5,10,15 Ping reset lengths 5, 10, 15 stored GETRESETPING none Supervisor Def. This command will display the packet sizes of three consecutive pings which, when received, will result in a controller reboot. Ex. [2]A:\# GETRESETPING Ping reset lengths = 5, 10, 15 SMTPSETUP none Supervisor Def. The SMTPSetup command configures the controllers email information. It allows the controller to send faults via email, based upon fault setup and email setup. Ex. [2] A:\ # SMTPSETUP 1. Email Enabled :Enabled 2. IP Address :xxx.xxx.xxx.xxx (IP of local mail server) 3. Re-send Threshold :1 4. Sender Email Address :Remote9600@RemoteSite.com 5. Email Recipient 1 :RemoteSentry1@Site1.com 6. Email Recipient 2 :RemoteSentry2@Site2.com 7. Email Recipient 3 : 8. Email Recipient 4 : 9. Email Recipient 5 : Enter Selection (-(previous), q(uit), d(one), <1>): Select a field to change. The threshold value is used to determine if the first email message didn't get sent, try again for the entered amount of times. SMTPSEND none Supervisor Def. This command will send a string to the first recipient in the SMTPSETUP mentioned above. It allows the operator a way of testing the SMTP setup section. Ex. [2] A:\ # SMTPSEND TESTING9600 ---------------------------------------------------------------------- MultiCommManager Version 7.42 Dec 22, 1998 ---------------------------------------------------------------------- Contents: ------------- 1. Introduction 2. New Features 3. Known Problems 4. Problems Fixed 5. Additional Files on the Installation disks 6. Current Firmware Versions 7. Technical Support 8. New Controller Commands 2. Introduction -------------------- This is a feature release of the MultiCommManager to add support for calling and called party numbers. 2. New Features ----------------------- Changes for calling and called party numbers. Before the second ring is displayed, the caller's phone number and the number dialed are displayed. Software such as fax software can use the phone numbers to route faxes, or for fax-back services. This feature requires modem code 1.06D (2.06D) and PRI code 2.49.43. Note: the Controller firmware must be updated before the PRI firmware. PRI code 2.49.43 will cause older versions of the controller to re-boot. Changes to let the user know when an update is completed. The controller will now display a message to indicate when an update is completed. Note! There are new RAS ISI drivers available on the MultiTech FTP site that reduce the number of clients getting disconnected after about 2 minutes. These drivers are part of the RAS 5.40 release. To install the new ISI driver: Busy out the segment (SETOOS 2A:4H); Wait till the segment is idle (GETMODEMS 2A:4H); Copy in the new bin file. Reboot the RAS. 3. Current Limitations ---------------------------- The latest online help and documentation is available on our Web site. It is best when updating devices that traffic is kept to a minimum. If during an update of the boot code area of the device, the update errors, or the device is reset, it is remotely possible the boot code would be destroyed requiring that the boot code prom be replaced. For this reason only use the -BOOT option when it is necessary to update device boot code. For this reason we recommend flashing devices at off peak hours, on an (ideally) idle system. Successfully updating one card at a time is also a good practice. Earlier CommPlete modem cards have a boot code prom that was smaller than the current one. Modems with boot code versions from 1.1 to 1.3 have a 2 meg boot code prom. Version 1.3 is the latest boot code for these modems. Modems with boot code version 1.5 to 2.0 have a 4 meg boot code prom. If version 1.5 to 2.0+ boot code is flashed into one of these early version modems, the boot code prom will be destroyed. The modem card may be examined to determine the boot code prom size (by checking the boot code version indicated on sticker applied at the factory. To get the boot code version (from the supervisor) reset the modem and immediately request the Modem Version. The Version reported from 0 to 90 seconds after a modem is reset is the boot code version. Technical support can also look up the information using the modem serial number. 4. Problems fixed: ------------------------ Fixed GETMODEMS to show config and security info for the MR4800E. Added a warning for T1SIGPOLL and loop start lines. T1Sigpoll does not work for loop start lines. A warning will be issued if t1sigpoll is set for a loop start line. Fixed GETSLOTS to display correct info when segments get powered down. Fixed the problem where Card Installed/Card Removed messages would occasionally appear, and red lights on empty controller segments. The T1STATUS command would cause the controller to reset when displaying information on a segment with modems set OOS. Note! There are new RAS ISI drivers available on the MultiTech FTP site that reduce the number of clients getting disconnected after about 2 minutes. These drivers are part of the RAS 5.40 release. To install the new ISI driver: Busy out the segment (SETOOS 2A:4H); Wait till the segment is idle (GETMODEMS 2A:4H); Copy in the new bin file. Reboot the RAS. 5. Additional files on the Installation Disks -------------------------------------------------------- The files listed here are files that provide additional information, or services other than the manager software. The files not described are required for installation, or are one of the four manager components. snmp.txt Information on installing Newt, SNMP, and the MultiCommManager MIB description. Inetwh32.dll Required by MCM online help for WEB Hot-link support. Inetwh16.dll setbrows.exe 6. Current Firmware Versions --------------------------------------- Current firmware for modems, and the MR4800E controller can be found on the Multi-Tech FTP site ftp://ftp.multitech.com Controller MR4800 All Revs 4.00 MR4800E All Revs 5.42 CC9600 All Revs 2.42 CC4800 Modems MT1432MR Rev D 8.08D MT1432MR Rev F 2.11B MT2834MR All Revs 1.14 MT2834MR-R All Revs 3.14 MT2834MR6 All Revs 6.04c Complete Modems MT3334HD8 All Revs 8.03 MT5634HD8 All Revs 1.06d MT5634HD16 All Revs 2.06d MT5634 boot code 2.02 Complete RAS Card RAS96 All Revs RasExpress 5.40 ***** Complete T1 Card RAS96T1 All Revs 1.07C RAS96T1 boot code 1.06 Complete PRI Card MTPRIHD23B All Revs 2.49.43 **** MTPRIHD23B boot code 2.32 Note! **** PRI ver 2.49.43 requires CC9600 ver 2.42 or greater to operate. This version of the PRI will cause earlier versions of the CC9600 controller to reboot. ***** RAS ver 5.40 requires PRI ver 2.49.43 or greater to operate. RAS 5.40 RASEXP.EXE should fail on startup if it sees an old version (< 2.49.43) PRI. It is recommended that the CC9600 be updated to version 2.42 first. Then update the PRI to version 2.49.43 next. Then update the RAS to version 5.40 last. 7. Technical Support ------------------------------- Any problems or questions should be directed to Multi-Tech Technical Support at (612) 785-3500 or (800) 328-9717. Please send any suggestions or possible enhancements to: Multi-Tech Systems, Inc., 2205 Woodale Drive, Mounds View, Minnesota 55112, c/o "R&D -MultiModemManager" Internet Address http://www.multitech.com FTP Site ftp://ftp.multitech.com Fax us at (612) 785-9874. 8. New Controller Commands NONE ---------------------------------------------------------------------- MultiCommManager Version 7.41 Nov 3, 1998 ---------------------------------------------------------------------- Contents: ------------- 1. Introduction 2. New Features 3. Known Problems 4. Problems Fixed 5. Additional Files on the Installation disks 6. Current Firmware Versions 7. Technical Support 8. New Controller Commands 9. Previous Releases 1. Introduction -------------------- This is a maintenance release of the MultiCommManager. 2. New Features ----------------------- >>> GETPIPES Controller command <<< This command displays the state of all the devices on a given communications pipe. Every call passes through several different devices to complete the connection. For example on a T1 segment a call goes through a T1 Channel, a Modem, and a Ras Line. Each device has its own view of the connection and the GETPIPES command allows you to show all their states simultaneously. (See the detailed description in section 8 below) >>> RASSTATUS <<< The RASSTATUS command has been added to allow you to get the current state of the RAS card. >>> RASSETUP <<< The RASSETUP command has been added to allow you to set up a RAS card without using the Set Environment (SE) command. >>> PING <<< A Ping utility has been added. PING IP-Address will ping an IP address and return the response time if the device responds. 3. Current Limitations ------------------------------ The latest online help and documentation is available on our Web site. It is best when updating devices that traffic is kept to a minimum. If during an update of the boot code area of the device, the update errors, or the device is reset, it is remotely possible the boot code would be destroyed requiring that the boot code prom be replaced. For this reason only use the -BOOT option when it is necessary to update device boot code. For this reason we recommend flashing devices at off peak hours, on an (ideally) idle system. Successfully updating one card at a time is also a good practice. Earlier CommPlete modem cards have a boot code prom that was smaller than the current one. Modems with boot code versions from 1.1 to 1.3 have a 2 meg boot code prom. Version 1.3 is the latest boot code for these modems. Modems with boot code version 1.5 to 2.0 have a 4 meg boot code prom. If version 1.5 to 2.0+ boot code is flashed into one of these early version modems, the boot code prom will be destroyed. The modem card may be examined to determine the boot code prom size (by checking the boot code version indicated on sticker applied at the factory. To get the boot code version (from the supervisor) reset the modem and immediately request the Modem Version. The Version reported from 0 to 90 seconds after a modem is reset is the boot code version. Technical support can also look up the information using the modem serial number. 4. Problems fixed: ------------------------ The modem status window was not displaying the disconnect reason correctly. The SE command has been improved. Less fields are required to be entered streamlining the configuration of devices. The UPDATE file check does not catch a hex file that has been truncated. The flash of the device later fails because of the truncated file. GETCALLS was showing the Disconnect time in the display. It will now display connect time. The PRI User ID was not always showing up with GETCALLS. When the User ID was returned to the controller it was attached to the wrong modem. 5. Additional files on the Installation Disks -------------------------------------------------------- The files listed here are files that provide additional information, or services other than the manager software. The files not described are required for installation, or are one of the four manager components. snmp.txt Information on installing Newt, SNMP, and the MultiCommManager MIB description. Inetwh32.dll Required by MCM online help for WEB Hot-link support. Inetwh16.dll setbrows.exe 6. Current Firmware Versions --------------------------------------- Current firmware for modems, and the MR4800E controller can be found on the Multi-Tech FTP site ftp://ftp.multitech.com Controller MR4800 All Revs 4.00 MR4800E All Revs 5.40 CC9600 All Revs 2.40 CC4800 Modems MT1432MR Rev D 8.08D MT1432MR Rev F 2.11B MT2834MR All Revs 1.14 MT2834MR-R All Revs 3.14 MT2834MR6 All Revs 6.04c Complete Modems MT3334HD8 All Revs 8.03 MT5634HD8 All Revs 1.05d MT5634HD16 All Revs 2.05d MT5634 boot code 2.02 Complete RAS Card RAS96 All Revs RasExpress 5.31 Complete T1 Card RAS96T1 All Revs 1.07C RAS96T1 boot code 1.06 Complete PRI Card MTPRIHD23B All Revs 2.48B.43 MTPRIHD23B boot code 2.31 Online Help version 1.20 includes MultiCommManager 7.20 7. Technical Support ------------------------------- Any problems or questions should be directed to Multi-Tech Technical Support at (612) 785-3500 or (800) 328-9717. Please send any suggestions or possible enhancements to: Multi-Tech Systems, Inc., 2205 Woodale Drive, Mounds View, Minnesota 55112, c/o "R&D -MultiModemManager" Internet Address http://www.multitech.com FTP Site ftp://ftp.multitech.com Fax us at (612) 785-9874. 8. New Controller Commands ------------------------------- 9. Previous releases ------------------------------- ---------------------------------------------------------------------- MultiCommManager Version 7.40 Oct. 1, 1998 ---------------------------------------------------------------------- Contents: ------------- 11. Introduction 12. New Features 13. Known Problems 14. Problems Fixed 15. Additional Files on the Installation disks 16. Current Firmware Versions 17. Technical Support 18. New Controller Commands 19. Previous Releases 3. Introduction -------------------- This is a feature release of the MultiCommManager to add support for modem dial out on a PRI line and V.90 modem support. 2. New Features ----------------------- >>> Support for PRI Dial <<< PRI code (2.47.43) now supports modem dial out on a PRI line. >>> SETFAULTS Controller command <<< The SETFAULTS command adds controller control of Faults and Alarms. A menu driven series of commands allows control of enabling a fault, fault alarm actions, and error thresholds. Prior to this release, the only Fault and Alarm control was through the MCM supervisor (See the detailed description in section 9 below) >>> -D Option <<< The GETFAULTS and GETCALLS commands have added support for the -D (Delete option). The Delete (-D) option deletes all items in the select list. For example GETFAULTS -D will delete all faults from the controller. GETCALLS -D 2A will delete all completed calls for modem 2A. >>> Three new Statistical Analyzer reports <<< Modem-Ras Connect History, and Modem-Ras Connections by modem. These reports combine the modem connect history and Ras port connection information together in one report. A new PRI report (PRI Connect History) displays PRI connect information from the processed event files. 3. Current Limitations ------------------------------ The latest online help and documentation is available on our Web site. It is best when updating devices that traffic is kept to a minimum. If during an update of the boot code area of the device, the update errors, or the device is reset, it is remotely possible the boot code would be destroyed requiring that the boot code prom be replaced. For this reason only use the -BOOT option when it is necessary to update device boot code. For this reason we recommend flashing devices at off peak hours, on an (ideally) idle system. Successfully updating one card at a time is also a good practice. Earlier CommPlete modem cards have a boot code prom that was smaller than the current one. Modems with boot code versions from 1.1 to 1.3 have a 2 meg boot code prom. Version 1.3 is the latest boot code for these modems. Modems with boot code version 1.5 to 2.0 have a 4 meg boot code prom. If version 1.5 to 2.0+ boot code is flashed into one of these early version modems, the boot code prom will be destroyed. The modem card may be examined to determine the boot code prom size (by checking the boot code version indicated on sticker applied at the factory. To get the boot code version (from the supervisor) reset the modem and immediately request the Modem Version. The Version reported from 0 to 90 seconds after a modem is reset is the boot code version. Technical support can also look up the information using the modem serial number. 4. Problems fixed: ------------------------ Some users get an all circuts busy message when attempting to dial in to a PRI segment. This occurred because when a previous user disconnected, the modem did not hang up. With version 2.48.43 of the PRI, the PRI will make sure the modem is hung up when the PRI line goes idle. This will eliminate the erroneous all circuts busy message later callers were getting. Modem firmware 1.04C or 2.04C is also required for this fix. If a telnet session is allowed to timeout, the controller will re-boot. The GETCALLS command does not show User Login Name. When the software or controller firmware is updated, the Logical Group assignments, and Host Select group information is not saved. After update, when the controller or Supervisor is started, if the version of the mr4800.gp file is not compatible with the current version, it is copied to mr4800V0.gp or mr4800V1.gp and a new (empty) mr4800.gp file is created. Thus the Logical group assignments need to be re-entered. Now the Group file (MR4800.GP) is converted to the latest level automatically. If you want a previous group file (mr4800V0.GP or mr4800V1.GP to be converted to the latest level, copy it over mr4800.gp, and reboot the controller, or re-start the manager. When FTPing files to a controller, the controller reports file sizes incorrectly (through FTP). The MR4800E Security database search speed has been improved. This will reduce the number of calls that time out at the User ID prompt when the controller is searching a large database file. 5. Additional files on the Installation Disks -------------------------------------------------------- The files listed here are files that provide additional information, or services other than the manager software. The files not described are required for installation, or are one of the four manager components. snmp.txt Information on installing Newt, SNMP, and the MultiCommManager MIB description. Inetwh32.dll Required by MCM online help for WEB Hot-link support. Inetwh16.dll setbrows.exe 6. Current Firmware Versions --------------------------------------- Current firmware for modems, and the MR4800E controller can be found on the Multi-Tech FTP site ftp://ftp.multitech.com Controller MR4800 All Revs 4.00 MR4800E All Revs 5.40 CC9600 All Revs 2.40 CC4800 Modems MT1432MR Rev D 8.08D MT1432MR Rev F 2.11B MT2834MR All Revs 1.14 MT2834MR-R All Revs 3.14 MT2834MR6 All Revs 6.04c Complete Modems MT3334HD8 All Revs 8.03 MT5634HD8 All Revs 1.04c MT5634HD16 All Revs 2.04c MT5634 boot code 2.0 Complete RAS Card RAS96 All Revs RasExpress 5.31 Complete T1 Card RAS96T1 All Revs 1.07C RAS96T1 boot code 1.06 Complete PRI Card MTPRIHD23B All Revs 2.48.43 MTPRIHD23B boot code 2.30 Online Help version 1.20 includes MultiCommManager 7.20 7. Technical Support ------------------------------- Any problems or questions should be directed to Multi-Tech Technical Support at (612) 785-3500 or (800) 328-9717. Please send any suggestions or possible enhancements to: Multi-Tech Systems, Inc., 2205 Woodale Drive, Mounds View, Minnesota 55112, c/o "R&D -MultiModemManager" Internet Address http://www.multitech.com FTP Site ftp://ftp.multitech.com Fax us at (612) 785-9874. 8. New Controller Commands COMMAND PARAMETER SECURITY LEVEL SETFAULTS None Supervisor Def. SETFAULTS is a Supervisor level command used to control Faults and Alarms on a controller. A menu driven interface allows control of enabling a fault, fault alarm actions, and error thresholds. Ex. [01] A:\ # SETFAULTS Display/Edit a Fault 1. Disconnect: Inactivity Timer Expired 2. Power Supply Failure 3. Card Installed 4. Card Removed 5. No Free Disk Space 6. Loss Of DTR Off Line 7. Undertime Call 8. No Connection 9. Inactive Line 10. Modem Reset Enter Selection (-(previous), d(one), n(ext), <1>): 7 Undertime Call 1. Fault Enabled :Yes 2. Alarm Enabled :Yes 3. Threshold :3 4. Alarm Action :Reset 5. Duration in Seconds :60 Enter Selection (-(previous), d(one), n(ext), f(actory defaults), <1>): 3 Threshold (-(previous), d(one), <2>): 4 Undertime Call 1. Fault Enabled :Yes 2. Alarm Enabled :Yes 3. Threshold :4 4. Alarm Action :Reset 5. Duration in Seconds :60 Enter Selection (-(previous), d(one), n(ext), f(actory defaults), <3>): 5 Duration in Seconds (-(previous), d(one), <60>): 50 Undertime Call 1. Fault Enabled :Yes 2. Alarm Enabled :Yes 3. Threshold :4 4. Alarm Action :Reset 5. Duration in Seconds :50 Enter Selection (-(previous), d(one), n(ext), f(actory defaults), <5>): d [5] A:\ # ---------------------------------------------------------------------- MultiCommManager Version 7.30 July 1, 1998 ---------------------------------------------------------------------- Contents: ------------- 1. Introduction 2. New Features 3. Known Problems 4. Problems Fixed 5. Additional Files on the Installation disks 6. Current Firmware Versions 7. Current MIB Versions 8. Technical Support 9. New Controller Commands 10. Previous Releases 4. Introduction -------------------- This is a maintainance release of the MultiCommManager. 2. New Features ----------------------- >>> Support for RAS Express 5.30 <<< New fields have been added to several dialogs. >>> Support for V.90 speeds and connect types <<< Support added to display V.90 connect speeds, and asymetric connect speeds. Asymetric connect speed information requires Commplete modem firmware greater than 1.01a for MT5634HD8 modems and 2.01a for MT5634HD16 modems. >>> Software Support for RAS96T1 version 1.07 <<< Several new setup fields were added: Wink High Time (in milliseconds), After Wink Time (in milliseconds), and Pre-Wink Time (in milliseconds) to provide more options for Wink-Start lines. Disconnect Timeout in seconds was also added. After a T1 Channel disconnects, the line is held off hook for Disconnect Timeout seconds to allow the line to clear. The default Disconnect Timeout is 11 seconds. >>> Software Support for MTPRIHD23 version 2.46.43 <<< New Field Options were added: Switch types (European and Japan), Line Coding (High Density Bipolar 3 Zero (HDB3)), Error Correction method (CRC4/CRC6). A new setup field, the ability to set the number of Active Channels was added. With version 2.46.43, the current boot code is embedded in the .HXP file. Use UPDATE with the -BOOT option to update PRI boot code. >>> New controller commands <<< New controller commands include T1CHPOLL and T1CHANNELSTATUS. (See the detailed description in section 9 below) >>> New faults <<< When a device resets, a reason is logged in the fault generated by the reset. When the device finishes it's reset cycle "(Finished Power on Reset)" is displayed. If a device is not responding it may be reset by the controller "(Not Responding - Busy Count, No Ack Count, or Poll No Response)" is displayed. When the controller sees a modem and T1 channel in a questionable state for a specified amount of time, the modem is reset and the message (Inconsistent State) is displayed. The T1CHANNELSTATUS command will show any T1 channels that are in an inconsistent state. T1CHPOLL is used to control the reporting interval and threshold. >>> UPDATE Improvements <<< PRI flash support has been added. You may now flash boot code in up to 24 modems simultaneously. A confirmation message has been added that is displayed after the file checked for validity. The message indicates Update options selected, number of devices, and the update file. If you attempt to update connected modems the following message appears: Some of the selected modems are currently connected. Update will NOT begin until ALL selected modems are idle. Do wish you to 1 - update only the idle modems now (abort connected modems). 2 - update all selected modems now (disconnect connected modems). 3 - wait for connected modems to disconnect 4 - Abort the update You may abort the connected modems, disconnect all the currently modems (reset them), wait till all modems are free, or abort the update and select a different set of devices. 3. Current Limitations ------------------------------ The latest online help and documentation is available on our Web site. It is best when updating devices that traffic is kept to a minimum. If during the update of the boot code area of the device update errors, or the device is reset, it is remotely possible the boot code would be destroyed requiring that the boot code prom be replaced. For this reason only use the -BOOT option when it is necessary to update device boot code. For this reason we recommend flashing devices at off peak hours, on an (ideally) idle system. Successfully updating one card at a time is also a good practice. Earlier CommPlete modem cards had a boot code prom that was smaller than the current one. Modems with boot code versions from 1.1 to 1.3 have a 2 meg boot code prom. Version 1.3 is the latest boot code for these modems. Modems with boot code version 1.5 to 2.0 have a 4 meg boot code prom. If version 1.5 to 2.0+ boot code is flashed into one of these early version modems, the boot code prom will be destroyed. The modem card may be examined to determine the boot code prom size (by checking the boot code version indicated on sticker applied at the factory. To get the boot code version (from the supervisor) reset the modem and immediately request the Modem Version. The Version reported from 0 to 90 seconds after a modem is reset is the boot code version. Technical support can also look up the information using the modem serial number. When using the update command to update a CommPlete T1 card, the -BOOT option must be used to update the T1 boot code. The latest T1 boot code is merged into the T1 firmware (xxx.HXT) file. If the -BOOT option is omitted, only the T1 firmware will be updated. Limited PRI support has been added to the Statistical Analyzer. More will be added in a future release. If a telnet session is allowed to timeout, the controller will re-boot. The command TELNETTIMEOUTOFF can be used to prevent this. TELNETTIMEOUTON can turn the telnet session timeout back on. 4. Problems fixed: ------------------------ If a GET-NEXT was performed on a mib variable outside our implementation of the standard mib, the software could lock up, or a GPF could occur. Attempts to download multiple files (or a large file) from a MR9600 controller using FTP could not only cause FTP to lock up but TCP/IP as well. Thus any attempts to telnet, ping, etc. would no longer work until the controller was rebooted. If a T1 card is reset, it "forgets" the Channels that were set OOS. The Controller will force these channels OOS after the T1 finishes it's reset. Three files have been added to the Installation disk that are required by the online help for internet support. 5. Additional files on the Installation Disks -------------------------------------------------------- The files listed here are files that provide additional information, or services other than the manager software. The files not described are required for installation, or are one of the four manager components. etherup.txt Provides information on flash updating of the MR4800E ethernet controller. update.txt Information on upgrading modems with old boot code and firmware after which the manager software can update firmware. snmp.txt Information on installing Newt, SNMP, and the MultiCommManager MIB description. isp.txt Information on setting up a dial in service flash.exe A self-extracting zip file that creates files necessary for flash updating modems with old boot code, and the MR4800E Ethernet controller. It is described in update.txt and by the flashpro.txt file in the self-extracting zip. mr4800.hxc MR4800 Controller firmware Version 4.0 required to flash update MT2834MR6 Modems. Configuration File Templates In the installation directory, several configuration file templates can be found. These files can be used as a basis for setting up modem configuration depending on the application and modem type. These files are simple ASCII text files that may be read by an editor, or by the Configuration Manager. If you are using the MultiCommManager with the Multi-Tech Remote Node Gateway or the Multi-Tech Fax Server, we recommend letting the product configure the modems instead of the MultiCommManager. default.cfg If no config file is attached to the modem via MultiCommManager Modem Inventory, this file is sent. 1432MR.cfg This is the default config file for 1432MR modems ISP.cfg These are example settings to be used for a dial in service for example an Internet Service Provider. 6. Current Firmware Versions --------------------------------------- Current firmware for modems, and the MR4800E controller can be found on the Multi-Tech FTP site ftp://ftp.multitech.com Controller MR4800 All Revs 4.00 MR4800E All Revs 5.30 CC9600 All Revs 2.30 CC4800 Modems MT1432MR Rev D 8.08D MT1432MR Rev F 2.11B MT2834MR All Revs 1.14 MT2834MR-R All Revs 3.14 MT2834MR6 All Revs 6.04b Complete Modems MT3334HD8 All Revs 8.03 MT5634HD8 All Revs 1.01a MT5634HD16 All Revs 2.01a MT5634 boot code 2.0 Complete RAS Card RAS96 All Revs RasExpress 5.30 Complete T1 Card RAS96T1 All Revs 1.07C RAS96T1 boot code 1.06 Complete PRI Card MTPRIHD23B All Revs 2.46.43 MTPRIHD23B boot code ?? Online Help version 1.20 includes MultiCommManager 7.20 7. Current MIB Versions --------------------------------- MR4800E.MIB for MR4800E 1.02C and earlier MULTI1.MIB for all other components 8. Technical Support ------------------------------- Any problems or questions should be directed to Multi-Tech Technical Support at (612) 785-3500 or (800) 328-9717. Please send any suggestions or possible enhancements to: Multi-Tech Systems, Inc., 2205 Woodale Drive, Mounds View, Minnesota 55112, c/o "R&D -MultiModemManager" Internet Address http://www.multitech.com FTP Site ftp://ftp.multitech.com Fax us at (612) 785-9874. 9a. New Controller Commands ----------------------------------------- COMMAND PARAMETER SECURITY LEVEL T1CHPOLL Device Supervisor Def. T1CHPOLL is a Supervisor level command used to set up the polling interval and threshold for the T1CHANNELSTATUS command. It is available for T1 firmware versions greater than 1.06A. The polling interval is the interval in seconds the T1 channel status information should be reported to the controller by the T1. The threshold is the number of times an inconsistant state is recognized, before the T1 channel (and modem) are reset. Three pieces of information are compared to determine if a channel is in an inconsistent state: the Central Office State; the T1 to Modem State; and the Controller Modem State. Note: The threshold (default 6) * polling interval (16 seconds) should be > 90 seconds, because the modem will not accept a call for 90 seconds after a reset to allow the T1 Channel to clear. Ex. [01] A:\ # T1CHPOLL 9b T1 9B Channel Poll Setup Polling Interval in Seconds:16 Error Threshold:6 Polling Interval in Seconds (<16>, -(previous), q(uit)): 20 Error Threshold (<6>, -(previous), q(uit)): T1 9B T1 Channel Polling Interval 20 (sec) Error Threshold 6 T1SIGPOLL None Supervisor Def. T1SIGPOLL is a Supervisor level command used to set up the polling interval and threshold used to look for inconsistant T1 channels. It is available for T1 firmware versions greater than 1.05. It is similar in function to the T1CHPOLL command in that it finds inconsistant T1 channels, and (after a threshold is reached) resets them. T1SIGPOLL uses Signal Bits data (different but similar to the T1CHPOLL information) reported to the controlller by the T1 every "polling interval" seconds. The polling interval is the interval in seconds the T1 signal polling information should be sent. The threshold is the number of times an inconsistant state is recognized, before the T1 channel (and modem) are reset. If a T1channel is inconsistant for "threshold" consecutive polls, the T1 channel (and modem) are reset . Three pieces of information are compared to determine if a channel is in an inconsistant state: the Receive signaling bits (Central Office State); the Transmit signaling bits(T1 to Modem State); and the Controller Modem State. NOTE: Using T1SIGPOLL turns off T1CHPOLL information. The threshold (default 6) * polling interval (16 seconds) should be > 90 seconds, because the modem will not accept a call for 90 seconds after a reset to allow the T1 Channel to clear. Ex. [01] A:\ # T1SIGPOLL 9b T1 9B Signal Bits Poll Setup Polling Interval in Seconds:0 Error Threshold:6 Polling Interval in Seconds (<0>, -(previous), q(uit)): 20 Error Threshold (<6>, -(previous), q(uit)): 10 T1 9B T1 Signal Bits Polling Interval 20 (sec) Error Threshold 10 T1CHSTATUS, T1CHANNELSTATUS None Guest (9600 only) Def. This command will display the State of each T1 Channel and modem, and flag any channels that seem to be in an inconsistent state. It uses T1 Channel information reported to the controller by the T1. The interval at which the T1 reports the Channel status is controlled by the T1CHPOLL command. Ex. [02] A:\ # T1CHSTATUS 9B Channel CO Modem OOS Channel CO Modem OOS 1 On Hook On Hook 2 Off Hook Off Hook 3 Off Hook Off Hook 4 Off Hook Off Hook 5 On Hook On Hook OOS 6 On Hook On Hook OOS 7 On Hook On Hook OOS 8 On Hook On Hook OOS 9 On Hook On Hook OOS 10 On Hook On Hook OOS 11 On Hook On Hook OOS 12 Off Hook Off Hook 13 Off Hook Off Hook 14 Off Hook Off Hook 15 Off Hook Off Hook 16 Off Hook Off Hook 17 Off Hook Off Hook 18 Off Hook Off Hook 19 Off Hook Off Hook 20 Off Hook Off Hook 21 Off Hook Off Hook 22 Off Hook Off Hook 23 Off Hook Off Hook 24 On Hook On Hook CO - Central Office, * - Inconsistent State 9b. Commands introduced in 7.20 ----------------------------------------- COMMAND PARAMETER SECURITY LEVEL GETSLOTS None Operator Def. Displays hardware type and location within the rack. It also displays number of devices in each slot. Ex. [01] A:\ # Getslots 1 MTRAS96 - T1A 2 2 MT5634HD8 8 3 MT5634HD8 8 4 MT5634HD8 8 GETPS, GETPOWERSTATUS None Guest (9600 only) Def. Displays the main power supply/ies status and which segments are powered up. Ex. [02] A:\ # Getpowerstatus Left Power Supply: Installed, All outputs good Right Power Supply: Not installed First Segment: Powered Second Segment: Not Powered Third Segment: Not Powered Fourth Segment: Not Powered [03] A:\ # GETTEMP None Guest (9600 only) Def. Displays the internal ambient temperature of the rack in Fahrenheit and Celsius. Ex. [03]A: \ # Gettemp 76.4 degrees fahrenheit 24.7 degrees Celsius SETRASOSTYPE Device Operator (9600 only) Def. Lets the controller know what operating system is loaded on each segment. Ex. [01] A:\ # Setrasostype 1a Operating System:Ras Express 5.2 (or later) Operating System 1. Ras Express pre(5.2) 2. SCO Unix 3. Windows NT 4. Novell Netware 5. Ras Express 5.2 (or later) 6. Other Enter Selection (1,2,3,4,<5>,6, -(previous), q(uit)): SYNC None Operator Def. Writes outstanding events (events that normally get written every hour) to the B:\ # MMM\MR.Log directory. The file will be named the current date and hour with an extension of hr. Ex. [01] A:\ # Sync [02] A:\ # GETRACK None Operator Def. Displays the model number and basic description of the chassis. Ex. [5] A:\ # getrack Chassis Type: CC9600 four segment chassis [6] A:\ # SETPOLLINGOFF Device Supervisor Def. Disables controller generated polling to specified device. The example below starts with displaying the status of the back plane by using the bpstatus command. Ex. [1] A:\# bpstatus Backplane Status: Busy:NoResp:NoAck -: no polling 0: count of 0 1-9: tens digit plus 1 *: >= ninety Slot A B C D E F G H I J K L M N O P 5: 000 000 6: 000 000 000 000 000 000 000 000 7: 000 000 000 000 000 000 000 000 8: 000 000 000 000 000 000 000 000 9: 000 000 10: 000 000 000 000 000 000 000 000 11: 000 000 000 000 000 000 000 000 12: 000 000 000 000 000 000 000 000 [2] A:\ # setpollingoff 5a [3] A:\ # bpstatus Backplane Status: Busy:NoResp:NoAck -: no polling 0: count of 0 1-9: tens digit plus 1 *: >= ninety Slot A B C D E F G H I J K L M N O P 5: --- 000 6: 000 000 000 000 000 000 000 000 7: 000 000 000 000 000 000 000 000 8: 000 000 000 000 000 000 000 000 9: 000 000 10: 000 000 000 000 000 000 000 000 11: 000 000 000 000 000 000 000 000 12: 000 000 000 000 000 000 000 000 [4] A:\ # SETPOLLINGON Device Supervisor Def. Re-enables polling between controller and specified device. The example below starts with displaying the status of the back plane by using the bpstatus command. Ex. [4] A:\ # bpstatus Backplane Status: Busy:NoResp:NoAck -: no polling 0: count of 0 1-9: tens digit plus 1 *: >= ninety Slot A B C D E F G H I J K L M N O P 5: --- 000 6: 000 000 000 000 000 000 000 000 7: 000 000 000 000 000 000 000 000 8: 000 000 000 000 000 000 000 000 9: 000 000 10: 000 000 000 000 000 000 000 000 11: 000 000 000 000 000 000 000 000 12: 000 000 000 000 000 000 000 000 [5] A:\ # setpollingon 5a [6] A:\ # bpstatus Backplane Status: Busy:NoResp:NoAck -: no polling 0: count of 0 1-9: tens digit plus 1 *: >= ninety Slot A B C D E F G H I J K L M N O P 5: 000 000 6: 000 000 000 000 000 000 000 000 7: 000 000 000 000 000 000 000 000 8: 000 000 000 000 000 000 000 000 9: 000 000 10: 000 000 000 000 000 000 000 000 11: 000 000 000 000 000 000 000 000 12: 000 000 000 000 000 000 000 000 [7] A:\ # T1DEBUG Device Supervisor (9600 only) Def. Displays status of AB Signalling bits for both the transmit and receive directions of each DS0 channel for the specified T1 device within the Commplete. TX = from Commplete T1 card to Central Office. RX = from Central Office to Commplete T1 card. Ex. [31] A:\ # t1debug 1b 1. Enable Signal Bit monitoring 2. Turn Off signal bit monitoring 3. Signal Poll interval (4) => 1 Completed enabling all selected devices! [32] A:\ # 01B 01B Tx/Rx Tx/Rx AB/AB AB/AB 01 00/00 02 00/00 03 00/00 04 00/00 05 00/00 06 00/00 07 00/00 08 00/00 09 00/00 10 00/00 11 00/00 12 00/00 13 00/00 14 00/00 15 00/00 16 00/00 17 00/00 18 00/00 19 00/00 20 00/00 21 00/00 22 00/00 23 00/00 24 00/00 E&M Immediate Start Protocol Tx(AB) Rx(AB) OFF HOOK 11 11 ON HOOK 00 00 RINGING NA NA [33] A:\ # t1debug 1b 1. Enable Signal Bit monitoring 2. Turn Off signal bit monitoring 3. Signal Poll interval (4) => 2 BPSTATUS None Supervisor Def. Displays the rack's back plane polling activity between the controller and each powered device. Each correctly operating device responds to three specific polls; "Busy", "No Response" and "No Acknowledgement". If the device does not reposnd the counter/s will increment. The example below shows all devices in a fully loaded CC9600 are responding correctly. Ex. [1] A:\ # bpstatus Backplane Status: Busy:NoResp:NoAck -: no polling 0: count of 0 1-9: tens digit plus 1 *: >= ninety Slot A B C D E F G H I J K L M N O P 1: 000 000 2: 000 000 000 000 000 000 000 000 3: 000 000 000 000 000 000 000 000 4: 000 000 000 000 000 000 000 000 5: 000 000 6: 000 000 000 000 000 000 000 000 7: 000 000 000 000 000 000 000 000 8: 000 000 000 000 000 000 000 000 9: 000 000 10: 000 000 000 000 000 000 000 000 11: 000 000 000 000 000 000 000 000 12: 000 000 000 000 000 000 000 000 13: 000 000 14: 000 000 000 000 000 000 000 000 15: 000 000 000 000 000 000 000 000 16: 000 000 000 000 000 000 000 000 [2] A:\ # PRISTATUS Specifier Operator Def. Retrieve the current status of the specified PRI card. Ex. [1] A:\ # pristatus 2a Getting PRI Info ..... Switch Type:AT&T 4ESS Line Coding: Binary 8 Zero Substitution (B8ZS) Framing Format: Extended Super Frame Error Correction Method: CRC-6 Enabled Call Distribution:One to One Set Carrier:PCM24/T1 Model:MTPRI-HD23B Version:2.43.01 Layer 1 Status:Up Layer 2 Status:Multi-Frame Established PRIOSBCHANNEL Device.Channel # Operator Def. Set the specified B Channel Out of Service. Check the results with getprichannels. Ex. [1] A:\ # priosbchannel 2a.1 PRIOCBCHANNEL Device.Channel # Operator Def. Set the specified B Channel In Service. Check the results with getprichannels. Ex. [1] A:\ # priocbchannel 2a.1 GETPRICHANNELS Device Operator Def. Set configuration paramaters for a PRI card. Ex. [1] A:\ # getprichannels 2a Getting PRI Info .... B Channels Chan 01: OOS Chan 02: ReadyChan 03: Ready Chan 04: ReadyChan 05: Ready Chan 06: ReadyChan 07: Ready Chan 08: Ready Chan 09: Ready Chan 10: Ready Chan 11: Ready Chan 12: Ready Chan 13: Ready Chan 14: Ready Chan 15: Ready Chan 16: Ready Chan 17: Ready Chan 18: Ready Chan 19: Ready Chan 20: Ready Chan 21: Ready Chan 22: Ready Chan 23: Ready Modem Channels (card 1) Ch 01 ( 3A): OOS Ch 02 ( 3B): OOS Ch 03 ( 3C): Ready Ch 04 ( 3D): Ready Ch 05 ( 3E): Ready Ch 06 ( 3F): Ready Ch 07 ( 3G): Ready Ch 08 ( 3H): Ready Modem Channels (card 2) Ch 01 ( 4A): Ready Ch 02 ( 4B): Ready Ch 03 ( 4C): Ready Ch 04 ( 4D): Ready Ch 05 ( 4E): Ready Ch 06 ( 4F): Ready Ch 07 ( 4G): Ready Ch 08 ( 4H): Ready ---------------------------------------------------------------------- MultiCommManager Version 7.20 Mar 2.1998 ---------------------------------------------------------------------- Contents: ------------- 20. Introduction 21. New Features 22. Known Problems 23. Problems Fixed 24. Additional Files on the Installation disks 25. Current Firmware Versions 26. Current MIB Versions 27. Technical Support 5. Introduction -------------------- This is a feature release of the MultiCommManager to add support for the PRI card. 2. New Features ----------------------- >>> Software Support for MTPRIHD23 PRI card <<< Support includes a new bitmap for the PRI card in the rack display, and changes to the Explorer window to show the PRI card. >>> New controller commands <<< New controller commands include bpstatus, getslots, getrack, setrasostype, setpollingon, setpollingoff, t1debug, priocbchannel priosbchannel, getprichannels, pristatus, prisetup. (See the detailed description below) >>> Flash Improvements <<< The UPDATE command has been improved, to reduce the number of timeouts that occur when a controller or devices are flashed on a system with high traffic. All the records of the hex file are checksumed before any data is sent to the device to insure the file was not corrupted during the file transfer. This will not catch errors where the hex file has been truncated or modified, so that the remaining hex records are intact. >>> Port Connect Report <<< A new RAS port connection report has been added to the Statistical Analyzer. >>> Support for RAS Express 5.29 <<< Several Setup dialogs associated with managing the RAS have been updated to reflect features in the 5.29 release of RAS Express. One additional dialog has been added RAS Additional Line Setup. >>> Device Online Faults <<< A device online fault will be generated when a T1, PRI, or RAS device reports to the controller that they have been reset. In addition, when the controller resets a device, a more descriptive fault is logged. >>> GETMODEMS command <<< The GETMODEMS command has been updated on the CC9600 controller to display the current call for a modem if it is currently connected. 3. Current Limitations ------------------------------ The online help has not been updated to reflect the changes in this release. It will be made available at a later date on our Web site. It is best when flashing devices that traffic is kept to a minimum. It is remotely possible that an error can occur during flash that requires reflashing the boot code, or even replacing the flash part. For this reason we recommend flashing devices at off peak hours, on an (ideally) idle system. Successfully updating 1 card at a time is also a good practice. When using the update command to update a CommPlete T1 card, the -BOOT option must be used to update the T1 boot code. The latest T1 boot code is merged into the T1 firmware (xxx.HXT) file. If the -BOOT option is omitted, only the T1 firmware will be updated. PRI support has not yet been added to the Statistical Analyzer. It will be added in a future release. 4. Problems fixed: ------------------------ When updating the controller or modems on a system with high traffic, the update may timeout. This has been fixed by ignoring all traffic for any devices not currently being updated. When flashing a controller the entire system is shut down during the update. This will NOT affect any devices currently accepting calls. Each FTP file transfer session caused a memory leak. This would cause a later FTP session to run out of memory causing the controller to reboot and causing the FTP transfer to time out. Devices other than modems did not have faults displayed when the GETFAULTS command was executed. Faults are now displayed for all devices. 5. Additional files on the Installation Disks -------------------------------------------------------- The files listed here are files that provide additional information, or services other than the manager software. The files not described are required for installation, or are one of the four manager components. etherup.txt Provides information on flash updating of the MR4800E ethernet controller. update.txt Information on upgrading modems with old boot code and firmware after which the manager software can update firmware. snmp.txt Information on installing Newt, SNMP, and the MultiModemManager MIB description. isp.txt Information on setting up a dial in service flash.exe A self-extracting zip file that creates files necessary for flash updating modems with old boot code, and the MR4800E Ethernet controller. It is described in update.txt and by the flashpro.txt file in the self-extracting zip. mr4800.hxc MR4800 Controller firmware Version 4.0 required to flash update MT2834MR6 Modems. Configuration File Templates In the installation directory, several configuration file templates can be found. These files can be used as a basis for setting up modem configuration depending on the application and modem type. These files are simple ASCII text files that may be read by an editor, or by the Configuration Manager. If you are using the MultiCommManager with the Multi-Tech Remote Node Gateway or the Multi-Tech Fax Server, we recommend letting the product configure the modems instead of the MultiCommManager. default.cfg If no config file is attached to the modem via MultiModemManager Modem Inventory, this file is sent. 1432MR.cfg This is the default config file for 1432MR modems ISP.cfg These are example settings to be used for a dial in service for example an Internet Service Provider. 6. Current Firmware Versions --------------------------------------- Current firmware for modems, and the MR4800E controller can be found on the Multi-Tech FTP site ftp://ftp.multitech.com Controller MR4800 All Revs 4.00 MR4800E All Revs 5.20 CC9600 All Revs 2.20 Modems MT1432MR Rev D 8.08D MT1432MR Rev F 2.11B MT2834MR All Revs 1.14 MT2834MR-R All Revs 3.14 MT2834MR6 All Revs 6.04b MT3334HD8 All Revs 8.03 MT5634HD8 All Revs 1.01 MT5634HD16 All Revs 2.01 Complete RAS Card RAS96 All Revs RasExpress 5.29 Complete T1 Card RAS96T1 All Revs 1.06 Complete PRI Card MTPRIHD23B All Revs 2.43.01 7. Current MIB Versions --------------------------------- MR4800E.MIB for MR4800E 1.02C and earlier MULTI1.MIB for all other components 8. Technical Support ------------------------------- Any problems or questions should be directed to Multi-Tech Technical Support at (612) 785-3500 or (800) 328-9717. Please send any suggestions or possible enhancements to: Multi-Tech Systems, Inc., 2205 Woodale Drive, Mounds View, Minnesota 55112, c/o "R&D -MultiModemManager" Internet Address http://www.multitech.com FTP Site ftp://ftp.multitech.com Fax us at (612) 785-9874. 9. New Controller Commands ----------------------------------------- COMMAND PARAMETER SECURITY LEVEL GETSLOTS None Operator Def. Displays hardware type and location within the rack. It also displays number of devices in each slot. Ex. [01] A:\ # Getslots 1 MTRAS96 - T1A 2 2 MT5634HD8 8 3 MT5634HD8 8 4 MT5634HD8 8 GETPS, GETPOWERSTATUS None Guest (9600 only) Def. Displays the main power supply/ies status and which segments are powered up. Ex. [02] A:\ # Getpowerstatus Left Power Supply: Installed, All outputs good Right Power Supply: Not installed First Segment: Powered Second Segment: Not Powered Third Segment: Not Powered Fourth Segment: Not Powered [03] A:\ # GETTEMP None Guest (9600 only) Def. Displays the internal ambient temperature of the rack in Fahrenheit and Celsius. Ex. [03]A: \ # Gettemp 76.4 degrees fahrenheit 24.7 degrees Celsius SETRASOSTYPE Device Operator (9600 only) Def. Lets the controller know what operating system is loaded on each segment. Ex. [01] A:\ # Setrasostype 1a Operating System:Ras Express 5.2 (or later) Operating System 1. Ras Express pre(5.2) 2. SCO Unix 3. Windows NT 4. Novell Netware 5. Ras Express 5.2 (or later) 6. Other Enter Selection (1,2,3,4,<5>,6, -(previous), q(uit)): SYNC None Operator Def. Writes outstanding events (events that normally get written every hour) to the B:\ # MMM\MR.Log directory. The file will be named the current date and hour with an extension of hr. Ex. [01] A:\ # Sync [02] A:\ # GETRACK None Operator Def. Displays the model number and basic description of the chassis. Ex. [5] A:\ # getrack Chassis Type: CC9600 four segment chassis [6] A:\ # SETPOLLINGOFF Device Supervisor Def. Disables controller generated polling to specified device. The example below starts with displaying the status of the back plane by using the bpstatus command. Ex. [1] A:\# bpstatus Backplane Status: Busy:NoResp:NoAck -: no polling 0: count of 0 1-9: tens digit plus 1 *: >= ninety Slot A B C D E F G H I J K L M N O P 5: 000 000 6: 000 000 000 000 000 000 000 000 7: 000 000 000 000 000 000 000 000 8: 000 000 000 000 000 000 000 000 9: 000 000 10: 000 000 000 000 000 000 000 000 11: 000 000 000 000 000 000 000 000 12: 000 000 000 000 000 000 000 000 [2] A:\ # setpollingoff 5a [3] A:\ # bpstatus Backplane Status: Busy:NoResp:NoAck -: no polling 0: count of 0 1-9: tens digit plus 1 *: >= ninety Slot A B C D E F G H I J K L M N O P 5: --- 000 6: 000 000 000 000 000 000 000 000 7: 000 000 000 000 000 000 000 000 8: 000 000 000 000 000 000 000 000 9: 000 000 10: 000 000 000 000 000 000 000 000 11: 000 000 000 000 000 000 000 000 12: 000 000 000 000 000 000 000 000 [4] A:\ # SETPOLLINGON Device Supervisor Def. Re-enables polling between controller and specified device. The example below starts with displaying the status of the back plane by using the bpstatus command. Ex. [4] A:\ # bpstatus Backplane Status: Busy:NoResp:NoAck -: no polling 0: count of 0 1-9: tens digit plus 1 *: >= ninety Slot A B C D E F G H I J K L M N O P 5: --- 000 6: 000 000 000 000 000 000 000 000 7: 000 000 000 000 000 000 000 000 8: 000 000 000 000 000 000 000 000 9: 000 000 10: 000 000 000 000 000 000 000 000 11: 000 000 000 000 000 000 000 000 12: 000 000 000 000 000 000 000 000 [5] A:\ # setpollingon 5a [6] A:\ # bpstatus Backplane Status: Busy:NoResp:NoAck -: no polling 0: count of 0 1-9: tens digit plus 1 *: >= ninety Slot A B C D E F G H I J K L M N O P 5: 000 000 6: 000 000 000 000 000 000 000 000 7: 000 000 000 000 000 000 000 000 8: 000 000 000 000 000 000 000 000 9: 000 000 10: 000 000 000 000 000 000 000 000 11: 000 000 000 000 000 000 000 000 12: 000 000 000 000 000 000 000 000 [7] A:\ # T1DEBUG Device Supervisor (9600 only) Def. Displays status of AB Signalling bits for both the transmit and receive directions of each DS0 channel for the specified T1 device within the Commplete. TX = from Commplete T1 card to Central Office. RX = from Central Office to Commplete T1 card. Ex. [31] A:\ # t1debug 1b 1. Enable Signal Bit monitoring 2. Turn Off signal bit monitoring 3. Signal Poll interval (4) => 1 Completed enabling all selected devices! [32] A:\ # 01B 01B Tx/Rx Tx/Rx AB/AB AB/AB 01 00/00 02 00/00 03 00/00 04 00/00 05 00/00 06 00/00 07 00/00 08 00/00 09 00/00 10 00/00 11 00/00 12 00/00 13 00/00 14 00/00 15 00/00 16 00/00 17 00/00 18 00/00 19 00/00 20 00/00 21 00/00 22 00/00 23 00/00 24 00/00 E&M Immediate Start Protocol Tx(AB) Rx(AB) OFF HOOK 11 11 ON HOOK 00 00 RINGING NA NA [33] A:\ # t1debug 1b 1. Enable Signal Bit monitoring 2. Turn Off signal bit monitoring 3. Signal Poll interval (4) => 2 BPSTATUS None Supervisor Def. Displays the rack's back plane polling activity between the controller and each powered device. Each correctly operating device responds to three specific polls; "Busy", "No Response" and "No Acknowledgement". If the device does not reposnd the counter/s will increment. The example below shows all devices in a fully loaded CC9600 are responding correctly. Ex. [1] A:\ # bpstatus Backplane Status: Busy:NoResp:NoAck -: no polling 0: count of 0 1-9: tens digit plus 1 *: >= ninety Slot A B C D E F G H I J K L M N O P 1: 000 000 2: 000 000 000 000 000 000 000 000 3: 000 000 000 000 000 000 000 000 4: 000 000 000 000 000 000 000 000 5: 000 000 6: 000 000 000 000 000 000 000 000 7: 000 000 000 000 000 000 000 000 8: 000 000 000 000 000 000 000 000 9: 000 000 10: 000 000 000 000 000 000 000 000 11: 000 000 000 000 000 000 000 000 12: 000 000 000 000 000 000 000 000 13: 000 000 14: 000 000 000 000 000 000 000 000 15: 000 000 000 000 000 000 000 000 16: 000 000 000 000 000 000 000 000 [2] A:\ # PRISTATUS Specifier Operator Def. Retrieve the current status of the specified PRI card. Ex. [1] A:\ # pristatus 2a Getting PRI Info ..... Switch Type:AT&T 4ESS Line Coding: Binary 8 Zero Substitution (B8ZS) Framing Format: Extended Super Frame Error Correction Method: CRC-6 Enabled Call Distribution:One to One Set Carrier:PCM24/T1 Model:MTPRI-HD23B Version:2.43.01 Layer 1 Status:Up Layer 2 Status:Multi-Frame Established PRIOSBCHANNEL Device.Channel # Operator Def. Set the specified B Channel Out of Service. Check the results with getprichannels. Ex. [1] A:\ # priosbchannel 2a.1 PRIOCBCHANNEL Device.Channel # Operator Def. Set the specified B Channel In Service. Check the results with getprichannels. Ex. [1] A:\ # priocbchannel 2a.1 GETPRICHANNELS Device Operator Def. Set configuration paramaters for a PRI card. Ex. [1] A:\ # getprichannels 2a Getting PRI Info .... B Channels Chan 01: OOS Chan 02: ReadyChan 03: Ready Chan 04: ReadyChan 05: Ready Chan 06: ReadyChan 07: Ready Chan 08: Ready Chan 09: Ready Chan 10: Ready Chan 11: Ready Chan 12: Ready Chan 13: Ready Chan 14: Ready Chan 15: Ready Chan 16: Ready Chan 17: Ready Chan 18: Ready Chan 19: Ready Chan 20: Ready Chan 21: Ready Chan 22: Ready Chan 23: Ready Modem Channels (card 1) Ch 01 ( 3A): OOS Ch 02 ( 3B): OOS Ch 03 ( 3C): Ready Ch 04 ( 3D): Ready Ch 05 ( 3E): Ready Ch 06 ( 3F): Ready Ch 07 ( 3G): Ready Ch 08 ( 3H): Ready Modem Channels (card 2) Ch 01 ( 4A): Ready Ch 02 ( 4B): Ready Ch 03 ( 4C): Ready Ch 04 ( 4D): Ready Ch 05 ( 4E): Ready Ch 06 ( 4F): Ready Ch 07 ( 4G): Ready Ch 08 ( 4H): Ready --------------------------------------------------------------- MultiCommManager Version 7.01 Dec 9.1997 --------------------------------------------------------------- Contents: ------------- 1. Introduction 2. New Features 3. Current Limitations 4. Problems Fixed 5. Additional Files on the Installation disks 6. Current Firmware Versions 7. Current MIB Versions 8. Technical Support 1. Introduction -------------------- This is both a maintenance and hardware support release. The MultiCommManager now supports the MT5634HD16 K56flex modem coupled with a dual T1 RAS card. See the section on Version 7.00 for information on the latest feature release. 2. New Features ----------------------- >>> Software Support for MT5634HD16 modem <<< Support includes new bitmap for MT5634HD16 and a rack display that distinguishes between them. 3. Current Limitations ------------------------------ See limitation descriptions in older versions. 4. Problems fixed: ------------------------ When adding a new IP through the explorer window, the default community strings would occasionally come up as public (read community) and supervisor (write community). The write community should always default to public. If a RAS card is not recognized as a RASExpress version 5.2 or later, then the RAS line in the explorer window will be grayed out and will not be selectable for viewing or control operations. An ANLB 14400 modem test failed fault was being erroneously reported on a RAS card on an intermittent basis. The Set Environment (SE) command was changed such that it prompts if RAS card defaults or system defaults are to be used when configuring a new RAS card. Choice options for the SE menu have been clarified and now allow you to quit and save changes, quit without saving changes or back up to the previous menu. Entering any string beginning with the letter Q in the SE menu caused to operation to quit and cancel changes. Now only "Q" or "q" will cause the abort to occur. 5. Additional files on the Installation Disks -------------------------------------------------------- The files listed here are files that provide additional information, or services other than the manager software. The files not described are required for installation, or are one of the four manager components. etherup.txt Provides information on flash updating of the MR4800E ethernet controller. update.txt Information on upgrading modems with old boot code and firmware after which the manager software can update firmware. snmp.txt Information on installing Newt, SNMP, and the MultiModemManager MIB description. isp.txt Information on setting up a dial in service flash.exe A self-extracting zip file that creates files necessary for flash updating modems with old boot code, and the MR4800E Ethernet controller. It is described in update.txt and by the flashpro.txt file in the self-extracting zip. mr4800.hxc MR4800 Controller firmware Version 4.0 required to flash update MT2834MR6 Modems. Configuration File Templates In the installation directory, several configuration file templates can be found. These files can be used as a basis for setting up modem configuration depending on the application and modem type. These files are simple ASCII text files that may be read by an editor, or by the Configuration Manager. If you are using the MultiCommManager with the Multi-Tech Remote Node Gateway or the Multi-Tech Fax Server, we recommend letting the product configure the modems instead of the MultiCommManager. default.cfg If no config file is attached to the modem via MultiModemManager Modem Inventory, this file is sent. 1432MR.cfg This is the default config file for 1432MR modems ISP.cfg These are example settings to be used for a dial in service for example an Internet Service Provider. 6. Current Firmware Versions --------------------------------------- Current firmware for modems, and the MR4800E controller can be found on the Multi-Tech FTP site ftp://ftp.multitech.com Controller MR4800 All Revs 7.01 MR4800E All Revs 5.01 CC9600 All Revs 2.01 Modems MT1432MR Rev D 8.08D MT1432MR Rev F 2.11B MT2834MR All Revs 1.14 MT2834MR-R All Revs 3.14 MT2834MR6 All Revs 6.04b MT3334HD8 All Revs 8.03 MT5634HD8 All Revs 1.00c MT5634HD16 All Revs 1.00c Complete RAS Card RAS96 All Revs RasExpress 5.21 Complete T1 Card RAS96T1 All Revs 1.00P 7. Current MIB Versions --------------------------------- MR4800E.MIB for MR4800E 1.02C and earlier MULTI1.MIB for all other components 8. Technical Support ------------------------------- Any problems or questions should be directed to Multi-Tech Technical Support at (612) 785-3500 or (800) 328-9717. Please send any suggestions or possible enhancements to: Multi-Tech Systems, Inc., 2205 Woodale Drive, Mounds View, Minnesota 55112, c/o "R&D -MultiModemManager" Internet Address http://www.multitech.com FTP Site ftp://ftp.multitech.com Fax us at (612) 785-9874. --------------------------------------------------------------- MultiCommManager Version 7.00 Nov 7, 1997 --------------------------------------------------------------- Contents: ------------- 1. Introduction 2. New Features 3. Known Limitations 4. Problems Fixed 5. Additional Files on the Installation disks 6. Current Firmware Versions 7. Current MIB Versions 8. Technical Support 1. Introduction -------------------- This is a major feature release for the MultiModemManager (as it was called) software. Welcome to MultiCommManager. This transformation has happened because we wanted to be able to manage all of the parts of the CommPlete rack from one software interface. The first major addition was support for management of RasExpress, Multi-Tech's built in Terminal Server that is used in the CommPlete. In the future we hope to add management support for all of Multi-Tech's SNMP manageable devices. 2. New Features ----------------------- >>> Generalization of MultiComm Manager <<< There are no longer modem groups and rack groups windows. These are replaced with a single Explorer window that has two root items: Logical View and Physical View. Logical View supports what modem groups used to show and Physical View shows what Rack Groups used to show. The Setup menu now has operations in it for Modems, RAS's, RAS ISI cards, RAS lines and T1 devices. The View menu now has views for Modems, RAS's, RAS lines, and T1 devices. Also both have new sub-menus called Legacy Management. This is to support (and hide somewhat) older MMM Interface Racks. The Control menu has been generalized to a great degree as the Test, OOS Set/Clear, and Reset items are now device generic. If you select a device that does not support an operation, an error message is received. And if you select multiple devices that are of different types but also support the same operation, then that operation is performed on each selected device. >>> Support for managing RAS/Express <<< When Physical Groups are opened to the Rack Device level, both RAS devices and T1 devices are now shown. RAS devices can be opened further to show ISI cards and when they are opened, communication lines are shown. When the RAS is selected, various RAS setup operations are available in the Setup menu, various RAS statistics can be viewed from the View menu, the RAS can be reset from the Control menu, and its software version retrieved from the Firmware menu. When an ISI card is selected, its Base Address and IRQ can set from the Setup menu. When a RAS communication line is selected, various RAS line setup operations are available in the Setup menu, various RAS line statistics can be viewed from the View menu and various control operations are available for RAS lines in the Control menu. When these items are displayed in the hierarchy they can display current state information, configuration information, or user id information. If you have a CommPlete that is already setup, all you need to do to use MultiCommManager 7.0 is upgrade your RAS cards to the latest version of RASExpress software and then use the SETRASOSTYPE command to allow the controller to talk to all of your RASExpress servers. The current version of RASExpress is available on the FTP site (FTP.multitech.com) under the MMM/Commplete/Release directory. See MR9600 controller README command for more information. >>> Controller Support for setting up RAS/Express <<< The MR9600 controller can now do initial setup on the RAS Express so that the end user can setup the entire rack from one interface. We have also made it easier to configure new RAS/T1 cards when they are inserted after the system is initially set up. 3. Known Limitations ------------------------------ * There is currently no way to show non-RASExpress OS types in the Explorer window. * The previous modem group file (mr4800.gp) used to define logical groups is not converted to the new format. This means that after the upgrade, all previously defined modem groups will be gone, and all modems will reside in the Unassigned group in the Logical View. The internal file mr4800.gp is copied to mr4800v0.gp and a new mr4800.gp is created. 4. Problems fixed: ------------------------ * No problems fixed aside from the addition of new features 5. Additional files on the Installation Disks -------------------------------------------------------- The files listed here are files that provide additional information, or services other than the manager software. The files not described are required for installation, or are one of the four manager components. etherup.txt Provides information on flash updating of the MR4800E ethernet controller. update.txt Information on upgrading modems with old boot code and firmware after which the manager software can update firmware. snmp.txt Information on installing Newt, SNMP, and the MultiCommManager MIB description. isp.txt Information on setting up a dial in service mr4800.hxc MR4800 Controller firmware Version 4.0 required to flash update MT2834MR6 Modems. Configuration File Templates (MR4800 and MR4800E controllers) On the Commplete server (MR9600 controller) modem configuration should be handled by RASExpress. In the installation directory, several configuration file templates can be found. These files can be used as a basis for setting up modem configuration depending on the application and modem type. These files are simple ASCII text files that may be read by an editor, or by the Configuration Manager. If you are using the MultiCommManager with the Multi-Tech Remote Node Gateway or the Multi-Tech Fax Server, we recommend letting the product configure the modems instead of the MultiCommManager. default.cfg If no config file is attached to the modem via MultiCommManager Modem Inventory, this file is sent. 1432MR.cfg This is the default config file for 1432MR modems ISP.cfg These are example settings to be used for a dial in service for example an Internet Service Provider. 6. Current Firmware Versions --------------------------------------- Current firmware for modems, and the MR4800E controller can be found on the Multi-Tech FTP site ftp://ftp.multitech.com Controller MR4800 All Revs 4.00 MR4800E All Revs 5.00 CC9600 All Revs 2.00 Modems MT1432MR Rev D 8.08D MT1432MR Rev F 2.11B MT2834MR All Revs 1.14 MT2834MR-R All Revs 3.14 MT2834MR6 All Revs 6.04b MT3334HD8 All Revs 8.03 MT5634HD8 All Revs 1.00c Complete RAS Card RAS96 All Revs RasExpress 5.21 Complete T1 Card RAS96T1 All Revs 1.01P 7. Current MIB Versions --------------------------------- MR4800E.MIB for MR4800E 1.02C and earlier (on Multi-Tech web site) MULTI1.MIB for all other components 8. Technical Support ------------------------------- Any problems or questions should be directed to Multi-Tech Technical Support at (612) 785-3500 or (800) 328-9717. Please send any suggestions or possible enhancements to: Multi-Tech Systems, Inc., 2205 Woodale Drive, Mounds View, Minnesota 55112, c/o "R&D -MultiCommManager" Internet Address http://www.multitech.com FTP Site ftp://ftp.multitech.com Fax us at (612) 785-9874. --------------------------------------------------------------- MultiModemManager Version 6.13 Sept 21.1997 --------------------------------------------------------------- Contents: ------------- 28. Introduction 29. New Features 30. Known Bugs 31. Problems Fixed 32. Additional Files on the Installation disks 33. Current Firmware Versions 34. Current MIB Versions 35. Technical Support 6. Introduction -------------------- This is a hardware support release. The MultiModemManager now supports the MT5634HD8 K56flex modem card and the CC2400 one segment (4 slot) rack. 2. New Features ----------------------- >>> Software Support for MT5634HD8 modem <<< Support includes new bitmap for MT3334HD8 and a rack display that distinguishes between them. >>> Software Support for CC2400 rack <<< Support includes a new rack display to indicate what cards are installed. 3. Current Limitations ------------------------------ See limitation descriptions in older versions. 4. Problems fixed: ------------------------ No problems fixed in this version. 5. Additional files on the Installation Disks -------------------------------------------------------- The files listed here are files that provide additional information, or services other than the manager software. The files not described are required for installation, or are one of the four manager components. etherup.txt Provides information on flash updating of the MR4800E ethernet controller. update.txt Information on upgrading modems with old boot code and firmware after which the manager software can update firmware. snmp.txt Information on installing Newt, SNMP, and the MultiModemManager MIB description. isp.txt Information on setting up a dial in service flash.exe A self-extracting zip file that creates files necessary for flash updating modems with old boot code, and the MR4800E Ethernet controller. It is described in update.txt and by the flashpro.txt file in the self-extracting zip. mr4800.hxc MR4800 Controller firmware Version 4.0 required to flash update MT2834MR6 Modems. Configuration File Templates In the installation directory, several configuration file templates can be found. These files can be used as a basis for setting up modem configuration depending on the application and modem type. These files are simple ASCII text files that may be read by an editor, or by the Configuration Manager. If you are using the MultiModemManager with the Multi-Tech Remote Node Gateway or the Multi-Tech Fax Server, we recommend letting the product configure the modems instead of the MultiModemManager. default.cfg If no config file is attached to the modem via MultiModemManager Modem Inventory, this file is sent. 1432MR.cfg This is the default config file for 1432MR modems ISP.cfg These are example settings to be used for a dial in service for example an Internet Service Provider. 6. Current Firmware Versions --------------------------------------- Current firmware for modems, and the MR4800E controller can be found on the Multi-Tech FTP site ftp://ftp.multitech.com Controller MR4800 All Revs 4.00 MR4800E All Revs 3.10 CC9600 All Revs 1.10 Modems MT1432MR Rev D 8.08D MT1432MR Rev F 2.11B MT2834MR All Revs 1.13H MT2834MR-R All Revs 3.13E MT2834MR6 All Revs 6.03 MT3334HD8 All Revs 8.03 MT5634HD8 All Revs 1.00b Complete RAS Card RAS96 All Revs RasExpress 5.20 Complete T1 Card RAS96T1 All Revs 1.00C 7. Current MIB Versions --------------------------------- MR4800E.MIB for MR4800E 1.02C and earlier MULTI1.MIB for all other components 8. Technical Support ------------------------------- Any problems or questions should be directed to Multi-Tech Technical Support at (612) 785-3500 or (800) 328-9717. Please send any suggestions or possible enhancements to: Multi-Tech Systems, Inc., 2205 Woodale Drive, Mounds View, Minnesota 55112, c/o "R&D -MultiModemManager" Internet Address http://www.multitech.com FTP Site ftp://ftp.multitech.com Fax us at (612) 785-9874. --------------------------------------------------------------- Version 6.12 July 22, 1997 --------------------------------------------------------------- Contents: ------------- 1. Introduction 2. New Features 3. Current Limitations 4. Problems Fixed 5. Additional Files on the Installation disks 6. Current Firmware Versions 7. Current MIB Versions 8. Technical Support 1. Introduction -------------------- This is a maintenance release of the MultiModemManager software. See the section on Version 6.00 for information on the latest feature release. 2. New Features ----------------------- >>> Support for analyzing events from multiple MR4800E / MR9600 controllers <<< When running the Statistical Analyzer, you can now select which IP's (meaning with ethernet controllers / MMM Agent sites, you wish to analyze events from. Only the selected sites are included in the analysis. There are now sub-directories underneath the C:\MRACK\MR.LOG directory (if your software was installed in the C:\MRACK directory) that hold the events for each different controller or MMM Agent PC. The user must manually put the event files there (ie. by doing FTP from the controller its designated directory). The directories are created in one of two ways: 1) when the user adds an IP site when running the MMM software in Supervisor mode (which is default) or 2) when the MMM software is started it creates the directories if they don't already exist. The name of the sub-directory is taken from the IP short name (which must be unique). 3. Current Limitations ------------------------------ See limitation descriptions in older versions. 4. Problems fixed: ------------------------ 1. The Overtime call Fault causes the Stat Analyzer to crash. (Usually with a GP). 2. When viewing a 9600 rack display with the one supply in the right side of the cage, the rack display shows it on the left side. This is also the same for the left side. 3. You cannot upgrade a MR4800 controller. It acts as if the upgrade was successful, but it was not. 4. The string, "Internal Status", was causing problems in the fault status Window. 5. Congested Rack fault alarm had options to Reset and Hang up modems 6. When doing Rack Display / Select All / Control Reset - you get a dialog that says there are Not Present items in the select list 7. Software would crash when playing with fault alarms. 8. When an MR4800E is being managed by a supervisor, and a card is inserted, only (n-1) modems appear. 9. If you go into fault alarms, and disable a fault and close the window, the controller would reboot. 10. The fault alarm defaults are different on the agent side, compared to the supervisor side. The supervisor side will not let you make any changes to fault alarms 11. On the supervisor of a MMM agent, if you try to change a fault alarm (disable it) it gives you an error in the F & S window of "Internal status > error from SNMP agent Status 5 (General Error) on this request. This works on the Agent side 12. From the supervisor, double clicking on an MMM agent, a not present modem in a defined modem group asserts the agent at sim.c=>2445 then ms.c=>1800. 13. Setup - System Defaults, changing from operator to automatic mode doesn't save to the .INI file. 14. Modem usage report has modems missing. (i.e. 2 modems connected, 30 modems IDLE, out of 35 total modems). 15. Card Installed only displays 2 modems, the A modem doesn't show up unless you close the IP, and re-open (modem group window). MMM Supervisor 16. Got a SMNP bad value while opening a modem group after a controller resets 17. Duration in the call traffic window for remote IP's turn "not available" after a call ends. 18. Installing MMM version 6.11 over MMM version 4.0 and/or 4.1 corrupts the .MR4800.INV or MR4800.CID file. Internal Error - Assertion Failed Expression mdm.c, Line 619 19. The F3 key crashes the Online window through the software. CSN.C, Line 134. 20. Callback security locks up the software. 21. When a 2834MR modem connects at 26.4K or 21.6K the modem has 2 baud rate lights on and the call traffic window tells you the correct speed but the modem status window only shows one baud light. 22. Password expiration in security does not work, it never prompts you to change it. 23. If you are doing callback security and a modem in your outbound group is OOSS/software it uses the modem anyway. 24. If I put a modem with three transformers per modem into a slot that had a PSTN modem in, I can no longer select leased line (grayed out) 25. Software crashes when you do a control action (reset, config) that times out, and then do another. 26. Modem card installed & Modem card removed fault alarms do not work above 0 threshold. Threshold also switches to a value of 1 after the alarm is tripped. This happens on many other faults. 27. Rack online has garbage in Fault/Status window when the controller reboots 28. Getting modem inventory for a MR6 modem, the TYPE/DIAL-UP is not highlighted.. 29. Supervisor to an arcnet agent, opening up a group crashes (assert with ms.c line 1489 and simd.c line 2281). 30. Statistical Analyzer - Every report that is made is labeled as a Connection report 31. Statistical Analyzer - crashes when processing Modem usage events 32. Statistical Analyzer - Free modems report shows up as garbage in ASCII Log Dump 33. Configuration Manager - #T command removed from firmware. Should also remove it from the software. 34. Configuration Manager - "Modem Baud Rate" from Master list does not have an option for 33,600, and says 28,800 is the default 5. Additional files on the Installation Disks -------------------------------------------------------- The files listed here are files that provide additional information, or services other than the manager software. The files not described are required for installation, or are one of the four manager components. etherup.txt Provides information on flash updating of the MR4800E ethernet controller. update.txt Information on upgrading modems with old boot code and firmware after which the manager software can update firmware. snmp.txt Information on installing Newt, SNMP, and the MultiModemManager MIB description. isp.txt Information on setting up a dial in service flash.exe A self-extracting zip file that creates files necessary for flash updating modems with old boot code, and the MR4800E Ethernet controller. It is described in update.txt and by the flashpro.txt file in the self-extracting zip. mr4800.hxc MR4800 Controller firmware Version 4.0 required to flash update MT2834MR6 Modems. Configuration File Templates In the installation directory, several configuration file templates can be found. These files can be used as a basis for setting up modem configuration depending on the application and modem type. These files are simple ASCII text files that may be read by an editor, or by the Configuration Manager. If you are using the MultiModemManager with the Multi-Tech Remote Node Gateway or the Multi-Tech Fax Server, we recommend letting the product configure the modems instead of the MultiModemManager. default.cfg If no config file is attached to the modem via MultiModemManager Modem Inventory, this file is sent. 1432MR.cfg This is the default config file for 1432MR modems ISP.cfg These are example settings to be used for a dial in service for example an Internet Service Provider. 6. Current Firmware Versions --------------------------------------- Current firmware for modems, and the MR4800E controller can be found on the Multi-Tech FTP site ftp://ftp.multitech.com Controller MR4800 All Revs 4.00 MR4800E All Revs 3.10 CC9600 All Revs 1.10 Modems MT1432MR Rev D 8.08D MT1432MR Rev F 2.11B MT2834MR All Revs 1.13H MT2834MR-R All Revs 3.13E MT2834MR6 All Revs 6.03 MT3334HD8 All Revs 8.03 Complete T1 Card RAS96T1 All Revs 1.00C 7. Current MIB Versions --------------------------------- MR4800E.MIB for MR4800E 1.02C and earlier MULTI1.MIB for all other components 8. Technical Support ------------------------------- Any problems or questions should be directed to Multi-Tech Technical Support at (612) 785-3500 or (800) 328-9717. Please send any suggestions or possible enhancements to: Multi-Tech Systems, Inc., 2205 Woodale Drive, Mounds View, Minnesota 55112, c/o "R&D -MultiModemManager" Internet Address http://www.multitech.com FTP Site ftp://ftp.multitech.com Fax us at (612) 785-9874. --------------------------------------------------------------- Version 5.01 Italy June 2, 1997 --------------------------------------------------------------- Contents: ------------- 1. Introduction 2. New Features 3. Current Limitations 4. Problems Fixed 5. Additional Files on the Installation disks 6. Current Firmware Versions 7. Current MIB Versions 8. Technical Support 1. Introduction -------------------- This is a maintenance release of the MultiModemManager software. See the section on Version 6.00 for information on the latest feature release. 2. New Features ----------------------- >>> Support for going online with the modems from a supervisor to an agent or controller <<< You can now select modems on an agent or controller and go online with them. Attempting to do this in the past generated an error message. >>> Support for Speed Shifts <<< Now connect speeds in the modem groups, rack groups and rack grid windows now display the current modem speed (not just the connect speed), taking into account any speed shifts that have occurred. 3. Current Limitations ------------------------------ See leased line section below. 4. Problems fixed: ------------------------ The way leased line was done has now changed with the introduction of firmware version 1.13h for the 2834MR. With modems with firmware earlier than 1.13h or 1432MRs, leased line functions one a one connect basis. After the modems disconnected, they will be in idle mode. If a new configuration is sent to them, they will re-connect. So the leased line modems have to be placed in a modem group that will re-configure the modems on a disconnect and on reset. These modems however cannot do dial-backup. With 1.13h and later, the modems will now function like stand-alone leased line modems that simply always try to connect and/or perform dial-backup when configured to do so. The catch with this is that to change a modem back to dial-up mode or to change any of its leased line settings (2-wire vs 4-wire, or to change the dial-backup number), its configuration must be changed and then the modem must be reset and re-configured. 5. Additional files on the Installation Disks -------------------------------------------------------- The files listed here are files that provide additional information, or services other than the manager software. The files not described are required for installation, or are one of the four manager components. etherup.txt Provides information on flash updating of the MR4800E ethernet controller. update.txt Information on upgrading modems with old boot code and firmware after which the manager software can update firmware. snmp.txt Information on installing Newt, SNMP, and the MultiModemManager MIB description. isp.txt Information on setting up a dial in service flash.exe A self-extracting zip file that creates files necessary for flash updating modems with old boot code, and the MR4800E Ethernet controller. It is described in update.txt and by the flashpro.txt file in the self-extracting zip. mr4800.hxc MR4800 Controller firmware Version 4.0 required to flash update MT2834MR6 Modems. Configuration File Templates In the installation directory, several configuration file templates can be found. These files can be used as a basis for setting up modem configuration depending on the application and modem type. These files are simple ASCII text files that may be read by an editor, or by the Configuration Manager. If you are using the MultiModemManager with the Multi-Tech Remote Node Gateway or the Multi-Tech Fax Server, we recommend letting the product configure the modems instead of the MultiModemManager. default.cfg If no config file is attached to the modem via MultiModemManager Modem Inventory, this file is sent. 1432MR.cfg This is the default config file for 1432MR modems ISP.cfg These are example settings to be used for a dial in service for example an Internet Service Provider. 6. Current Firmware Versions --------------------------------------- Current firmware for modems, and the MR4800E controller can be found on the Multi-Tech FTP site ftp://ftp.multitech.com Controller MR4800 All Revs 4.00 MR4800E All Revs 3.10 CC9600 All Revs 1.10 Modems MT1432MR Rev D 8.08D MT1432MR Rev F 2.11B MT2834MR All Revs 1.13H MT2834MR-R All Revs 3.13E MT2834MR6 All Revs 6.03 MT3334HD8 All Revs 8.03 Complete T1 Card RAS96T1 All Revs 1.00C 7. Current MIB Versions --------------------------------- MR4800E.MIB for MR4800E 1.02C and earlier MULTI1.MIB for all other components 8. Technical Support ------------------------------- Any problems or questions should be directed to Multi-Tech Technical Support at (612) 785-3500 or (800) 328-9717. Please send any suggestions or possible enhancements to: Multi-Tech Systems, Inc., 2205 Woodale Drive, Mounds View, Minnesota 55112, c/o "R&D -MultiModemManager" Internet Address http://www.multitech.com FTP Site ftp://ftp.multitech.com Fax us at (612) 785-9874. --------------------------------------------------------------- Version 6.11 April 15, 1997 --------------------------------------------------------------- Contents: ------------- 1. Introduction 2. New Features 3. Current Limitations 4. Problems Fixed 5. Additional Files on the Installation disks 6. Current Firmware Versions 7. Current MIB Versions 8. Technical Support 1. Introduction -------------------- This is a maintenance release of the MultiModemManager software. See the section on Version 6.00 for information on the latest feature release. 2. New Features ----------------------- >>> Support for the CommPlete Rack CC9600 rack <<< The Manager now supports the new rack by adding a new rack display. >>> Native support for SNMP<<< Since we natively support SNMP, we now handle issues that Newt used to handle (such as Trap Administration). When using our native SNMP support, there is a new sub-menu under the Setup | SNMP menu called Default Trap IP. This allows you to set where traps are sent to by default. Also we now dynamically support traps to multiple supervisors (as on the MR4800E controller). When an Supervisor does a login to an Agent, then they are dynamically added to a list of IP's where Traps are sent. The Supervisor "logs in" upon software startup or when the IP of an agent is added to the list of managed agents in the Rack Group Window. When we start up we try to load SNMP.DLL (this is Newt's SNMP support library). If we can load it, then we run with Newt, if not we try to load MMMSNMP.DLL (our native SNMP support library). To run without Newt, either take the NetManage directory out of your search path or rename SNMP.DLL to SNMP.SAV (or some other name). Note that you have the re-boot your machine before these changes will take effect. For more information on removing NEWT, read NEWT95.DOC available at our FTP site (ftp://ftp.multitech.com). >>> Controller flashing is now available <<< On the 1.00 version of the MR9600 firmware and the 3.00 version of the MR4800E firmware, both controller and modem flash updating is now supported. It is however only supported through the telnet command line. Refer to the controller documentation and/or readme command to see how this works. >>> Dial Tone Test <<< A new test has been added that will check if a dial tone is present for a modem. This test is not implemented for the CC9600 rack, because dial tone is not present in most T1 configurations. >>> Console Lock <<< The Lock Console menu item has been added to the ABOUT menu. This allows an administrator to protect the console from unwanted access while he/she is away. The Set SNMP Password menu item has been changed to Set System Password. If the manager is started and the system password is other than the default, the console will be locked. >>> Disable Faults <<< The Fault - Alarm dialog (Setup | Fault Alarms) has been changed to allow an administrator to Disable any Fault. When a Fault is disabled, it is not displayed in the Fault Status window, or written to the event file. No Trap is sent for a disabled fault. The dialog uses two list boxes to separate Faults with Alarms from Faults that do not generate an alarm. >>> Supervisor Mode Default <<< The default mode for the management console has been changed from Independent to Supervisor. 3. Current Limitations ------------------------------ Support for the CommPlete rack is kind of thin right now. We only show and allow you to select modems. The T1 and RAS card is only supported via Telnet on the MR9600 controller. We will have more complete support in a later release. When flashing modems, try to isolate them to a rack with little or no traffic. When the amount of traffic on a rack is high, the probability of time-out errors when flashing modems increases. 4. Problems fixed: ------------------------ When a MR4800 agent stops responding because it is turned off, or the M.I C. (Management Interface Card) connection is broken, The Modem Group Window, and Rack Group Window will gray the rack and modems of the non-responsive rack. 5. Additional files on the Installation Disks -------------------------------------------------------- The files listed here are files that provide additional information, or services other than the manager software. The files not described are required for installation, or are one of the four manager components. etherup.txt Provides information on flash updating of the MR4800E ethernet controller. update.txt Information on upgrading modems with old boot code and firmware after which the manager software can update firmware. snmp.txt Information on installing Newt, SNMP, and the MultiModemManager MIB description. isp.txt Information on setting up a dial in service flash.exe A self-extracting zip file that creates files necessary for flash updating modems with old boot code, and the MR4800E Ethernet controller. It is described in update.txt and by the flashpro.txt file in the self-extracting zip. mr4800.hxc MR4800 Controller firmware Version 4.0 required to flash update MT2834MR6 Modems. Configuration File Templates In the installation directory, several configuration file templates can be found. These files can be used as a basis for setting up modem configuration depending on the application and modem type. These files are simple ASCII text files that may be read by an editor, or by the Configuration Manager. If you are using the MultiModemManager with the Multi-Tech Remote Node Gateway or the Multi-Tech Fax Server, we recommend letting the product configure the modems instead of the MultiModemManager. default.cfg If no config file is attached to the modem via MultiModemManager Modem Inventory, this file is sent. 1432MR.cfg This is the default config file for 1432MR modems ISP.cfg These are example settings to be used for a dial in service for example an Internet Service Provider. 6. Current Firmware Versions --------------------------------------- Current firmware for modems, and the MR4800E controller can be found on the Multi-Tech FTP site ftp://ftp.multitech.com Controller MR4800 All Revs 4.00 MR4800E All Revs 3.10 CC9600 All Revs 1.10 Modems MT1432MR Rev D 8.08D MT1432MR Rev F 2.11B MT2834MR All Revs 1.13D MT2834MR-R All Revs 3.13E MT2834MR6 All Revs 6.03 MT3334HD8 All Revs 8.03 Complete T1 Card RAS96T1 All Revs 1.00C 7. Current MIB Versions --------------------------------- MR4800E.MIB for MR4800E 1.02C and earlier MULTI1.MIB for all other components 8. Technical Support ------------------------------- Any problems or questions should be directed to Multi-Tech Technical Support at (612) 785-3500 or (800) 328-9717. Please send any suggestions or possible enhancements to: Multi-Tech Systems, Inc., 2205 Woodale Drive, Mounds View, Minnesota 55112, c/o "R&D -MultiModemManager" Internet Address http://www.multitech.com FTP Site ftp://ftp.multitech.com Fax us at (612) 785-9874. --------------------------------------------------------------- Version 6.00 March 25, 1997 --------------------------------------------------------------- Contents: ------------- 1. Introduction 2. New Features 3. Current Limitations 4. Problems Fixed 5. Additional Files on the Installation disks 6. Current Firmware Versions 7. Current MIB Versions 8. Technical Support 1. Introduction -------------------- This is a "support for new hardware" and a "remove the need for NEWT" release. In this case the new hardware is the Multi-Tech CommPlete Rack (CC9600). We now support SNMP natively (using a Winsock compliant TCP/IP stack) in the Manager and no longer need the services of Newt from NetManage. This also means that the MultiModemManager can now run on Windows NT (as a 16-bit application) and on Windows 95 built-in TCP/IP. If you are running Windows 3.1, you will need software that provides a TCP/IP stack, such as NEWT, Trumpet, etc. 2. New Features ----------------------- >>> Support for the CommPlete Rack CC9600 rack <<< The Manager now supports the new rack by adding a new rack display. >>> Native support for SNMP<<< Since we natively support SNMP, we now handle issues that Newt used to handle (such as Trap Administration). When using our native SNMP support, there is a new sub-menu under the Setup | SNMP menu called Default Trap IP. This allows you to set where traps are sent to by default. Also we now dynamically support traps to multiple supervisors (as on the MR4800E controller). When an Supervisor does a login to an Agent, then they are dynamically added to a list of IP's where Traps are sent. The Supervisor "logs in" upon software startup or when the IP of an agent is added to the list of managed agents in the Rack Group Window. When we start up we try to load SNMP.DLL (this is Newt's SNMP support library). If we can load it, then we run with Newt, if not we try to load MMMSNMP.DLL (our native SNMP support library). To run without Newt, either take the NetManage directory out of your search path or rename SNMP.DLL to SNMP.SAV (or some other name). Note that you have the re-boot your machine before these changes will take effect. For more information on removing NEWT, read NEWT95.DOC available at our FTP site (ftp://ftp.multitech.com). >>> Controller flashing is now available <<< On the 1.00 version of the MR9600 firmware and the 3.00 version of the MR4800E firmware, both controller and modem flash updating is now supported. It is however only supported through the telnet command line. Refer to the controller documentation and/or readme command to see how this works. 3. Current Limitations ------------------------------ Support for the CommPlete rack is kind of thin right now. We only show and allow you to select modems. The T1 and RAS card is only supported via Telnet on the MR9600 controller. We will have more complete support in the next release. When flashing modems, try to isolate them to a rack with little or no traffic. When the amount of traffic on a rack is high, the probability of time-out errors when flashing modems increases. 4. Problems fixed: ------------------------ Fixed a problem where the Manager could not handle security (*.DB) files larger than 65k. Fixed a problem where if no short name was entered for an IP Site, the IP would either not turn green or the name would get messed up. 5. Additional files on the Installation Disks -------------------------------------------------------- The files listed here are files that provide additional information, or services other than the manager software. The files not described are required for installation, or are one of the four manager components. etherup.txt Provides information on flash updating of the MR4800E ethernet controller. update.txt Information on upgrading modems with old boot code and firmware after which the manager software can update firmware. snmp.txt Information on installing Newt, SNMP, and the MultiModemManager MIB description. isp.txt Information on setting up a dial in service flash.exe A self-extracting zip file that creates files necessary for flash updating modems with old boot code, and the MR4800E Ethernet controller. It is described in update.txt and by the flashpro.txt file in the self-extracting zip. mr4800.hxc MR4800 Controller firmware Version 4.0 required to flash update MT2834MR6 Modems. Configuration File Templates In the installation directory, several configuration file templates can be found. These files can be used as a basis for setting up modem configuration depending on the application and modem type. These files are simple ASCII text files that may be read by an editor, or by the Configuration Manager. If you are using the MultiModemManager with the Multi-Tech Remote Node Gateway or the Multi-Tech Fax Server, we recommend letting the product configure the modems instead of the MultiModemManager. default.cfg If no config file is attached to the modem via MultiModemManager Modem Inventory, this file is sent. 1432MR.cfg This is the default config file for 1432MR modems ISP.cfg These are example settings to be used for a dial in service for example an Internet Service Provider. 6. Current Firmware Versions --------------------------------------- Current firmware for modems, and the MR4800E controller can be found on the Multi-Tech FTP site ftp://ftp.multitech.com Controller MR4800 All Revs 4.00 MR4800E All Revs 3.00 CC9600 All Revs 1.00 Modems MT1432MR Rev D 8.08D MT1432MR Rev F 2.11B MT2834MR All Revs 1.13D MT2834MR-R All Revs 3.13E MT2834MR6 All Revs 6.02 HD3334MR8 All Revs 6.03 7. Current MIB Versions --------------------------------- MR4800E.MIB for MR4800E 1.02C and earlier MULTI1.MIB for all other components 8. Technical Support ------------------------------- Any problems or questions should be directed to Multi-Tech Technical Support at (612) 785-3500 or (800) 328-9717. Please send any suggestions or possible enhancements to: Multi-Tech Systems, Inc., 2205 Woodale Drive, Mounds View, Minnesota 55112, c/o "R&D -MultiModemManager" Internet Address http://www.multitech.com FTP Site ftp://ftp.multitech.com Fax us at (612) 785-9874. --------------------------------------------------------------- Version 5.01 January 17, 1997 --------------------------------------------------------------- 1. Introduction -------------------- This is a maintenance release of the MultiModemManager Software. The main reason for this release is to provide support for the new MT2834MR6 modem card. The following sections describe the latest features, bug fixes, current limitations, and modem firmware levels as of the release date. 2. New Features ----------------------- >>>Support for the MT2834MR6 modem card<<< All of the Manager displays have been updated to handle the 6 modem card. >>>Sizable Windows in the Statistical Analyzer<<< The main window in the Statistical Analyzer is now fully sizable. >>>Modified Graphic reports in the Statistical Analyzer<<< The Connect and Disconnect Graphs have been modified to improve readability. Fields that would be represented by 0 items will not be displayed. Some of the more common fields are still displayed regardless of the number of items represented. 3. Problems fixed: ----------------------- When Installing 5.0 over an earlier version of the manager (4.3 or earlier), the 4.3 files are not properly converted to the 5.0 version. This requires the user to re-enter modem Inventory and config file assignments. The Version 5.0 supervisor was unable to recognize a 4.4 Agent. The default config file templates V32.CFG and V34.CFG have been removed. The default config file template 1432MR.CFG is been added as a template for 1432MR modems. 4. Current Limitations ------------------------------ Flashing modems via the MR4800E is not available. It will be made available in a later release of the Manager Software, and MR4800E firmware. When flashing modems, try to isolate them to a rack with little or no traffic. When the amount of traffic on a rack is high, the probability of time-out errors when flashing modems increases. 5. Additional files on the Installation Disks -------------------------------------------------------- The files listed here are files that provide additional information, or services other than the manager software. The files not described are required for installation, or are one of the four manager components. etherup.txt Provides information on flash updating of the MR4800E ethernet controller. update.txt Information on upgrading modems with old boot code and firmware after which the manager software can update firmware. snmp.txt Information on installing Newt, SNMP, and the MultiModemManager MIB description. isp.txt Information on setting up a dial in service flash.exe A self-extracting zip file that creates files necessary for flash updating modems with old boot code, and the MR4800E Ethernet controller. It is described in update.txt and by the flashpro.txt file in the self-extracting zip. mr4800.hxc MR4800 Controller firmware Version 4.0 required to flash update MT2834MR6 Modems. Configuration File Templates In the installation directory, several configuration file templates can be found. These files can be used as a basis for setting up modem configuration depending on the application and modem type. These files are simple ASCII text files that may be read by an editor, or by the Configuration Manager. If you are using the MultiModemManager with the Multi-Tech Remote Node Gateway or the Multi-Tech Fax Server, we recommend letting the product configure the modems instead of the MultiModemManager. default.cfg If no config file is attached to the modem via MultiModemManager Modem Inventory, this file is sent. 1432MR.cfg This is the default config file for 1432MR modems ISP.cfg These are example settings to be used for a dial in service for example an Internet Service Provider. 6. Current Firmware Versions --------------------------------------- Current firmware for modems, and the MR4800E controller can be found on the Multi-Tech FTP site ftp://ftp.multitech.com Controller MR4800 All Revs 4.00 MR4800E All Revs 2.01 Modems MT1432MR Rev D 8.08D MT1432MR Rev F 2.11B MT2834MR All Revs 1.13D MT2834MR6 All Revs 6.01A 7. Current MIB Versions --------------------------------- MR4800E.MIB for MR4800E 1.02C and earlier MULTI1.MIB for MR4800E 2.0 and Manager 5.0 8. Technical Support ------------------------------- Any problems or questions should be directed to Multi-Tech Technical Support at (612) 785-3500 or (800) 328-9717. Please send any suggestions or possible enhancements to: Multi-Tech Systems, Inc., 2205 Woodale Drive, Mounds View, Minnesota 55112, c/o "R&D -MultiModemManager" Internet Address http://www.multitech.com FTP Site ftp://ftp.multitech.com Fax us at (612) 785-9874. --------------------------------------------------------------- Version 5.0 January 6, 1996 --------------------------------------------------------------- 1. Introduction -------------------- This is a feature release of the MultiModemManager Software. The main reason for this release is to provide support for the new MT2834MR6 modem card. The following sections describe the latest features, bug fixes, current limitations, and modem firmware levels as of the release date. 2. New Features ----------------------- >>>Support for the MT2834MR6 modem card<<< All of the Manager displays have been updated to handle the 6 modem card. >>>Sizable Windows in the Statistical Analyzer<<< The main window in the Statistical Analyzer is now fully sizable. >>>Modified Graphic reports in the Statistical Analyzer<<< The Connect and Disconnect Graphs have been modified to improve readability. Fields that would be represented by 0 items will not be displayed. Some of the more common fields are still displayed regardless of the number of items represented. 3. Problems fixed: ----------------------- 4. Current Limitations ------------------------------ Flashing modems via the MR4800E is not available. It will be made available in a later release of the Manager Software, and MR4800E firmware. When flashing modems, try to isolate them to a rack with little or no traffic. When the amount of traffic on a rack is high, the probability of time-out errors when flashing modems increases. 5. Additional files on the Installation Disks -------------------------------------------------------- The files listed here are files that provide additional information, or services other than the manager software. The files not described are required for installation, or are one of the four manager components. etherup.txt Provides information on flash updating of the MR4800E ethernet controller. update.txt Information on upgrading modems with old boot code and firmware after which the manager software can update firmware. snmp.txt Information on installing Newt, SNMP, and the MultiModemManager MIB description. isp.txt Information on setting up a dial in service flash.exe A self-extracting zip file that creates files necessary for flash updating modems with old boot code, and the MR4800E Ethernet controller. It is described in update.txt and by the flashpro.txt file in the self-extracting zip. mr4800.hxc MR4800 Controller firmware Version 4.0 required to flash update MT2834MR6 Modems. mreboot.hex MR4800E Ethernet controller boot code Version 1.17 mr4800e.hex MR4800E Ethernet controller firmware Version 2.00 Configuration File Templates In the installation directory, several configuration file templates can be found. These files can be used as a basis for setting up modem configuration depending on the application and modem type. These files are simple ASCII text files that may be read by an editor, or by the Configuration Manager. If you are using the MultiModemManager with the Multi-Tech Remote Node Gateway or the Multi-Tech Fax Server, we recommend letting the product configure the modems instead of the MultiModemManager. default.cfg If no config file is attached to the modem via MultiModemManager Modem Inventory, this file is sent. V32.cfg This is the default config file for V32 modems or to simulate V32 modems. V34.cfg This is the default config file for V34 modems. ISP.cfg These are example settings to be used for a dial in service for example an Internet Service Provider. 6. Current Firmware Versions --------------------------------------- Current firmware for modems, and the MR4800E controller can be found on the Multi-Tech FTP site ftp://ftp.multitech.com Controller MR4800 All Revs 4.00 MR4800E All Revs 2.00 Modems MT1432MR Rev D 8.08D MT1432MR Rev F 2.11B MT2834MR All Revs 1.13D MT2834MR6 All Revs 6.01A 7. Current MIB Versions --------------------------------- MR4800E.MIB for MR4800E 1.02C and earlier MULTI1.MIB for MR4800E 2.0 and Manager 5.0 8. Technical Support ------------------------------- Any problems or questions should be directed to Multi-Tech Technical Support at (612) 785-3500 or (800) 328-9717. Please send any suggestions or possible enhancements to: Multi-Tech Systems, Inc., 2205 Woodale Drive, Mounds View, Minnesota 55112, c/o "R&D -MultiModemManager" Internet Address http://www.multitech.com FTP Site ftp://ftp.multitech.com Fax us at (612) 785-9874. --------------------------------------------------------------- Version 4.97 Beta November 18, 1996 (restricted release) --------------------------------------------------------------- 1. Introduction -------------------- This is a Beta Release of the MultiModemManager 5.0 Software. The main reason for this release is to provide support for the new 6 modem cards. The following sections describe the latest features, bug fixes, current limitations, and modem firmware levels as of the release date. 2. New Features ----------------------- >>>Support for the MT2834MR6 modem card<<< All of the Manager displays have been updated to handle the 6 modem card. >>>Sizable Windows in the Statistical Analyzer<<< The main window in the Statistical Analyzer is now fully sizable. >>>Modified Graphic reports in the Statistical Analyzer<<< The Connect and Disconnect Graphs have been modified to improve readability. Fields that would be represented by 0 items will not be displayed. Some of the more common fields are still displayed regardless of the number of items represented. 3. Problems fixed: ----------------------- 4.. Current Limitations ------------------------------ Flashing modems should not be attempted with this Beta version of the software. Flash support for the MT2834MR6 modems is not yet available. It will be made available in a later Beta version. 5. For more information -------------------------------- On flashing modems see Update.txt On installing Newt, SNMP, and the MultiModemManager MIB description See SNMP.TXT On setting up an ISP see ISP.TXT 6. Current Firmware Versions --------------------------------------- Controller MR4800 All Revs 3.01.02 MR4800E All Revs 1.02C Modems MT1432MR Rev D 8.08D MT1432MR Rev F 2.11B MT2834MR All Revs 1.13D MT2834MR6 All Revs 6.00_4 --------------------------------------------------------------- Version 4.4 December 3, 1996 --------------------------------------------------------------- 1. Introduction -------------------- This is a Maintenance update of the MultiModemManager Software. The following sections describe the latest features, bug fixes, current limitations, and modem firmware levels as of the release date. 2. New Features ----------------------- >>>Sizable Windows in the Statistical Analyzer<<< The main window in the Statistical Analyzer is now fully sizable. >>>Modified Graphic reports in the Statistical Analyzer<<< The Connect and Disconnect Graphs have been modified to improve readability. Fields that would be represented by 0 items will not be displayed. Some of the more common fields are still displayed regardless of the number of items represented. 3. Problems fixed: ----------------------- When a modem status graph is displayed, the bar graph sometimes displayed zero for a bar value, when it should have displayed the max value. The HP OpenView compiler could not compile the multi1.mib. A problem was found in the way the compiler process line comments. the comments were changed to allow HP OpenView to compile the mib. When the Send Config To Modems dialog box is used to Config a number of modems, the Store command (&W) was sometimes sent when the Store in Memory check box was not checked. When a MR4800E is reset, the Supervisor can receive SNMP errors. The Supervisor will now detect when a MR4800E is reset, and close any windows displaying information about the MR4800E In the Statistical Analyzer, garbage can be displayed for Caller ID names when there is no caller ID information available. This has been changed to display CID - Private for Blocked numbers, and CID - Not Available when the information can not be displayed. 4.. Current Limitations ------------------------------ 5. For more information -------------------------------- On flashing modems: See Update.txt On installing Newt, SNMP, and the MultiModemManager MIB description: See SNMP.TXT On setting up an ISP: See ISP.TXT 6. Current Firmware Versions --------------------------------------- Controller MR4800 All Revs 3.00 MR4800E All Revs 1.02C Modems MT1432MR Rev D 8.08D MT1432MR Rev F 2.11B MT2834MR All Revs 1.13D --------------------------------------------------------------- Version 4.3A August 27, 1996 --------------------------------------------------------------- This is a Maintenance update of the MultiModemManager Software. The following fix was implemented in this MMM version. 1. Modem Status Graph's ---------------------------------- If a received value is greater than the lower graph value, then completely fill the bar for that signal. The bar graph completely blanked out in the previous version bar graph display's. --------------------------------------------------------------- Version 4.3 August 2, 1996 --------------------------------------------------------------- 1. Introduction -------------------- This is a Maintenance update of the MultiModemManager Software. The following sections describe the latest features, bug fixes, current limitations, and modem firmware levels as of the release date. 2. New Features ----------------------- >>>UnderTime Call fault alarm added<<< Can now do actions on calls shorter than 'X' amount of seconds. >>>Supervisor Modem Status Graphs<<< Supervisor now able to display the graph information for a remote agent, (Signal strength graph, Noise strength graph, Signal to noise ratio graph). This does not, however, include the ethernet controller. >>>Updating Firmware Via the Backplane (28.8k Modems Only)<<< This feature will allow the user to update modem and controller firmware using the MultiModemManager Software. This requires controller version 3.0, firmware version 1.10C or greater, and boot code version 20.0 (AT*FI returns the boot code version). For more information see Update.txt. >>>New Connection Speeds<<< Two new connection speeds were added, 31.2k and 33.6k. When a connection of either of these two speeds is made the 28.8k light will blink instead being continuously lit. The lights will blink faster for a 33.6k connection. >>>Unlimited Number of Groups in Both Rack and Modem Groups<<< A supervisor is now able to have an unlimited number of groups in both rack and modem groups with different IP's. >>>More Information in the Rack Grid and Modem Group Displays<<< The ability to list the modem group name, the modem status (connect speed, type, and class), modem connect time, modem configuration, and User ID using both the rack grid display and the rack/modem group display. >>>Config On Power Up Options Changed<<< The config on power up options have been changed to Config on Rack Power Up AND Config On Modem Reset. Config On Rack Power Up will cause each modem of the rack to be configed whenever the software "discovers" a new rack. This happens on software startup, when you turn on a rack, and when a rack controller is reset. Config on Modem Reset will cause the modem to be configed whenever the modem is reset, either by turning on the rack or resetting the modem. >>>Statistical Analyzer - Connection By Modem Report<<< Two new items were added to this report; disconnect reason and transmit/receive levels. 3. Problems fixed: ----------------------- Only a certain number of cascaded error or fault alarm messages can appear on the system at one time. No longer locks up the system if too many appear. Call Back "Host Select" if only 1 modem (Both) in its own group wouldn't call back has been repaired. The feature of one login per user repaired. Connect messages in the call traffic window(s) now appear properly, (at connect speed, type and class) Supervisor now has the added fault displays for a Modem Card Installed/Removed, Power Supply Installed(upper/lower)/Removed(upper/lower) of remote agents. Improved the Modem status window limitations for the supervisor, now able to set/clear OOS for a modem while the Modem Status window is visible. Several SNMP problems cleared up. Configuring or Resetting a whole rack from the supervisor no longer causes SNMP error messages. Copying many modems between remote groups from the supervisor no longer causes lockup. The Modem Inventory scrolling lock up problem while viewing remote agents in the Modem/Rack group window was also repaired. Disallowed the Control Menu actions to "Not Present" modems or racks. Corrected the ability to enter in same group name with different case types. All modems within rack now selected with just rack highlighted. Filtering by modems in the stat analyzer repaired. User ID now recorded in stats for security callback. When one user per login is checked, a pass-through user could log in more than once. Disconnect fault alarms only worked with a threshold of zero (0). 4.. Current Limitations ------------------------------ The update via the backplane will work only for 28.8k modems. It also is not available to an SNMP manager managing remote modems. 5. Current Firmware Versions --------------------------------------- Controller MR4800 All Revs 3.00 MR4800E All Revs 1.01 Modems MT1432MR Rev D 8.08D MT1432MR Rev F 2.11B MT2834MR All Revs 1.12 ----------------------------------------------------------------- Version 4.1 Dec. 11 1995 ----------------------------------------------------------------- 1. Introduction -------------------- This is a Maintenance update of the MultiModemManager Software. The following sections describe the latest features, bug fixes, current limitations, and modem firmware levels as of the release date. 2. New Features ----------------------- >>>New Modem Status Window ( 2834 modems Only )<<< A new modem status window has been created for 28.8k modems. This window allows the user to switch between four different displays: diagnostic information, signal strength graph, signal to noise ratio graph, and a noise strength graph. The graphs are available only with V.34 connections, and firmware version greater than 110C. In firmware version 110C, send the config command %DP1 to the modem either through the Online Window, or as a User Defined command in the Configuration Manager. The %DP1 command will cause the data pump to collect extra data during handshake (Connect and re-train) that is used for the signal and noise graphs. Signal strength graph: shows the relative signal strength ( in dBm ) of the signal you are receiving versus frequency for a given frequency range ( in Hz). Noise strength graph: shows the relative noise strength ( in dBm ) of the signal you are receiving versus frequency for a given frequency range ( in Hz ). Signal to noise ratio graph: shows the relative ratio of signal strength to noise strength of the signal you are receiving versus frequency for a given frequency range ( in Hz ). >>>Import ( Security Database ) <<< This feature allows the user to import security database records from a text file. This feature could be used to edit individual records or an entire database using a text editor. This feature could also be used to import an externally defined database. Import will replace existing records after user confirmation. Undefined fields will be set to default values. How to use Import: I. Security Database Editor -- What To Do 1. A database must be opened before you may import records. Open an existing database or select a New database. 2. From the File menu select Import 3. Select the .txt file to open. Uncheck the box next to header included if the file to import does not contain a header line. 4. If a header is not included with the text file select the fields from the Available Fields list which the text file will import. Place them in the proper order in the Active Fields list. 5. The records will now be imported. Note: If you import a record with a user id that already exists, it will ask if you wish to replace the record. If you replace the current record it will replace the entire record, NOT just the fields you are importing. II. Text file format ( *.txt ) 1. Header Line ( Optional ) A header line must be the first line of the text file if a header line is being used. If a header line is not being used, the fields must be defined upon importing to the database editor. The header line is made up of keywords, which define the fields being imported. The key words are user name, user id, password, password flag, active user, callback type, callback number, start date, end date, valid time mon, valid time tue, valid time wed, valid time thurs, valid time fri, valid time sat, valid time sun, password exp, exp interval, pswd exp date, all groups, groups. The user id field is required ( it used to sort records in the database ). Any combination of these fields is allowed and they may be used in any order, but they must be separated by a comma. 2. Record Entries The record entries must follow the format of the header line, if one is used. If a header line is not used the type and order of the fields will be required input to import the database. Each record must contain the same number of fields and the fields in the same order. Each field must be separated by a comma. If the field contains a comma it must be enclosed in quotation marks ( " ). If fields are not defined they are set to default values. The record must have a carriage return at the end of the line. The format of each field is discussed in the following table: Keyword Format / Valid Input ------------ ---------------------------- user name User name up to 30 characters long user id User id up to 16 characters long password User password up to 16 characters long password flag TRUE if password is needed, FALSE otherwise active user TRUE or ACTIVE if the user is active, FALSE or INACTIVE otherwise callback type PASS THROUGH, FIXED, or VARIABLE callback number callback phone number up to 30 characters long start date MM/DD/YY ( month/day/year ) end date MM/DD/YY ( month/day/year ) valid time mon M???????????????????????? valid time tue T???????????????????????? valid time wed W???????????????????????? valid time thurs T???????????????????????? valid time fri F???????????????????????? valid time sat S???????????????????????? valid time sun N???????????????????????? ? = 0 if user disabled for that hour starting at 0:00 and ending at 23:00 1 if user enabled for that hour password exp TRUE if password expiration is on FALSE otherwise exp interval expiration interval in days pswd exp date MM/DD/YY ( month/day/year ) all groups TRUE or ALL if member of all groups FALSE or SELECTED otherwise groups names of the groups the user is a member of the >>>Export ( Security Database )<<< This function allows a user to export security database records to a text file. The user selects the records to be exported, the file the records are exported to, and the fields of the database which are exported. How to use Export: I. Security Database Editor-- What To Do 1. Select the records you wish to export. 2. From the File Menu select Export 3. Select the fields from the Available list and place in the Active list the fields of the records you want to export in the order you want them in the .txt file. 4. Select the name of file you want to export to. If you want a header included make sure the check box for Header Included is checked. 5. The records will now be exported. >>>User Record Templates (Security Database editor)<<< This feature allows an administrator to create default templates for entering users in an open Data base file. You can create up to 10 different templates. For example a template for a Normal User can have a limitation on account date, access times, have password expiration on, and membership in a limited number of groups. A template for an administrator might have no limitation on account date, be a member of all groups, and unlimited access times. I. Add or Edit a Template -- What To Do 1. Select the menu Edit | Set Template. This will bring up a list box where existing templates may be edited and new templates added. 2. Select the add button. After a name for the new template is given, a Security Database Record is displayed where defaults for the User Record template can be added or edited. You may set all the fields except User Name, User ID, Password, and CallBack Number. Blank items will be set to default values. II. Use a Template to add a new User 1. Open a Security database file. 2. Select the Menu Record | ADD | ... and the submenu of the Template you wish to use. This brings up a Security Database record with the template defaults filled in. Any of the fields of the record may be updated or edited and saved as a new user. >>>Find text locator (Security Database editor)<<< Find may be used to find a string in any of the database records of the open Security Database file. Find Next searches down the file. Find Previous Searches Up. If a string is not found, or the Top or Bottom of the file is reached, the message String Not Found is printed. I. To use Find 1. Click the Find toolbar button. This will bring up a dialog where the text to search for may be entered, as well as selecting case sensitive, or continuing the search Up or Down. 2. Click the Find Next button to search down the file. 3. Click the Find Previous button to search Up the file. 3. Problems fixed: ----------------------- In the Manager, the pager feature could use up local memory causing the error "No Local Heap available". This problem occurred using text pagers, but not with the simple digital pager option. Some third party MIB compilers could not compile the Manager source MIB definitions (multi1.mib and multi2.mib). multi1.mib has been changed so it can be compiled by any third party SNMP Manager. This change eliminates the need for multi2.mib. In the Statistical Analyzer, the ASCII Log Dump reports for Connection Statistics reported the Blocks Transmitted and Blocks Received incorrectly for 28.8 modems. 4.. Current Limitations ------------------------------ The new modem status graph information is not available to an SNMP manager managing remote modems. Modem Usage statistical gathering has been activated by default. Modem usage statistics are gathered for use by the Statistical Analyzer whether the modem usage graph is active or not. This information may be displayed in real time by selecting the Modem Usage Graph in the Multi-Modem Manager or by selecting Modem usage reports in the Statistical Analyzer. If for any reason this information is not desired, modem usage may be disabled by editing the MR4800.INI file. In the MR4800.INI file add the line NoModemUsage=1 under [MrackManager] to enable Modem Usage processing. When the Modem Usage Graph is disabled in the Manager, the Statistical Analyzer Modem Usage reports will not be generated. Selecting a polling interval that is short (2-4 seconds) on a supervisor with high call traffic, can cause the software to stop responding to the system. The polling interval is used to determine when a SNMP request should time-out. With a shorter polling interval more requests will time out. We recommend starting with a polling interval of 10 seconds. 5. Current Firmware Versions --------------------------------------- Controller MR4800 All Revs 2.04 Modems MT1432MR Rev D 8.08D MT1432MR Rev F 2.10A MT2834MR All Revs 1.10C ----------------------------------------------------------------- Version 4.0 Aug. 30 1995 ----------------------------------------------------------------- 1. Introduction -------------------- This is a feature release of the MultiModemManager software with SNMP. 2. New Features ----------------------- Multi-Document Interface (MDI) The new user interface makes the MultiModemManager software an MDI application. This allows for the opening of multiple rack windows, modem status windows, etc. and makes all windows resizable. Unmanaged Modem Configuration This feature allows the MultiModemManager to configure and get current version information for any standalone Multi-Tech modem that can be called into. SNMP Management via the MultiModemManager This feature allows a MultiModemManager Supervisor node to remotely manage other MultiModemManager Agent nodes residing on the same TCP/IP network. Expanded SNMP MIB for Third Party SNMP Management Several new tables and variables have been added to the Multi-Tech source MIB definition to allow for more complete SNMP management by third party SNMP management software packages. Configuration Files In the installation directory several configuration file templates can be found. These files can be used as a basis for setting up modem configuration depending on the application and modem type. These files are simple ASCII text files that may be read by an editor, or by the Configuration Manager. default.cfg If no config file is attached to the modem via MultiModemManager Modem Inventory, this file is sent. V32.cfg This is the default config file for V32 modems or to simulate V32 modems. V34.cfg This is the default config file for V34 modems. ISP.cfg These are example settings to be used for a dial in service for example an Internet Service Provider. If you are using the MultiModemManager with the following Multi-Tech products we recommend letting the product configure the modems instead of the MultiModemManager. Multi-Tech Remote Node Gateway; Multi-Tech Fax Server; 3. Current Limitations ------------------------------ - You can only have one Supervisor per Agent but a Supervisor can have many Agents. - Statistics are only available at an Agent node. - Configuration and Security Database files can only be edited at the site that they reside. - There is no mechanism (ie. FTP) to transfer configuration or security database files. - All times are reported as local times (ie. if you have an Agent on the east coast and the Supervisor is on the west coast, all events on the Agent will be reported with Eastern Standard Time). - Agent Callback Queue cannot be viewed on the Supervisor node. - Agent Modem Usage cannot be viewed on the Supervisor node. 4. Known Bugs --------------------- Some sites were reporting a problem that causes a Stack Overflow in the Manager software over time. This seems to be related to processing for the Modem Usage Graph. For this release the Modem Usage Graph has been disabled by default. The Modem Usage Graph may be enabled by INI setting. In the MR4800.INI file add the line NoModemUsage=0 under [MrackManager] to enable Modem Usage processing. When the Modem Usage Graph is disabled in the Manager, the Statistical Analyzer Modem Usage reports will not be generated. 5. Current Firmware Versions --------------------------------------- Controller MR4800 All Revs 2.04 Modems MT1432MR Rev D 8.08D MT1432MR Rev F 2.10 MT2834MR All Revs 1.10 **************************************************************** ----------------------------------------------------------------- Version 3.3 June. 19 1995 ---------------------------------------------------------------- 1. This is a Maintenance update of the MultiModemManager Software. It is meant to run with controller (MR4800) firmware 2.04 and modem (MT1432MR) firmware 8.06 or above. 2. New Features: One Login per User ID An option has been added to the MultiModemManager password security that will allow an administrator to allow 1 active session per User ID. If this option is checked, when a User attempts to make a second active session, he/she will fail with an invalid password attempt. The Administrator will see a Fault/Status indicating an attempt was made to login a second time. The default is unlimited active logins for each User ID. Case Sensitive Login An option has been added to the security defaults that allows an administrator to choose whether User ID/Passwords are case sensitive. The default is case sensitive User ID/Passwords. 3. Current Limitations: Some sites were reporting a problem that causes a Stack Overflow in the Manager software over time. This seems to be related to processing for the Modem Usage Graph. For this release the Modem Usage Graph has been disabled by default. The Modem Usage Graph may be enabled by INI setting. In the MR4800.INI file add the following line to enable Modem Usage Processing under [MrackManager] NoModemUsage=0. When the Modem Usage Graph is disabled in the Manager, the Statistical Analyzer Modem Usage reports will not be generated. To turn ON Modem Usage reporting for the MANAGER and Statistical Analyzer: ==>Mr4800.ini file [MrackManager] NoModemUsage=0 4. Problems Fixed: The pager phone number string has been increased from 16 to 48 characters The Overtime call Fault alarm has been changed to trigger the Overtime Call Fault, 1 time per Overtime period. For example if the Overtime Call threshold is 10 minutes, and the caller is allowed to continue, Faults will be registered for the call in 10 minute intervals. When the manager is processing Security calls, and the Administrator has an active Security file open, sharing violations could occur. The Manager will now have read access to the Security files. If a Caller attempts to change his/her password and the file is in use, the caller will be given an error message indicating the password change was ignored. 5. Current Firmware Versions: Controller MR4800 All Revs 2.04 Modems MT1432MR Rev D 8.08 MT1432MR Rev F 2.08 MT2834MR All Revs 1.08 ---------------------------------------------------------------- Version 3.2 Dec. 2 1994 ----------------------------------------------------------------- 1. This is a Maintenance update of the MultiModemManager Software. It is meant to run with controller (MR4800) firmware 2.04 and modem (MT1432MR) firmware 8.06 or above. 2. New Features: MT2834 Support Support has been added for the MT2834 modem card. This included updating the Rack Display window to reflect at a glance what type of modem card is installed in each slot of the rack. The Modem Status Window has been updated to show the new LEDs available on the MT2834 modem card. Alternate Event Log Directory The event log may be directed to a user delectable directory. In the system defaults dialog, Enter the path name of a directory where event files are to be written. The path name must be an absolute path name, and the directory must already exist. If the message "Error creating event file" is received, the path may be invalid, the directory may not exist, the drive may be full, or you don't have access rights to the directory. Password Expiration. A new security feature allows an administrator to force callers to change their password after a set period. When a caller's password expires, he/she is given a message that informs them to change their password. In the Security Defaults dialog Check the Allow Password Change box to allow users to change their password. The format for changing a password is to enter at the password prompt "old-password/new-password/new-password" In the Security Messages dialog the messages: Password Expiration Message, New Password Prompt, and Confirm Password Prompt messages may be customized by the system administrator. Using the Security Database Editor, in the database entry for the user, check the Enable Password Expiration box to force the caller to change his/her password when the Password Expiration Date is reached. Each Security record may have a separate expiration date and interval. Statistical Analyzer Performance The first of a series of performance improvements to the Statistical Analyzer reduces the processing time for events by as much as 50%. Modem Usage Report In the Statistical Analyzer, A Modem Usage Graph and Modem Usage report has been added. Check the Modem Usage Report Box in the Analysis window to generate these reports. The Modem Usage Graph is the counterpart of the live Modem Usage Graph in the MultiModemManager. It shows the percentage of modems in Answer, Originate, OOS, Faulty, and Idle for the selected period. The Modem Usage Text Report shows the same usage percentages for the selected period divided in even time increments. A Summery is displayed at the end of the report that shows Peak Usage, Average Usage, and Low Usage for the selected period. 3. Problems fixed: During processing in the Statistical Analyzer, the error "No More Local heap available" may be received, while processing events over a span of more than one day. In the Statistical Analyzer, the message "Nothing Output" can be incorrectly received when a Modem Usage report is written. ---------------------------------------------------------------- Version 3.00 Sep. 26 1994 ---------------------------------------------------------------- 1. This is a Feature Release of the MultiModemManager Software with SNMP. It is meant to run with controller (MR4800) firmware 2.04 and modem MT1432MR) firmware 8.06 (Rev D.) and 2.07 (Rev F.) or above. 2. New Features: Remote SNMP Management If you chose to remotely manage your racks, you may do so using the MultiModemManager's SNMP interface on a LAN or WAN network utilizing the TCP/IP communications protocol. This is a separately priced feature of the MultiModemManager. For more information concerning this topic please contact Multi-Tech or your sales representative. Modem Grouping This feature allows much greater control over the modems in a management system. Modem Grouping allows a system administrator to divide modems by function in the same rack, or across rack boundaries. All modem control functions (Configuration, Modem Inventory, Reset, Set/Clear OOS, Callback security, ...) Can now be controlled at the Modem Group level . Modem Control at the rack level is still available. For more information concerning this topic refer to the MultiModemManager On-line Help. Host Select Security This feature makes use of Modem Grouping, by allowing the caller to select which modem group (or Host) will perform the callback. After the caller passes UserID/Password security, he/she is allowed to Enter a choice of which Modem Group will perform the Security callback. The default message can be modified by the system administrator. This feature requires modem firmware greater than 2.07a or 8.07a Fault Alarms Several faults have been added to the existing list of fault alarms along with a new Fault Action that allows a Fault Alarm to dial a pager. Another new Fault will indicate when system disk space falls below a threshold. Dial a Pager A new Fault Action can be used to dial a digital or text pager from a COM port when a fault threshold has been reached. This will allow a system administrator to be notified of possible problems when they occur. The MultiModemManager currently supports Alpha Pager and WinBeep software for text pagers. Modem Usage Graph This graph shows up to the minute modem activity for the previous 12 hour period including the percentage of modems that are OOS, Idle, Faulty, and Connected in Answer or Originate mode. The Modem Usage graph and a Text report, are also available in the Statistical analyzer. ASCII Delimited Dump File. A new dump format available in the Statistical Analyzer allows the ASCII Log to be output as lines of values separated by a delimiter (such as comma or space). Several database programs can import data in this format. Help Text Help text is now available, by selecting the menu item or clicking F1. Password Change A new security feature controlled by the system administrator, allows a user to change his/her password during a login attempt. The format is currentpassword/newpassword/newpassword entered at the password prompt. This feature requires a firmware level greater than 8.07a or 2.07a Caller ID Support The Call Traffic Window will display the phone number and name of an individual that dials in on a phone line that supports Caller ID. The call must not be answered before the 2nd ring to receive this information. This feature requires a modem hardware upgrade, Caller ID phone lines, and a firmware level greater than 8.07a or 2.07a The Caller ID firmware is inactive by default, and is activated via Modem AT command. AT*C0 (default) Turn off Caller ID Detection. AT*C1 Turn on Caller ID detection for the manager. AT*C2 Turn on Caller ID reporting on the serial port and detection by the manager. The position of the Fault/Status, Call Traffic, and Callback Queue window are saved upon exit. The available memory, free disk space and free disk percentage are displayed in the about dialog. 3. Problems fixed: When the manager is started automatically in the Windows start-up or in a batch file, the manager will sometimes not find the active racks. This is indicated by the Rack Group icon not turning green (it remains gray). A modem with Inbound Security does not hang-up the call after the threshold of Invalid UserID attempts is reached. ----------------------------------------------------------------- Version 2.03B May 23 1994 ---------------------------------------------------------------- 1. This is a Maintenance update of the MultiModemManager Software. It is meant to run with controller (MR4800) firmware 2.04 and modem (MT1432MR) firmware 8.06 or above. Information on the Statistical analyzer can be found in the file mrstats.txt on the release disk. 2. New Features: - An updated MultiModemManager document is available. It now contains information on the statistical analyzer. The document (revision E) may be obtained through Multi-Tech tech support. - Multiple database files may be searched by the manager for valid users. A dialog may be used to select *.db files from the available list of *.db files created by the Security database editor and located in the installation directory. mr4800.db is the default database file. - An administrator may now have the manager attempt a callback using the same Connection Class and Type used by the caller when the inbound connection was made. - The fault/status window, and call traffic window now have a delete all button that will clear all items in the listbox. - Disconnect types other than NORMAL will now generate a fault. - The first of a series of features and fixes to the Fault Alarms. Fault Alarms may be triggered for Disconnect statuses other than NORMAL. A Fault may be triggered for a modem that receives a RING message, but does not answer the call (RING-NO-ANSWER). The meaning of the fault alarm ANSWER-NO-CONNECT has been clarified to be triggered when a modem answers but fails to negotiate a connection. - Fault threshold counts will now be cleared for a successful call. - A New dialing option "Blind Dial Prefix" may be clicked to have the manager dial a prefix without waiting for a dialtone. This feature is necessary when a modem does not recognize a PBX dial tone. - The Statistical Analyzer report viewer has been improved. A text search may be case insensitive. A line of the report may be double clicked to start or continue a text search from that point. Report text may be copied into the clipboard. Selected text may be printed from the viewer. - Several commands have been added to the master configuration list in the Configuration Manager. Registers S9, S18, S19, S36, S37. Commands $SP, &RF and B. The #Pn and Xn defaults were not consistent with the Factory defaults for these modems. The #Pn default was changed from #P2 to #P0. Xn was changed from X0 to X4. 3. Problems fixed: - If a modem's security type is BOTH, and the modem is the only available modem, a caller will now be called back using the same modem that answered the call. - Congested rack faults can be issued by the manager when the rack is not congested. Percentage values may be greater than 100%. - The Rack group window does not display 7 or more racks correctly. - The Inactivity Timer was not being set correctly. Now, the Inactivity is set by setting the S-register (S30) in the modem config file. - The Security database editor would allow a user id of 12 characters when only 10 are valid. - The Security Database file could become corrupted if a file was edited and implicitly saved by Opening another file. If the file is explicitly saved with the SAVE or CLOSE command, the file was not corrupted. ---------------------------------------------------------------- Version 2.03a 01-22-94 ---------------------------------------------------------------- 1. This is a Maintenance update of the MultiModemManager Software. It is meant to run with controller (MR4800) firmware 2.04 and modem (MT1432MR) firmware 8.06 or above. Information on the Statistical analyzer can be found in the file mrstats.txt on the release disk. 2. New Features: - Graphs will now show connection totals, and each legend total will show % of total. - The connection history report will only list completed calls. A future report will show Call events (i.e. busy calls, dial errors, etc.) 3. Problems fixed: - The Gateway User ID report does not list the Gateway User id on the report line. Now, the Gateway User id is attached to every connection made while the Gateway User id is in effect. - Generating a Connection Statistics report can result in a General Protection fault at 0x1C:0x301D. - Some Duration's in reports or the Call Traffic Window are printed incorrectly (i.e. 000-12345:22222:00 instead of 003:10:01:01). - LED values are incorrect for the Disconnect Statistics in the ASCII Log Dump. DTR and OOS are displayed incorrectly. - When in Operator mode if the manager is left unattended, unanswered message boxes can run windows out of display memory. A message box will be displayed if more than 10 message boxes remain unanswered. No further message boxes will be displayed until the unanswered message boxes are responded to. - When in Automatic mode an attempt to update the System Defaults is not saved to the mr4800.ini. The "Save the changes to File" dialog is never displayed. - Several message boxes that were not displayed in Automatic mode (for example the Modem Firmware Version request) will now be displayed in Automatic mode as well as Operator mode. ---------------------------------------------------------------- Version 2.03 10-06-92 ---------------------------------------------------------------- 1. This version of the MultiModemManager software is meant to run with controller (MR4800) firmware 2.04 and modem (MT1432MR) firmware 8.06 or above. 2. New Features: - Information on the Statistical analyzer can be found in the file mrstats.txt on the release disk. - Variable Callback Blacklisting: An administrator can make it an error to dial out to a specific phone number, or a class of phone numbers. A Blacklist dialog allows entering and editing of Black list phone numbers. The asterisk '*' is considered a "wild character". Any phone number that begins with the digits left of the * will be blacklisted. This allows an administrator to blacklist an entire area code. If the * is the first character of the phone number string, all variable callback numbers are blacklisted. - The Fault window has been re-designed as a scrollable dialog. It shows approximately the last 200 Faults and Statuses. A fault is listed with a red flag. To show a fault has been seen or acknowledged by an administrator the line can be selected and "confirmed". The flag icon changes from red to red/yellow to indicate confirmation. Statuses are listed as yellow flags. - The Connection window has been re-designed as a scrollable dialog. A history of the last 200 connections is maintained. An icon shows the state of the connection: dial (AT), ring (bell), connect (green phone off hook), and disconnect (yellow phone on hook). As information about the state of the connection is received by the manager it is filled in the dialog. User id, phone number dialed, connection duration, and starting time is some of the information available. - Event logging may be turned on/off by selecting it's button in the defaults dialog. - Connection Reports have been added to the Statistical Analyzer. Some of the reports available are Connection History; Fault/Status Reports; Connections sorted by User ID; and Connection Statistics reports. - An ASCII viewer has been added to the Statistical Analyzer that allows viewing and or printing of Connection reports, and the ASCII Log Dump. Simple text searching may also be done from the report viewer. - Send/Receive errors between the Manager software and the Controller are logged as faults and displayed when in operator mode. - On Rev F. 2.07 modem cards, the out of service switch can be detected by the manager software. - On Rev x.07 modem cards, the modem commands #US (User Start) and #UE (User End) have been implemented, to allow the manager to monitor modem usage for the Asynchronous Gateway. 3. Problems fixed: - In Version 2.02c starting the manager software with the config option Power on/reset would take an unusually time to config each of the modems. - Faults for Overtime calls can now be disabled by clearing the select box in the Fault Alarms dialog. - Several dialog boxes did not have the default pushbutton highlighted; did not have the default pushbutton highlighted; and did not have input focus set correctly. - The range of effective dates for a Security User ID to be active did not work correctly. - Several enhancements and fixes were made to the DBIII and ASCII Log Dump reports in the Statistical Analyzer. - When an active rack quit sending reports to the manager software, no indication was made. A message box will now report this state. ---------------------------------------------------------------- Version 2.02 09-08-92 ---------------------------------------------------------------- 1. This version of the MultiModemManager software is meant to run with controller (MR4800) firmware 2.04 and modem (MT1432MR) firmware 8.06 or above. 2. Problems fixed: - A fault will be generated when after three callback attempts have failed and a security callback could not be completed. - When deleting a rack from the active rack list, errors could occur when closing the related windows. - The modem status window routine was rewritten to resolve several problems that had been reported. - Toolbar buttons were incorrectly overwriting other child windows. The toolbar now is created so that child windows will be clipped and not overwritten. - When the full rack display is shown, the power switches on the rack will be correctly displayed as to their state (installed or not installable, powered on or not powered on). ---------------------------------------------------------------- Version 2.01 05-28-93 ---------------------------------------------------------------- 1. This version of the MultiModemManager software is meant to run with controller (MR4800) firmware 2.04 and modem (MT1432MR) firmware 8.06 or above. 2. Problems fixed: - Fixed local heap problem related to the updating of the status window toggle display. Also, modified buffer allocation during fault processing to use a correctly sized buffer. - Increased the stack size available. This was needed when multiple Modem Status windows were open. - Changed the Setup menu item "Messages..." to "Security...". - The Configuration Manager had several problems related to the reading of an already created configuration file (e.g. X4 would be read in as X0). The parsing routine used to read in configuration files was modified to better handle these conditions. ---------------------------------------------------------------- Version 2.00 ---------------------------------------------------------------- 1. This version of the MultiModemManager software is meant to run with controller (MR4800) firmware 2.04 and modem (MT1432MR) firmware 8.06 or above. 2. Additions: - Callback Security: Software controlled callback security allows the user the ability to set up a database of users which will be interrogated by the rack manager software for each call to a security protected modem. The advantage of having a centralized security database is that the security information can be easily maintained. Also, this removes the 30 user limit of the normal callback security available in our stand-alone modem. Note: You must have version 8.06 modem firmware in your MT1432MR's to be able to use the Callback Security feature. - Callback Queue: This allows the system administrator the ability to viewing pending callback events and delete entries from the callback queue. - Rack List: This allows the system administrator to view the current racks that are on-line with the Rack Manager application. You can also remove a rack from the rack list so that it will become inactive. This operation may need to be done if a rack is know to be down, but the Rack Manager application is still attempting to access it. - NEW Configuration Manager: Modify the method used in keeping track and entering configuration information to allow for user defined commands and smaller sets of configuration information. The NEW configuration manager allows the system administrator to enter only those commands which are different from the factory defaults for the modem. Configuration information is sent to the modem after performing an "AT&W1Z" which will return the modem to its original factory defaults. - IMPORTANT! NEW Configuration file format: A NEW configuration file format has been put into use with this revision of the MultiModemManager system. This new format is NOT compatible with the OLD configuration file format. While the file extension (.CFG) has remained the same, the content of the files has radically changed. The NEW configuration format is based on a simple ASCII file which is specifically organized to help in processing of Master List commands verses User-Defined commands. All of your previous configuration files have been moved to the OLDCFG sub-directory inside of your MultiModemManager installation directory. In order to make a smooth transition between the OLD and NEW configuration file formats, you should be aware of the following things: - The NEW configuration manager is best utilized by creating configuration files which reflect the differences between the factory default configuration and the desired configuration. - If you have assigned configurations to certain modems, you MUST create NEW configuration files to replace the OLD ones. This should be done before running the Rack Manager software. - IMPORTANT! NEW Event file format: The OLD Rack Manager application wrote data file for a specific collection period. When the period expired, a file was written containing the data from that period. The files name was encoded to contain the starting date and time of the period that was being recorded. The NEW Rack Manager application creates a file for each day of operation. The file is then index by hour so that all the data for a given day is recorded in one file. The NEW event files have the extension *.EVT and can be found in the MR.LOG directory. This new method of recording event data improves the flexibility in how this data can be analyzed. - Modem Inventory (updated): Update the modem inventory information to include all the necessary items needed for callback security. This allows a modem to be set up as a non-security, inbound only, outbound only or both modem. - NEW Rack Manager Interface: The Rack Manager interface has been modified (along with the other system applications) to be easier to work with by providing a toolbar that contains frequently needed functions. This along with other "look & feel" modifications will hopefully improve the overall use ability of the product. - More on the NEW Configuration file format: The configuration (*.cfg) files that are created in the Configuration Manager are just text files. A configuration file is split into two sections: built-in commands and user defined commands. For each line that contains built-in commands, the line starts with 'AT' and then continues with a string of built-in commands concatenated together. An example of a line that contains built-in commands is given below: 'ATE0V1Q0&E1&E15' There can be more than one line of built-in commands. (the single quotes are for presentation only and should not be in the configuration file -- this also applies to the examples below). A single line in the text file separates the built-in commands from the user-defined commands. It consists of a line starting with the following string: ' // User Defined' The leading space is must be present to have the line defined as the start of the user defined commands. For each line that contains user-defined commands, the line starts with 'AT' and is followed immediately by the user command (which can be several commands concatenated together). Following that there should be at least one tab or space followed by a '// ' string which denotes the start of the description. Below is an example of a user-defined command line: 'AT$MB9600 // Set the baud rate to 9600' The space after the '//' is required. There can be more than one line of user-defined commands. Below is an example of a complete configuration file. ATE0V1Q1$SB19200$MB9600&E1&E4&E15 AT#A0$E0$F0 // User Defined AT+FAA=1 // Turn on fax/data auto-detect AT&D3 // Reset on DTR drop - NEW Statistical Analyzer For the 2.00 release of the MultiModemManager software, the Statistical Analyzer application is not included. There will be an update release for 2.00 which will include the NEW Statistical Analyzer. The event data that is being collected by the Manager software will be able to be analyzed with the NEW Statistical Analyzer when it is available. **************************************************************** Usage notes: 1. As of version 1.01, the MultiModemManager software requires Windows version 3.1. While versions 1.01 and 1.02 of the MultiModemManager will run on Windows 3.0, it is not reccommended. A future release of the software will not run on Windows 3.0. 2. Remote access to the manager workstation can be accomplished by using a remote access software package which allow remotely controlling a host running Windows. Using a remote package, a user can access the MultiModemManager software running on the manager node from another site. This can be accomplished across a network or by modem. The MultiModemManager software should be left running on the manager (host) node at all times. Remotely accessing the host will allow the user to have remote control over the software to perform various manager operations. When the remote link is to be terminated the MultiModemManager software should be left operational to allow for continued monitoring of modem events. Please refer to the particular software packages instructions on how to set this up. **************************************************************** Any problems or questions should be directed to Multi-Tech Technical Support at (612) 785-3500 or (800) 328-9717. Please send any suggests or possible enhancements to: Multi-Tech Systems, Inc., 2205 Woodale Drive, Mounds View, Minnesota 55112, c/o "R&D -MultiModemManager" or fax us at (612) 785-9874.