SG300-52 Can't ping the default gateway

[Geoffrey Diaz]

Hello, 

I recently purchased a new SG300-52 switch. Having trouble pinging the default gateway 192.168.1.254 and connecting to the web panel using the default gateway IP address. When I initially started I was able to ping the gateway IP 192.168.1.254 and access the web interface. I changed the password and then took a break for a few minutes. When I came back I was at the admin panel login screen and tried putting in my credentials but it timed out. Since then I have tried a factory reset twice and still cannot ping. I reinstalled my server OS and reconfigured the NIC. 

I'm using CentOS and have configured the IP as 192.168.1.100 255.255.255.0

[root@web1 ~]# ping 192.168.1.254
PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data.
From 192.168.1.100 icmp_seq=1 Destination Host Unreachable

I had a lot of trouble trying to connect to the console. I ended up having to use some adapters and can now access CLI. 

Server
|
USB to DB9 (serial) adapter
|
Cisco Cable (DB9 to RJ45)
|
Null Model Adapter (RJ45 to DB9)
|
Switch

I have just tried adding the ip to vlan 1 and the gateway is still not pingable from the server. 

switchd0cfa7#show run
config-file-header
switchd0cfa7
v1.4.2.4 / R800_NIK_1_4_194_194
CLI v1.0
set system mode switch

file SSD indicator encrypted
@
ssd-control-start
ssd config
ssd file passphrase control unrestricted
no ssd file integrity control
ssd-control-end cb0a3fdb1f3a1af4e4430033719968c0
!
voice vlan oui-table add 0001e3 Siemens_AG_phone________
voice vlan oui-table add 00036b Cisco_phone_____________
voice vlan oui-table add 00096e Avaya___________________
voice vlan oui-table add 000fe2 H3C_Aolynk______________
voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
voice vlan oui-table add 00d01e Pingtel_phone___________
voice vlan oui-table add 00e075 Polycom/Veritel_phone___
voice vlan oui-table add 00e0bb 3Com_phone______________
hostname switchd0cfa7
username cisco password encrypted 1f44f6ccae8e9b653d4e85db7f0b877816f91edb privilege 15
!
interface vlan 1
ip address 192.168.1.100 255.255.255.0
no ip address dhcp
!
exit

[mipopov]

Hello Geoffrey,

First update the switch to latest firmware:

https://software.cisco.com/download/home/283019669/type/282463181/release/1.4.9.4?i=!pp

Console port (DB9) is direct connection to the switch over RS-232 protocol (serial) and it is not a network protocol. If you are trying to ping the switch over serial connection, it will not respond.

To ping the switch IP you need to connect the NIC of the server to one port that is member of this VLAN1 (by default all the ports are members).

Hope it helps.

Cheers,

Mike

[Geoffrey Diaz]

Thank you. I am now able to ping the switch. I am trying to find a way to change the default-gateway to a different public IP so I can access the switch remotely from web browser. I have searched for a way but everything I have tried does not work. The switch is at a datacenter with one of my servers connected to it by both ethernet and the cisco cable. The server has two NICS and both are connected to the switch. (This is one of the reasons why I could not access the switch because of using the switch netmask and the public IP netmask. Disabling one of the NIC's allowed me to be able to ping the switch but I had to use KVM over IP to access the server to be able to do all of this.)

The uplink from the datacenter is attached to port 48 of the switch. It appears that if I just set up the server NIC using any IP that is given to me by the datacenter it works fine and is pingable from my office, I can ssh into the server. If I change the switch default-gateway to one of those public IP's I can't connect to the switch browser admin panel. I have to login to the console cli and redo everything by 'set system mode router' and then back to 'set system mode switch' which changes it back to default gateway 192.168.1.254. 

Do you know of a way I can find out how to change the default gateway IP to a public IP so i can access from my office? Or is this not recommended? 

[Deepak Kumar]

Hi,

Try to upgrade the Switch and factory reset to the switch (If it is a lab). 

Regards,

Deepak Kumar