VNIC0 , vnic1

[mabuhantash]

hi

after creating a service profile expert and write the proper MAC and Wwwnp , I create two vnic , vnic0, vnic1 and one VHBA

the serveice profile associted anf no errors , but it give me major faults that the adapter 1/1/1 and 1/1/2  link down , and VIf 687 is down too.

I chek the pin groug it is okay and the uplink is Up and work in trun mode the vlan is defualt and there is no trunk , shall I make the vlan number same as vlans used in swich or not??

I try to reset the card but it not give me solution, is it common when I insall the OS does that may change , the power status is on?? and it wait for bootable media

any suggestions or help??

you can see the errors???

please note that the second I/O is not connected and it shows accesibilty proplems ., the fist Uplink od I/o module 2 is Up even it is not connected.  very stange I try to connect two cables on I/O module 1 it give me up on first and on the seconed link failure os down ?? is that related to above issue Severity,Code,ID,Affected object,Cause,Last Transition,Description

cleared,F0320,49372,sys/chassis-1/blade-1/fault-F0320,identity-unestablishable,2010-12-12T15:19:39,Server 1/1 (service profile: org-root/ls-UCS-ESX-1) has an invalid FRU: mismatch-identity-unestablishable

cleared,F0206,48691,sys/chassis-1/blade-1/adaptor-1/fault-F0206,connectivity-problem,2010-12-12T15:19:23,Adapter 1/1/1 is unreachable

cleared,F0331,49762,org-root/ls-UCS-ESX-1/fault-F0331,server-inaccessible,2010-12-12T15:19:09,Service profile UCS-ESX-1 cannot be accessed

cleared,F0322,49761,sys/chassis-1/blade-1/fault-F0322,equipment-inaccessible,2010-12-12T15:19:09,Server 1/1 (service profile: org-root/ls-UCS-ESX-1) inaccessible

major,F0283,49340,sys/chassis-1/blade-1/fabric-A/path-1/vc-685/fault-F0283,link-down,2010-12-12T14:45:20,ether VIF 1 / 1 A-685 down, reason: VIC Enable not received

major,F0283,49339,sys/chassis-1/blade-1/fabric-A/path-1/vc-686/fault-F0283,link-down,2010-12-12T14:45:20,ether VIF 1 / 1 A-686 down, reason: VIC Enable not received

major,F0283,49338,sys/chassis-1/blade-1/fabric-A/path-1/vc-687/fault-F0283,link-down,2010-12-12T14:45:20,fc VIF 1 / 1 A-687 down, reason: None

major,F0283,49337,sys/chassis-1/blade-1/fabric-A/path-1/vc-8879/fault-F0283,link-down,2010-12-12T14:45:20,ether VIF 1 / 1 A-8879 down, reason: VIC Enable not received

major,F0207,49182,sys/chassis-1/blade-1/adaptor-1/host-eth-1/fault-F0207,link-down,2010-12-12T14:20:39,Adapter  host interface 1/1/1/1 link state: down

major,F0479,49181,sys/chassis-1/blade-1/adaptor-1/host-eth-1/vif-685/fault-F0479,vif-down,2010-12-12T14:20:39,Virtual interface 685 link state is down

major,F0209,48692,sys/chassis-1/blade-1/adaptor-1/ext-eth-2/fault-F0209,link-down,2010-12-12T14:17:31,Adapter uplink interface 1/1/1/2 link state: down

[Robert Burns]

Mohammad,

+ What version of UCS and which adapter are you using?

+ Have you tried to re-acknowledge the blade? Also I'd suggest a Chassis re-ack.  This will be momentarily disruptive while the connectivity between IOM and FI is rebuilt, but I'm seeing errors in your logs in regards to "unsupported-connectivity".

Provide answers to/attempt the above and let me know.

Regards,

Robert

[DE.Scott.Smith]

I am having the same issue.   If you de-associate the profile and reboot you get no issues.   Once I reassociate the profile and reboot the errors come back.

[DE.Scott.Smith]

Found the following concerning UCS and ESX 4.1:

http://terenceluk.blogspot.com/2011/03/esxi-41-hosts-in-standby-mode-causes.html