Nexus5548 - "faulty" interface status

One of our enclosures lost one of it's backup links to a Nexus5548.   Looking at the interfaces the status reads "faulty". The interface in question is Eth1/5, but what I also noticed there were a couple interfaces not in use w/ the same status. I tried switching out the gbic and disabling/enabling the interface, but nothing helped. Any thoughts? Is a reboot my only option?
<code>
switch# show int status
Port          Name               Status    Vlan      Duplex Speed   Type
Eth1/1        --                 connected 226       full    10G     10Gbase-SR
Eth1/2        --                 connected 226       full    10G     10Gbase-SR
Eth1/3        --                 connected trunk     full    10G     10Gbase-SR
Eth1/4        --                 faulty    1         full    10G     --
Eth1/5        --                 faulty    trunk     full    10G     10Gbase-SR
Eth1/6        --                 connected trunk     full    10G     10Gbase-SR
Eth1/7        --                 notconnec trunk     full    10G     10Gbase-SR
Eth1/8        --                 connected trunk     full    10G     10Gbase-SR
Eth1/9        --                 notconnec 1         full    10G     10Gbase-SR
Eth1/10       --                 notconnec 1         full    10G     10Gbase-SR
Eth1/11       --                 faulty    1         full    10G     --
Eth1/12       --                 connected trunk     full    10G     10Gbase-SR
Eth1/13       --                 faulty    1         full    10G     --
Eth1/14       --                 connected trunk     full    10G     10Gbase-SR
Eth1/15       --                 sfpAbsent 1         full    10G     --
Eth1/16       --                 connected trunk     full    10G     10Gbase-SR
Eth1/17       --                 sfpAbsent 1         full    10G     --
Eth1/18       --                 sfpAbsent 1         full    10G     --
Eth1/19       --                 sfpAbsent 1         full    10G     --
Eth1/20       --                 sfpAbsent 1         full    10G     --
Eth1/21       --                 sfpAbsent 1         full    10G     --
Eth1/22       --                 sfpAbsent 1         full    10G     --
Eth1/23       --                 sfpAbsent 1         full    10G     --
Eth1/24       --                 sfpAbsent 1         full    10G     --
Eth1/25       --                 sfpAbsent 1         full    10G     --
Eth1/26       --                 sfpAbsent 1         full    10G     --
Eth1/27       --                 sfpAbsent 1         full    10G     --
Eth1/28       --                 sfpAbsent 1         full    10G     --
Eth1/29       --                 sfpAbsent 1         full    10G     --
Eth1/30       --                 faulty    1         full    10G     --
Eth1/31       --                 connected trunk     full    10G     10Gbase-LR
Eth1/32       --                 connected trunk     full    10G     10Gbase-SR
switch#       --                 notconnec routed    auto    auto    --
</code>

Yes try reload. To me this looks like hardware issue might need replacement.
NXOS version?
Any recent upgrade?
Thanks,
Richard.

Similar Messages

Gigabit interface status faulty please help

When I do a show interface status on 4500 switch I got a status faulty
I did never see such thing
Port- Name-Status-Vlan-Duplex-Speed Type
Gi2/7-jsh3 faulty 188 full XXBaseSX
Could you please help?
Thanks a lot

this usually indicates the port is faulty (bad; not working; will not work)
this may have been set via the POST of the device. the internal tests failed and the port was marked FAULTY.
this could also be the result of a good port simply went bad for some unknown reason.
try to disable/reEnable the port. will probably still say faulty. (cannot initialize a faulty port)
try to reset the blade the port is on, or the supervisor if it resides on that.
do a "show test" (catOS) to see what the POST found when it did its powerOnSelfTests.
i've seen plenty of FAULTY ports and 99% of the time, the port is simply bad and must be replaced. (usually an ASIC or the likes)

Sh Interface status

Hi! What's the command for sh interface status in CAT OS?
Thks!

Hi Friend,
You will not get the exact output as you get is IOS but you can take the output from this commands
sh port
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/sw_8_5/cmd_ref/sh_p_sn.htm#wp1715472
sh mac
Have a look at this for details on "sh mac" command
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/sw_8_5/cmd_ref/sh_ml_n.htm#wp1028548
HTH, if yes please rate the post.
Ankur

