Beny, I'de have to check but I dont believe vrf-table-label is currently supported on PE-P or PE-PE interfaces where the you use agg-sonet. If you need to make this work with agg-sonet, you will need a tunnel- pic (or vt interface) as described at this link:
http://tinyurl.com/yrjbt5 To work around this, you may consider using multiple LSPs between the PEs. The LSPs will load-balance the traffic based on the hash algorithm. There are a few knobs available that can influence what attributes are considered for the hash calculation. This coupled with auto-bandwidth may give you a nice spread. Hope this helps. -Ariff On May 20, 2007, at 7:04 PM, Beny Dwi Setyawan wrote: > Dear All, > > > > I'm having problem when using aggregate sonet for MPLS backbone, > the vrf > routing table established on PE01 from PE02, but I can't reach the > routing > from PE01. > > I used vrf-table-label since I don't have LS-PIC on the PE02 for vt > interfaces. Does anyone of you ever experience this problem before? > Bellow is the network : > > > > PE01 <-- STM-1 --> P-Core-1 <-- aggregate sonet (4 x STM-1) --> > P-Core-2 > <-- aggregate sonet (2 x STM-1) --> PE02 > > Please need your suggestion since I don't have available PIC on > PE02 if > the > solution is to add LS-PIC on it for vt interfaces. > > > > Regards, > > > > Beny D Setyawan > > > > > > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp