cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1887
Views
0
Helpful
3
Replies

getting error about conectivity

lior.krispin1
Level 1
Level 1

hello,

need your help frieands....

recently i got error massage about connectivity from vNic (attched snapshot)

this problem is in all my blades ...

thanks

3 Replies 3

Walter Dey
VIP Alumni
VIP Alumni

+ 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".

+ did this ever work

fltAdaptorHostIfLink-down

Fault Code: F0207

Message

Adapter [transport] host interface [id]/[id]/[id] link state: [linkState]Adapter [transport] host interface [chassisId]/[slotId]/[id]/[id] link state: [linkState]

Explanation

This fault typically occurs as a result of one of the following issues:

  • The fabric interconnect is in End-Host mode, and all uplink ports failed.
  • The server port to which the adapter is pinned failed.
  • A transient error caused the link to fail.

Recommended Action

If you see this fault, take the following actions:


Step 1 If an associated port is disabled, enable the port.

Step 2 Reacknowledge the server with the adapter that has the failed link.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major
Cause: link-down
mibFaultCode: 207
mibFaultName: fltAdaptorHostIfLinkDown
moClass: adaptor:HostIf
Type: network
Callhome: none
Auto Cleared: true
Is Implemented: true

Evan Mickel
Cisco Employee
Cisco Employee

As the issue spans the full chassis, I would not personally suggest a blade re-ack to resolve this, I would also do my best to avoid a chassis re-ack to avoid disruption.  Those are fair items to suggest, but later down the line IMO.

My first stop in working an issue like this would be to look into whether there is a pattern in terms of the fabric.  Look to IOMs and the backplane ports (Equipment/Chassis X/IO Modules/IO Module Y/Backplane Ports) to make sure that ports are carved out for each server on each IOM.

Checking the fabric ports would be worthwhile as well from the same location listed above.  If you see backplane ports down or missing, you can either reset the DCE interfaces from each blade to see if that resolves your issue, or you can reboot the IOM if you trace this down to being specific to one of the IOMs.

you can ack'ing a single IOM in a Chassis, which is non disruptive, in case your setup is dual homed and working.

Review Cisco Networking for a $25 gift card

Review Cisco Networking for a $25 gift card