Guest

Preview Tool

Cisco Bug: CSCur46748 - FIB platform upda ERRO when reconfig ipv4/6 intf address (dpa-dpc lost)

Last Modified

Jan 10, 2017

Products (1)

  • Cisco Carrier Routing System

Known Affected Releases

5.4.0.BASE

Description (partial)

Symptom:
When reconfiguring interface address, the dpa-dpc connection got lost:
-----
RP/0/RP0/CPU0:ott02-sim-09-uut(config-if)# description interface11 -> ott02-si$
RP/0/RP0/CPU0:ott02-sim-09-uut(config-if)# ipv4 address 91.3.0.1 255.255.255.0
RP/0/RP0/CPU0:ott02-sim-09-uut(config-if)# ipv6 address 0901:0a03:0003:0000:00$
RP/0/RP0/CPU0:ott02-sim-09-uut(config-if)# mtu 1514
RP/0/RP0/CPU0:ott02-sim-09-uut(config-if)# load-interval 30
RP/0/RP0/CPU0:ott02-sim-09-uut(config-if)# no shutdown
RP/0/RP0/CPU0:ott02-sim-09-uut(config-if)# exit
RP/0/RP0/CPU0:ott02-sim-09-uut(config)#
RP/0/RP0/CPU0:ott02-sim-09-uut(config)#commit
Wed Oct 29 19:41:53.067 UTC
RP/0/RP0/CPU0:Oct 29 19:41:53.510 : ipv4_arm[321]: %IP-IP_ARM-3-CFLCT_FORCED_DOWN : The IPv4 address 91.3.0.1/24 on TenGigE0/RP0/CPU0/6 conflicts with other IPv4 addresses and has been forced down
RP/0/RP0/CPU0:Oct 29 19:41:53.518 : ipv6_arm[355]: %IP-IP_ARM-3-CFLCT_FORCED_DOWN : The IPv6 address 901:a03:3::1/112 on TenGigE0/RP0/CPU0/6 conflicts with other IPv6 addresses and has been forced down
RP/0/RP0/CPU0:Oct 29 19:41:53.608 : fib_mgr[318]: %OS-MMAP_PEER-6-CONNECT : Failed to connect from process 4825 to 9415: No such file or directory
RP/0/RP0/CPU0:Oct 29 19:41:53.883 : config[66797]: %MGBL-CONFIG-6-DB_COMMIT : Configuration committed by user 'root'. Use 'show configuration commit changes 1000000006' to view the changes.
RP/0/RP0/CPU0:ott02-sim-09-uut(config)#RP/0/RP0/CPU0:Oct 29 19:41:57.445 : fib_mgr[318]: %ROUTING-FIB-3-PLATF_UPD_FAIL : FIB platform update failed: Obj=DATA_TYPE_LDI_LW[ptr=0xa9da7d78,refc=0,flags=0x1000] Action=DELETE Proto=ipv4. Cerr='dpc_rm_svr' detected the 'warning' condition 'There was a failure in communicating with the DPC RM server - possibly it has restarted. Operation may be retried.'  : fib_mgr : (PID=4825) :  -Traceback= 4ebf80 4efe04 4741da 57ba96 58472c 4323fd 44cafa 435dd0 436110 436459 436c5b 7fcc6d3733c8 7fcc6d38531e 4192ce 42c8d4 7fcc6376a9bc
RP/0/RP0/CPU0:Oct 29 19:41:57.452 : fib_mgr[318]: %ROUTING-FIB-3-PD_FAIL : FIB platform error: fib_ldi_platform_update 1725: PD action DELETE failed for passed_ldi 0xa9da7d78 type DATA_TYPE_LDI_LW flags 0x1000. Shared LDI 0xa9c5aa58 num_slots 1 num_buckets 1 depth 1 ldi type 3 ldi protocol ipv4 flags 0x8200  : 0x4b88a200 'dpc_rm_svr' detected the 'warning' condition 'There was a failure in communicating with the DPC RM server - possibly it has restarted. Operation may be retried.'   : fib_mgr : (PID=4825) :  -Traceback= 4efe04 474(TRUNCATED)

-----

Conditions:
image info:
RP/0/RP0/CPU0:ott02-sim-09-uut#run cat /etc/bui*txt
Wed Oct 29 19:33:23.105 UTC
### XR Information

User = midhun
Host = sjc-ads-3104
Workspace = /nobackup/midhun/sdev_1027
Lineup = sunstone-dev.lu
XR version = 5.3.0.03C

### Thirdparty Information

Refpoint = thirdparty/opensource/release@tp-graphene2/10
Hostname     : sjc-ads-2908
 Workspace    : /nobackup/aselvana/pts/tp_test
 Source Base  : ios_ena
 Devline      : tp-graphene2.lu
 Devline Ver  : unknown
 Devline Type : ACME Project (Devline uses a project: tp-graphene2%14)

### Calvados Information for architecture

Refpoint = calvados/release@flex-531/5
Built By     : midhun
 Built On     : Mon Oct 27 13:10:31 PDT 2014
 Build Host   : sjc-ads-3104
 Workspace    : /nobackup/midhun/sdev_1027
 Source Base  : ios_ena
 Devline      : sunstone-dev.lu
 Devline Type : ACME Project (Devline uses a project: sunstone-dev%21)
 sunstone-dev   EFR-00000288824   Project
 flex-531       EFR-00000286524   Project
 flex-xr        EFR-00000283233   Project
 ci-531         EFR-00000282550   Lineup
 ci-530         EFR-00000282350   Lineup
 ci-522         EFR-00000280208   Lineup
 ci-521         EFR-00000277817   Lineup
 default        EFR-00000276591   Lineup
RP/0/RP0/CPU0:ott02-sim-09-uut#
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.