Guest

Preview Tool

Cisco Bug: CSCun85005 - Incorrect log message when deleting sub-interface

Last Modified

Feb 08, 2017

Products (1)

  • Cisco Carrier Routing System

Known Affected Releases

4.3.1.BASE

Description (partial)

Symptom:
On XR platforms, when we delete a sub-interface after shut command, log shows that interface state changed to up.

RP/0/RSP0/CPU0:BDK_PBN_CR-03(config-subif)#int g0/0/1/0.100                    <<<<<<< Here we shut down the subinterface
RP/0/RSP0/CPU0:BDK_PBN_CR-03(config-subif)#shut
RP/0/RSP0/CPU0:BDK_PBN_CR-03(config-subif)#commit
LC/0/0/CPU0:Mar 10 12:16:12.806 : ifmgr[206]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/1/0.100, changed state to Administratively Down
RP/0/RSP0/CPU0:Mar 10 12:16:12.924 : config[65788]: %MGBL-CONFIG-6-DB_COMMIT : Configuration committed by user 'cisco'. Use 'show configuration commit changes 1000000338' to view the changes.

RP/0/RSP0/CPU0:BDK_PBN_CR-03(config-subif)#no int g0/0/1/0.100                <<<<<<<< We delete the sub-interface.
RP/0/RSP0/CPU0:BDK_PBN_CR-03(config)#commit
LC/0/0/CPU0:Mar 10 12:16:19.376 : ifmgr[206]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/1/0.100, changed state to Down
LC/0/0/CPU0:Mar 10 12:16:19.376 : ifmgr[206]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/1/0.100, changed state to Down
LC/0/0/CPU0:Mar 10 12:16:19.378 : ifmgr[206]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/1/0.100, changed state to Up
RP/0/RSP0/CPU0:Mar 10 12:16:19.517 : config[65788]: %MGBL-CONFIG-6-DB_COMMIT : Configuration committed by user 'cisco'. Use 'show configuration commit changes 1000000339' to view the changes.

As you can see the ifmgr process logs a message while deleting the subinterface that:  ifmgr[206]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/1/0.100, changed state to Up

This can be easily tested on ASR9000/CRS by enabling: "logging events link-status software-interfaces".

Conditions:
"logging events link-status software-interfaces" should  be enabled.
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.