cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3490
Views
0
Helpful
6
Replies

F0283 VIF 1 / 2 B-42/44 down, reason: Bound Physical Interface Down

Sandemann
Level 1
Level 1

Hi

I have some issues after migrate from CX4 SAN to VNX SAN. Everything is moved from CX4 to VNX and I have disabled FC Uplink port that is connected to CX4. Both my FI's is only connected to VNX.

We want SAN boot on our ESXi host, and some of them is install on a boot LUN on VNX, and some other is install local at the Blade.

My issue is that all my host shall boot from SAN. But suddenly this fails.

I zones the host on our MDS switches, and does everything in VNX, so the host shall see its boot LUN. SAN Boot Target is changed so it sees the VNX SAN.

In the install I see my boot LUN, and install ESXi without any issues. Remove the installation media and reboots the server.

When it shall boot back up, it says:

Reboot and Select proper Boot device

or Insert Boot Media in selected Boot device and press a key.

And i gets 8 major error messages like this:

VIF 1 / 2 B-42/44 down, reason: Bound  Physical Interface Down

What is wrong. I do the same thing now, as I did when I installed the hosts that is working.

6 Replies 6

Robert Burns
Cisco Employee
Cisco Employee

Can you try to re-ack the Server the Profile is associated to.  The error you're seeing usually means the host Iniitator interface (VIF) is down because it has no uplink to correclty pin to.  You said you shut down the ports the CX4 was previously connected to by disabling it.  Can you re-ack the blade which should re-pinn to the new/remaining uplink.

If that doesn't correct the problem I'd look into your boot policy.  Double and triple check the boot targets entered in the profile and make sure they match the targets on the VNX, and that each one is online and logged into the MDS ("zone flogi database").  The symptoms you're seeing used to be common with Clariion arrays as they are Active/Passive.  During the installation any available path has access to the LUN for the installation, but they rebooting required the first listed target in the boot policy to be the "owner" of the LUN.  This was easily fixed by trespassing the LUN to the other Storage Processor on the array.  With VNX I'm pretty sure they are Active/Active arrays so this shouldn't matter.

Regards,

Robert