HPE Storage Users Group

Settin up a new 7200 here and I have it networked to two standalone HP switches (no uplink to our production network). I have the Virtual Service processor setup in VMware and I can see it comes with 2 virtual NICs. However, since the VSP need access to the 3par (private network) and HP support (production network) what options do I have? Generally I would have 2 IP's on the VM but I don't see any options in the SPOCC to add another IP to allow access to a second subnet. Anyone run into this before?

bparrucc wrote:Settin up a new 7200 here and I have it networked to two standalone HP switches (no uplink to our production network). I have the Virtual Service processor setup in VMware and I can see it comes with 2 virtual NICs. However, since the VSP need access to the 3par (private network) and HP support (production network) what options do I have? Generally I would have 2 IP's on the VM but I don't see any options in the SPOCC to add another IP to allow access to a second subnet. Anyone run into this before?

HP has stated that the only reason the VSP has two nics is that the physical has 2 nics. You can only use 1

I was afraid of that. Any options for me here? I can't imagine I'm the only one keeping SAN storage on it's own isolated switch.

I've not really come across that setup before, you definitely keep the data traffic on their own switches, be it FC or iSCSI, but the management normally goes on a management network, which is normally routable to the LAN to enable access to the internet for phone home, and so that you can manage it from your desktop, and finally to route to the SMTP server to send internal email alerts.

I've not seen it implemented with a totally segregated management network before, how are you going to manage the San? As y need a direct connection to the inserv nodes, the imc doesn't connect through the SP.

I have a physical windows server with a nic connecting to the storage switches. I installed the Management Console on there. This box has another nic with a production IP on it.

bparrucc wrote:I have a physical windows server with a nic connecting to the storage switches. I installed the Management Console on there. This box has another nic with a production IP on it.

Set that box as the gateway for the VSP and turn on RRAS and allow it to route outbound traffic for the VSP. You've already compromised your airgap so allowing the VSP to communicate through your dual homed host isn't a further transgression.

Afidel's solution is certainly one way.

I'm not sure I understand why you can't put the vsp and node mgmt ports on your production LAN, and leave the actual fc/iscsi traffic completely air gapped

Actually that was my next question which i was thinking about last night.

so all iscsi is on the storage switch
then the 2 mgmt ports will be on the lan as well as the VSP correct?

bparrucc wrote:Actually that was my next question which i was thinking about last night.

so all iscsi is on the storage switch
then the 2 mgmt ports will be on the lan as well as the VSP correct?

Absolutely correct

Worked great. Thank you guys.