Hallo @ all,
i wanna enable LDP on a device, which is currently only capable for native IP traffic. If i do this, i need to propagte the loopback0 of this device so, that labels are distributed within the backbone. Afterwards, all traffic destined for that loopback will get a label.
That also means that the attached network (they redistributed from BGP) will also have an MPLS label on it. The next-hop (loopback0) is learned from.
My question is, if there is a way of seperating the traffic, so that some attached networks are routed via IP (without MPLS Label) and the VRF traffic is obviously routed via MPLS? I thought about having another loopback address for the LDP process, but you'll need as well a separate BGP peering for the VPNv4 AFI. I currently don't see any option besides having a kind of VRF lite, separate the traffic via VLAN and bring the VRF traffic on the upstream router into a VRF. But the option doesn't scale that good.
Maybe some of you have some ideas of any other option to solve this.
... View more
yes, we have that problem also when configuring 50ms. I also tried QoS, but when i understand it correctly, BFD packets were sent into prio level 1 by default.
that bundle in my example is is bundle-ether with only one interface, sound strange, but we use it cause future extensions are more easy. on the other hand, we have the same problem also on physical interfaces.
we also have one bundle with 6x10G between two ASR9k running some software and flapping BFD session. From my understanding all six interface must have a problem in that case, because the BFD packet are sent over all six interface in parallel. Also those routers are connected only with patch cable (no leased line or DWDM), i would assume that not all six interface can have a problem at the same time.
... View more
i have problem with flapping BFD session on a bundle-interface. have the following config.
bfd multipath include location 0/0/CPU0 multipath include location 0/1/CPU0 bundle coexistence bob-blb logical ! router isis TEST interface bundle-ether 105 bfd minimum-interval 20 bfd multiplier 3 bfd fast-detect ipv4 bfd fast-detect ipv6 !
RP/0/RSP1/CPU0:Feb 3 15:12:45.823 : isis: %ROUTING-ISIS-5-ADJCHANGE : Adjacency to x-x-x-x (Bundle-Ether105) (L2) Down, BFD session DOWN LC/0/1/CPU0:Feb 3 15:12:45.825 : bfd_agent: %L2-BFD-6-SESSION_REMOVED : BFD session to neighbor 22.214.171.124 on interface Bundle-Ether105 has been removed RP/0/RSP1/CPU0:Feb 3 15:12:50.325 : isis: %ROUTING-ISIS-5-ADJCHANGE : Adjacency to x-x-x-x (Bundle-Ether105) (L2) Up, New adjacency LC/0/1/CPU0:Feb 3 15:12:52.608 : bfd_agent: %L2-BFD-6-SESSION_STATE_UP : BFD session to neighbor 126.96.36.199 on interface Bundle-Ether105 is up LC/0/2/CPU0:Feb 3 15:12:55.293 : bfd_agent: %L2-BFD-6-SESSION_STATE_UP : BFD session to neighbor fe80::b615:1111:1111:1111 on interface Bundle-Ether105 is up
sh bfd counters packet private interface bundle-ether 105 Wed Feb 3 15:16:27.356 CET Bundle-Ether105 Recv Rx Invalid Xmit Delta Async: 10179863 15190 12910224 Echo: 0 0 0 0 sh bfd session interface bundle-ether 105 Wed Feb 3 15:16:51.777 CET Interface Dest Addr Local det time(int*mult) State Echo Async H/W NPU ------------------- --------------- ---------------- ---------------- ---------- BE105 188.8.131.52 0s(0s*0) 60ms(20ms*3) UP No n/a
Problem is not clear to me, because flap are only happening every one or two hours. there are some interface that are working with same config, some interface are not. i'm using typhoon linecard and version 5.1.2. I also had not that aggressive timers, but it's still the same problem.
... View more
Hi all, i have some problem regarding BGP table convergence. There are two router (ASR1K and CRS-3) which have a direct interface and peering with loopback0 adresses. The BGP Peering is established, and prefixes are transfered. However, from ASR1K to CRS-3 the convergence is very slow. The CRS-3 only learnes about 200 prefixes/s. The other direction CRS-3 to ASR1K works as apected, BGP full table is transfered within 30s. This is the output on ASR1K. MTU-Path-Discovery is enabled on both routers. ASR1K#sh ip bgp neighbors x.x.x.x BGP neighbor is x.x.x.x, remote AS xxxx, internal link Description: CRS-3 Inherits from template BGP-TEMPLATE for session parameters BGP version 4, remote router ID x.x.x.x BGP state = Established, up for 2d17h Last read 00:00:23, last write 00:00:02, hold time is 180, keepalive interval is 60 seconds Keepalives are temporarily in throttle due to closed TCP window Does anybody have an idea about this? Best Regards Marco
... View more