topic Re: Nimble service port in Array Setup and Networking

Nimble service port

marcusburrows — Tue, 16 Jun 2020 13:26:56 GMT

I would like to know more about the Nimble array service port. Is it merely a non-floating IP address or is it connected to a separate iLO-style chip? I assume it has its own MAC address. Many thanks.

Re: Nimble service port

StorageMike — Tue, 16 Jun 2020 14:18:34 GMT

Do you mean the serial port near the SAS outputs? If so you'll need to connect to this using the cable that came with the Nimble Array. Connetion via Putty using 115200 baud should allow you to connect

Re: Nimble service port

marcusburrows — Tue, 16 Jun 2020 14:46:18 GMT

Ah sorry. That's my bad. I was referring to the Diagnostics IP rather than any physical port. So, to clarify I'll re-word the original question:

I would like to know more about the Diagnostics IP addresses. Are they merely a non-floating IP addresses or are they connected to a separate iLO-style chip (and therefore have a separate MAC address)?

Many thanks again!

Re: Nimble service port

Sheldon Smith — Tue, 16 Jun 2020 14:53:34 GMT

The Diagnostic IP floats on the management NICs of the designated controller. I don't believe it matters which management port happens to 'have' the diagnostic IP at any time and don't see why it would.

Re: Nimble service port

StorageMike — Tue, 16 Jun 2020 14:57:05 GMT

The diagnostic ip stay with the controller assigned they don't move around like a VIP. They are used when something happens to the management ip.

There is more info - https://infosight.hpe.com/InfoSight/media/cms/active/public/pubs_GUI_Administration_Guide_NOS_50x.whz/jun1443657118614.html If you search the guide it's also refered to as the support ip address

Re: Nimble service port

marcusburrows — Tue, 16 Jun 2020 15:01:12 GMT

Many thanks!

Re: Nimble service port

marcusburrows — Tue, 16 Jun 2020 15:01:56 GMT

Many thanks! : )

Both replies confirm what I was suspecting, that it isn't an iLO-style lights out port.

Re: Nimble service port

Candhade — Wed, 17 Jun 2020 08:57:36 GMT

Each controller on an array must have a dedicated Diagnostic IP (support IP address), which can be used for troubleshooting and technical support purposes in the event that a controller is not reachable through the management IP address. The support IP addresses must be placed on the group management subnet.

Significance of having this Diagnostic IP

Management IP is floating between both the controllers meaning when a controller failover happens, Management IP to connect to the Array remains the same.

Diagnostics IP is configured on individual controller, Diagnostics IPs of both the controllers and Management IP (all 3 IPs) are required for Array heartbeats and DNAs to send to Nimble Support.

We can consider Diagnostic IP as the Specific Controller Management IP.

The Diagnostics IP of the standby controller does not have the ability to manage the array or group.

Let's assume we have 2 arrays in a scale-out Group, then we need 4 Diagnostics IPs and 1 Group IP (floating). We need to manage the Group, we connect using the Management IP and if there is a need to connect to a specific controller of a specific Array within the group, we connect using the Diagnostic IP.

(Login credentials remains the same whether you connect to the Management IP or the Diagnostics IP)

Note: Diagnostic IP is also called as Support IP.

Re: Nimble service port

marcusburrows — Wed, 17 Jun 2020 09:30:01 GMT

Many thanks for that full explanation! : )