vNICs and ping connectivity

[Kernel-Panic]

Hello all, in my UCS environment I've created two iSCSI vNICs for connecting to our Nimble storage; in the Nimble web console it can see the two initiator addresses are connected, however in the Nimble cmd line console I can't ping the IP addresses associated with these vNICs - is this normal i.e. do vNICs not usually reply to pings? 

[Kernel-Panic]

Thanks again Kirk,

From the Fabric Interconnects I was able to get the following info:

nic 1 - 00:25:B5:91:1A:8F - Fabric A veth757 (00-vNIC-A)

nic 2 - 00:25:B5:91:1B:8F - Fabric B veth758 (01-vNIC-B)

nic 3 - 00:25:B5:91:1A:9F - Fabric A veth759 (02-iSCSI-A)

nic 4 - 00:25:B5:91:1B:9F - Fabric B veth760 (03-iSCSI-A)

This seems to tally with the below info in UCS:

When I looked at the the vmnics in the ESXi 'configure management network' section it showed the following:

vmnic0 - (00:25:B5:91:1A:8F) status: connected

vmnic1 - (00:25:B5:91:1B:8F) status: connected

vmnic2 - (00:25:B5:91:1A:9F) status: iSCSIBootvSwitch

vmnic3 - (00:25:B5:91:1B:9F) status: connected

I chose vmnic0 for the management interface, assigned it the IP address and it worked!   :)

The only slightly odd thing is that although the Nimble boot LUN allows multiple connections, ESXi seems to be only making one connection via vmnic2 (which is the UCS vNIC '02-iSCSI-A') - is this a deliberate policy from ESXi?