Technical data

48 Known limitations and considerations in this release
217316-A Rev 00
• Nortel Networks recommends that you do not enable or disable I/O slots
during an HA failover. Wait for the
system ready message on the master
CPU before enabling or disabling an I/O slot. (Q00885940)
• If you change the
ha-cpu flag, the switch saves the change to /flash/boot.cfg
only on both the master and backup CPUs, even though both CPUs were
booted up using pcmboot.cfg. Because the flag’s status has been changed, the
backup CPU immediately boots up with pcmboot.cfg. However, because the
change to the
ha-cpu flag was saved to boot.cfg, the HA status of the switch
does not change. (Q00911908)
• No error message is displayed if you do not have matching software versions
on the primary and secondary CPU and are in HA mode. (Q00248522)
• The robustness value may incorrectly display in the
show ip igmp
mrdisc-nei
CLI output on the receiving switch. The incorrect value is then
copied to the standby CPU. This value is for informational purposes only and
does not affect the operation of your switch. (Q00536682-01)
• After a failover (HA enabled), if the new master CPU does not complete table
synchronization prior to another failover, then the new master CPU reboots.
(Q00157504)
• The bootconfig flag,
verify-config, changes from true to false if you
reboot a High Availability (HA) chassis with incompatible protocols. This
behavior allows the switch to boot properly if the previous configuration
contains features not supported by HA. (Q00883779)
• In HA mode, when you reset ECMP multiple times, and you perform HA
failover, the switch displays the following message on the backup CPU:
“wrong updateFDB.” This condition has no effect on the switch.
(Q00912709)
• When you remove a module during CPU failover, the switch resets.
(Q00790435)
Link Aggregation Group (MLT/IEEE 802.3ad)
• When you add a port to an aggregation group, the values of the rate-limiting
parameters on the port remain the same (that is, they are not updated, based on
the values configured for the other aggregation group ports). To work around
this limitation, first add all the ports to the aggregation group, and then change
the rate limiting values of any port. (Q00805119)
• When the timer expires, the LACP Partner operation is not removed.
(Q00762380)