08-31-2011 08:24 AM - edited 03-07-2019 01:59 AM
For some reason I cannot telnet to the management IP address of our coreswitch (I can connect to other interfaces btw).
The management IP address is 192.168.2.1. I am trying to telnet to this address from a different vlan (192.168.13.0/24).
This switch is currently setup for IP routing.
This is the routing table from the 3750
------------------------------------------------------
Gateway of last resort is 192.168.9.3 to network 0.0.0.0
C 192.168.13.0/24 is directly connected, Vlan913
S 192.168.15.0/24 [1/0] via 192.168.9.1
S 204.110.216.0/24 [1/0] via 192.168.9.1
C 192.168.9.0/24 is directly connected, Vlan909
S 192.168.10.0/24 [1/0] via 192.168.9.3
172.17.0.0/23 is subnetted, 2 subnets
S 172.17.4.0 [1/0] via 192.168.9.6
C 172.17.2.0 is directly connected, Vlan762
C 192.168.55.0/24 is directly connected, Vlan955
S 204.110.213.0/24 [1/0] via 192.168.9.1
S 204.110.212.0/24 [1/0] via 192.168.9.1
192.168.5.0/24 is variably subnetted, 5 subnets, 2 masks
S 192.168.5.81/32 [1/0] via 192.168.9.1
S 192.168.5.63/32 [1/0] via 192.168.9.1
S 192.168.5.62/32 [1/0] via 192.168.9.1
S 192.168.5.49/32 [1/0] via 192.168.9.1
S 192.168.5.0/24 [1/0] via 192.168.9.1
S 204.110.215.0/24 [1/0] via 192.168.9.1
S 204.110.214.0/24 [1/0] via 192.168.9.1
S 192.168.7.0/24 [1/0] via 192.168.9.3
S 204.110.209.0/24 [1/0] via 192.168.9.1
S 192.168.50.0/24 [1/0] via 192.168.9.1
S 204.110.208.0/24 [1/0] via 192.168.9.1
C 192.168.2.0/24 is directly connected, Vlan1
S 204.110.211.0/24 [1/0] via 192.168.9.1
S 204.110.210.0/24 [1/0] via 192.168.9.1
S* 0.0.0.0/0 [1/0] via 192.168.9.3
Interface IP-Address OK? Method Status Protocol
Vlan1 192.168.2.1 YES NVRAM up up
Vlan762 172.17.2.255 YES NVRAM up up
Vlan909 192.168.9.2 YES NVRAM up up
Vlan913 192.168.13.1 YES NVRAM up up
Vlan955 192.168.55.1 YES NVRAM up up
The host IP address is 192.168.13.11/24 DG 192.168.13.1
If I connect to the switch on 192.168.13.1 I can then telnet from there
to anything on the 192.168.2.0 subnet.
Any ideas?
Solved! Go to Solution.
09-01-2011 11:05 AM
Yeah, that's a given except for it gives my problems.
c:\>route delete 192.168.2.0
The route specified was not found.
I'll figure out though. Thanks again for everyones help.
09-01-2011 11:33 AM
hi,
you can't delete this route this is a normal route entered in the table from the OS, the route for the subnet always points out the interface in this subnet.
Regards.
Alain.
09-01-2011 12:04 PM
I actually disabled that management NIC. It was inteded a long time ago, to just be used for management traffic,
but there really isn't a lot of management traffic to begin with. And it's a very small network in that remote office.
So I just cleared the windows routing table and added a static default route to 192.168.13.1.
'route add 0.0.0.0 mask 0.0.0.0 192.168.13.1'
Once I did that everything worked fine.
Thanks a whole bunch guys!! Kills me I didn't think of "route print"
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