msa 2050 net manager port Unable to obtain IP

[vv4]

follow ，it is the msa 2050 error info :

# show network-parameters
Network Parameters Controller A
-------------------------------
IP Address: 172.168.0.153
Gateway: 172.168.0.254
Subnet Mask: 255.255.255.0
MAC Address: 00:c0:ff:28:d6:57
Addressing Mode: DHCP
Link Speed: 1000mbps
Duplex Mode: full
Health: OK
Health Reason:
Health Recommendation:

Network Parameters Controller B
-------------------------------
IP Address: 10.0.0.3
Gateway: 10.0.0.1
Subnet Mask: 255.255.255.0
MAC Address: 00:c0:ff:28:d6:57
Addressing Mode: DHCP
Link Speed: 100mbps
Duplex Mode: full
Health: Unknown
Health Reason: The network port health is unknown. It may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Controller B Unable to obtain IP , but the health light is green , msa 2050 can use ... when i shutdown controller A , and then ,restart controller B , contro B net port able  obtain IP , why the net manage port  can't working at  the same time ... how can i do it 

[support_s · Accepted solution]

System recommended content:

1. HPE MSA 2050 Storage - Troubleshooting

2. HPE MSA Firmware Release Notes for MSA 1050 (VE270P008) and MSA 2050/2052 (VL270P008) | Issues and workarounds

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[Cali]

The Link Speed of B is only 100mbps.

What happens, if you only swap the Network Cable between Controller A & B?

If then Controller A has 100mps Link, the Switch Port has the wrong Setup.

Cali

[vv4]

control A and B  were connect to the same switch

"The Link Speed of B is only 100mbps" , why ?  i don't konw what happen, this is the problem 

[giladzzz]

Hi

when you set the managment IP on MSA machines it needs a working link

otherwize it does not apply.

Regards

Give a KUDO if this helps

[ArunKKR]

Hi,

It seems to be an unique issue which I have not come across earlier.
You could try the below troubleshooting steps.

Ensure that network cable is connected to Ethernet management ports of both controllers.

Connect an USB CLI cable to controller B

Use tera term utility.

https://osdn.net/projects/ttssh2/releases/

Connect to controller using the COM port that shows up in device manager.

Refer to the pages 38-41 of the MSA user guide:

https://www.hpe.com/psnow/doc/a00017710en_us

Set a static IP address to controller B using a command of the below format:

set network-parameters ip 172.168.0.154 netmask 255.255.255.0 gateway 172.168.0.254 controller b

Restart management controller B using the below command:

restart mc b

Check whether the assigned static IP address is reachable/accessible.

Change MC B addressing mode to DHCP using below command:

set network-parameters dhcp

Restart both management controllers using the below command:

restart mc both

If issue persists, schedule a downtime.

Shut down both the controllers using the below command:

shutdown both
Allow 3-5 minutes for controllers to shut down and OK to remove LED to light up.

Remove the power to both power supply units of controller enclosure 1.

Provide power after 2-3 minutes and check status.

[vv4]

Thank you for your suggestion  . 

I think that is maybe the firmware  causing . (the  mfg port unable obtain IP at the same time , when in upgrading , the process will be unsucessful )    . so , I try to upgrade firmware one by one  to  new version :  VL270P008

below , it  is  machine output info  after upgrade 

# show versions
                         Controller A Versions        Controller B Versions
                           --------------------             ----------------------
Bundle Version:  VL270P008                        VL270P008
Build Date: Wed Oct 5 22:50:59 MDT 2022 Wed Oct 5 22:50:59 MDT 2022

Success: Command completed successfully. (2023-05-23 00:51:10)
# show network-parameters
Network Parameters Controller A
-------------------------------
IP Address: 172.168.0.153
Gateway: 172.168.0.254
Subnet Mask: 255.255.255.0
MAC Address: 00:c0:ff:28:d6:57
Addressing Mode: DHCP
Link Speed: 1000mbps
Duplex Mode: full
Health: OK
Health Reason:
Health Recommendation:

Network Parameters Controller B
-------------------------------
IP Address: 172.168.0.146
Gateway: 172.168.0.254
Subnet Mask: 255.255.255.0
MAC Address: 00:c0:ff:28:d5:41
Addressing Mode: DHCP
Link Speed: 1000mbps
Duplex Mode: full
Health: OK
Health Reason:
Health Recommendation:

Maybe  the mfg port isn't working at the same time  that is the firmware isn't  same   version   or  two  controllers  are not  same batch . ( I haven't take a picture of firmware version from  old version 's controller , sorry ) 

[Sunitha_Mod]

Hello @vv4,

Let us know if you were able to resolve the issue.

If you have no further query and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.