SWITCH_QOS_TB-5-TRUST_DEVICE_LOST

Why do I get this error message on one of my switches? When it happens it knocks the port out anywhere from a few minutes to a few hours. Here is the config for the port:
switchport access vlan 50
switchport trunk encapsulation dot1q
switchport trunk native vlan 50
switchport mode trunk
switchport voice vlan 20
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
mls qos trust device cisco-phone
mls qos trust cos
auto qos voip cisco-phone
spanning-tree portfast
spanning-tree guard root
mark gibson

we are facing the issue with IP phones and they lost connectvity and start upgrading.
found some errors on the switch logs,
TB-5-TRUST_DEVICE_LOST: cisco-phone no longer detected on port Gi7/2, operational port trust state is now untrusted.
Jan 17 15:03:05: %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: cisco-phone no longer detected on port Gi7/11, operational port trust state is now untrusted.
Jan 17 15:06:44: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Gi7/42, port's configured trust state is now operational.
Jan 17 15:08:51: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Gi7/23, port's configured trust state is now operational.
Jan 17 15:33:57: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Gi7/10, port's configured trust state is now operational.
Jan 17 15:39:19: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Gi7/9, port's configured trust state is now operational.
Jan 17 15:41:20: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Gi7/13, port's configured trust state is now operational.
Jan 17 15:41:29: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Gi7/7, port's configured trust state is now operational.
Jan 17 15:50:59: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Gi7/30, port's configured trust state is now operational.
Jan 17 15:51:34: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Gi7/37, port's configured trust state is now operational.
Jan 18 02:01:31: %SYS-5-CONFIG_I: Configured from 10.14.2.10 by snmp
Jan 18 05:35:08: %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: cisco-phone no longer detected on port Gi8/15, operational port trust state is now untrusted.
Jan 18 05:36:21: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Gi8/15, port's configured trust state is now operational.
Jan 18 07:31:38: %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: cisco-phone no longer detected on port Gi1/45, operational port trust state is now untrusted.
Jan 18 07:33:01: %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: cisco-phone no longer detected on port Gi1/26, operational port trust state is now untrusted.
Jan 18 07:34:58: %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: cisco-phone no longer detected on port Gi9/7, operational port trust state is now untrusted.
Jan 18 07:35:37: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Gi7/11, port's configured trust state is now operational.
Jan 18 07:40:27: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Gi1/45, port's configured trust state is now operational.
Jan 18 07:45:41: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Gi1/43, port's configured trust state is now operational.
Jan 18 07:51:43: %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: cisco-phone no longer detected on port Gi3/3, operational port trust state is now untrusted.
Jan 18 07:51:58: %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: cisco-phone no longer detected on port Gi2/48, operational port trust state is now untrusted.
Jan 18 07:55:48: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Gi2/48, port's configured trust state is now operational.
Jan 18 07:56:48: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Gi3/3, port's configured trust state is now operational.
Jan 18 09:04:33: %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: cisco-phone no longer detected on port Gi3/3, operational port trust state is now untrusted.
Jan 18 09:09:09: %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: cisco-phone no longer detected on port Gi1/45, operational port trust state is now untrusted.
Jan 18 10:16:21: %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: cisco-phone no longer detected on port Gi1/1, operational port trust state is now untrusted.
Jan 18 10:17:43: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Gi1/1, port's configured trust state is now operational.
Jan 20 03:34:13: %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: cisco-phone no longer detected on port Gi7/9, operational port trust state is now untrusted.
Jan 20 03:35:17: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Gi7/9, port's configured trust state is now operational.
show run int gig8/15
Building configuration...
Current configuration : 236 bytes
interface GigabitEthernet8/15
switchport access vlan 1132
switchport mode access
switchport voice vlan 1162
qos trust cos
qos trust device cisco-phone
tx-queue 3
   priority high
   shape percent 33
spanning-tree portfast
end
Need help.

