OPERATIONAL DEFECT DATABASE
...
...
Type of behavior change: - This change is applicable ONLY for Curie platform. 1. C8300-1N1S-4T2X 2. C8300-1N1S-6T 3. C8300-2N2S-4T2X 4. C8300-2N2S-6T 5. C8200-1N-4T 6. C8200L-1N-4T Release introduced: - 17.5.1
Old behavior: - As per current implementation, 1. Console line speed change is allowed ONLY through " Router(config)#line console 0 Router(config-line)#speed " but the clear indication to user is missing, saying that user cannot change console line speed by changing config-register value. At present when user changes the config-register value using following CLI. Router(config)#config-register 0x1800 Router(config)#end It never indicates user that it is NOT going to change speed of console line instead it says following, Router#sh ver | i register Configuration register is 0x1820 (will be 0x1800 at next reload) config-terminal, it does NOT change the speed but displays wrong message on what would be config-register value at next reload. In fact, when user tries to change the speed bits through config-register it ignores them completely but shows miss leading message to user.
New behavior: - With the new change, 1. console line speed setting is still done the old way i.e. ONLY speed CLI can change the console line speed and speed bits changed through config-register CLI are ignored. 2. Having said that when user tries to change speed bits through config-register CLI, it throws warning to use saying Router#conf t Router(config)#config-register 0x2102 ====================>NEW CONFIG, WHICH INCLUDES SPEED BIT CHANGE New Config-register value is trying to change console speed as well, speed can be changed using speed CLI only so ignoring speed bits and applying remaining configuration config-register value will be 0x3922 at next reload ==============>GIVES NOTICE, OF NOT CHANGING THE SPEED Router(config)#end Router#sh ver | i register Configuration register is 0x9E20 (will be 0x3922 at next reload) ======>MENTIONING CORRECT NEW VALUE TO BE Router# 3. The warning msg above, would appear only when the new config-register value has change in speed bits, if it does not have speed bit change then no warning is given. 4. Please note this change is applicable to Curie platform ONLY.
Impact on customer: 1. Functional behavior would remain the same. 2. User would get proper message on what would be the value of config-register at next reload.
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
