PS6100 controller management IP accidentally removed

Hello, 

 If in fact the dedicated (aka out-of-band) Management was disabled, the management address becomes the same as the iSCSI Discovery Address.  So, first try to connect via SSH or web to the iSCSI Discovery Address IP.  Using the same login grpadmin and password.  

 Re: Serial. EQL only requires a standard NULL modem configuration.  9600 baud, 8, n, 1,  NO flowcontrol. 

  This PDF has a lot of information about the EQL iSCSI SAN. 

https://i.dell.com/sites/doccontent/shared-content/data-sheets/en/Documents/esg-TechWP-EQL-ConfigGuide-v14-4.pdf 

Assuming you get into the GUI, the online help has info on setting dedicated management. 

http://psonlinehelp.equallogic.com/V5.0/Content/V5TOC/Configuring_a_management_network.htm

 This earlier forum posting has info on how to configure dedicated management from the CLI. (Serial or SSH) 

 https://www.dell.com/community/EqualLogic/How-to-enable-the-interface-via-CLI-GUI/td-p/4042394

  Regards, 

Don

Hello,

first .. dont mix SANHQ and Groupmanger Its not possible within SANHQ to make configuration changes so we assume you have used the GroupManger(the JAVA App).

If you disable the dedicated Management it will fallback into the iSCSI network because the dedicated is a optional one.

So enter the IP or Name of the iSCSI WKN(Well Known Network) and see if you can connect to Groupmanager again. Your PC needs access to the iSCSI network so think twice.

Otherwise.... a STANDARD RS232 cable and a putty/hyperterminal with 9600,8,1,N is enough to connect and for enabling and configuring from the commandline.  Every PS comes with 2 cables and they are the same as for very old Dell PowerConnect switches for example.

Regards,
Joerg

My apologies, I did not see the replies here, the default settings on my profile were not sent to notify me of replies. I purchased a RS232 female-female serial cable, it should arrive tomorrow. The only such cable I could find around the office was female serial on one end to cat5 on the other end. I did find a cat5 to RS232 female adapter but it isn't working, PuTTY just shows a blank screen and doesn't respond to any keyboard commands.

How do I find the iSCSI Discovery Address? I'm assuming this would be done through ESXi vSphere Client. Can I assume this is also where one would find the "iSCSI WKN"?

Yes the iSCSI GroupIP is the same as you have entered into the ESXi swISCSI Discovery address. 

Try to connect your laptop/pc into a switch port and configure it with an unused IP from your iSCSI subnet. Try to ping the iSCSI GroupIP and if its works start your browser and point it to http://groupip (Hint: they disabled https somewhere in FW 8.1 or so)

Regards,
Joerg

Yes it can. But when you speaking about "vSphere Client" and a 10 year period you are referring to the old Windows #C Client right?
The "path" havent changed in all the years.... from my brain.... Host->Configuration->Storage Adapters. Select the Software iSCSI one and than you need something like "Dynamic Discovering".

You can send me a PM and when you like we can use something like MS Teams/Teamviewer and i can guide you.

BTW. EQL also have ssh enabled so even if you cant get the JAVA working you can connect with the help of putty or your favorite ssh client.  If you have a VM around you can easily add a 2nd. vNIC and place it on the right iSCSI portgroup(must be created first mostlikely) so there is no need for messing around with your phys. switch.

Regards,
Joerg

I'm not really sure how to even find the iSCSI GroupIP. The guy who setup our VMware network and this SAN left behind an Excel spreadsheet (10 years ago!) with a lot of IP information but it's all Greek to me. Is there an easy way to get this GroupIP address from vSphere Client?

Pasting a image take some time because it must be aproved by the forum moderator first.

If you can reach your ESXi shell by ssh please type in the following commands and paste the results as text here.

esxcfg-vmknic -l
esxcfg-vswitch -l

