Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi All,I am running a lab using Cisco xrd 7.11.2 control-plane on ContainerLab.In the lab topology I have an ASBR using InterAS-Option-C to exchange IPv6 prefixes with another AS. That ASBR is also a PE router for a VPNv4 and VPNv6 services.VPNv4 wor...
Hi,I am testing in the lab trying to stitch an mpls-te tunnel to an sr-te tunnel.So basically, path from pe2 to pe1 should be traffic-engineered and should use both mpls-te and sr-te for specific reasons. It should be as follows:Pe1-P3-Cr1-[P1] = MPL...
In lab testing with MPLS-TE and SR-TE I see that with MPLS-TE policy and tunnel active, when SR-TE policy is configured, the route announced by SR-TE takes preference over MPLS-TE.Following is the output from MPLS-TE:RP/0/RP0/CPU0:pe2#sh route 10.0.0...
Hi All,I am trying to find out the maximum amount of flowspec prefixes that is supported by ASR9k, ASR9900, NCS55A1, and NCS57B.Please advise providing relevant links as I have been searching (Cisco community, release notes, implementation guides, ar...
Hello,I wanted to find out if there was a work around for this issue, on IOSXR code 6.5.3, which does not have the option to specify "bind-source interface <SOURCE_INTERFACE>". Regards,Abid Ghufran
Hi,Testing further, I have not found a way to have either the ERO or the RRO carry the SR-TE BSUID as the final mpls label, however I have found a slightly complex way of achieving the following result:Pe1-P3-Cr1-[P1] = MPLS-Te[P1]-P4-Cr2-P2-Pe2 = SR...
ISIS interface metric is as default.Following is the configuration for mpls-te:RP/0/RP0/CPU0:pe2#sh run explicit-path name PATH-TO-Pe1_1
Thu Aug 6 12:57:22.781 UTC
explicit-path name PATH-TO-Pe1_1
index 10 next-address strict ipv4 unicast 10.0.0.1...
