Guest

Preview Tool

Cisco Bug: CSCul23401 - 10G slice Breakout config lost for both LC after router reload

Last Modified

Sep 21, 2018

Products (1)

  • Cisco Carrier Routing System

Known Affected Releases

5.0.1.BASE 5.2.1.BASE

Description (partial)

Symptom:
10G slice Breakout config lost and all 10G interfaces created are back to 100G interfaces

Conditions:
100% reproducible if following the steps below:

(1) Did router PXE-boot 
(2) when router was up,  config MgmtEth0 port (unrelated to 10G breakout)
    commit id 1000000001 -- username root
    commit id 1000000002 -- MgmtEth0 port  

(3) Both LC (LC0, LC5) were up. All interfaces on LC0 and LC5 were 100G (not breaked-out yet)
    Loaded my config file P_521.cfg which has the breakout config on LC0 and LC5     
/auto/tftpboot-ottawa/jhu2/pbt/config/jhu2/P_521.cfg

RP/0/RP0/CPU0:ios#conf t
RP/0/RP0/CPU0:ios(config)#load disk0:/P_521.cfg
 RP/0/RP0/CPU0:ios(config)#commit replace
Do you wish to proceed? [no]: y
RP/0/RP0/CPU0:Nov 11 16:59:41.821 : config[67733]: %MGBL-CONFIG-6-DB_COMMIT : Configuration committed by user 'root'. 
se 'show configuration commit changes 1000000003' to view the changes. 


(4) After config applied, we can see the breakoout config in sh wun and in commit id 1000000003 

RP/0/RP0/CPU0:pbt-2-P#sh run | inc break    
Building configuration...
hw-module location 0/0/CPU0 slice 2 breakout 10G
hw-module location 0/0/CPU0 slice 3 breakout 10G
hw-module location 0/0/CPU0 slice 4 breakout 10G
hw-module location 0/5/CPU0 slice 0 breakout 10G
hw-module location 0/5/CPU0 slice 1 breakout 10G


RP/0/RP0/CPU0:pbt-2-P#show configuration commit changes 1000000003 | inc break             
Building configuration...
hw-module location 0/0/CPU0 slice 2 breakout 10G
hw-module location 0/0/CPU0 slice 3 breakout 10G
hw-module location 0/0/CPU0 slice 4 breakout 10G
hw-module location 0/5/CPU0 slice 0 breakout 10G
hw-module location 0/5/CPU0 slice 1 breakout 10G
  fast-reroute per-prefix tiebreaker secondary-path index 255
  fast-reroute per-prefix tiebreaker secondary-path index 255


(4) did router power-cycle to make 10G breakout work. 
    After router was up, breakout config are still in sh run but lost in commit id 1000000003. 


RP/0/RP0/CPU0:pbt-2-P#sh run | inc break    
Building configuration...
hw-module location 0/0/CPU0 slice 2 breakout 10G
hw-module location 0/0/CPU0 slice 3 breakout 10G
hw-module location 0/0/CPU0 slice 4 breakout 10G
hw-module location 0/5/CPU0 slice 0 breakout 10G
hw-module location 0/5/CPU0 slice 1 breakout 10G


RP/0/RP0/CPU0:pbt-2-P#sh configuration commit changes 1000000003  | inc break
Building configuration...
  fast-reroute per-prefix tiebreaker secondary-path index 255
  fast-reroute per-prefix tiebreaker secondary-path index 255



(5) Need to apply my config again for the 10G interfaces which were just created after router power-cycle.
    Since breakout config is not in 1000000003, when I loaded the config and commit replace, 
    
RP/0/RP0/CPU0:pbt-2-P(config)#load disk0:/P_100G.cfg
RP/0/RP0/CPU0:pbt-2-P(config)#commit replace
Do you wish to proceed? [no]: y
RP/0/RP0/CPU0:Nov 11 18:06:27.713 : config[68098]: %MGBL-CONFIG-6-DB_COMMIT : Configuration committed by user 'root'. Use 
'show configuration commit changes 1000000004' to view the changes. 


RP/0/RP0/CPU0:pbt-2-P#sh configuration commit changes 1000000004 | inc break
Building configuration...
no hw-module location 0/0/CPU0 slice 2 breakout 10G
no hw-module location 0/0/CPU0 slice 3 breakout 10G
no hw-module location 0/0/CPU0 slice 4 breakout 10G
no hw-module location 0/5/CPU0 slice 0 breakout 10G
no hw-module location 0/5/CPU0 slice 1 breakout 10G

- 
(6) Did router power-cycle. 
 - The breakout config lost in sh run 
 - 10G interfaces which was created earlier were back to 100G interfaces.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.