IF your ESXi isnt stone aged the following will display the ISCSI Portal address the ESXi used to connect to the EQL.

esxcli iscsi adapter target portal list

Regards,
Joerg

[root@esx-node-11:~] esxcli iscsi adapter target portal list
Adapter Target                                                                  IP              Port Tpgt
------- ------------------------------------------------------------------------ -------------- ---- -
vmhba68 iqn.2001-05.com.equallogic:0-8a0906-56718920c-3690017702950017-grp01-001 172.22.149.170 3260 1

The 172.22.149.170 is the iSCSI GroupIP of the my EQL.

This is the virtual switch setup on one of our ESXi hypervisors, under Configure > Networking > Virtual Switches. Is this perhaps indicative of the iSCSI Group network addresses, the 192.168.130.x network?

Thank you, Beryllium, that helps. Thank you both for all of your suggestions! Getting closer ...

Hopefully nothing below is divulging anything dangerous to the public. I don't believe so as this is all internal data.

[root@gpiesxi-1:~] esxcli iscsi adapter target portal list
Adapter Target IP Port Tpgt
------- ---------------------------------------------------------------------------------- -------------- ---- ----
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-4b5fdb248-b860000001851ae8-gpiterm3 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-801fdb248-2c60000005651b98-gpiapp01-vol1 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-cbafdb248-a0a0000006751c40-gpiaccounting1-vol1 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-104fdb248-cc60000006a51c6a-gpifile1-vol1 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-11dfdb248-f9c0000006f51cbf-gpiprint1-vol1 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-46efdb248-c820000007b51cd4-gpimain1-vol1 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-61bfdb248-6d10000009e536c2-gpintranet-vol1-c 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-f3297b448-e0c004ae69d53ff9-gpisql2-vol1-c 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-ad197b448-6fc004ae6bd54484-gpamapp1-vol1 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-ea897b448-75e004ae6cb54ad5-gpsapbi1-vol1 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-57297b448-8a6004ae6d154aed-gpsapbi-prod-vol2 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-73afdb248-ce6979f5eca55e72-c-drive 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-75cfdb248-6de979f5ecd55e72-f-drive 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-772fdb248-ce4979f5ed055e72-g-drive 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-a3797b448-be23c597ecf56fea-gpidca-vol1 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-98397b448-f143c597ed257051-gpidcb-vol1 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-e9097b448-2683c597edf572ca-gppdq-vol1 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-ad197b448-1f297a5d48f586ca-gpwinpak 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-40797b448-a4897a5d49b587ab-gpamts2012 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-99897b448-2d20051db6d59946-gpiweb2016 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:0-1cb196-d2197b448-3c80051db785a564-vcsa 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:4-52aed6-096cf42b6-ed40000004a5d6b6-gpibackupproxy1 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:4-52aed6-294cf42b6-61c000000575d6b6-gpibackupproxy2 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:4-52aed6-5a5cf42b6-4160000005e5d780-gppocketwise 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:4-52aed6-f5acf42b6-1dc000000615d782-gpwebapps1 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:4-52aed6-5fecf42b6-e42000000705dc7b-azuremigration 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:4-52aed6-97ecf42b6-16c0000007a5f22f-iland 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:4-52aed6-173cf42b6-1a0a34108e360319-vmwskyline 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:4-52aed6-356cf42b6-394a34108e660345-gpiapp1 192.168.130.25 3260 1
vmhba64 iqn.2001-05.com.equallogic:4-52aed6-342cf42b6-3dea34108f4606b5-gpiapp1-new 192.168.130.25 3260 1
[root@gpiesxi-1:~] esxcfg-vmknic -l
Interface Port Group/DVPort/Opaque Network IP Family IP Address Netmask Broadcast MAC Address MTU TSO MSS Enabled Type NetStack
vmk0 Management Network IPv4 172.16.71.10 255.255.255.0 172.16.71.255 90:b1:1c:48:0b:6d 1500 65535 true STATIC defaultTcpipStack
vmk0 Management Network IPv6 fe80::92b1:1cff:fe48:b6d 64 90:b1:1c:48:0b:6d 1500 65535 true STATIC, PREFERRED defaultTcpipStack
vmk1 iSCSI IPv4 192.168.130.30 255.255.255.0 192.168.130.255 00:50:56:6b:c1:50 9000 65535 true STATIC defaultTcpipStack
vmk1 iSCSI IPv6 fe80::250:56ff:fe6b:c150 64 00:50:56:6b:c1:50 9000 65535 true STATIC, PREFERRED defaultTcpipStack
vmk2 vMotion IPv4 192.168.93.30 255.255.255.0 192.168.93.255 00:50:56:6d:26:49 1500 65535 true STATIC defaultTcpipStack
vmk2 vMotion IPv6 fe80::250:56ff:fe6d:2649 64 00:50:56:6d:26:49 1500 65535 true STATIC, PREFERRED defaultTcpipStack
[root@gpiesxi-1:~] esxcfg-vmknic -l
Interface Port Group/DVPort/Opaque Network IP Family IP Address Netmask Broadcast MAC Address MTU TSO MSS Enabled Type NetStack
vmk0 Management Network IPv4 172.16.71.10 255.255.255.0 172.16.71.255 90:b1:1c:48:0b:6d 1500 65535 true STATIC defaultTcpipStack
vmk0 Management Network IPv6 fe80::92b1:1cff:fe48:b6d 64 90:b1:1c:48:0b:6d 1500 65535 true STATIC, PREFERRED defaultTcpipStack
vmk1 iSCSI IPv4 192.168.130.30 255.255.255.0 192.168.130.255 00:50:56:6b:c1:50 9000 65535 true STATIC defaultTcpipStack
vmk1 iSCSI IPv6 fe80::250:56ff:fe6b:c150 64 00:50:56:6b:c1:50 9000 65535 true STATIC, PREFERRED defaultTcpipStack
vmk2 vMotion IPv4 192.168.93.30 255.255.255.0 192.168.93.255 00:50:56:6d:26:49 1500 65535 true STATIC defaultTcpipStack
vmk2 vMotion IPv6 fe80::250:56ff:fe6d:2649 64 00:50:56:6d:26:49 1500 65535 true STATIC, PREFERRED defaultTcpipStack