Urgent- Faulty QM Status

Dear Pals,
Data is loaded up to DSO, and at the time of activation it got error saying that "Faulty QM Status" and "Request Deletion Failed". Actually I 've deleted previous request which was an error. And again trying to delete this present erraneous request, but its not allowing me to delete this request and throwing above statements.
Please can any one help me out in this regards?
Best regards
Niranjan

Hi,
try to change the QM status to RED and retry your deletion.
if it didn't work try the same setting the QM to GREEN.
let us know
hope this helps...
Olivier.

Show interface status (IOS layer 2switch)

Is it possible to modify the width of the column containing the description of the interfaces when I issue the "show interface status?" on IOS cisco switches?

I don't believe so but you can type show interface description if you want to see the entire description that is associated to the port.
HTH,
Edison.

GL Interface status code of "P"

I noticed that on our GL_INTERFACE table several records which had the status code of "P" instead of "NEW". Since we have no Oracle documentation (especially the Techinical Reference Manuals),does anybody know or can find out what that code means?
Normally, I would though it means pending. When you import the records, if the transactions have a problem or does not balance, these records remain on the interface. I never though that it will set these records as pending. We were trying to import records from two sources at the same time. One set of records from a source had an invalid flexfield combo. After we fixed the problem, all the transaction processed without an problems and the GL_INTERFACE table cleared.
Is this a new function to 11i? I came from a 10.7.4 NCA enviroment and never seen this before. Thanks for your assistance.
David Correia
System Analysis
NECMSC

hi david,
this feature is also there in 10.7. If any one record contains any problem, then all the records in that batch will be stopped. And once the same is corrected the whole batch will be imported. until then the records will be in status 'P', ie pending. This feature is there in 10.7 also.

Interface status when connected to an ADM?

I have a couple of quick questions, maybe someone can help me with them.
These are the facts:
- I have a fiber optic running about 20km between two sites.
- On one end I have an ASR1006 with a SIP-10G and in one of its sub-slots it has a SPA-5x1GE. This SPA has a 1000BASE-ZX SFP installed.
- There's a smf jumper running from the SFP to the ODF an this ODF goes to an ADM.
- I know that the other end (at 20km aprox) is disconnected.
- The A/L led on the SPA, next to the SFP port is steady orange.
So, what status should be shown on the "show interface" output? Right now it's "interface down, line procotol down"
If all is set correctly (logs are clean) should the line protocol be up?
Should the interface be up?
At the ODF there are 2 connectors (RX and TX) so they might be inverted and I cannot access that, I would need to call the provider and don't want to do it unless if it necessary.
Thanks.

The problem is probably the result of an mismatch between the optical transceiver (SFP) in the ASR1006 and the service provider's ADM.
You need to know from the service provider what type of interface (speed, reach [1000BASE-?X]) they have installed in their ADM connecting to your equipment. Typically, for an in-building interconnection, between the termination equipment and the service provider's equipment, they would be using a short reach interface (1000BASE-SX), which would operate over multimode fiber or maybe a long reach interface (100BASE-LX), which can run over MMF or SMF. The 1000BASE-ZX SFP is designed for very long links (up to 70 kilometers) and operates at 1550nm over SMF fiber. I'm guessing your link between the ASR and ADM is <500 meters.
If everything is functioning properly, the "show interface" would be Interface UP, Line Protocol UP. If their is a transceiver mismatch, the devices may be unable to read the bits to bring the link up. The client ADM port (facing you) may be shut down as you mentioned the other end of the backbone fiber (20km) is not connected.
http://www.cisco.com/en/US/products/hw/modules/ps4999/products_tech_note09186a00807a30d6.shtml
http://www.cisco.com/en/US/docs/interfaces_modules/transceiver_modules/installation/note/78_15160.html
I hope I am understanding your network topology.

ACE - Query VLAN Interfaces Status

Hi,
I am wondering what the status of the query vlan interface means in the command 'show ft peer detail':
Query Vlan IF State : UP, Manual validation - please ping peer
I am pretty sure that I did not see this status when I configured query vlan last time. Current version is A2(2.3).
Unfortunately this status does not seem to be documented anywhere on CCO.
I appreciate any help!
Thanks,
Daniel

