Remote RMM-1400 Intelligent Remote Site Management Device Release Notes

Transcription

1 Remote RMM-1400 Intelligent Remote Site Management Device Release Notes Version 5.01 December 2012 Part Number by Kentrox, Inc. All rights reserved.

2 Copyright 2012 by Kentrox, Inc. All Rights Reserved. The material discussed in this publication is the proprietary property of Kentrox, Inc. Kentrox retains all rights to reproduction and distribution of this publication. Kentrox is a registered trademark of Kentrox, Inc. Applied Innovation, Applied Innovation Inc., the AI logo, and other names are the intellectual property of Kentrox. All other product names are trademarks or registered trademarks of their respective owners. Information published here is current as of this document s date of publication, but is subject to change without notice. You may verify product information by contacting our headquarters. Kentrox is an Equal Opportunity/Affirmative Action employer. Kentrox, Inc Innovation Dr. Dublin, Ohio USA Toll Free: (800) International: +1 (614) Fax: +1 (614)

3 New Features Remote RMM-1400 Intelligent Remote Site Management Device Release Notes Version 5.01 December 2012 These release notes document two new features for Remote RMM-1400 version This document also provides software update instructions. Instructions for use of this product are detailed in the following documents: Remote RMM-1400 Intelligent Remote Site Management Device Command Reference Guide Remote RMM-1400 Intelligent Remote Site Management Device Configuration Guide Remote RMM-1400 Intelligent Remote Site Management Device Installation Guide New Features The Remote RMM-1400 version 5.01 includes the following new features: Delays in Wireless Reconnection Attempts (Issue 72989) Add TACACS+ AAA (Issue 73049) Delays in Wireless Reconnection Attempts The Remote RMM-1400 adheres to specific guidelines when scheduling attempts to wirelessly re-establish lost PPP connections. When a connection is lost, the Remote RMM-1400 immediately tries to reconnect. If unsuccessful, another attempt is immediately initiated. If the second attempt fails, the Remote RMM-1400 will continue to periodically try to establish a successful connection. After the first two tries, connection attempts are made at intervals of 1 minute, 2 minutes, 8 minutes and then every 15 minutes until successful. 1

4 Add TACACS+ AAA The Remote RMM-1400 now provides user authentication and authorization for remote access into a network using the TACACS+ AAA protocol. The Remote RMM-1400 can be configured to use local user authentication when attempts to contact the primary and secondary RAS servers fail. Note: The Remote RMM-1400 can be configured with an IP address, a specific port designation and a password for each RAS server. The following sections provide information on how to update Remote RMM-1400 software to version The expansion unit software for both the RMB version 1.13 and for non-rmb peripherals version 1.70 have not recently changed. Although the software may not need updating, instructions have been included for reference. Note: It is not necessary to update the Remote RMM-1400 stage 2 bootloader. Obtaining the Software Remote RMM-1400 version 5.01 software consists of the following file: 544REM501.img This is a binary file containing the Remote RMM-1400 version 5.01 software image. The expansion units require the following files: 160B2L310.img 670B2L314.img 685B2L320.img This is a stage 2 bootloader that is compatible with the Expand D software. Important: You must load this file before loading the main Expand D software (160DEP170.img). This is a stage 2 bootloader that is compatible with the Remote RME-S8 software. Important: You must load this file before loading the main Remote RME-S8 software (160DEP170.img). This is a stage 2 bootloader that is compatible with the Remote RME-E8 software. Important: You must load this file before loading the main Remote RME-E8 software (160DEP170.img). 2

5 681B2L340.img 680B2L314.img This is a stage 2 bootloader that is compatible with the Remote RME-B64 software. Important: You must load this file before loading the main Remote RME-B64 software (160DEP170.img). This is a stage 2 bootloader that is compatible with the main Expand FDCI software. Important: You must load this file before loading the main Expand FDCI software (160DEP170.img). 160DEP170.img This is a binary file containing the expansion unit version 1.70 firmware image. This image is used with all five expansion units. The RMB expansion unit requires the following file: 684RMB113.img This is a binary file containing the RMB expansion unit version 1.13 software image. If you need assistance with obtaining the software, please contact your sales representative or Kentrox Technical Support. Updating the Remote RMM-1400 Software Tip: Back up the Remote RMM-1400 configuration before updating the software. Important: You must have a supervisor user profile to perform this procedure. To update the Remote RMM-1400 firmware: 1. Using an FTP/SFTP utility, connect to and log into Remote RMM Change the current directory to /images. 3. Using binary mode, transfer the Remote RMM-1400 image (544REM501.img) to boot.img. 4. Close the FTP/SFTP connection to Remote RMM-1400 and exit the FTP/SFTP utility. 5. Access and log into Remote RMM At the main CLI prompt, reset Remote RMM-1400: reload The following message appears: Do you wish to save your running configuration? (y/n) 3

