I have a Cisco 2610 router in a local county complex that houses 2 different agencies. I have separated their networks by using Vlans.
I use the single ethernet interface with one sub-interface for my router connection to the trunk port of the switch. I am using dot1q 2 encapsulation on the subinterface for my Vlan. I am using RIP as the routing protocol.
This config has been working for the past month. Now the router will not route any packets. While telnetted into the router, I can ping every device on each subnet. From every device, I can ping the router interface that is on that subnet. I CANNOT ping the opposite router interface, nor any device on the opposite subnet.
I have tried erasing the starting-config and reloading my saved one via TFTP. I have also re-loaded my IOS version (thinking something could have become corrupted) Neither one worked. I have erased the starting-config and reloaded and re-wrote the running config from scratch... still the same thing.
Has anyone else seen this happen? could it possibly be a hardware malfunction? Nothing on the network has been changed in any way. It just stopped routing =(
Thank you,
Matt
I use the single ethernet interface with one sub-interface for my router connection to the trunk port of the switch. I am using dot1q 2 encapsulation on the subinterface for my Vlan. I am using RIP as the routing protocol.
This config has been working for the past month. Now the router will not route any packets. While telnetted into the router, I can ping every device on each subnet. From every device, I can ping the router interface that is on that subnet. I CANNOT ping the opposite router interface, nor any device on the opposite subnet.
I have tried erasing the starting-config and reloading my saved one via TFTP. I have also re-loaded my IOS version (thinking something could have become corrupted) Neither one worked. I have erased the starting-config and reloaded and re-wrote the running config from scratch... still the same thing.
Has anyone else seen this happen? could it possibly be a hardware malfunction? Nothing on the network has been changed in any way. It just stopped routing =(
Thank you,
Matt