RELEASE NOTES. Remote RMX-3200, Remote RMM-1400, Remote RMM-800, Remote RMC-700, Remote RMM-700 Intelligent Site Management Devices Version 6.

Transcription

1 Remote RMX-3200, Remote RMM-1400, Remote RMM-800, Remote RMC-700, Remote RMM-700 Intelligent Site Management Devices Version 6.30 Release Notes Rev A March 2016 RELEASE NOTES Westell Technologies Part # Rev A

2 Copyright 2016 by Westell Inc. All Rights Reserved. Westell, Kentrox and Optima Management System are registered trademarks of Westell. All other names are trademarks of their respective owners. Information is correct at time of publication and is subject to change without notice. Contact Westell in Aurora, Illinois to verify current product information. Westell, Inc. is an Equal Opportunity/Affirmative Action employer. Westell, Inc. 750 North Commons Drive Aurora, IL USA Toll Free: (800) International: +1 (630) Fax: +1 (630) Page 1

3 New Feature Remote RMX-3200, Remote RMM-1400, Remote RMM-800, Remote RMC-700, and Remote RMM-700 Intelligent Site Management Devices Release Notes Version 6.30 March 2016 These release notes document new features, enhancements, and a fix for Remote RMX-3200, Remote RMM-1400, Remote RMM-800, Remote RMC-700, and Remote RMM-700 Version This document also provides software update instructions for Version Instructions for use of each Remote device shall be detailed in the following respective documents available online at: Command Reference Guides Configuration Guides Installation Guides Web Interface User Guide Navigate to the Support Portal via the Services & Support tab. First-time users will need to follow the instructions to obtain a username and password to access the Support Portal documentation library. New Feature Remote Version 6.30 includes the following new feature: SNMP Pass-through (Issue BGZ1048) SNMP Pass-through Version 6.30 adds the SNMP pass-through feature to all Remote models. With this feature, the Remote acts as a transparent proxy/router for SNMP requests from a third-party management system to devices attached to the Remote. The Remote Page 2

4 New Feature forwards SNMP requests intended for configured devices. Replies from the attached devices are passed back to the original requesting management system. The SNMP pass-through feature is managed with these CLI commands: To configure a pass-through for a given community string to the specified IP address: config snmp pass-through <community> <ip address> [<port>] The community is valid for SNMP v1 or v2. Port 161 is assumed on the target if not specified. To remove a pass-through configuration: config snmp no pass-through { <community> * } To view the pass-through configuration: show snmp summary The pass-through supports traps from the third party device via NAT translation. The third party device is assumed to have the management station configured as its SNMP manager, not the Remote. As the trap is routed through the Remote, the trap packet is modified to have the Remote as the source of the trap, not the third party device s private IP address. The user must configure an iptables rule as shown below. Given the following setup: Management station at mgmt_ip, e.g Remote WAN interface at remote_wan_ip, e.g Remote local network at remote_local_net/remote_local_prefix, e.g /24 Iptables CLI configuration: config iptables -t nat -A POSTROUTING -s <remote_local_ip/remote_local_prefix> -d <mgmt_ip> -p udp --dport 162 -j SNAT --to-source <remote_wan_ip> For example: config iptables -t nat -A POSTROUTING -s /24 -d p udp --dport 162 -j SNAT --to-source Page 3

5 Fix Fix Remote Version 6.30 includes the following fix: Logging Fix to Avahi Package (Issue BGZ938) Logging Fix to Avahi Package Version 6.30 applies a logging fix to the Avahi package to resolve a compatibility issue reported by Windows 10 users. The following sections provide information on how to update Remote RMX-3200, Remote RMM-1400, Remote RMM-800, Remote RMC-700, and Remote RMM-700 software to Version The expansion unit software version 1.70 for non RMB peripherals has not recently changed. The expansion unit software version 1.20 for RMB peripherals remains the same for Remote Version Although the software may not need updating, instructions have been included for reference. Obtaining the Software Remote RMX-3200, Remote RMM-1400,Remote RMM-800, Remote RMC-700, and Remote RMM-700 Version 6.30 software consists of the following files: Table RN-1 Version 6.30 Software Files Device Software Image File Stage 2 Bootloader Image File Remote RMX RMX630.img 535B2L406.img Remote RMM REM630.img 544BL130.img Remote RMM REM630.img 562BL100.img Remote RMM-700 and Remote RMC REM630.img 560BL111.img Version 6.30 update requires no action with the stage 2 bootloader files; they are listed here for reference only. The expansion units require the following files: Table RN-2 Expansion Unit Software Files Device Software Image File Stage 2 Bootloader Image File Page 4

