Weird InterVLan Routing issue

[ssbauer3275]

We currently have 3 VLANs

Vlan1 - All servers, network devices and a few special cases of PC's

Vlan2 - Building B

Vlan3 - Building A

Are server room is in building b with our virtual and storage solution but we moved our archiving storage solution to building A to build a disaster recovery solution.

Anyone on VLAN1 regardless which building they are in can access the archiving storage with no issues.  Anyone on VLAN2 or VLAN3 from both buildings can access the archiving storage but it is dramatically slow.

We have moved the cable to difference ports, switch cables, changed switches but still no resolution.

The switch trunk port is set to untagged VLAN1 and tagged for VLAN2 and VLAN3.  We also set the port the storage server is to untagged VLAN1 and tagged VLAN/VLAN3 but that didnt help.

No error logs and no idea whatelse to do.

We are thinking about moving the storage back to building b server room to see if it fixes the error but would like to figure this out without moving it.

[Richard Burts]

If I am understanding your description correctly then anyone (in either building) that is in vlan 1 can access archiving storage with no issue and everyone (no matter which building) has slow response. That certainly sounds like the problem is something to do with routing between vlans.

Can you tell us if someone in vlan 2 attempts to access something in vlan 3 whether that is also slow?

Can you tell us what kind of switches these are? Are both switches doing routing between vlans or is it just one switch, and if so then which switch is routing between vlans?

I am a little puzzled at your statement that "We also set the port the storage server is to untagged VLAN1 and tagged VLAN/VLAN3". Is the server on a trunk port or an access port?

HTH

Rick 

[ssbauer3275]

If someone on vlan2 tries to access a PC in vlan3...no issues.

The switches are SG300's.  We have 1 core switch in building b doing all the routing and all the other switches go directly back to the core switch via fiber.

The port that the storage solution is on a trunk port.

[Richard Burts]

Thanks for the additional information. It raises a couple of possibilities:

- is it possible that spanning tree is blocking ports that would provide more direct access from the clients to the storage server?

- is it possible that there is a duplex mismatch between the switch interface and the server interface?

HTH

Rick

[ssbauer3275]

- is it possible that spanning tree is blocking ports that would provide more direct access from the clients to the storage server? - We never setup spanning tree so I am not sure

- is it possible that there is a duplex mismatch between the switch interface and the server interface? - They are both set at auto and running 1000 Full

Than you for your quick replies