HP HSR6600 Router and Router Processing modules series - A6600_HSR6602-CMW520-R3102 Release Notes

13
Restrictions and cautions
The CLI, Web and SNMP management interfaces vary depending on the whether the device MPU is HP
or H3C branded. When an HP brand MPU and H3C brand MPU are both running in a
SR6600/A6600 router, the equipment will adopt the brand name of active MPU. For how to change the
brand name of MPU from H3C to HP, please refer to 'HP A6600 Routers Fundamentals Configuration
Guide' and 'HP A6600 Routers Fundamentals Command Reference'. This Release Note only contains
CLI examples from an HP branded product.
This code cannot be downgraded to the version early than R2603.
Open problems and workarounds
RTD58795
 Symptom: Cannot login the device through Console interface.
 Condition: Configure 4K BGP peers, but do not configure ‘update-no-advertise’, the BGP route fresh
frequently.
 Workaround: None.
RTD59059
 Symptom: The packet fragments fails to pass the 4to6 tunnel.
 Condition: None.
 Workaround: None.
RTD60035
 Symptom: In the version after F2604, the password encryption within configuration files has been
enhanced and cannot be interpreted by earlier revisions of the agent code. This means that if a unit
is downgraded to earlier code, it may no longer be possible to login and manage the device.
 Condition: Upgrade the code from the version before F2604 to F2064 or later version.
 Workaround:
 Before upgrading to the new code, it is necessary to ensure password control is disabled.
Execute the “undo password-control enable” and then save this configuration file as a backup
in case you need to downgrade the software again. If it is later necessary to downgrade to
earlier software, force the router to use this backup configuration file by executing a ”startup
saved-configuration (filename)” command before rebooting to the old code. Then, after the
code has been downgraded, the device can be logged in from the console or by Telnet, but not
SSH. The SSH authentication details will need to be reset.
 If no backup configuration has been saved but it is still possible to access the device
management via some method while running the old code (e.g. Console, Telnet or SSH), then
you can redefine all the device management passwords as required.
 If after a downgrade it is impossible to login to the device via any method, then there are two
ways to recover the router:
 From the BOOT menu, set the new code to run again and reboot the device. Disable Telnet
authentication:
User-interface vty 0 4
Authentication mode none