3 Posts

November 4th, 2015 22:00

Hi Daniel, thank you for your reply. Yes you are right, we have a switch to switch connection. The M8024 is connected to our Core Switch via the external port 1/xg22 using a fiber cable. We used external port 1/xg23 to connect to the separate server using the twinax cable. IP of M8024 is 172.16.17.2, separate server is 172.16.17.3 and Core Switch is 172.16.16.1.

All the ports are in Group 1 assigned with VLAN 16 and Management VLAN 4022.

port-aggregator group 1

add ethernet 1/xg1-1/xg24

vlan add 16

mtu disable

negotiation

lacp auto

minimum active uplinks 1

exit

172.16.17.2 is already assigned to OOB interface, how can it be assigned to a VLAN and to which VLAN?

3 Posts

November 24th, 2015 01:00

Hi Daniel. Still my issue has not been resolved. Let me rephrase my issue, maybe you can help us more:

We have a PowerConnect M8024 switch connected to our M1000e chassis. I connected an iSCSI SAN Storage to one of the 10GB external ports (1/xg24) using a Dell 10GBASE SFP+ Twinax Cable. My switch IP is 172.16.17.2 and the iSCSI SAN IP is 172.16.17.3. I can ping the switch (172.16.17.2) from one of the blade servers hosted on the M1000e chassis but I cannot ping the iSCSI SAN port (172.16.17.3).

One network engineer tried to help us and suggested that the switch needs to be converted from Simple Mode to Advanced Mode. Is this a correct statement? What is the difference between Simple Mode and Advanced Mode? If I convert to Advanced Mode, will this change the operation and/or behavior of the switch or it will just allow me to configure more settings on the switch? This switch is already in production, will converting to Advanced Mode affect any servers on the blade chassis?

No Events found!

Top