ISCSI Vnics on VLan policiy not taking the native VLan

[Andres Gonzalez]

Hello Cisco Guys.

We are experiencing an issue after deploying the Intersight solution.

After deploying the service profile on multiple servers, they boot up successfully. We have verified connectivity for management, vMotion, and NFS, and all are functioning correctly. However, we are unable to establish connectivity through the iSCSI vNICs (Vnic_NVME_A/B). Troubleshooting Steps Taken 

MTU is set to 9000.

Ping test from the fabric to the gateway succeeds, confirming connectivity between the fabric and the controller. •

Port channel policy speed is set to auto. We are running same configuration in other UCS PODS, the difference is they are managed from UCS Manager not from intersight. We would appreciate your guidance in troubleshooting this iSCSI connectivity issue. If I move the Vlan to another portgroup (vmotion) I got access.

Something is missing with the last Vnics.

[Matthew Faiello · Accepted solution]

Andres....Understand, and assume you have a healthy native vlan configured from the FI upstream to the TOR/EOR Switch?
So the iscsi-vNIC connectivity via the native vlan is working on one Port-Group, but not the desired/intended Port-Group? Same VLAN in the distributed Port Group and Uplink Port Group?....If all of that is solid,
Can you please open a TAC Case, upload UCSM Tech Support and please provide me with the TAC Case Number?
mfaiello@cisco.com

Thanks,

Matt

[Andres Gonzalez]

HI Matt.

Basically Vnic 6 and 7 are not passing trough the ISCSI Vlan, if i recall, the IOM and blade MLOMs only have 4 lanes, difference was I think in UCS manager this got auto mapped. Not sure on Intersight how it works.

Thanks.

TAC Case Number: 698861696