05-07-2018 03:20 AM - edited 03-01-2019 01:32 PM
Hello Team,
I need your help in one of the weird issue i am facing.
UCSM version running on 2.2 8c.
Esxi are configured with iSCSI boot.
From iscsi initiator IP pool, one of the IP assigned to iscsi vnic (for example 1.1.1.1) as inititor but reflecting different IP (For example 1.1.1.2) in standard iscsi switch which creates automatically.
Ideally it should be (1.1.1.1) at vsphere level but thats not case.
Upon investigation found that it is picking the IP (For example 1.1.1.2) which were previously assigned to it as per "Prev Assigned To" Tab under LAN--> Pools.
Tried resetting the service profile but no luck.
Tried removing that port group and reboot the host which automatcily brings the old configuration.
Any solutions??
Cheers !
Andy
05-07-2018 07:19 PM
Greetings.
It sounds like the service profile/iscsi VNIC is pulling the intended IP fine, but the VMK port inside of ESXi is pulling an additional IP?
Please confirm your iSCSI vnics are not the 1st vnic defined in your vnic list, and are not VMK0...
This may take a round of logs from vsphere to see what is going on.
Please confirm you don't have any duplicate macs, and that vmk0's mac matches the hardware mac of the 1st vnic in the service profile.
Thanks,
Kirk...
05-07-2018 08:56 PM
Hello Krik,
Thank you for your reply !! Find below the answers.
Yes, from UCS service profile prospective iscsi VNIC is pulling the intended IP fine from the pool, but vmk port pulling the IP which was in tab "Prev Assigned To". This the weird behaviour.
iSCSi NICs are at the bottom in the SP and part of VMK1 not vmk0.
NO duplicate MACs in the system and vmk0's mac matches the hardware mac of the 1st vnic in the service profile.
What logs i need to refer in vshpere?
Cheers!!
Andy
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide