Port one seemed to be assigned to VLAN1 which I didn't think I was using. I moved the connection from our existing network in to port 2 - which then gave me access to the web interface where I could see for certain that VLAN10 (management) was on port 2 only on each switch in the stack.
So, I can at least get more visibility of what is happening now which should help going forward.
This effectively closes my issue of not being able to assign an IP address - VLAN1 seems to not allow that, but my VLAN10 does.
Currently, our existing non-SAN network is on 10.10.10.x
I hoped that I'd set the new switches so that ports one and two on each switch could connect to that network and the remaining ports used just for the SAN traffic.
So far I've been connecting to the switch using a serial cable. When I try and see the IP address for the switch it says 0.0.0.0. When I try and set the IP for VLAN10 to something in the 10.10.10.x subnet I'm told that I can't have routing on a management vlan.
Ideally, I want an IP address for the switch on our existing data network so that I can get to the management web site that way. Before I created the two VLANs it did appear on our data network after getting an address from DHCP. Since adding the two VLANS that no longer happens.
can you give a net topology - would be helpful to understand your connection path.
"Currently I can't see the switches on our existing network - despite plugging in a network cable to port 1 on switch 1"
Are you connecting a server directly into this port to verify you've set up your managment correctly (there are two methods to access your switch - Telnet, GUI).
First chance I get I'll look over what youve sent (just got back from a long trip). A quick note on the null ip address (0.0.0.0); I assume you've set the switch inband managment to "ip addresss DHCP". This return tells you that it did not recieve the DHCP BPDU. Assign an available static ip address and attempt to do a quick ping to verify your path. If that works but no DHCP then I suggest you utilize the helper-address feature...
dwild
4 Posts
1
September 20th, 2011 04:00
Port one seemed to be assigned to VLAN1 which I didn't think I was using. I moved the connection from our existing network in to port 2 - which then gave me access to the web interface where I could see for certain that VLAN10 (management) was on port 2 only on each switch in the stack.
So, I can at least get more visibility of what is happening now which should help going forward.
This effectively closes my issue of not being able to assign an IP address - VLAN1 seems to not allow that, but my VLAN10 does.
dwild
4 Posts
0
September 19th, 2011 04:00
Hi,
Currently, our existing non-SAN network is on 10.10.10.x
I hoped that I'd set the new switches so that ports one and two on each switch could connect to that network and the remaining ports used just for the SAN traffic.
So far I've been connecting to the switch using a serial cable. When I try and see the IP address for the switch it says 0.0.0.0. When I try and set the IP for VLAN10 to something in the 10.10.10.x subnet I'm told that I can't have routing on a management vlan.
Ideally, I want an IP address for the switch on our existing data network so that I can get to the management web site that way. Before I created the two VLANs it did appear on our data network after getting an address from DHCP. Since adding the two VLANS that no longer happens.
jp1110
67 Posts
0
September 19th, 2011 04:00
can you give a net topology - would be helpful to understand your connection path.
"Currently I can't see the switches on our existing network - despite plugging in a network cable to port 1 on switch 1"
Are you connecting a server directly into this port to verify you've set up your managment correctly (there are two methods to access your switch - Telnet, GUI).
jp1110
67 Posts
0
September 24th, 2011 14:00
First chance I get I'll look over what youve sent (just got back from a long trip). A quick note on the null ip address (0.0.0.0); I assume you've set the switch inband managment to "ip addresss DHCP". This return tells you that it did not recieve the DHCP BPDU. Assign an available static ip address and attempt to do a quick ping to verify your path. If that works but no DHCP then I suggest you utilize the helper-address feature...
I'll get back to you on the rest.