This post is more than 5 years old
1 Rookie
•
89 Posts
0
74140
March 6th, 2016 02:00
EqualLogic Group Member network configuration error: "Management interface must not be on san subnet"
Hi,
Currently we have new EqualLogic 6100 device with this network configuration:
Group Manager IP - 192.168.0.2 (VLAN1).
Member network config:
eth0 - 192.168.0.3 (VLAN1)
eth1 - 10.10.10.3 (VLAN2)
eth2 - 10.10.10.4 (VLAN2)
eth3 - 10.10.10.5 (VLAN2)
eth4 - empty
I would like to assign 192.168.0.4 to eth4 but got error: "Management interface must not be on san subnet"
I am sure that ALL eth interfaces has access to VLAN1 and VLAN2, does that mean error states that eth4 must not access VLAN2 and only access VLAN1 on the switch?
Or eth0 also should have only access to VLAN2 in order to reconfigure eth0 and eth4?
Thanks
No Events found!
Origin3k
4 Operator
•
2.3K Posts
1
March 6th, 2016 05:00
> Does Group Manger IP should be in iscsi VLAN?
Yes!
Note: When ever you setup an EQL it will ask for a iSCSI port because nothing more is needed to bring it up. The earlier EQLs doest have a dedicated MGMT Port and later you have the option to convert the last ethX as a MGMT port. This is the reason why you setup ISCSI at the beginning. (Think about a mixed member group of newer and older models and you get a picture)
Ok.... again is this the one and only member in the group and there is do production host connected right?
For the IP change we need a 3rd. subnet for temporary use.
- Dont touch eth0-3 and the Group IP Address right now
- Setup the MGMT Ports and the Group Management IP Adress to the tempr. Subnet. Use Group Config->Adv.-> MGMT Network. You can edit the MGMT Port of the member as well as the MGMT IP Adress
- When saving the config you will loose access. You have to place your admin PC into the templ. subnet as well
- Connect again to the GroupMgr with the new temp. IP
- Now you can change the Group IP Adress to 10.10.10..x
- Now you can change eth0 to 10.10.10.2
- At the end you can change the MGMT IP Address of the group as well as the MGMT Port back to 192.168.0.x
- Change the IP of your admin PC back
As a fallback you should consider to hook up a serial cable the the active controller of the EQL. Use 9600,8,1,N with your favorite terminal programm (putty.exe on windows). All the steps you also can perform from the commandline.
If this group and the single member not in production yet you also can reset the config and start from the beginning.
Regards,
Joerg
Origin3k
4 Operator
•
2.3K Posts
1
March 6th, 2016 02:00
Aehll.... a PS6100 have 4 iSCSI ports which are named eth0 - eth3 and a optinal, dedicated MGMT Port. The IP addresses of your eth0,1,2,3 Ports have to be all in the same subnet. After that you can setup and enable the MGMT ports which, of course, needs to me in another subnet.
Example:
eth0 - 10.10.10.2
eth1 - 10.10.10.3
eth2 - 10.10.10.4
eth3 - 10.10.10.5
mgmt - 192.168.0.3
Regards,
Joerg
natip
1 Rookie
•
89 Posts
0
March 6th, 2016 03:00
The problem is
If I try to change eth0 to 10.10.10.2, I get error: "At least one IP on the member must be on network 192.168.0.x".
If I try to change eth4 to 192.168.0.4, I get error: "Management interface must not be on SAN subnet".
So how to reconfigure device network?
natip
1 Rookie
•
89 Posts
0
March 6th, 2016 04:00
Configuration is like this:
Group Manager IP - 192.168.0.2 (VLAN1).
Member network config:
eth0 - 192.168.0.3 (VLAN1)
eth1 - 10.10.10.3 (VLAN2)
eth2 - 10.10.10.4 (VLAN2)
eth3 - 10.10.10.5 (VLAN2)
eth4 - empty
192.168.0.x (VLAN1) network is for management.
10.10.10.x (VLAN2) network is for ISCSI.
Does Group Manger IP should be in iscsi VLAN?
natip
1 Rookie
•
89 Posts
0
March 6th, 2016 04:00
I have changed Group's Manager IP to IP in ISCSI VLAN and was able to setup eth4, now my config looks like this:
Group Manager IP:
10.10.10.6 (VLAN2).
Member network config:
eth0 - 10.10.10.2 (VLAN2)
eth1 - 10.10.10.3 (VLAN2)
eth2 - 10.10.10.4 (VLAN2)
eth3 - 10.10.10.5 (VLAN2)
eth4 - 192.168.0.4 (VLAN1)
Is this correct?
Why Group Manager IP must be in ISCSI network?
Shouldn't Group Manager IP and Member Management IP be in the same network?
Thanks
Origin3k
4 Operator
•
2.3K Posts
1
March 6th, 2016 04:00
Is this the only and only member in the group? Please show us a screenshot of the group configuration general tab or tell us what your ISCSI WKA (Group IP Address) and MGMT WKA (Management IP Address) is or better should be.
For me it looks look you mixed up MGMT with iSCSI. If the config for eth0 is 192.168.0.3 the member use this for ISCSI.
Yes this can be fixed... but we need to more infos about the group and which subnet you would like to use for iSCSI and MGMT. Again..... MGMT is optional and can be setup "later".
Regards,
Joerg
Origin3k
4 Operator
•
2.3K Posts
0
March 6th, 2016 05:00
> Shouldn't Group Manager IP and Member Management IP be in the same network?
No!
On or more EQL member(s) living within a Group. The group is a virtual thing and have a single unique IP adress called WKA (Well known address) and its named "Group IP Adress" in the GUI and have a address from your ISCSI subnet. Think about a Cluster IP....
The Group IP Address is the most important one in EQL terms because to this one all you productions hosts will connect to at the first (will be redirected later to the pyhs. iSCSI ports/addresses).
Also when you try to add a additional EQL member to the group you will add it to this ISCSI Address.
And now... MGMT.
There is also a virtual MGMT IP and a single pyhl. IP Address on every EQL member. If you enable MGMT on a EQL Group you reach Group Manager GUI there as well a SSH for now. Also SANHQ and VSM neejavascript:void(0);ds to connect to the MGMT IP.
Again... support for a IP OOB Management comes very late in the EQL timeline.
Regards,
Joerg