If you create a static route for the loopback instead of rip does it work? Is there a firmware version difference between the switches where it works and the ones where it doesn’t? Are you able to access the web gui via the loopback?
When RIP is removed from the switch and just a default route (floating static) is placed on the switch, both telnet to the loopback and to the vlan interface works. The upstream router has a route to point the loopback to the vlan interface.
The issue with ping working and telnet not working was due to a stateful firewall being the default gateway and the routed path being asynchronous. When an internal router was used for the default gateway work the system works.
Once the default gateway was removed and the RIP command were reissued to the vlan interfaces and the rip routes confirmed in the routing table the issue came back.
We are filtering the routes advertised via RIP due to the number of router that the N2000 can handle. We would like only advertise the 10.0.0.0/8 router to point back to the internal routers.
With the testing below the issue seems to be that telnet \ ssh \ https services will not honor the 10.0.0.0/8 route on the switch. When a /16 route to the client is inserted the system works. The added /16 route is the same destination of the 10.0.0.0/8 route. If the route was added with RIP or static did not matter. With the prior configuration the 0.0.0.0/0 was not honored either.
Some additional tests were performed to see were the routes break, different netmasks were tested. The routes were inserted as static routes. The route was the only non-connected route in the routing table.
route/mask - result
10.40.0.0/16 - Works
10.40.0.0/15 - Works
10.40.0.0/14 - Works
10.40.0.0/13 - Works
10.32.0.0/12 - Works
10.32.0.0/11 - Works
10.0.0.0/10 - Broken
10.0.0.0/9 - Broken
10.0.0.0/8 - Broken
==== Tests ====
More testing was performed:
> Client - 10.40.50.51
* Test1: Removed the distribute command to enable full routing table.
* Result - Telnet works (loopback and vlan interface)
* Test2: Used distribute command to allow 10.0.0.0/8 network
* Result: Telnet does not work and ping does not work (loopback and vlan interface)
----Routing Tables----
No default gateway is configured.
R *10.0.0.0/8 [120/2] via 10.8.0.10, Vl100
R *10.0.0.0/16 [120/2] via 10.8.0.10, Vl100
C *10.8.0.0/24 [0/1] directly connected, Vl100
C *10.250.8.105/32 [0/1] directly connected, Lo0
----Traceroute from switch to client----
Traceroute to 10.40.50.51 ,30 hops max 0 byte packets:
Hop Count = 1 Last TTL = 1 Test attempt = 1 Test Success = 0
DELL-Josh Cr
Moderator
•
9.5K Posts
0
July 14th, 2015 18:00
Hi,
If you create a static route for the loopback instead of rip does it work? Is there a firmware version difference between the switches where it works and the ones where it doesn’t? Are you able to access the web gui via the loopback?
Try updating the firmware to the latest version. There were some fixes to loopback interface behavior and switches not responding to telnet or ssh. http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=N8K2G&fileId=3461947867&osCode=NAA&productCode=networking-n2000-series&languageCode=EN&categoryId=NI
Henry Bennett
2 Posts
0
July 15th, 2015 10:00
Thanks for the reply.
The web gui , ssh and telnet all behave the same.
When RIP is removed from the switch and just a default route (floating static) is placed on the switch, both telnet to the loopback and to the vlan interface works. The upstream router has a route to point the loopback to the vlan interface.
The issue with ping working and telnet not working was due to a stateful firewall being the default gateway and the routed path being asynchronous. When an internal router was used for the default gateway work the system works.
Once the default gateway was removed and the RIP command were reissued to the vlan interfaces and the rip routes confirmed in the routing table the issue came back.
We are filtering the routes advertised via RIP due to the number of router that the N2000 can handle. We would like only advertise the 10.0.0.0/8 router to point back to the internal routers.
With the testing below the issue seems to be that telnet \ ssh \ https services will not honor the 10.0.0.0/8 route on the switch. When a /16 route to the client is inserted the system works. The added /16 route is the same destination of the 10.0.0.0/8 route. If the route was added with RIP or static did not matter. With the prior configuration the 0.0.0.0/0 was not honored either.
Some additional tests were performed to see were the routes break, different netmasks were tested. The routes were inserted as static routes. The route was the only non-connected route in the routing table.
route/mask - result
10.40.0.0/16 - Works
10.40.0.0/15 - Works
10.40.0.0/14 - Works
10.40.0.0/13 - Works
10.32.0.0/12 - Works
10.32.0.0/11 - Works
10.0.0.0/10 - Broken
10.0.0.0/9 - Broken
10.0.0.0/8 - Broken
==== Tests ====
More testing was performed:
> Client - 10.40.50.51
* Test1: Removed the distribute command to enable full routing table.
* Result - Telnet works (loopback and vlan interface)
* Test2: Used distribute command to allow 10.0.0.0/8 network
* Result: Telnet does not work and ping does not work (loopback and vlan interface)
----Routing Tables----
No default gateway is configured.
R *10.0.0.0/8 [120/2] via 10.8.0.10, Vl100
R *10.0.0.0/16 [120/2] via 10.8.0.10, Vl100
C *10.8.0.0/24 [0/1] directly connected, Vl100
C *10.250.8.105/32 [0/1] directly connected, Lo0
----Traceroute from switch to client----
Traceroute to 10.40.50.51 ,30 hops max 0 byte packets:
Hop Count = 1 Last TTL = 1 Test attempt = 1 Test Success = 0
--------------------------------------------------
* Test3: Used IP ROUTE command add 10.40.0.0/16 -> 10.8.0.10 route. (same dest as 10.0.0.0/8)
* Result: Telnet Works and Ping works (loopback and vlan interface)
----Routing Table----
R *10.0.0.0/8 [120/2] via 10.8.0.10, Vl100
R *10.0.0.0/16 [120/2] via 10.8.0.10, Vl100
C *10.8.0.0/24 [0/1] directly connected, Vl100
S *10.40.0.0/16 [1/0] via 10.8.0.10, Vl100
C *10.250.8.105/32 [0/1] directly connected, Lo0
----Traceroute from switch to client----
1 10.8.0.10 167 ms 167 ms 167 ms
2 [obfuscated] 3640 ms 3640 ms 3640 ms
3 [obfuscated] 1828 ms 1828 ms 1828 ms
4 [obfuscated] 1845 ms 1845 ms 1845 ms
5 10.40.1.1 16 ms 1016 ms 16 ms
6 10.40.50.51 858 ms 858 ms 858 ms
--------------------------------------------------
*Test4: Used RIP distribute to allow the add the route (same dest as 10.0.0.0/8)
*Result: Telnet works and RIP works (loopback and vlan interface)
----Routing Table----
R *10.0.0.0/8 [120/2] via 10.8.0.10, Vl100
R *10.0.0.0/16 [120/2] via 10.8.0.10, Vl100
C *10.8.0.0/24 [0/1] directly connected, Vl100
R *10.40.0.0/16 [120/2] via 10.8.0.10, Vl100
C *10.250.8.105/32 [0/1] directly connected, Lo0
----Traceroute from Switch to Client ----
1 10.8.0.10 167 ms 167 ms 167 ms
2 [obfuscated] 3640 ms 3640 ms 3640 ms
3 [obfuscated] 1828 ms 1828 ms 1828 ms
4 [obfuscated] 1845 ms 1845 ms 1845 ms
5 10.40.1.1 16 ms 16 ms 16 ms
6 10.40.50.51 858 ms 858 ms 858 ms
--------------------------------------------------