Hi Daniel,
The FT Query VLAN interface is an optional, yet very good, feature to be used when using redundant ACE modules or appliances. Without it, if the FT VLAN was to go down, the standby ACE will no longer receive FT heartbeats from the active ACE and therefore take the active role. However, if the active ACE is still running fine in the active role, then you don't want the standby ACE to take over as active because that will put them into an active/active scenario, which may lead to connectivity issues.
This is where the FT Query VLAN interface comes in. If the FT VLAN goes down, the standby ACE will notice this, but before taking the active role, it will ping it's peer IP address configured on the interface that is designated as the FT Query VLAN. If the ping is successful, then it will stay in the standby role, thereby saving you some headaches.
The status that you are seeing is the ACE's way of telling you that the interface is UP, but if you want to know if it can successfully ping the peer IP address, then you would have to manually ping the peer IP address from the CLI. The ACE does not periodically check the ping connectivity through any automatic mechanism. The automatic mechanism is only triggered by the FT VLAN going down.
Does this help?
Sean

AP 1252 dot11radio interface status shows RESET

Hi,
This is regarding an issue with one of my access point. The access point 1252 is autonomous one running the IOS version
C1250 Software (C1250-K9W7-M), Version 12.4(10b)JDA3, RELEASE SOFTWARE (fc1)
The status of the dot11Radio 0 interface is showing as RESET. I have pasted the interface brief details below.
ap03#
ap03#
ap03#sh ip int brief
Interface                  IP-Address      OK? Method Status                Protocol
BVI1                       <ipaddress>       YES DHCP   up                    up
Dot11Radio0                unassigned      YES TFTP   reset                 down
Dot11Radio0.102            unassigned      YES unset reset                 down
Dot11Radio0.104            unassigned      YES unset reset                 down
Dot11Radio0.105            unassigned      YES unset reset                 down
Dot11Radio0.108            unassigned      YES unset reset                 down
Dot11Radio1                unassigned      YES TFTP   administratively down down
GigabitEthernet0           unassigned      YES TFTP   up                    up
GigabitEthernet0.102       unassigned      YES unset up                    up
GigabitEthernet0.104       unassigned      YES unset up                    up
GigabitEthernet0.105       unassigned      YES unset up                    up
GigabitEthernet0.106       unassigned      YES unset up                    up
GigabitEthernet0.108       unassigned      YES unset up                    up
ap03#
Due to this the clientsa re not getting associated.
I tried rebooting the AP; shut the dot11radio0 interface and unshut it; verified the switch end duplex speed settings. Looks good.
Can anyone suggest me how to proceed?
Thankyou.

Hi,
Yes the Access Point was working fine all these days and for the last one week, I am facing this problem. Please find the running configuration of the Access point as below..
Building configuration...
Current configuration : 8275 bytes
version 12.4
no service pad
service timestamps debug datetime msec localtime show-timezone
service timestamps log datetime msec localtime show-timezone
service password-encryption
hostname ap03
logging buffered 65536 notifications
enable secret 5 $1$.WG7$dvJpY1XHuixBk3wA4sfR3/
aaa new-model
aaa group server radius rad_eap
server auth-port 1812 acct-port 1813
aaa authentication login default group tacacs+ local enable
aaa authentication login eap_methods group rad_eap
aaa authorization exec default group tacacs+ local
aaa accounting exec default start-stop group tacacs+
aaa session-id common
clock timezone MST -7
clock summer-time MDT recurring
ip rcmd rsh-enable
ip rcmd remote-host datacom datacom enable
ip rcmd remote-host datacom datacom enable
ip rcmd remote-host datacom datacom enable
ip rcmd remote-host datacom datacom enable
ip rcmd remote-host datacom datacom enable
ip rcmd remote-host datacom datacom enable
ip rcmd remote-host datacom datacom enable
ip rcmd remote-host ncc ncc
ip rcmd remote-host ncc ncc
ip rcmd remote-host ncc ncc
ip rcmd remote-host ncc ncc
ip rcmd remote-host ncc ncc
ip rcmd remote-host ncc ncc
ip rcmd remote-host ncc ncc
ip rcmd remote-host datacom datacom enable
ip rcmd remote-host datacom datacom enable
ip rcmd remote-host datacom datacom enable
ip rcmd remote-host netsvcs netsvcs enable
ip rcmd remote-host netsvcs netsvcs enable
ip rcmd remote-host netsvcs netsvcs enable
ip rcmd remote-host netsvcs netsvcs enable
ip rcmd remote-host netsvcs netsvcs enable
ip rcmd remote-host netsvcs netsvcs enable
ip rcmd remote-host netsvcs netsvcs enable
ip rcmd remote-host netsvcs netsvcs enable
ip rcmd remote-host netsvcs netsvcs enable
ip rcmd remote-host datacom datacom enable
ip domain list u04129.albertsons.com
ip domain list albertsons.com
ip domain name u04129.albertsons.com
ip name-server
ip ssh time-out 90
dot11 activity-timeout unknown default 28800
dot11 ssid Courage-34idkeysNCswuZue3765#%@&
   vlan 102
   authentication open eap eap_methods
   authentication key-management wpa
