Guest

Preview Tool

Cisco Bug: CSCuo40220 - Panini Pim Process Crashing continuosly while applying the BWA_ECMP conf

Last Modified

Aug 07, 2018

Products (1)

  • Cisco Network Convergence System 6000 Series Routers

Known Affected Releases

5.2.1.BASE

Description (partial)

Symptom:
Commit Failure and Crash.

Conditions:
Pim Process Crashed after applying the configs stepwise.
Step 1:
 
route-policy EAST
 
                   if destination in (232.1.0.0/16 le 32, 232.2.0.0/16 le 32, 232.3.0.0/16 le 32, 239.11.0.0/16 le 32, 239.12.0.0/16 le 32, 239.13.0.0/16 le 32) and source in (192.168.102.2/2
 
                  set weight 50000
 
              endif
 
             end-policy
 
 
            route-policy WEST
 
            if destination in (232.1.0.0/16 le 32, 232.2.0.0/16 le 32, 232.3.0.0/16 le 32, 239.11.0.0/16 le 32, 239.12.0.0/16 le 32, 239.13.0.0/16 le 32) and source in (192.168.102.2/24 le 32
 
             set weight 50000
 
             endif
 
            end-policy
 
Step 2:
 
router isis detectv
nsf ietf
net 49.0300.0400.1921.6800.2005.00
interface loopback5
 
                          passive
 
                          address-family ipv4 unicast
interface loopback5
 
                          passive
 
                          address-family ipv4 unicast
interface TenGigE0/0/0/0/5
 
                           priority 100
 
                           address-family ipv4 unicast
 
                           metric 40 level 2
interface TenGigE0/0/0/0/9
 
                           priority 100
 
                           address-family ipv4 unicast
 
                           metric 100 level 2
interface TenGigE0/0/0/0/8
 
                           priority 100
 
                           address-family ipv4 unicast
 
                           metric 100 level 2
interface TenGigE0/0/0/0/2
 
                           priority 100
 
                           address-family ipv4 unicast
 
                           metric 100 level 2
interface TenGigE0/0/0/0/3
 
                           priority 100
 
                           address-family ipv4 unicast
 
                           metric 100 level 2
interface TenGigE0/0/0/0/4
 
                           priority 100
 
                           address-family ipv4 unicast
 
                           metric 100 level 2
interface TenGigE0/0/0/0/7
 
                           priority 100
 
                           address-family ipv4 unicast
 
                           metric 40 level 2
 
Step 3:
 
multicast-routing address-family ipv4
 
              interface all enable
 
Step 4::
 
router pim
 
                       address-family ipv4
 
                        rpf-redirect route-policy EAST
 
                       interface TenGigE0/0/0/0/2
 
                       enable
 
                       rpf-redirect bundle EAST bandwidth 100000000 threshold 50000000
 
                       interface TenGigE0/0/0/0/3
 
                       enable
 
                       rpf-redirect bundle EAST bandwidth 100000000 threshold 50000000
 
                       interface TenGigE0/0/0/0/7
 
                       enable
 
                       rpf-redirect bundle EAST bandwidth 100000000 threshold 50000000
 
                       interface TenGigE0/0/0/0/4
 
                       enable
 
                       rpf-redirect bundle EAST bandwidth 100000000 threshold 50000000
 
                       interface TenGigE0/0/0/0/8
 
                       enable
 
                       rpf-redirect bundle WEST bandwidth 100000000 threshold 50000000
 
                       interface TenGigE0/0/0/0/9
 
                       enable
 
                       rpf-redirect bundle WEST bandwidth 100000000 threshold 50000000
 
 
 
Config is failing and seeing pim process is crashing after the step 4
 
RP/0/RP0/CPU0:pireg-panini-r3(config-pim-ipv4-if)#show configuration failed
Thu Apr 17 02:19:34.674 UTC
RP/0/RP1/CPU0:Apr 17 02:19:35.623 : processmgr[51]: %OS-SYSMGR-3-ERROR : pim(1)
(jid 1152) exited, will be respawned with a delay (slow-restart)  
RP/0/RP1/CPU0:Apr 17 02:19:35.623 : processmgr[51]: %OS-SYSMGR-3-ERROR : pim(115
2) (fail count 2) will be respawned in 10 seconds 
RP/0/RP0/CPU0:Apr 17 02:19:40.745 : processmgr[51]: %OS-SYSMGR-3-ERROR : pim(1)
(jid 1152) exited, will be respawned with a delay (slow-restart)  
RP/0/RP0/CPU0:Apr 17 02:19:40.745 : processmgr[51]: %OS-SYSMGR-3-ERROR : pim(115
2) (fail count 2) will be respawned in 10 seconds 
!! APPLY ERRORS: This configuration was accepted by the system,
!! but errors occurred when the system attempted to make the
!! configuration operational. The individual errors for each
!! failed configuration command can be found below. These errors
!! will cause an inconsistency between the system's running
!! configuration and its operational state, which may be addressed
!! by using the 'no' form of the command to remove it from the
!! running configuration.
 
 
router pim
address-family ipv4
  rpf-redirect route-policy EAST
!!% The process 'pim' unregistered before responding to an apply request
  interface TenGigE0/0/0/0/2
   rpf-redirect bundle EAST bandwidth 100000000 threshold 50000000
!!% The process 'pim' unregistered before responding to an apply request
  !
  interface TenGigE0/0/0/0/3
   rpf-redirect bundle EAST bandwidth 100000000 threshold 50000000
!!% The process 'pim' unregistered before responding to an apply request
  !
  interface TenGigE0/0/0/0/4
   rpf-redirect bundle EAST bandwidth 100000000 threshold 50000000
!!% The process 'pim' unregistered before responding to an apply request
  !
  interface TenGigE0/0/0/0/7
   rpf-redirect bundle EAST bandwidth 100000000 threshold 50000000
!!% The process 'pim' unregistered before responding to an apply request
  !
  interface TenGigE0/0/0/0/8
   rpf-redirect bundle WEST bandwidth 100000000 threshold 50000000
!!% The process 'pim' unregistered before responding to an apply request
  !
  interface TenGigE0/0/0/0/9
   rpf-redirect bundle WEST bandwidth 100000000 threshold 50000000
!!% The process 'pim' unregistered before responding to an apply request
  !
!
!
End
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.