Jump to content

Recommended Posts

Posted

I'm stumped!

 

In our disaster recovery site we have a Cisco 2960G switch, which connects together a QNAP NAS device to a VMWare ESXi box. They ain't talking to each other after a power cut yesterday!

 

This was set up by our previous network support company, anyway the switch itself has a IP of 10.201.95.246 and a subnet of 255.255.0.0 for VLAN 1 which is our switch IP range and presumably so it can be managed.

 

The QNAP and ESXi box should be talking over VLAN500 which has a blank IP/subnet, ports 17-18 and 19-20 are all set up for this VLAN500, as P01 and P02 (EtherChannels?).

 

Ignoring the ESXi box for a moment, Ports 2 and 3 on the QNAP connect back to Ports 17-18 on the switch and on the QNAP 2-3 has been assigned as IP 192.168.130.10 Subnet 255.255.255.0 Gateway 192.168.130.254 VLAN 500.

 

So to simplify things I configured Port 13 on the Cisco to VLAN 500, plugged a laptop in set IP 192.168.130.13 Subnet 255.255.255.0 Gateway 192.168.130.254...but it won't receive any traffic or ping the QNAP so I'm now confused as to what to do next!

Posted

Can you ping the ESXI box? or a secondary laptop if you plug another into the VLAN500? Often find some NAS's unhappy with their NICs after hard reboots.

 

Steve

  • Thanks 1
Posted

Well the NM decided to have a look too and he didn't get much further! (We even did a factory reset on the switch and just set it up from scratch to try and work it out but to no avail!)

 

We didn't quite understand where the 192.168.130.254 gateway is coming from either. Tomorrow's plan is to stick a basic 5 port switch in just to try and get the laptop talking to either the QNAP or the ESX box!

Posted

Can you ping the others though? Ignoring the NAS?

 

As the NAS can be setup as a DHCP server (Obviously normally disabled), and if you can't ping that either sounds more like the settings on the NAS fubared.

 

The switch may be working fine :)

 

Steve

Posted
Might be worth just trying the qnap with one network cable connected, and into a different port on the switch - so go configure another port to vlan 500 - just to see if trunking is contributing to the issue. As one of the other posters said, get 2 laptops in vlan 500 talking to each other on the same ports first so you know the ports are fine.
Posted

What info do you get back when you do show run int vlan 500? Protocol and Interface up?

Have you tried connecting to the NAS with NIC card connected?

Posted

Plug 2 laptops in VLAN 500 and try and ping each other.

 

Are all the devices you are trying to communicate with in the same subnet?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...