In playing with a new CRS317 as a LSR/P-router (with 2 CCR1036’s as LERs/PE-routers), trying out the hardware MPLS forwarding, I’m bumping into an issue…
Initially, TE tunnel LSPs between the CCRs get established with explicit nulls for the P->egress-PE segment. Awesome! The CRS only has to swap the label, which gets done in hardware, so everything is happy (1% CPU, and 7-ish Gbps total flowing through the CRS; no packet loss on a parallel ping, no appreciable jitter.)
But, as soon as the automatic bandwidth adjustment kicks in, the LSPs switch to implicit null for the p->egress-PE segment. Awful! Now the CRS has to pop the label, which can only be done in software, so everything turns foul (100% CPU, about 3Gbps total flowing through the CRS; 80%+ packet loss on a parallel ping, huge jitter.)
I don’t see any way to prevent RSVP-TE from using implicit nulls. LDP has a setting for that, TE doesn’t seem to.
Am I missing something?
If not… MT guys, can you change that behavior?
Thanks,
–Eric