6 Table RN-2 Expansion Unit Software Files Expand D Remote RME-S8 Remote RME-E8 Remote RME-B64 Expand FDCI 160DEP170.img (Same for all these expansion units) 160B2L310.img 670B2L314.img 685B2L320.img 681B2L340.img 680B2L314.img RMB-1 684RMB120.img none If you need assistance obtaining the software, please contact your sales representative or Westell Customer Support. Updating the Remote RMX-3200, Remote RMM-1400, Remote RMM- 800, Remote RMC-700, and/or Remote RMM-700 Software This update procedure applies equally to Remote RMX-3200, Remote RMM- 1400,Remote RMM-800, Remote RMC-700 and/or Remote RMM-700, and refers to those as the Remote. All instructions regarding the Remote pertain to the user s respective Remote model. Tip: It is recommended that you back up the Remote configuration before updating the software. Important: You must have a supervisor user profile to perform this procedure. To update the Remote firmware: 1. Using an FTP/SFTP utility, connect to and log into the Remote. 2. Change the current directory to /images. 3. Load any bootloader update needed by your Remote to bootloader.img. 4. Using binary mode, transfer the Remote image for your model (see Table RN-1 under Obtaining the Software on page 4) to boot.img. 5. Close the FTP/SFTP connection to the Remote and exit the FTP/SFTP utility. 6. Access and log into the Remote. 7. At the main CLI prompt, reset the Remote: reload The following message appears: Do you wish to save your running configuration? (y/n) 8. Save the running configuration by copying the running configuration to the startup configuration file: Page 5

7 y The following message appears: Are you sure you wish to reset? (y/n) 9. Confirm the reset: y The Remote resets and comes back online. 10. Access and log into the Remote. 11. (optional) At the main CLI prompt, verify that the software has been updated properly: show version The command response appears similar to the following example: (JT-RMC)>show (JT-RMC) show>version Product: Remote RMC-700 Version: 6.20 Build date: ,11:41:31.0,-04:00 Build ID: 001 Image type: KTX560-Production Bootloader Version: 1.11 (JT-RMC) show> Updating the RMB-1 Expansion Unit Software To update the RMB-1 expansion unit software: Page 6 1. Using an FTP/SFTP utility, connect to and log into Remote RMX-3200 or Remote RMM-1400 (referred to as the Remote through the balance of these instructions). 2. Change the current directory to /images/peripherals/rmb Using binary mode, transfer the RMB-1 software image (684RMB120.img) to boot.img. 4. Close the FTP/SFTP connection to the Remote and exit the FTP/SFTP utility. 5. Access and log into the Remote. 6. 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

8 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 appears similar to the following example: (Dub)>show peripherals unit 1 Unit number: 1 Description: Type: RMB-1 Admin state: Managed Name: RMB1-103CD9 IP address: N/A Oper state: Online Manager name: SteveRMM-51-2 Manager IP address: Type: RMB-1 Model: B A:1 Firmware version: 1.20 Firmware build date: ,09:34:20.0,-5: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-1 software download is complete, and you can verify that the correct firmware version (1.20) 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. Updating the Expansion Unit Stage 2 Bootloader and Firmware This update procedure applies equally to Remote RMX-3200, Remote RMM- 1400,Remote RMM-800, Remote RMC-700. and Remote RMM-700, and refers to those as the Remote. All instructions regarding the Remote pertain to the user s respective Remote model. To update the expansion unit stage 2 bootloader and firmware: 1. Using an FTP/SFTP utility, connect to and log into the Remote. Page 7

9 2. Using binary mode, transfer the expansion unit s stage 2 bootloader image to stage2boot.img in the appropriate directory: /images/peripherals/discrete-expansion for Expand DEP /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) Important: The stage 2 bootloader image must be loaded as directed in Step 2 above prior to the transfer of the firmware image as directed in Step 3 below. 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 the Remote and exit the FTP/SFTP utility. 5. Access and log into the Remote. 6. 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. 8. (optional) Verify that the expansion unit firmware and stage 2 bootloader have been updated properly: show expansion-images The command response appears similar to the following example: Page 8

10 (Dub)>show expansion-images discrete-expansion/boot.img Product: AIExpansion-Shelf Version: 1.70 Build date: ,11:27:10.0,-04:00 Build ID: 003 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: ,11:27:10.0,-04:00 Build ID: 003 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: ,11:27:10.0,-04:00 Build ID: 003 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 Page 9

11 fb64-expansion/boot.img Product: AIExpansion-Shelf Version: 1.70 Build date: ,11:27:10.0,-04:00 Build ID: 003 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: ,11:27:10.0,-04:00 Build ID: 003 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-1/boot.img Product: RMB-1 Version: 1.20 Build date: ,09:34:20.0,-05:00 Build ID: 001 Image type: KTX684-Production Production Release RMB-1/stage2boot.img No Image Information Available. (Dub)> Page 10