6 7. Save the running configuration by copying the running configuration to the startup configuration file: y The following message appears: Are you sure you wish to reset? (y/n) 8. Confirm the reset: y Remote RMM-1400 resets and comes back online. 9. Access and log into Remote RMM (optional) At the main CLI prompt, verify that the software has been updated properly: show version The command response similar to the following displays: (Dub)>show version Product: Remote RMM-1400 Version: 5.01 Build date: ,14:14:42.0,-05:00 Build ID: 003 Image type: KTX544-Production Bootloader Version: 1.10 (Dub)> Updating the Expansion Unit Software To update the expansion unit software: 1. Using an FTP/SFTP utility, connect to and log into Remote RMM Change the current directory to /images/peripherals/rmb. 3. Using binary mode, transfer the RMB software image (684RMB113.img) to boot.img. 4. Close the FTP/SFTP connection to Remote RMM-1400 and exit the FTP/SFTP utility. 5. Access and log into Remote RMM At the main CLI prompt, reload all managed expansion units: diag peripheral * reload The following message appears: Are you sure you wish to reset the peripheral? (y/n) 4

7 7. Confirm the reset: y Expansion units reset and come back online. 8. Verify that the expansion unit software has been updated properly: show peripherals unit 1 The command response similar to the following displays: (Dub)>show peripherals unit 1 Unit number: 1 Description: Type: RMB Admin state: Managed Name: RMB1-103CD9 IP address: N/A Oper state: Online Manager name: Dub Manager IP address: Type: RMB Model: B A:0 Firmware version: 1.13 Firmware build date: ,11:10:47.0,-05:00 Firmware build ID: 001 Serial number: Manufacture date: 02/21/12 Stage2 bootloader version: 1.01 Stage2 bootloader build date: Mon Mar 8 10:10:22 EST 2010 MAC address: 00:40:72:10:3C:D9 Chassis serial number: Chassis slot number: 1 Chassis model: B A:0 Chassis manufacture date: 02/21/12 Chassis MAC address: 00:40:72:10:3C:D9 (Dub)> Important: Oper state: Online indicates that the RMB software download is complete, and you can verify that the correct firmware version (1.13) is displayed. If Oper state does not appear as Online, enter command show peripherals unit 1 again until Oper state: Online appears. If Oper state: Online appears, and the firmware version is incorrect, repeat steps 6 through 8 above. 5

8 Updating the Expansion Unit Stage 2 Bootloader and Firmware To update the expansion unit stage 2 bootloader and firmware: 1. Using an FTP/SFTP utility, connect to and log into Remote RMM Using binary mode, transfer the stage 2 bootloader image (160B2L310.img, 670B2L314.img, 681B2L340.img, 685B2L320.img, or 680B2L314.img) to stage2boot.img in the appropriate directory: /images/peripherals/discrete-expansion for Expand DEP (160B2L310.img) /images/peripherals/serial18-expansion for Remote RME-S8 (670B2L314.img) /images/peripherals/fe8-expansion for Remote RME-E8 (685B2L320.img) /images/peripherals/fb64-expansion for Remote RME-B64 (681B2L340.img) /images/peripherals/bistate48-expansion for Expand FDCI (680B2L314.img) 3. Using binary mode, transfer the firmware image (160DEP170.img) to boot.img in the desired directory. Note: Since the five expansion units use the same firmware, the firmware image can be transferred to boot.img in any of the five directories listed in step Close the FTP/SFTP connection to Remote RMM-1400 and exit the FTP/SFTP utility. 5. Access and log into Remote RMM At the main CLI prompt, reload all managed expansion units: diag peripheral * reload The following message appears: Are you sure you wish to reset the peripheral? (y/n) 7. Confirm the reset: y Expansion units reset and come back online. 6

9 8. (optional) Verify that the expansion unit firmware and stage 2 bootloader have been updated properly: show expansion-images The command response similar to the following displays: (Dub)>show expansion-images discrete-expansion/boot.img Product: AIExpansion-Shelf Version: 1.70 Build date: ,16:54:06.0,-04:00 Build ID: 002 Image type: AIModExpan-Production Production release. discrete-expansion/stage2boot.img Version: 3.10 Build date: Thu Jul 6 13:52:11 EDT 2006 Image type: AI160-Stage2Boot serial8-expansion/boot.img Product: AIExpansion-Shelf Version: 1.70 Build date: ,16:54:06.0,-04:00 Build ID: 002 Image type: AIModExpan-Production Production release. serial8-expansion/stage2boot.img Version: 3.14 Build date: Wed Nov 29 10:08:25 EST 2006 Image type: AI670-Stage2Boot bistate48-expansion/boot.img Product: AIExpansion-Shelf Version: 1.70 Build date: ,16:54:06.0,-04:00 Build ID: 002 Image type: AIModExpan-Production Production release. bistate48-expansion/stage2boot.img Version: 3.14 Build date: Wed Nov 29 10:08:31 EST 2006 Image type: AI680-Stage2Boot 7

10 fb64-expansion/boot.img Product: AIExpansion-Shelf Version: 1.70 Build date: ,16:54:06.0,-04:00 Build ID: 002 Image type: AIModExpan-Production Production release. fb64-expansion/stage2boot.img Version: 3.40 Build date: Thu Jul 26 14:44:57 EDT 2007 Image type: AI681-Stage2Boot fe8-expansion/boot.img Product: AIExpansion-Shelf Version: 1.70 Build date: ,16:54:06.0,-04:00 Build ID: 002 Image type: AIModExpan-Production Production release. fe8-expansion/stage2boot.img Version: 3.20 Build date: Tue Mar 6 15:17:11 EST 2007 Image type: AI685-Stage2Boot RMB/boot.img Product: RMB Version: 1.13 Build date: ,11:10:56.0,-05:00 Build ID: 001 Image type: KTX684-Production Production Release RMB/stage2boot.img No Image Information Available. (Dub)> 8