03-20-2019 06:40 AM
We have a router and switch from a customer on our network for testing. The switch is connected to the router. The router is then connected to our switch, which is connected to our Core switch via trunk connection. The core switchis then connected to our FW and the FW is connected to our edge router. The router and switch from our customer is replacing older equipment. So the routes on our hardware has not changed. I do not think it has to do with our equipment, but not sure.
I am having an issue pinging the distant end we are working with, and they are having the same issue. I have followed the following config. The route shows it to be the our edge router to go out the door.
Below is the config.
Any help would be appreciated.
03-20-2019 06:45 AM
Hello,
no config has been posted. Also if possible put together a brief schematic drawing of what your topology looks like in order to avoid confusion about what is connected to what...
03-20-2019 06:50 AM
Hi,
I am having an issue pinging the distant end we are working with, and they are having the same issue. I have followed the following config. The route shows it to be the our edge router to go out the door.
No config has attached and I didn't get your issue. Please share details with some logs.
The router and switch from our customer is replacing older equipment. So the routes on our hardware has not changed. I do not think it has to do with our equipment, but not sure.
Take the full details because I am not aware what your requirement and which is hardware you have. Maybe this router is EOL or resource or performance is not fetting in the customer bucket. Please share some details.
Regards,
Deepak Kumar
03-20-2019 07:31 AM - edited 03-20-2019 07:35 AM
Hello
@gbenoit83 wrote:
The router and switch from our customer is replacing older equipment. So the routes on our hardware has not changed. I do not think it has to do with our equipment, but not sure.
You willl need to make amendments to this router and switch so it can talk you exiting network, you cannot expect for it to work straight off the bat especially if the hardware is coming from an old network!
In any case sounds like you need to create an additional L2/L3 vlan on YOUR core switch with the addressing that of the customer rtr and assign the access port connecting from your switch to this customer rtrs in that vlan, also change any static routes on the customer rtr to point towards the core switch new svi.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide