Array Setup and Networking
1752793 Members
5968 Online
108789 Solutions
New Discussion юеВ

CS210 NIC assignment

 
SOLVED
Go to solution
BenLoveday
Valued Contributor

CS210 NIC assignment

Hi everyone,

I'm working through documenting our iSCSI and Management connections on the CS210 arrays and wondered what others thought about the NIC assignment.

In the Nimble documentation it suggests using as an example both onboard NIC ports for management traffic and the two ports on the add-in card for iSCSI. I wondered if it was better to split both types of traffic between the two PCI devices to improve physical HBA redundancy but I don't know if that is going a bit over the top or whether that might cause performance issues due to the two adapters being different chipsets (not sure if this is the case or not).

Any thoughts?

Cheers,

Ben Loveday

7 REPLIES 7
jrich52352
Trusted Contributor

Re: CS210 NIC assignment

well if you really wanted to take full advantage of it, you can do mgmt+data, i mean really how much mgmt traffic is going through there? cant be much...

you might want to call support, will probably be the only way to get a solid answer on this, because as you pointed out, it really depends on how the hardware is setup..

but to that point, if you are using all 1gb connection, even if you used all 4 ports (2 data, 2 data+mgmt) I cant imagine you'll over saturate any of the bus.

I'd play around and test by I have the 10gb addin cards so wouldnt be able to produce any useful results.

Nick_Dyer
Honored Contributor
Solution

Re: CS210 NIC assignment

Hey Ben,

Typically eth1 & eth2 are allocated for management traffic only with eth3 & eth4 for data traffic, and as you say eth3 & eth4 are on the same PCI card. I wouldn't worry too much about the resilliency of the card itself. If there were a PCI failure it would cause an instant handover of the controllers to ensure data traffic is up and good, so when it came to replace the PCI card/controller through RMA it would be easy to do as it would already be the secondary role.

Nick Dyer
twitter: @nick_dyer_
BenLoveday
Valued Contributor

Re: CS210 NIC assignment

Thanks Justin, unfortunately I need to keep mgt and iSCSI separate but you are right in that would work!

Cheers,

Ben

BenLoveday
Valued Contributor

Re: CS210 NIC assignment

Thanks Nick,

I guess you've answered my question really! I wasn't sure whether a PCI card failure would trigger the controller handover which is perfect.

One other question I have in relation to this is can one change the nic assignment on the iSCSI side after volumes have been provisioned? I'm not bothered about having to reconfigure iqn names from the host side but just wanted to make sure it didn't change any of the volume config. I wouldn't have thought so but wanted to ask an expert!

Cheers!

Ben

Nick_Dyer
Honored Contributor

Re: CS210 NIC assignment

Hi Ben,

Is your question relating to when a controller takeover occurs and the volumes are presented from the other ports? There is no reconfiguration to do here at all (from IP addresses, IQN, MPIO etc) as the controllers are a mirror image of eachother in that respect.

The only time you have to do reconfiguration of some sort would be if you were to replicate the volume from one array to another and then clone/promote that volume.

Hope the above helps (if I understood it correctly!).

Nick Dyer
twitter: @nick_dyer_
jrich52352
Trusted Contributor

Re: CS210 NIC assignment

I wouldnt say that unfortunate, more like good design

BenLoveday
Valued Contributor

Re: CS210 NIC assignment

Thanks Nick, that's exactly what I needed to know :-)