Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
After the 9k reload; random LC and its interfaces lose the config line "transceiver permit pid all" and this failedu can be seen through "show config failed startup" command.
When an asr9k upgrades and/or reloads ; the conflg line is lost and failed.
(config)#load configuration failed startup (config)#show commit changes diff (config)#commit The workaround is not an option for automated software upgrade processes or for the 611 migration process
on 5.3.3 image customer have reported that the "transceiver permit pid all" configuration line has been failed to apply anytime they upgrade the node and reload the box. This can be viewed from "show configuration failed startup" . Due to this the SNMP does not report the correct values for the Tx and Rx power on the port. This command enables the DOM on the interface which is mainly used only to monitor the node. What to collect: sh configuration failed startup sh controllers vic ltrace all location show sysdb trace verification location sh tech sysdb file harddisk:shtechsysdb background sh tech cfgmgr file harddisk:shtechcfgmgr background sh tech snmp file harddisk:shtechsnp back admin sh tech install file harddisk:shtechinstall background How to check the issue: Trace of the Issue: Verified registered wuth sysdb later but the sysdb called the vic verifier much before: Jul 26 15:51:54.396 0/1/CPU0 5114 128 1 296 145 Uber-verify called 'cfg/if/act/TenGigE0_1_0_1_9/etherctrl/transceiver/permit/enable_pluggable_pid Jul 26 15:51:54.397 0/1/CPU0 5114 136 1 5 448 Verify called 'cfg/if/act/TenGigE0_1_0_1_9/etherctrl/transceiver/permit/enable_pluggable_pid' Jul 26 15:51:54.397 0/1/CPU0 5114 136 1 5 448 verify reply: reject <<<<<< Jul 26 15:51:54.490 0/1/CPU0 5114 128 1 296 145 Abort called 'cfg/if/act/TenGigE0_1_0_1_9/etherctrl/transceiver/permit/enable_pluggable_pid' <<<<<<<< Jul 26 15:53:12.941 vic/prb 0/1/CPU0 t1 0x0348 line 903 vic_cfg_verif_register( bay:0 if_inst:1 port:9 TenGigE0_1_0_1_9/etherctrl/) <<<<<<<<<< sh configuration failed startup Wed Jul 27 10:42:17.909 UTC ?[K!!15:42:47 UTC Tue Jul 26 2016 !! SEMANTIC ERRORS: This configuration was rejected by !! the system due to semantic errors. The individual !! errors with each failed configuration command can be !! found below. interface TenGigE0/1/0/1/0 transceiver permit pid all !!% 'CfgMgr' detected the 'fatal' condition 'This configuration has not been verified and can not be accepted by the system.' ! interface TenGigE0/1/0/1/1 transceiver permit pid all !!% 'CfgMgr' detected the 'fatal' condition 'This configuration has not been verified and can not be accepted by the system.' ! interface TenGigE0/1/0/1/2 transceiver permit pid all !!% 'CfgMgr' detected the 'fatal' condition 'This configuration has not been verified and can not be accepted by the system.' ! interface TenGigE0/1/0/1/3 transceiver permit pid all !!% 'CfgMgr' detected the 'fatal' condition 'This configuration has not been verified and can not be accepted by the system.' ! interface TenGigE0/1/0/1/4 transceiver permit pid all !!% 'CfgMgr' detected the 'fatal' condition 'This configuration has not been verified and can not be accepted by the system.' ! interface TenGigE0/1/0/1/5 transceiver permit pid all !!% 'CfgMgr' detected the 'fatal' condition 'This configuration has not been verified and can not be accepted by the system.' !