HP HSR 6600 Router Series - HP A6600_HSR6602-CMW520-R3103P04 Release Notes Release Notes

14
Operation changes
Operation changes in CMW520-R2604
The super authentication blacklist feature is supported
When you use the super command to switch the user privilege level for a user that has passed AAA
authentication, if you enter the super password for five consecutive times, the super command is locked
for the user and unlocked 15 minutes later.
This function applies to only AAA authentication users, and does not apply to non-authenticated users or
password authentication users.
This feature is enabled by default, and cannot be disabled.
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.
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.