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. Take a look at: http://www.juniper.net/techpubs/software/junos/junos83/swconfig83-services/download/tunnel-config.pdf Search for MX960. Hope this helps. Your tunnel should work once you create this association. Kind regards, Truman On 23/12/2009, at 2:49 PM, Jonathan Lassoff wrote: > Excerpts from Truman Boyes's message of Tue Dec 22 18:25:23 -0800 2009: >> Have you enabled the tunnel-services statement at the [ edit chassis fpc >> slot-number pic pic-number] stanza? > > Thanks Truman! > > Nope. I've yet to find reference to this in the documentation relating > to setting up tunnels. Do you have any recommendations for where I find > out more about what this is doing architectually? > > On which slot and pic number do you think I should choose? I read that > the MX's DPCs have built-in tunnel-services PICs along with a number of > fixed interface PICs. > > I assumed I should choose the DPC and PIC number for the upstream > interface that goes towards the tunnel's outer IP destination: > > j...@mx1.sfo2-re0> show configuration chassis fpc 3 > pic 0 { > tunnel-services { > bandwidth 1g; > } > } > > However, I'm still seeing the same ICMPv6 responses, and traffic is not > passing. > > Thanks, > Jonathan > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp