11-13-2014 07:30 AM - edited 03-01-2019 11:55 AM
Fw 2.0 3c I have several major "link down's" & "bmc-pre-config-pnuoslocal-failed" - where acknowledge fault is greyed out. There are many other major events I can acknowledge and clear though.
Thanks
<faultInst
ack="yes"
cause="link-down"
changeSet=""
code="F0283"
created="2014-01-06T13:03:11"
descr="ether VIF N/A / 1 A-1888 down, reason: Non participating"
dn="sys/rack-unit-1/fabric-A/path-1/vc-1888/fault-F0283"
highestSeverity="major"
id="1208592"
lastTransition="2014-01-06T13:03:11"
lc=""
occur="1"
origSeverity="major"
prevSeverity="major"
rule="dcx-vc-down"
severity="major"
status="created"
tags="network,server"
type="network">
</faultInst>
<faultInst
ack="yes"
cause="bmc-pre-config-pnuoslocal-failed"
changeSet=""
code="F0367"
created="2014-06-23T02:45:43"
descr="No link between IOM port 4/2/2 and fabric interconnect B:1/8"
dn="sys/chassis-4/slot-2/fabric/port-2/fault-F0367"
highestSeverity="major"
id="591419"
lastTransition="2014-06-23T02:45:43"
lc=""
occur="1"
origSeverity="major"
prevSeverity="major"
rule="ether-switch-intfio-satellite-connection-absent"
severity="major"
status="created"
tags="network"
type="connectivity">
</faultInst>
11-13-2014 08:08 AM
Hello,
The first error message you reported is usually cause by the reasons I describe here, did you check that already?
https://supportforums.cisco.com/discussion/12072961/vif-bound-physcial-interface-down
Second error message, did you check the port 1/8 on FI-B already, to be sure the cable is properly connected?, to see if the port is enabled in the FI? Did you check if there are CRC errors or changed the cable? or did you confirm the IOM is 100% healthy?
If the Acknowledge Fault button is grayed, it means that it was acknowledge already, but if the alert does not go away it means that even after the alert was ascked, the condition is still taking place.
-Kenny
11-13-2014 09:55 AM
The first one was related to that url and a nic being disabled within windows.
Fi port 1/8 looks fine and the io module is in an operable status. But the fabric port 2/2 is in an overall status of "up" and acknowledged. But the discovery is "absent" instead of "present" as on other fabric ports without the faults.
Does a re-ack of chassis or reset of the io module need to be done to clear fault?
Thanks
11-13-2014 10:04 AM
Both, reack of chassis and IOM reseat (not reset) may work, just see what is less disruptive... However, I would still look for a possible bad SFP/cable. Have you checked the port's LED status physically? I mean is it solid green/amber?
-Kenny
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