Solved!
Go to SolutionVLANning issues on MXL blades
Hi,
I have a new M100e enclosure with a PS4110xs SAN, a few blade servers and two Force10 MXL switches (switches and SAN on fabric A)
I have it all set up and working fine, but using the default VLAN for everything
I want to hook the switches up to a Juniper EX3300 via SFP+ ports and route the SAN subnet out so that I can remotely connect to the management IP of the EqualLogic for VMM integration
However, whenever I try and put the SAN ports into a separate VLAN - even before I look into trunking to the Juniper - I lose all connectivity on the SAN network.
I've created a new VLAN (VLAN120) but as soon as I put ports into it they cannot ping each other.
int vlan120
tagged te0/1 (This is the SAN port)
tagged te0/12 (this is one server)
tagged te0/16 (this is the other server)
as soon as I do that I lose all connectivity to the SAN and the servers cannot ping each other over the iSCSI network.
I've tried using 'untagged' intead of 'tagged' with the same effect.
The VLAN is active (no shut)
I'm at a loss as to what the issue is.
Any help gratefully received.
Mark.
DELL-Josh Cr
Community Manager
•
9699 Posts
•
43744 Points
1214
0
Posted March 16th, 2015 16:00
Hi Mark,
That looks correct for putting them in VLAN 120. Do they work when on VLAN 1? Does VLAN 120 use a different subnet? Is routing enabled?
DELL-Josh Cr
Community Manager
•
9699 Posts
•
43744 Points
1214
0
Posted March 16th, 2015 18:00
Since you are using the same ip in both VLAN it could be still part of VLAN 1. Try going to each of those interfaces and running
No tagged interface
No switchport
Show config
And see if that removed it from VLAN 1. You may also want to assign different VLANs different subnets.
I tried that on one of the interfaces, but get the following errors
int te0/16
no tagged interface
^
% Error: Invalid input at "^" marker.
no switchport
%error: Port has Layer-2 config on it Te 0/16.
show config
!
interface TenGigabitEthernet 0/16
no ip address
mtu 12000
switchport
flowcontrol rx on tx off
spanning-tree rstp edge-port
no shutdown
also when I have either tagged or untagged a port to VLAN120 I can see that is no longer associated with VLAN1 by doing a show vlan command
for this example I just did it to one port to show you
show vlan
Codes: * - Default VLAN, G - GVRP VLANs, R - Remote Port Mirroring VLANs, P - Primary, C - Community, I - Isolated
O - Openflow
Q: U - Untagged, T - Tagged
x - Dot1x untagged, X - Dot1x tagged
o - OpenFlow untagged, O - OpenFlow tagged
G - GVRP tagged, M - Vlan-stack, H - VSN tagged
i - Internal untagged, I - Internal tagged, v - VLT untagged, V - VLT taggedNUM Status Description Q Ports
* 1 Active U Po1()
U Te 0/1-15,17-32,42-44,49-56
U Te 1/1-32,42-44,49-56
120 Active T Te 0/41
U Te 0/16
T Te 1/41DELL-Josh Cr
Community Manager
•
9699 Posts
•
43744 Points
1214
0
Posted March 17th, 2015 10:00
Do the ports show down once you switch vlans or do they show connected but just don’t ping?
DELL-Josh Cr
Community Manager
•
9699 Posts
•
43744 Points
1214
0
Posted March 17th, 2015 11:00
Do the servers have NICs in VLAN 1 as well? Having both VLANs use the same subnet shouldn’t be a problem if they are fully isolated from each other, but the fact that it works in VLAN 1 and not when it is in VLAN 120 seems like there is some sort of conflict.
m455954
12 Posts
1214
0
Posted March 17th, 2015 11:00
I figured out the issue - I had 2 trunk links into VLAN120 from the Juniper - as soon as I disabled the second interface it all sprang into life
Now I need to try and figure out how to set up a LAG between the two MXL's in the stack and a Juniper ex3300 - I've managed to get the connectivity I need but with only a single link - as it's a remote site I want some redundancy :-)