dot11 ssid Freedom-jKb%&552en@546AsdfG65eD
   vlan 105
   authentication open eap eap_methods
   authentication network-eap eap_methods
   authentication key-management wpa
dot11 ssid Galaxy-73j4CA58fd66y3lKICK#%@&*
   vlan 104
   authentication open
dot11 ssid Quake-35f8d4q9e5@365%lFh&ju#ef2
   vlan 108
   authentication open eap eap_methods
   authentication key-management wpa
dot11 holdoff-time 60
dot11 arp-cache optional
power inline negotiation prestandard source
dot1x timeout reauth-period server
username Cisco password 7 02250D480809
username ggg privilege 15 secret 5 $1$E4Ms$78SOM7s3gZ8QxU.mlnEpj.
bridge irb
interface Dot11Radio0
no ip address
no ip route-cache
encryption vlan 104 key 1 size 128bit 7 80B78765DD670039FE1557E4BFB4 transmit-key
encryption vlan 104 mode wep mandatory
encryption vlan 108 mode ciphers tkip
encryption vlan 102 mode ciphers tkip
encryption vlan 105 mode ciphers tkip
ssid Courage-34idkeysNCswuZue3765#%@&
ssid Freedom-jKb%&552en@546AsdfG65eD
ssid Galaxy-73j4CA58fd66y3lKICK#%@&*
ssid Quake-35f8d4q9e5@365%lFh&ju#ef2
power local 17
packet retries 64 drop-packet
no preamble-short
channel 2412
station-role root
beacon dtim-period 4
no dot11 extension aironet
bridge-group 1
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
interface Dot11Radio0.102
encapsulation dot1Q 102
no ip route-cache
no cdp enable
bridge-group 102
bridge-group 102 subscriber-loop-control
bridge-group 102 input-type-list 201
bridge-group 102 output-type-list 201
bridge-group 102 port-protected
bridge-group 102 block-unknown-source
no bridge-group 102 source-learning
no bridge-group 102 unicast-flooding
bridge-group 102 spanning-disabled
interface Dot11Radio0.104
encapsulation dot1Q 104
no ip route-cache
no cdp enable
bridge-group 104
bridge-group 104 subscriber-loop-control
bridge-group 104 input-type-list 201
bridge-group 104 output-type-list 201
bridge-group 104 port-protected
bridge-group 104 block-unknown-source
no bridge-group 104 source-learning
no bridge-group 104 unicast-flooding
bridge-group 104 spanning-disabled
interface Dot11Radio0.105
encapsulation dot1Q 105
no ip route-cache
no cdp enable
bridge-group 105
bridge-group 105 subscriber-loop-control
bridge-group 105 input-type-list 201
bridge-group 105 output-type-list 201
bridge-group 105 port-protected
bridge-group 105 block-unknown-source
no bridge-group 105 source-learning
no bridge-group 105 unicast-flooding
bridge-group 105 spanning-disabled
interface Dot11Radio0.108
encapsulation dot1Q 108
no ip route-cache
no cdp enable
bridge-group 108
bridge-group 108 subscriber-loop-control
bridge-group 108 input-type-list 201
bridge-group 108 output-type-list 201
bridge-group 108 port-protected
bridge-group 108 block-unknown-source
no bridge-group 108 source-learning
no bridge-group 108 unicast-flooding
bridge-group 108 spanning-disabled
interface Dot11Radio1
no ip address
no ip route-cache
shutdown
dfs band 3 block
channel dfs
station-role root
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
bridge-group 1 spanning-disabled
interface GigabitEthernet0
no ip address
no ip route-cache
duplex auto
speed auto
interface GigabitEthernet0.102
encapsulation dot1Q 102
no ip route-cache
bridge-group 102
no bridge-group 102 source-learning
bridge-group 102 spanning-disabled
interface GigabitEthernet0.104
encapsulation dot1Q 104
no ip route-cache
bridge-group 104
no bridge-group 104 source-learning
bridge-group 104 spanning-disabled
interface GigabitEthernet0.105
encapsulation dot1Q 105
no ip route-cache
no cdp enable
bridge-group 105
no bridge-group 105 source-learning
bridge-group 105 spanning-disabled
interface GigabitEthernet0.106
encapsulation dot1Q 106 native
no ip route-cache
bridge-group 1
no bridge-group 1 source-learning
bridge-group 1 spanning-disabled
interface GigabitEthernet0.108
encapsulation dot1Q 108
no ip route-cache
no cdp enable
bridge-group 108
no bridge-group 108 source-learning
bridge-group 108 spanning-disabled
interface BVI1
ip address dhcp client-id GigabitEthernet0
no ip route-cache
ip http server
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
ip radius source-interface BVI1
no logging trap
access-list 1421 permit
access-list 1421 permit
access-list 1421 permit 0.0.0.255
access-list 1421 permit 0.0.0.255
access-list 1421 permit 0.0.255.255
access-list 1421 permit 0.0.255.255
access-list 1421 permit 0.0.255.255
access-list 1421 permit 0.0.255.255
access-list 1421 deny   any
access-list 201 permit 0x0800 0x0000
access-list 201 permit 0x0806 0x0000
access-list 201 deny   0x0000 0xFFFF
snmp-server view NCC mib-2 included
snmp-server community TROUbleIStrouBLE view NCC RO
snmp-server community CHECKtheMAIL RO
snmp-server community HAVocREEk RW
snmp-server community 1aPe3nLnmDt4yVYmbgWoUVjJYz1 view NCC RO 1421
snmp-server community 1aUQ5DAIH2bTBlvJg6RFS5qfsr RO 1421
snmp-server community 1OGgsN21DI4q01QeeIhJGF961 RW 1421
snmp-server enable traps tty
tacacs-server host
tacacs-server host
tacacs-server directed-request
tacacs-server key 7 110A1D5347415C5B53737F7D2E26
radius-server attribute 32 include-in-access-req format %h
radius-server host auth-port 1812 acct-port 1813 key 7 10190C4A533C07185D50721569013D3C3638022F4E0E42400102773D0D481A5E0E
radius-server vsa send accounting
bridge 1 route ip
line con 0
line vty 5 15
sntp server
end

