> [..] > > You'll still need mpls and traffic-eng tunnels configured on each > > interface of the label path. You can verify with show mpls > interfaces. > > Yeah, figured that one out, that "mpls traffic-eng tun" is needed on > all MPLS-enabled interfaces (... that would carry this tunnel). Need > to test that next, with a shorter path, don't want to touch all the > production network right now. > > > And then there's the IGP. > > Uh, what exactly?
It's been far too long since I brushed up on MPLS-TE, but I've never tried to build an explicit label path without OSPF/ISIS. Your application is different, so I'm interested to see you get it working. Cory _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
