Ah ... ok. I send you a PM how to create a Portgroup on the ESXi so that you connect from a VM by adding a 2nd. vNIC. Since you can now connect to the EQL please try "putty grpadmin[NAME].168.130.25" or a browser.
We have a PS6100 with Primary and Secondary controller cards. The Management port on the Primary controller went down (the 4 iSCSI ports remain functional). It failed over to the Secondary Management port. One of my employees used Dell SAN Headquarters to poke around to see what was happening with the Primary controller. In the process he unselected some option about dedicated management network. He meant to hit the Cancel button on that screen but instead selected an OK button. Now SAN HQ will not talk to the Management port on the controller so Group Manager no longer functions. It's not critical, the SAN is still working fine. But now we need to fix the issue so that Group Manager can talk to the controller again. He did at least note that the Management port was reporting its IP address as 192.168.130.25 before he closed the Group Manager application. We have tried connecting a computer directly to the Management port via Ethernet cable with the computer using the IP address 192.168.130.2, using both a regular Ethernet cable and a crossover Ethernet cable. The Management port never responds to pings so it doesn't appear to be getting connectivity. I'm guessing my next option is to use a serial cable to configure the Management port via command line.   Is that correct, and if so where can we find instructions for doing this via serial cable and command line? Not finding much online. I know how to use PuTTY for serial connections but am also wondering if this SAN requires any special serial cable?   Do not have Dell warranty / support on this SAN. Hardware support is provided through 3rd party.   Please help if you can. TIA!
PS6100 controller management IP accidentally removed