Similar Messages

  • SWITCH_QOS_TB-5-TRUST_DEVICE_LOST affecting 7941 phones only

    Hi, 
    We've got a weird problem that seems to only affect 7941 and 7970 phones. We've getting a lot of errors in the logs on the switches:
    Feb 20 14:17:34: %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: cisco-phone no longer detec
    ted on port Fa2/0/21, operational port trust state is now untrusted.
    Feb 20 14:19:12: %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: cisco-phone no longer detec
    ted on port Fa2/0/23, operational port trust state is now untrusted.
    Feb 20 14:26:12: %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: cisco-phone no longer detec
    ted on port Fa2/0/6, operational port trust state is now untrusted.
    Feb 20 14:30:10: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on
     port Fa2/0/6, port's configured trust state is now operational.
    Feb 20 14:35:32: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on
     port Fa2/0/21, port's configured trust state is now operational.
    Feb 20 14:35:55: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on
     port Fa2/0/23, port's configured trust state is now operational.
    When you look at the devices that are affected by this, it's only 7941 and 7970 phones. These phones are experiencing "robot" voices and the call quality is terrible.
    This was only affecting one particular switch stack (3750's - 5 in a stack mixture of v1 and v2's, all on the latest firmware). This is now affecting another site on another 3750 switch stack (on older firmware). The phones are all on the latest firmware and we've tried rolling back the firmware, but it's still happening.
    Struggling to get a support case logged as the individual phones and switches aren't on support, but the CUCM servers are.
    Any ideas what might be causing this?

    All the ports have our standard config on them:
    interface FastEthernet1/0/6
     switchport access vlan 309
     switchport voice vlan 415
     no logging event link-status
     srr-queue bandwidth share 10 10 60 20
     srr-queue bandwidth shape 10 0 0 0
     priority-queue out
     mls qos trust device cisco-phone
     mls qos trust cos
     no snmp trap link-status
     auto qos voip cisco-phone
     storm-control broadcast level 5.00
     storm-control multicast level 5.00
     spanning-tree portfast
     service-policy input EndUser
    end
    global qos:
    mls qos map policed-dscp  24 26 46 to 0
    mls qos map cos-dscp 0 8 16 24 32 46 48 56
    mls qos srr-queue input bandwidth 90 10
    mls qos srr-queue input threshold 1 8 16
    mls qos srr-queue input threshold 2 34 66
    mls qos srr-queue input buffers 67 33
    mls qos srr-queue input cos-map queue 1 threshold 2 1
    mls qos srr-queue input cos-map queue 1 threshold 3 0
    mls qos srr-queue input cos-map queue 2 threshold 1 2
    mls qos srr-queue input cos-map queue 2 threshold 2 4 6 7
    mls qos srr-queue input cos-map queue 2 threshold 3 3 5
    mls qos srr-queue input dscp-map queue 1 threshold 2 9 10 11 12 13 14 15
    mls qos srr-queue input dscp-map queue 1 threshold 3 0 1 2 3 4 5 6 7
    mls qos srr-queue input dscp-map queue 1 threshold 3 32
    mls qos srr-queue input dscp-map queue 2 threshold 1 16 17 18 19 20 21 22 23
    mls qos srr-queue input dscp-map queue 2 threshold 2 33 34 35 36 37 38 39 48
    mls qos srr-queue input dscp-map queue 2 threshold 2 49 50 51 52 53 54 55 56
    mls qos srr-queue input dscp-map queue 2 threshold 2 57 58 59 60 61 62 63
    mls qos srr-queue input dscp-map queue 2 threshold 3 24 25 26 27 28 29 30 31
    mls qos srr-queue input dscp-map queue 2 threshold 3 40 41 42 43 44 45 46 47
    mls qos srr-queue output cos-map queue 1 threshold 3 5
    mls qos srr-queue output cos-map queue 2 threshold 3 3 6 7
    mls qos srr-queue output cos-map queue 3 threshold 3 2 4
    mls qos srr-queue output cos-map queue 4 threshold 2 1
    mls qos srr-queue output cos-map queue 4 threshold 3 0
    mls qos srr-queue output dscp-map queue 1 threshold 3 40 41 42 43 44 45 46 47
    mls qos srr-queue output dscp-map queue 2 threshold 3 24 25 26 27 28 29 30 31
    mls qos srr-queue output dscp-map queue 2 threshold 3 48 49 50 51 52 53 54 55
    mls qos srr-queue output dscp-map queue 2 threshold 3 56 57 58 59 60 61 62 63
    mls qos srr-queue output dscp-map queue 3 threshold 3 16 17 18 19 20 21 22 23
    mls qos srr-queue output dscp-map queue 3 threshold 3 32 33 34 35 36 37 38 39
    mls qos srr-queue output dscp-map queue 4 threshold 1 8
    mls qos srr-queue output dscp-map queue 4 threshold 2 9 10 11 12 13 14 15
    mls qos srr-queue output dscp-map queue 4 threshold 3 0 1 2 3 4 5 6 7
    mls qos queue-set output 1 threshold 1 138 138 92 138
    mls qos queue-set output 1 threshold 2 138 138 92 400
    mls qos queue-set output 1 threshold 3 36 77 100 318
    mls qos queue-set output 1 threshold 4 20 50 67 400
    mls qos queue-set output 2 threshold 1 149 149 100 149
    mls qos queue-set output 2 threshold 2 118 118 100 235
    mls qos queue-set output 2 threshold 3 41 68 100 272
    mls qos queue-set output 2 threshold 4 42 72 100 242
    mls qos queue-set output 1 buffers 10 10 26 54
    mls qos queue-set output 2 buffers 16 6 17 61
    mls qos
    Thanks

  • Power Controller reports power Imax error detected

    Hi,
    My 3560 switch w/ IOS 12.2(35)SE have below message last night. Would anyone know what happen?
    Sep 23 18:54:58.468 UTC: %ILPOWER-7-DETECT: Interface Fa0/10: Power Device dete
    ted: IEEE PD
    Sep 23 18:54:58.468 UTC: %ILPOWER-5-INVALID_IEEE_CLASS: Interface Fa0/10: has d
    tected invalid IEEE class: 7 device. Power denied
    Sep 23 18:57:37.542 UTC: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error,
    Interface Fa0/12: Power Controller reports power Imax error detected
    Sep 23 18:57:44.580 UTC: %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: cisco-phone no lon
    er detected on port Fa0/12, port set to untrusted.
    Sep 23 18:57:48.674 UTC: %ILPOWER-7-DETECT: Interface Fa0/12: Power Device deteted: Cisco PD
    Sep 23 18:57:48.741 UTC: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Fa0/12: Power Controller reports power Tstart error detected
    Thanks and Regards
    Ernest

    Hi Leo
    Thank you for your quick response but as I said before that Nortel IP phnoe has a designed fault in power module so it meant to fail and cisco switch generate syslog for this Power Controller reports power Imax error detected. Once we replace with new phone, the error disappear and works all fine.
    Now the solution I am looking for this issue as follows:
    While the faulty IP phone still pluged in and keep booting, the switch generate error log and our syslog server keep sending out email alert until one of our engineer log into switch and shut the port. Very often if this happen in weekend or at night then we get hundreds of email.
    Therfore I think it would be nice if Cisco 3750 put this swithport into errdisable state but it's not happening.
    This is the output of errdisable;
    #sh errdisable detect
    ErrDisable Reason            Detection    Mode
    arp-inspection               Enabled      port
    bpduguard                    Enabled      port
    channel-misconfig (STP)      Enabled      port
    community-limit              Enabled      port
    dhcp-rate-limit              Enabled      port
    dtp-flap                     Enabled      port
    gbic-invalid                 Enabled      port
    inline-power                 Enabled      port
    invalid-policy               Enabled      port
    l2ptguard                    Enabled      port
    link-flap                    Enabled      port
    loopback                     Enabled      port
    lsgroup                      Enabled      port
    mac-limit                    Enabled      port
    pagp-flap                    Enabled      port
    port-mode-failure            Enabled      port
    pppoe-ia-rate-limit          Enabled      port
    psecure-violation            Enabled      port/vlan
    security-violation           Enabled      port
    sfp-config-mismatch          Enabled      port
    small-frame                  Enabled      port
    storm-control                Enabled      port
    udld                         Enabled      port
    vmps                         Enabled      port
    ===========================================
    Another thing that this command "power inline port 2x-mode" is not available in our IOS, I am not sure how this command will help.
    Look forward for someone response.
    Thank you all.

  • Accu X

    Can enybody tell me how to get an accu for my NOMAD jukebox Zen Xtra (30GB) MP3 player.
    On the dutch site the accu is out of stock or no longer deli'verable.
    So my MP 3 player is use less.
    Regards Theo

    Its happening constantly,  i cant tell the exact time period as the log file on the switch isnt large enough to keep two consecutive drops.  I cant change the log file yet as I am a contractor and the employeer hasnt given me the abilities to do so on the switch.  The experience on the phone is that the call is dropped, I have had mixed reports of reboots, the device never loses power however.  It does unregister.
    008955: Jul 18 08:31:57.440: %IPPHONE-6-UNREGISTER_NORMAL: ephone-80:SEP18339D15DD36 IP:10.75.210.154 Socket:51 DeviceType:Phone has unregistered normally.
    008957: Jul 18 08:32:04.609: %IPPHONE-6-REGISTER_NEW: ephone-49:SEP10BD180038A9 IP:10.75.210.151 Socket:18 DeviceType:Phone has registered.
    Actually about once an hour
    Jul 30 09:05:38.187 EDT: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Fa4/0/37, port's configured trust state is now operational.
    Jul 30 09:54:07.714 EDT: %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: cisco-phone no longer detected on port Fa4/0/37, operational port trust state is now untrusted.
    Jul 30 09:54:38.356 EDT: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Fa4/0/37, port's configured trust state is now operational.

  • Cisco Touch 8 on MX Product

    I have a customer that has an MX200 who's touch panel 8 keeps saying "no network connection. I know that inside this "kit" is an SX20 codec. At first, I blamed my customer's network because I thought that the touch 8 was being connected thru the customer's network to get to the SX20 being that there is no second ethernet port to connect the panel directly in the codec (like with a C40). To my surprise, the Touch 8 gets connected on the same type of connector as an EX product (big block connector) behind the MX200 unit. Since there is no second ethernet port on the SX20 for touch panel pairing and it's using that big connector, I wonder how the whole thing works internally. Is there a network switch inside the MX200 to allow connections of both the SX20 and the Touch panel 8? I tried looking for documentation on this and can't seem to find anything...
    Please advise. Thanks

    I have found the Root cause of the issue, which the switch's Auto QoS policy is untrusting the endpoint for a short period of time and each time this happens we lose network connectivity  see below:
    Jun 11 16:59:25.399: %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: cisco-phone no longer detected on port Gi6/14, operational port trust state is now untrusted.
    Jun 11 16:59:41.719: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Gi6/14, port's configured trust state is now operational.
    Is this a known issue or does any one know how this can be resolved?

Maybe you are looking for

  • File Sender - get files from DB4 and OS400

    Hi, I'm configuring File - IDOC scenario on XI system, which is on Win platform. I want to pick up flat txt files on DB4 and OS400 via FTP but I+m constantly getting message: Could not process due to error: com.sap.aii.adapter.file.ftp.FTPEx: 550  No

  • Entries in a text field would link to different pages

    Can anyone help with how to set up a text field so that a number entered will take the user to a specific page?  Different numbers entered would take users to a page specific to that number.

  • I can't remove keyboards after Emoji App

    I'm having trouble with removing keyboards and I can't access some of the keys of the keyboard. If I go to Settings>>General>>Keyboard>>Keyboards.  I can add keyboards and have now added like 10 of them but I can't delete them.  I click on Edit and t

  • Can I share my forms with another account?

    I have a Forms account for work but would like to transfer my forms to another co-workers account. I would like to keep my account and all my forms though.

  • What does error -10810 mean ?

    Hi ...   What does error -10810 mean ?  I could find anything on Google for this.