Nexus 7000 w/ 2000 FEX - Interface Status When N7K has power issues

I have multiple nexus 2Ks connected to two N7Ks with my servers connecting to multiple N2Ks accordingly with dual NIC failover capability.
What happens, or what state do the N2K interfaces go into if one of my N7K's looses power given the N2K is effectivly still receiving power?

Hi Ans,
You are rigth, I have defaulted againt the port, now configured with switchport mode FEX, and now the FET-10G is validated
NX7K-1-VDC-3T-S1-L2FP(config-if)# description FEX-101
NX7K-1-VDC-3T-S1-L2FP(config-if)#   switchport
NX7K-1-VDC-3T-S1-L2FP(config-if)#   switchport mode fex-fabric
NX7K-1-VDC-3T-S1-L2FP(config-if)#   fex associate 101
NX7K-1-VDC-3T-S1-L2FP(config-if)#   medium p2p
NX7K-1-VDC-3T-S1-L2FP(config-if)#   channel-group 101
NX7K-1-VDC-3T-S1-L2FP(config-if)#   no shutdown
NX7K-1-VDC-3T-S1-L2FP(config-if)#
NX7K-1-VDC-3T-S1-L2FP(config-if)# sh int e7/33 status
Port             Name            Status    Vlan      Duplex Speed   Type
Eth7/33          FEX-101         notconnec 1         auto    auto    Fabric Exte
NX7K-1-VDC-3T-S1-L2FP(config-if)#
Thanks for your help, and have a nice weekend.
Atte,
EF

