05-09-2012 01:36 PM
Greetings fellow Jun'ites,
I am new to Juniper and router config in general, been more systems and *NIX. So, I apologize in advance for any misuse of nomenclature, or if this topic has been covered over and over ad nauseum already.
This is in a lab environment that is air-gapped. I have two M320s, eastcoast and westcoast, with the same hardware setup, running 9.3R4.4. They are talking BGP. All has been working well. All routes have been advertised and received correctly. The hardware is as follows: one router1600 engine, an FCP1 card is in slot FCP0 that has 3 1GB SFP copper PICs, in FCP1 we have an FCP3 with 1 10GB Zenpak PIC. I added a 10GB PIC to the FCP3 which was recognized without incident.
I configured the interface which is now advertised and received without incident. But, on the "eastcoast" router I added a device, 192.168.5.3, on the network, 192.168.5.0/24 off that new card it is not accessible from anywhere else, but on the local M320 itself, only via ping and telnet, but not traceroute. Did the same on the other router, westcoast, with 192.168.1.0/24 and the device 192.168.1.3.
From my limited knowledge the routes are published, I can ping the interfaces, 192.168.1.1 and 192.168.5.1 from all over the network, (we have cisco 3606s hanging off the M320s 1gb interfaces). Also, the device is a Spirent TestCenter with two 10GB interfaces.
Files of config and put of show route for each router are attached.
Solved! Go to Solution.
05-10-2012 01:34 PM - edited 05-10-2012 01:35 PM
It sounds like your Spirent doesn't have a route back to the source, when you ping from the remote device/router. You might need to give your Spirent a default route, pointing to its locally connected router interface.