Blade ICE BMD00098 manual Management Module/GbESM Connectivity

Page 20

BLADE OS 5.1 Release Notes

Management Module/GbESM Connectivity

Currently, the IBM management module is designed to provide one-way control of the GbESM. As a result, the GbESM may lose connectivity to the management module via the management port under the following conditions:

￿If new IP attributes are pushed from the management module to the GbESM while the IP Routing table is full, the new attributes will not be applied.

Solution: Enable “External Management over all ports,” connect to the switch using other interface and then clear the routing table. Then push the IP address from the management module. If this does not work, use Solution 2 below.

￿If you execute the /boot/reset CLI command on the GbESM or the GbESM resets itself, the management module might not push the IP attributes to the switch, and connectivity may be lost.

Solution 1: If you should experience any connectivity issues between the switch module and the management module, go to the “I/O Module Configuration” window on the management module’s Web interface. Under the “New Static IP Configuration” section, click Save to trigger the management module to push the stored IP attributes to the switch module.

Solution 2: If Solution 1 does not resolve your connectivity issue, then go to the “I/O Module Admin/Power/Restart” window on the management module’s Web interface. Restart the switch module in question.

Solution 3: If this still does not resolve the issue, enable Preserve new IP configuration on all resets setting on the management module and restart the switch module via the “I/O Module Admin/Power/Restart” window on the management module’s Web interface.

Note – As a rule, always use the management module Web interface to change the GbESM management IP attributes (IP address, mask and gateway), and then click Save to push the IP attributes to the switch module. Use of the command-line interface to change the switch module management IP attributes may result in duplicated entries for the management IP Interface in the switch route table and/or loss of connectivity via the management module.

20

BMD00098, December 2009

Image 20
Contents Release Notes Blade OS 5.1 Release Notes Release Notes Hardware Support 10Gb Uplink ESM FaceplateRecommended SFP+ transceiver Updating the Switch Software Image Loading New Software to Your SwitchUsing the Bladeos CLI Using the Iscli Using the BBI Link Layer Detection Protocol New and Updated FeaturesRemote Monitoring SFlow Monitoring Operation/Administration/Maintenance ProtocolUni-Directional Link Discovery Protocol Internal Loopback Interface Rate LimitingHot Links Ospf EnhancementsLacp Trunk Enhancements Layer 2 Failover EnhancementsACL Precedence Enhancement Forwarding Database EnhancementsCLI List and Range Inputs ISL Layer 2 Protocol EnhancementsSTP Fast Uplink Bridge Priority Chassis Internal Network BC-S Chassis SupportINT1 Other Features Supplemental Information Management ModuleManagement Module/GbESM Connectivity Secure Shell SSH Trunk Group Configuration TipsSecure Management Network Spanning Tree Configuration Tips Syslog Configuration TipInternal Port Autonegotiation FTP/TFTP Directory PathKnown issues Access Control ListsIgmp Relay Interoperability with Older HubsLink Aggregation Control Protocol Linking at 10/100MbStatic Mrouter QoS MeteringRadius with SSHv2 RIP MIBsTrunk and Link Loop Trunk TrafficStrong Password Expiration