The web gui, ssh and telnet all behave the same. Username "admin" password XXXXXXXXXXXXXXXXXXXXXXXXXXX privilege 15 encryptedĪaa authentication login "Management" radius localĪaa authentication enable "Management" noneĪaa authorization exec "Management" radius local It feels like the system is not using the routing table or that the TCP connection is not completing due to some stateful connection checking out differing interfaces. This the first N2000 that I have converted to RIP I have other N-Series (N3048 and N2048) that is showing the same issues and I have some that actually work fine (all the working are N3000). * Syslog based logging still work from the router * Switch is pingable via the loopback and the vlan interface * Can use networks that are directly connected to the switch to connect. * Cannot use telnet \ ssh \ https to contact the switch from routed networks * RIPv2 from network delivers the route 0.0.0.0/0 to the switch. * Added RIPv2 routing to transmit the loopback interface's address * Added loopback address 10.250.8.105/32 to the loopback0 interface I made the following changes to the switch and the switch was no longer available to telnet \ ssh \https. I had a N2048 switch connected to our network with an IP address on a vlan with a static default route.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |