I'm not really sure why or what has changed. We have a 3120X-S that is not able to reach anything outside its network but external sources are able to reach the file share that resides on the blade. Here is the config information:
#sh run
Building configuration...
Current configuration : 7220 bytes
!
! Last configuration change at 17:41:58 EDT Mon Apr 8 2019 by
! NVRAM config last updated at 16:38:13 EST Wed Mar 6 2019 by
!
version 15.0
no service pad
service timestamps debug datetime localtime
service timestamps log datetime localtime
service password-encryption
!
hostname MIC0002-BL
!
boot-start-marker
boot-end-marker
!
enable secret 5 xyz
enable password 7 xyz
!
username xyz privilege 15 secret 5 *xyz*
aaa new-model
!
!
aaa authentication login default local group radius
aaa authentication login NETWORK_ADMIN group radius local
aaa authentication login LOCAL_ADMIN local
aaa authentication dot1x default group radius
aaa authorization network default group radius local
aaa accounting dot1x default start-stop group radius
!
!
!
!
!
!
aaa session-id common
clock timezone EST -5 0
clock summer-time EDT recurring
switch 1 provision ws-cbs3120x-s
system mtu routing 1500
!
!
ip domain-name xyz.com
!
!
spanning-tree mode pvst
spanning-tree extend system-id
!
vlan internal allocation policy ascending
!
ip ssh version 2
!
////Interface Info\\\
!
interface Vlan1
no ip address
shutdown
!
interface Vlan8
ip address 10.15.8.9 255.255.255.0
ip helper-address 10.15.8.20
!
interface Vlan100
ip address 10.15.1.25 255.255.255.0
!
interface Vlan900
ip address 10.255.0.12 255.255.254.0
!
ip default-gateway 10.15.1.25
ip http server
ip http secure-server
!
snmp-server group SNMPv3_MIC_Group v3 priv write SNMPv3_MIC_View
!
!
radius server XYZ
address ipv4 10.15.8.21 auth-port 1812 acct-port 1813
key 7 "XYZ"
!
radius server XYZ
address ipv4 10.8.8.19 auth-port 1812 acct-port 1813
key 7 "XYZ"
\\\\\//////
#sh ip route
Default gateway is 10.15.1.25
Host Gateway Last Use Total Uses Interface
10.8.8.89 10.15.1.2 0:01 32382 Vlan100
The 10.8.8.89 doesn't even reside on the switch and is using the wrong gateway. I have tried to remove it, but its not built into the CLI so it errors out. The new gateway is 10.15.1.8. I can ping the gateway and other resources locally but nothing externally.
#ping 10.15.1.8
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.15.1.8, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/205/1015 ms
#ping 10.15.8.20
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.15.8.20, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/8 ms
#ping 10.15.15.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.15.15.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
#ping 10.8.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.8.1.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
I wouldn't be to worried but I am not able to remote (SSH or Telnet) without going through our core switch.
Thoughts?