"Is this perhaps indicative of the iSCSI Group network addresses, the 192.168.130.x network?"

Yes, its the 192.168.130.x Subnet.

Regards,
Joerg

I connected an ethernet cable from an unused network card on a server in the same rack as the SAN and iSCSI switches to an open port in one of the iSCSI switches. I set the IP of the NIC in the server to 192.168.130.214 / 255.255.255.0. Both ends of the cable show activity via the lights. I tried to ping 192.168.130.25 and get no replies. Tried http://192.168.130.25, as expected, no connection. Tried https and also no connection. So I'm not at all sure how to connect to the iSCSI network, which is connected through two Force 10 S25 switches. I can see from his spreadsheet that he has all ports on both switches assigned to vlan's. I made sure that the ports I tried on both switches are assigned to the "iSCSI" vlan. Looks like he has each switch configured for 6 vlan's. I'm wondering if I should be trying the "Management" vlan instead. It looks like he has the Management vlan on the 172.16.71.0/24 subnet. Previously the SAN was using 172.16.71.25 for the Management port on the controllers.

Sure wish I was better educated on this stuff. I'm so sorry for asking for so much help!

Posting an image of one of the worksheets in the Excel file he left behind. The "VMH" entries refer to our VMware Hypervisors (3 of them). "SAN CTRL" are the SAN Controller ports. "ISW#" refer to the iSCSI Force 10 switches. The entries for "TrendNet" and "Sonicwall" you can ignore, those devices have been replaced over the years. The first was a switch, the second a firewall.