> From: Jonathan Lassoff <[email protected]> > Date: Tue, 22 Dec 2009 23:10:54 -0800 > Sender: [email protected] > > Excerpts from Truman Boyes's message of Tue Dec 22 20:12:34 -0800 2009: > > Hi Jonathan, > > > > You can use any of your DPCs. On non-MX JUNOS routers you need to have > > tunnel > > pics (ie. packet that needs to be encapsulated/tunneled/etc will switch from > > PFE to PIC to PFE). MX does not require this because you can make the DPC > > perform tunnel-services. > > > > Once you create the tunnel-services function on the DPC, you can associate > > the > > IPIP tunnel interface with the tunnel service. Ie. Change the IPIP.0 to: > > ip-3/0/0.0, which corresponds to your FPC 3 PIC 0, port 0 unit 0. > > > That seems to have done the trick. > > One thing I found when trying this on my platform is that configuring: > > fpc 3 { > pic 0 { > tunnel-services { > bandwidth 1g; > } > } > } > > Which is: > > FPC 3 REV 15 750-021157 xxxxxx DPCE 40x 1GE R TX > CPU REV 03 710-022351 xxxxxx DPC PMB > PIC 0 BUILTIN BUILTIN 10x 1GE(LAN) RJ45 > > Yields an ip-3/0/10, instead of the ip-3/0/0 that's shown as an example in > the documentation. > > I configured this, and traffic passes just fine.
On a GE PIC (1/4 of a DPC, not a physical PIC) the tunnel "PIC" supports only GE capacity and "steals" it from the other ports. Since the physical GE porta are 3/0/0-3/0/9, the pseudo-PIC for the tunnel is labeled 3/0/10. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [email protected] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
