Why on earth would anything that was supposed to work actually work... Sent from my iPhone
> On Feb 1, 2016, at 6:23 PM, Adam Vitkovsky <adam.vitkov...@gamma.co.uk> wrote: > > Action=CREATE Proto=ipv4. Cerr='FIB' detected the 'warning' condition > 'Unsupported operation' : fib_mgr : (PID=7989) : > > Looks like the routing process had some troubles carving up VRF one IPv4 > table in the FIB. > -it's most likely a bug > -but hey it's just a warning condition :) > > adam > > Adam Vitkovsky > IP Engineer > > T: 0333 006 5936 > E: adam.vitkov...@gamma.co.uk > W: www.gamma.co.uk > > This is an email from Gamma Telecom Ltd, trading as “Gamma”. The contents of > this email are confidential to the ordinary user of the email address to > which it was addressed. This email is not intended to create any legal > relationship. No one else may place any reliance upon it, or copy or forward > all or any of it in any form (unless otherwise notified). If you receive this > email in error, please accept our apologies, we would be obliged if you would > telephone our postmaster on +44 (0) 808 178 9652 or email > postmas...@gamma.co.uk > > Gamma Telecom Limited, a company incorporated in England and Wales, with > limited liability, with registered number 04340834, and whose registered > office is at 5 Fleet Place London EC4M 7RD and whose principal place of > business is at Kings House, Kings Road West, Newbury, Berkshire, RG14 5BY. > > > -----Original Message----- >> From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of >> Aaron >> Sent: Monday, February 01, 2016 11:06 PM >> To: cisco-nsp@puck.nether.net >> Subject: [c-nsp] NCS-5001 - MPLS L3VPN Issue >> >> I'm not sure if I'm doing something wrong here or if i'm running into on mpls >> l3vpn/vrf issue. (I already have igp, mpls, and mp-bgp config'd and >> working) >> >> >> >> I create the vrf... add an interface to it... config the bgp vrf stanza, >> commit, >> then suddenly I get errors on the screen. my l3vpn ip address on loopback 1 >> is not reachable either. (I do see the vpnv4 being advertised to and from >> other pe's in the vpn) >> >> >> >> After rollback, errors stop. >> >> >> >> RP/0/RP0/CPU0:eng-lab-5001-1#conf >> >> Mon Feb 1 16:52:20.151 CST >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config)#vrf one >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-vrf)# address-family ipv4 unicast >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-vrf-af)# import route-target >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-vrf-import-rt)# 1:1 >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-vrf-import-rt)# ! >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-vrf-import-rt)# export route-target >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-vrf-export-rt)# 1:1 >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-vrf-export-rt)# ! >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-vrf-export-rt)# ! >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-vrf-export-rt)# >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-vrf-export-rt)#interface Loopback1 >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-if)# vrf one >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-if)# ipv4 address 111.222.131.220 >> 255.255.2$ >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-if)#! >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-if)#router bgp 64512 >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-bgp)# >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-bgp)# vrf one >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-bgp-vrf)# rd 10.101.12.244:1 >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-bgp-vrf)# address-family ipv4 unicast >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-bgp-vrf-af)# maximum-paths ibgp 3 >> unequa$ >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-bgp-vrf-af)# redistribute connected >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-bgp-vrf-af)#commi >> >> Mon Feb 1 16:52:42.100 CST >> >> RP/0/RP0/CPU0:eng-lab-5001-1(config-bgp-vrf-af)# >> >> >> >> RP/0/RP0/CPU0:eng-lab-5001-1#RP/0/RP0/CPU0:Feb 1 16:52:57.169 : >> fib_mgr[165]: %ROUTING-FIB-3-PLATF_UPD_FAIL : FIB platform update >> failed: >> Obj=DATA_TYPE_LOADINFO[ptr=0x8be02618,refc=0x2,flags=0x >> >> 8441] Action=CREATE Proto=ipv4. Cerr='FIB' detected the 'warning' condition >> 'Unsupported operation' : fib_mgr : (PID=7989) : -Traceback= 7f3a251c3638 >> 54fd2e 5507d5 551a0a 7f3a251b85ed 5519a0 4 >> >> c5c96 4c78ea 6106dc 616310 619403 624fd3 62ea9a 44a7ef 46cf3a 46d41e >> >> RP/0/RP0/CPU0:Feb 1 16:52:57.169 : fib_mgr[165]: %ROUTING-FIB-3- >> PD_FAIL : >> FIB platform error: fib_ldi_platform_update 2076: PD action CREATE failed for >> passed_ldi 0x8be02618 type DATA_TYPE_LOAD >> >> INFO flags 0x8441. Shared LDI 0x8be02618 num_slots 1 num_buckets 1 depth >> 2 ldi type 1 ldi protocol mpls flags 0x8441 : 0x4ff40400 'FIB' detected the >> 'warning' condition 'Unsupported operation' >> >> : fib_mgr : (PID=7989) : -Traceback= 5507d5 551a0a 7f3a251b85ed 5519a0 >> 4c5c96 4c78ea 6106dc 616310 619403 624fd3 62ea9a 44a7ef 46cf3a 46d41e >> 44806c >> 44f283 >> >> RP/0/RP0/CPU0:eng-lab-5001-1# >> >> RP/0/RP0/CPU0:eng-lab-5001-1#RP/0/RP0/CPU0:Feb 1 16:53:12.170 : >> fib_mgr[165]: %ROUTING-FIB-3-PLATF_UPD_FAIL : FIB platform update >> failed: >> Obj=DATA_TYPE_LOADINFO[ptr=0x8be01f60,refc=0x1,flags=0x >> >> 8441] Action=CREATE Proto=ipv4. Cerr='FIB' detected the 'warning' condition >> 'Unsupported operation' : fib_mgr : (PID=7989) : -Traceback= 7f3a251c3638 >> 54fd2e 55a9c2 5fbb0b 4dabea 4f4eb0 4f5d80 >> >> 5b2412 5b3460 43321a 7f3a236aca01 7f3a236be32e 4224de 44043e >> 3031c07254 >> >> RP/0/RP0/CPU0:Feb 1 16:53:12.170 : fib_mgr[165]: %ROUTING-FIB-3- >> PD_FAIL : >> FIB platform error: fib_ldi_platform_update 2076: PD action CREATE failed for >> passed_ldi 0x8be01f60 type DATA_TYPE_LOAD >> >> INFO flags 0x8441. Shared LDI 0x8be01f60 num_slots 1 num_buckets 1 depth >> 2 ldi type 1 ldi protocol mpls flags 0x8441 : 0x4ff40400 'FIB' detected the >> 'warning' condition 'Unsupported operation' >> >> : fib_mgr : (PID=7989) : -Traceback= 55a9c2 5fbb0b 4dabea 4f4eb0 4f5d80 >> 5b2412 5b3460 43321a 7f3a236aca01 7f3a236be32e 4224de 44043e >> 3031c07254 >> >> >> >> RP/0/RP0/CPU0:eng-lab-5001-1#show configuration commit changes last 1 >> >> Mon Feb 1 16:53:19.427 CST >> >> Building configuration... >> >> !! IOS XR Configuration version = 6.0.0 >> >> vrf one >> >> address-family ipv4 unicast >> >> import route-target >> >> 1:1 >> >> ! >> >> export route-target >> >> 1:1 >> >> ! >> >> ! >> >> ! >> >> interface Loopback1 >> >> vrf one >> >> ipv4 address 111.222.131.220 255.255.255.255 >> >> ! >> >> router bgp 64512 >> >> vrf one >> >> rd 10.101.12.244:1 >> >> address-family ipv4 unicast >> >> maximum-paths ibgp 3 unequal-cost >> >> redistribute connected >> >> ! >> >> ! >> >> ! >> >> end >> >> RP/0/RP0/CPU0:eng-lab-5001-1#rollback configuration >> coRP/0/RP0/CPU0:Feb 1 >> 16:53:27.171 : fib_mgr[165]: %ROUTING-FIB-3-PLATF_UPD_FAIL : FIB >> platform update failed: Obj=DATA_TYPE_LOADINFO[ptr=0x8 >> >> be02618,refc=0x1,flags=0x8441] Action=CREATE Proto=ipv4. Cerr='FIB' >> detected the 'warning' condition 'Unsupported operation' : fib_mgr : >> (PID=7989) : >> -Traceback= 7f3a251c3638 54fd2e 55a9c2 5fb >> >> b0b 4dabea 4f4eb0 4f5d80 5b2412 5b3460 43321a 7f3a236aca01 7f3a236be32e >> 4224de 44043e 3031c07254 >> >> RP/0/RP0/CPU0:Feb 1 16:53:27.171 : fib_mgr[165]: %ROUTING-FIB-3- >> PD_FAIL : >> FIB platform error: fib_ldi_platform_update 2076: PD action CREATE failed for >> passed_ldi 0x8be02618 type DATA_TYPE_LOAD >> >> INFO flags 0x8441. Shared LDI 0x8be02618 num_slots 1 num_buckets 1 depth >> 2 ldi type 1 ldi protocol mpls flags 0x8441 : 0x4ff40400 'FIB' detected the >> 'warning' condition 'Unsupported operation' >> >> : fib_mgr : (PID=7989) : -Traceback= 55a9c2 5fbb0b 4dabea 4f4eb0 4f5d80 >> 5b2412 5b3460 43321a 7f3a236aca01 7f3a236be32e 4224de 44043e >> 3031c07254 >> >> RP/0/RP0/CPU0:eng-lab-5001-1#rollback configuration ? >> >> last Rollback last <n> commits made >> >> to Rollback up to (and including) a specific commit >> >> to-exclude Rollback up to (and excluding) a specific commit >> >> 1000000110 Commit ID >> >> 1000000109 Commit ID >> >> . >> >> RP/0/RP0/CPU0:eng-lab-5001-1#rollback configuration last 1 >> >> Mon Feb 1 16:53:32.835 CST >> >> Loading Rollback Changes. >> >> Loaded Rollback Changes in 1 sec >> >> Committing. >> >> 19 items committed in 1 sec (18)items/sec >> >> Updating. >> >> Updated Commit database in 1 sec >> >> Configuration successfully rolled back 1 commits. >> >> RP/0/RP0/CPU0:eng-lab-5001-1# >> >> >> >> RP/0/RP0/CPU0:eng-lab-5001-1#sh install committed >> >> Mon Feb 1 17:01:12.242 CST >> >> Node 0/RP0/CPU0 [RP] >> >> Boot Partition: xr_lv1 >> >> Committed Packages: 4 >> >> ncs5k-xr-6.0.0 version=6.0.0 [Boot image] >> >> ncs5k-mgbl-2.0.0.0-r600 >> >> ncs5k-mpls-1.0.0.0-r600 >> >> ncs5k-k9sec-1.0.0.0-r600 >> >> >> >> RP/0/RP0/CPU0:eng-lab-5001-1#sh platform >> >> Mon Feb 1 17:01:24.460 CST >> >> Node name Node type Node state Admin state >> Config state >> >> ---------------------------------------------------------------------------- >> ------- >> >> 0/RP0 NCS-5001 OPERATIONAL UP >> NSHUT >> >> 0/FT0 NCS-5001-FN-FR OPERATIONAL UP >> NSHUT >> >> 0/FT1 NCS-5001-FN-FR OPERATIONAL UP >> NSHUT >> >> RP/0/RP0/CPU0:eng-lab-5001-1# >> >> >> >> >> >> >> >> >> >> Aaron >> >> _______________________________________________ >> cisco-nsp mailing list cisco-nsp@puck.nether.net >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ > > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/