Cisco SFP GLC-LH-SM unknown in show interface status

Hi all,
Client installed a single mode fibre run from Distribution Switch to Access switch. The distance is not even greater than 100 Metres but the client insisted since the fibre is free.
On the Cisco Catalyst 2960X-24TS-L (Access layer not stacked) the SFP is identified, but on the Cisco Catalyst 2960X-24TS-L (Distribution switch stacked) the SFP module is "unknown".
access_sw#
Gi1/0/49 access_sw po notconnect 1 auto auto 1000BaseLX SFP
dist_sw#
Gi1/0/49 dist_sw po notconnect 1 auto auto unknown
Distribution switch is running 150-2.EX4
Access switch is running 150-2.EX5
I have configured on both sides speed nonegotiate, above output is showing that the 2 are not even talking to each other since their status is still auto auto...
Any ideas is gladly appreciated in terms of what show commands or diagnostic tests I can do for the interface just to test it?
I have tried to test it but it is saying diagnostic monitoring is not running, how can I run that feature as well? Is that network impacting if I did?
Kind regards,

Hi,
Is there a link light on either side of the connection?
Is the SFP on the distro switch also LX?
If there is no link light, try crossing the strands on one side of the connection and test again.
HTH

Cisco AP 1310 interface status "reset"

any idea why the ap 1310 send the interface to "reset" state:
Feb 28 18:03:00.820 -0600: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot1
1Radio0, changed state to up
*Feb 28 18:03:19.870 -0600: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state
to down
*Feb 28 18:03:19.917 -0600: %LINK-5-CHANGED: Interface Dot11Radio0, changed stat
e to reset
*Feb 28 18:03:20.873 -0600: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot1
1Radio0, changed state to down
*Feb 28 18:03:23.519 -0600: %DOT11-4-UPLINK_ESTABLISHED: Interface Dot11Radio0,
Associated To AP GDL-GDL1-CR001- 001d.a2b0.3910 [None]
*Feb 28 18:03:23.520 -0600: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state
to up

I think it is seems like bug. Upgrade or downgrade the IOS and try.

Interface status on Cisco CAt 4500 switch as source-monitoring

Hi Guys,
I have assigned int gi3/45 on my Cisco 4500 CAT switch as the monitoring port as source and gi3/47 as the destination.
I see this:
GigabitEthernet3/45 is up, line protocol is down (monitoring)
but on the destination port both are up, interface up and line protocol up.
is this natural? I have executed the no shutdown on gi3/45 but it still says down!
is this normal? or there is a problem? i have monitoring on my edge switch CAT 3560 but both are saying UP/UP, shouldn't this be the same since both swithces are running Cisco IOS.
Please respond. I appreciate your input and thanks in advance.
Masood

this interface (g 3/45) is the destination, it says so "monitoring", it normal for the "destination" or "monitoring" port to be up/down coz it's not sending or receiving traffic destined to it, only the mirrored packets from the source port. can you post the "show monitor session #"?

Interface Status in Router

Why does the Ethernet Interface is showing Up and down state when a cable is not connected. Is this a problem if not please let me know why it behaves when compared to Serial interface.

That should not be a problem. Ethernet and Serial are very different technologies, the chip sets in the interfaces are very different, their physical protocols are very different, and the behavior of their interfaces is therefore different.
HTH
Rick

Intel Management Engine Interface Status Device Power Failure

Dear community, Recently I noticed that my Intel Management Engine Interface is not working and show the STATUS_DEVICE_POWER_FAILURE error. My computer is a Lenovo Yoga 2 prowith Windows 8.1 latest Windows update and fresh installMy BIOS has laster firmware 76CN43WWI've installed the laster Intel MEI driver 9.5.15.1730 and the latest Intel chipset driver 10.0.27 Please someone help me to find a solution. Best regards

Have the same problem and it stops me from upgrading to windows 10. Found a solution?

Nexus5548 - "faulty" interface status

Similar Messages

Maybe you are looking for