============================================== == MR4800E version 5.54.00 release information == ============================================== Contents --------------------------------------- 1. Changes in 5.54.00 2. MR4800E MIB 3. Update 4. Known Limitations 5. New Controller Commands --------------------------------------- -- 1. Changes in 5.54.00 ----------------- This is a feature release of the CommPlete Communications Server. Support has been added to email faults to as many as 5 email addresses. Email recipients are setup using the SMTPSETUP command. Designating a fault to trigger an email notification is done via the SETFAULTS command. The UPTIME and VER commands have been expanded to return information about devices. A new help operator ? has been added. Usage is ?# where # is any alphabetic character. The result of this command will be to list all controller commands that begin with that character. The UnderTime Call fault did not calculate the duration correctly in many cases -- 2. MR4800E MIB --------------------- The MIB can be found on the MultiCommManager release disk 7.xx or on the Multi-Tech FTP site ftp.multitech.com in the file MMM/SOFTWARE/MIB/MULTI1.MIB -- 3. Update -------------------------- UPDATE is used to send new firmware to the controller or a device. The -BOOT option is used to write the boot code area of the device. -BOOT should only be used when it is necessary to update the device boot code along with the device firmware. This is because if the device is interrupted (i.e. reset) while the boot code area is being written, the device may be in an unrecoverable state. Requesting the device version may be used to determine the boot code version. For the T1 and PRI firmware the boot code is embedded in the firmware hex file. For the Modem, the boot code is a separate hex file. General: Make sure there is enough room on the drive to hold the hex file. FTP the hex file to the controller (B drive). Telnet to the controller. Type UPDATE (Use -BOOT only when it is necessary to update boot code.) To view progress, type UPDATE To abort ALL devices, type ABORT To abort only selected devices, type ABORT When update is complete, the hex file may be deleted. Controller: (.hxc) Make sure there is enough room on the B drive before FTPing the file. When update is complete, answer es to reboot the controller. Modem(s): (.hex) Make sure the modem firmware is correct for the type of modem being flashed. -- 4. Known Limitations --------------- When an E1 is moved from one segment to another. The saved settings on the E1 are not preserved. The E1 settings must be loaded and saved again using E1SETUP. - Only one telnet session and only one ftp session can be active at once to the controller (one of each is OK). - The MR4800E must be managed by the MultiCommManager versions 7.xx or later - It is best when updating devices that call 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 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. -- 5. New Controller Commands --------- LISTMOD Supervisor level command that lists all currently loaded modules. LOADMOD Supervisor level command that loads a module. The module file should be named [ModuleName].MLM where ModuleName must be 8 characters or less. The module should reside in the A:MODULES directory. RUNMOD Supervisor level command that loads (if the module is not loaded) and runs the specified module. This has no use for the existing IP query modules, but may be useful in the future as new modules are implemented for the controller. UNLOADMOD Supervisor level command that unloads a module that was previously loaded. An error is returned if the given module is not currently loaded. SETRESETPING Supervisor level command that can be used to set the packet sizes of three consecutive pings which will cause the controller to reboot. This mechanism forr emotely resetting the controller can be used as a last resort if the telnet orSN MP interfaces are not responsive. GETRESETPING Supervisor level command that displays the packet sizes of three consecutive pings which, when received, will result in a controller reboot. SMTPSETUP Supervisor level command that configures the controller's email information. It allows the controller to inform administrators of faults via email, Up to five recepients may be setup. Faults triggering email notifications can be set up on an individual basis using the SETFAULTS command.