few ports LED light amber - slow reply

[BorislavPenchev0962]

Hello all,

we have few Ports on C3650 with LED Status ACT_AMBER and slower replies to clients.
Ports 6, 12, 13, 14 and 20 - no CRC/input errors or drops. Ports are connected to eLux OS thin/speed clients.
we tried the following:

when client is disconnected - port LED goes off;

sh/no sh - same result; 

switch reboot - same behavior
switch upgrade to 16.12.05 - same behavior

any suggestion would be appreciated !

[Kasun Bandara]

what is the output of #sh interface for specific interface?

[balaji.bandi]

where is this switch connected ? what you see logs ?

post below :

show version

show vlan

show spann brief

show ip interface brief

[JimWicks]

When you initially plug a device into the switch, the port-LED will briefly stay Amber while it goes through the STP listening/learning states into forwarding, then it should turn green.

 If the port remains Amber after the initial STP timers have passed, then that would probably indicate that your switch and the connected end device have not negotiated the link speed/duplex correctly between them.  Your port is probably stuck at 10/Half on one side or something nasty like that, which would also explain the bad performance being experienced by the connected devices..............if that turns out to be the case (if you enable term-mon and wait a while, or do a "show logg" you should see periodic messages indicating any mis-match during negotiation), make sure you have got the Speed/Duplex set to Auto on both sides, or if you decided on hard-coding these then make sure both sides are nailed onto the same Speed/Duplex.  If one end is set to Auto and the other side is nailed-up to a specific Speed/Duplex then bad results can sometimes happen depending upon how your connected device ethernet driver operates.

[marce1000]

  - Use 'switchport mode host' for simple users or host-clients.

 M.

[Leo Laohoo]

Post the complete output to the command "sh interface <PORT> controll".

[BorislavPenchev0962]

we configured manually speed 100 (max in this case) and duplex full. Port went green, but in few minutes went back to amber.

probably as we use derived-config templates for the ports  and dot1x as per client connected configuration has been changed back?

when we re/patch cable - port goes to amber;

here some outputs:

interface GigabitEthernet1/0/6
switchport mode access
device-tracking attach-policy aaa
no logging event link-status
speed auto 10 100
no cdp enable
access-session closed
no snmp trap link-status
source template AAAAA
spanning-tree portfast

 Templates:

interface GigabitEthernet1/0/6
switchport access vlan 12
switchport mode access
switchport voice vlan 123
device-tracking attach-policy aaa
no logging event link-status
speed auto 10 100
no cdp enable
authentication periodic
authentication timer reauthenticate server
access-session closed
access-session port-control auto
mab
no snmp trap link-status
dot1x pae authenticator
storm-control broadcast level 2.50
storm-control action trap
spanning-tree portfast
spanning-tree bpduguard enable
spanning-tree guard root
service-policy type control subscriber BBB
service-policy input CCC
service-policy output D

spanning tree:

sh spanning-tree detail

 VLAN0123 is executing the rstp compatible Spanning Tree protocol
  Bridge Identifier has priority 4096, sysid 100, address 707d.b9b1.7380
  Configured hello time 2, max age 20, forward delay 15, transmit hold-count 6
  We are the root of the spanning tree
  Topology change flag not set, detected flag not set
  Number of topology changes 0 last change occurred 4d17h ago
  Times:  hold 1, topology change 35, notification 2
          hello 2, max age 20, forward delay 15
  Timers: hello 0, topology change 0, notification 0, aging 300

 Port 6 (GigabitEthernet1/0/6) of VLAN0123 is designated forwarding
   Port path cost 19, Port priority 128, Port Identifier 128.6.
   Designated root has priority 4196, 
   Designated bridge has priority 4196, 
   Designated port id is 128.6, designated path cost 0
   Timers: message age 0, forward delay 0, hold 0
   Number of transitions to forwarding state: 1
   The port is in the portfast mode
   Link type is point-to-point by default
   Bpdu guard is enabled
   Root guard is enabled on the port
   BPDU: sent 12914, received 0

a good port:

interface GigabitEthernet1/0/21
 switchport mode access
 device-tracking attach-policy aaa
 no logging event link-status
 speed auto 10 100
 no cdp enable
 access-session closed
 no snmp trap link-status
 source template AAAAA
 spanning-tree portfast
end

#show int g1/0/21
GigabitEthernet1/0/21 is up, line protocol is up (connected)
  
  MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 100Mb/s, media type is 10/100/1000BaseTX
  input flow-control is on, output flow-control is unsupported
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:01, output 00:00:01, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: Class-based queueing
  Output queue: 0/40 (size/max)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     249852 packets input, 40011882 bytes, 0 no buffer
     Received 11342 broadcasts (0 multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 0 multicast, 0 pause input
     0 input packets with dribble condition detected
     591303 packets output, 53552577 bytes, 0 underruns
     Output 4656 broadcasts (0 multicasts)
     0 output errors, 0 collisions, 1 interface resets
     0 unknown protocol drops
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 pause output
     0 output buffer failures, 0 output buffers swapped out

#show int g1/0/21 switchport
Switchport: Enabled
Administrative Mode: static access
Operational Mode: static access
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: native
Negotiation of Trunking: Off
Access Mode VLAN: 5
Administrative Native VLAN tagging: disabled
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk Native VLAN tagging: enabled
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk associations: none
Administrative private-vlan trunk mappings: none
Operational private-vlan: none
Trunking VLANs Enabled: ALL
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL

Protected: false
Unknown unicast blocked: disabled
Unknown multicast blocked: disabled
Vepa Enabled: false
Appliance trust: none

Port 21 (GigabitEthernet1/0/21) of VLAN0123 is designated forwarding
   Port path cost 19, Port priority 128, Port Identifier 128.20.
   Designated root has priority 4196,  
   Designated bridge has priority 4196,  
   Designated port id is 128.20, designated path cost 0
   Timers: message age 0, forward delay 0, hold 0
   Number of transitions to forwarding state: 1
   The port is in the portfast mode
   Link type is point-to-point by default
   Bpdu guard is enabled
   Root guard is enabled on the port
   BPDU: sent 137844, received 0

[marce1000]

       - When port(s) go to amber -> check logs

 M.

[Leo Laohoo]

I do not see anything wrong with this output. 

If the ports go into amber, are there anything in the logs? 

Is error-disable auto-recovery enabled?

[BorislavPenchev0962]

1 its probably speed/duplex issue, but l think that configuration is changing itself

/as we use derived-config templates for the ports and dot1x/

if we manually put 100/full - green leds for a few minutes

2 when commands are applied:to change security-violation enabled, is still security-violation Disabled ?

Switch(config)# errdisable recovery cause psecure-violation
Switch(config)# errdisable recovery interval 30

3 we tried to shut/no shut clients

#sh hardware led port status

Current Mode: STATUS
ACT_GREEN ACT_GREEN BLACK BLACK ACT_GREEN ACT_GREEN ACT_GREEN ACT_GREEN BLACK ACT_GREEN BLACK ACT_GREEN ACT_GREEN ACT_GREEN BLACK BLACK BLACK ACT_GREEN BLACK ACT_GREEN BLACK ACT_GREEN BLACK BLACK BLACK BLACK BLACK BLACK

#sh hardware led port status

Current Mode: STATUS
ACT_GREEN ACT_GREEN BLACK BLACK ACT_GREEN ACT_GREEN ACT_GREEN ACT_GREEN BLACK ACT_GREEN BLACK ACT_GREEN ACT_GREEN ACT_GREEN BLACK BLACK BLACK ACT_GREEN BLACK ACT_GREEN BLACK ACT_GREEN BLACK BLACK BLACK BLACK BLACK BLACK

[JimWicks]

"show logg"  ??

[BorislavPenchev0962]

this looks like this bug: CSCvu34364 https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvu34364

but there is no workaround?

[BorislavPenchev0962]

we replaced the switch and now experience the same issue ... here show logg:

------------------ show logging ------------------


Syslog logging: enabled (0 messages dropped, 2 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.



No Inactive Message Discriminator.


    Console logging: disabled
    Monitor logging: level debugging, 0 messages logged, xml disabled,
                     filtering disabled
    Buffer logging:  level notifications, 119 messages logged, xml disabled,
                    filtering disabled
    Exception Logging: size (4096 bytes)
    Count and timestamp logging messages: disabled
    File logging: disabled
    Persistent logging: disabled

No active filter modules.

    Trap logging: level informational, 175 message lines logged
        Logging to   (data) (udp port 514, audit disabled,
              link up),
              174 message lines logged, 
              0 message lines rate-limited, 
              0 message lines dropped-by-MD, 
              xml disabled, sequence number disabled
              filtering disabled
        Logging to   (data) (udp port 514, audit disabled,
              link up),
              175 message lines logged, 
              0 message lines rate-limited, 
              0 message lines dropped-by-MD, 
              xml disabled, sequence number disabled
              filtering disabled
        Logging to   (udp port 514, audit disabled,
              link up),
              175 message lines logged, 
              0 message lines rate-limited, 
              0 message lines dropped-by-MD, 
              xml disabled, sequence number disabled
              filtering disabled
        Logging Source-Interface:       VRF Name:
        Vlan1000                        

Log Buffer (32768 bytes):

*Mar 14 19:04:06.952: %SPANTREE-5-EXTENDED_SYSID: Extended SysId enabled for type vlan
*Mar 14 19:04:08.803: %LINK-3-UPDOWN: Interface Lsmpi18/3, changed state to up
*Mar 14 19:04:08.806: %LINK-3-UPDOWN: Interface EOBC18/1, changed state to up
*Mar 14 19:04:08.807: %LINEPROTO-5-UPDOWN: Line protocol on Interface LI-Null0, changed state to up
*Mar 14 19:04:08.809: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to down
*Mar 14 19:04:08.809: %LINK-3-UPDOWN: Interface LIIN18/2, changed state to up
*Mar 14 19:03:27.445: %STACKMGR-4-SWITCH_ADDED: Switch 1 R0/0: stack_mgr: Switch 1 has been added to the stack.
*Mar 14 19:03:32.180: %STACKMGR-4-SWITCH_ADDED: Switch 1 R0/0: stack_mgr: Switch 1 has been added to the stack.
*Mar 14 19:03:34.183: %STACKMGR-4-SWITCH_ADDED: Switch 1 R0/0: stack_mgr: Switch 1 has been added to the stack.
*Mar 14 19:04:09.889: %LINEPROTO-5-UPDOWN: Line protocol on Interface Lsmpi18/3, changed state to up
*Mar 14 19:04:09.889: %LINEPROTO-5-UPDOWN: Line protocol on Interface EOBC18/1, changed state to up
*Mar 14 19:04:09.890: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to up
*Mar 14 19:04:09.890: %LINEPROTO-5-UPDOWN: Line protocol on Interface LIIN18/2, changed state to up
*Mar 14 19:04:11.621: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
*Mar 14 19:04:13.471: %SYS-5-CONFIG_P: Configured programmatically by process MGMT VRF Process from console as vty0
*Mar 14 19:04:13.522: %CRYPTO_ENGINE-5-KEY_ADDITION: A key named TP-self-signed-2471666016 has been generated or imported by crypto config
*Mar 14 19:04:13.550: %SYS-5-CONFIG_P: Configured programmatically by process MGMT VRF Process from console as vty0
*Mar 14 19:04:13.562: %CRYPTO_ENGINE-5-KEY_ADDITION: A key named SWI-123-001.kubus-it.de has been generated or imported by crypto config
*Mar 14 19:04:13.589: %CRYPTO_ENGINE-5-KEY_ADDITION: A key named SLA-KeyPair has been generated or imported by crypto config
*Mar 14 19:04:13.620: %CRYPTO_ENGINE-5-KEY_ADDITION: A key named SLA-KeyPair2 has been generated or imported by crypto config
*Mar 14 19:04:13: %SYS-5-LOG_CONFIG_CHANGE: Buffer logging: level notifications, xml disabled, filtering disabled, size (32768)
*Mar 14 19:04:13: %SYS-5-LOG_CONFIG_CHANGE: Console logging disabled
*Mar 14 19:04:13: %AAAA-4-CLI_DEPRECATED: WARNING: Command has been added to the configuration using a type 7 password. However, type 7 passwords will soon be deprecated. Migrate to a supported password type
*Mar 14 19:04:13: %AAAA-4-CLI_DEPRECATED: WARNING: Command has been added to the configuration using a type 7 password. However, type 7 passwords will soon be deprecated. Migrate to a supported password type
*Mar 14 19:04:13: %AAAA-4-CLI_DEPRECATED: WARNING: Command has been added to the configuration using a type 7 password. However, type 7 passwords will soon be deprecated. Migrate to a supported password type
*Mar 14 19:04:13: %AAAA-4-CLI_DEPRECATED: WARNING: Command has been added to the configuration using a type 7 password. However, type 7 passwords will soon be deprecated. Migrate to a supported password type
*Mar 14 19:04:13: %AAAA-4-CLI_DEPRECATED: WARNING: Command has been added to the configuration using a type 7 password. However, type 7 passwords will soon be deprecated. Migrate to a supported password type
*Mar 14 20:04:15: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1000, changed state to down
*Mar 14 20:04:17: %LINK-5-CHANGED: Interface GigabitEthernet0/0, changed state to administratively down
*Mar 14 20:04:18: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to down
*Mar 14 20:04:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan100, changed state to down
*Mar 14 20:04:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan200, changed state to down
*Mar 14 20:04:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2220, changed state to down
*Mar 14 20:04:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2553, changed state to down
*Mar 14 20:04:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2886, changed state to down
*Mar 14 20:04:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan3220, changed state to down
*Mar 14 20:04:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan3553, changed state to down
*Mar 14 20:04:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan3886, changed state to down
*Mar 14 20:04:20: %LINK-5-CHANGED: Interface Vlan1, changed state to administratively down
*Mar 14 20:04:21: %AAAA-4-CLI_DEPRECATED: WARNING: Command has been added to the configuration using a type 7 password. However, type 7 passwords will soon be deprecated. Migrate to a supported password type
*Mar 14 20:04:21: %SYS-5-CONFIG_I: Configured from memory by console
*Mar 14 20:04:21: %FMANRP_QOS-4-COPPMODIFY: Police rate modification for COPP system class (system-cpp-police-topology-control) is discouraged. User can go to default rate by running 'cpp system-default' CLI.
*Mar 14 20:04:21: %FMANRP_QOS-4-COPPMODRANGE: Police rate modification for COPP system class (system-cpp-police-forus) is out-of-range. User can go to default rate by running 'cpp system-default' CLI.
*Mar 14 20:04:21: %FMANRP_QOS-4-COPPMODRANGE: Police rate modification for COPP system class (system-cpp-default) is out-of-range. User can go to default rate by running 'cpp system-default' CLI.
*Mar 14 20:04:21: %SYS-5-CONFIG_P: Configured programmatically by process CPP MQC QoS Policy manager from console as vty1
*Mar 14 20:04:22: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Mar 14 20:04:23: %SYS-5-RESTART: System restarted --
Cisco IOS Software [Gibraltar], Catalyst L3 Switch Software (CAT3K_CAA-UNIVERSALK9-M), Version 16.12.4, RELEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2020 by Cisco Systems, Inc.
Compiled Thu 09-Jul-20 18:20 by mcpre
*Mar 14 20:04:24: %SNMP-5-COLDSTART: SNMP agent on host SWI-123-001 is undergoing a cold start
*Mar 14 20:04:25: %ILPOWER-5-DETECT: Interface Gi1/0/6: Power Device detected: IEEE PD
*Mar 14 20:04:25: %ILPOWER-5-DETECT: Interface Gi1/0/10: Power Device detected: IEEE PD
*Mar 14 20:04:25: %ILPOWER-5-DETECT: Interface Gi1/0/12: Power Device detected: IEEE PD
*Mar 14 20:04:25: %ILPOWER-5-DETECT: Interface Gi1/0/13: Power Device detected: IEEE PD
*Mar 14 20:04:25: %ILPOWER-5-DETECT: Interface Gi1/0/14: Power Device detected: IEEE PD
*Mar 14 20:04:26: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/13: Power granted
*Mar 14 20:04:26: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/14: Power granted
*Mar 14 20:04:26: %ILPOWER-5-DETECT: Interface Gi1/0/18: Power Device detected: IEEE PD
*Mar 14 20:04:26: %ILPOWER-5-DETECT: Interface Gi1/0/20: Power Device detected: IEEE PD
*Mar 14 20:04:26: %ILPOWER-5-DETECT: Interface Gi1/0/22: Power Device detected: IEEE PD
*Mar 14 20:04:26: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/6: Power granted
*Mar 14 20:04:26: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/10: Power granted
*Mar 14 20:04:26: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/12: Power granted
*Mar 14 20:04:26: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/18: Power granted
*Mar 14 20:04:26: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/22: Power granted
*Mar 14 20:04:27: %PKI-2-NON_AUTHORITATIVE_CLOCK: PKI functions can not be initialized until an authoritative time source, like NTP, can be obtained.
*Mar 14 20:04:27: %CRYPTO_ENGINE-5-KEY_ADDITION: A key named CISCO_IDEVID_SUDI_LEGACY has been generated or imported by pki-sudi
*Mar 14 20:04:27: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/20: Power granted
*Mar 14 20:04:27: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up
*Mar 14 20:04:27: %CRYPTO_ENGINE-5-KEY_ADDITION: A key named CISCO_IDEVID_SUDI has been generated or imported by pki-sudi
*Mar 14 20:04:27: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/2, changed state to up
*Mar 14 20:04:28: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to up
*Mar 14 20:04:28: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/2, changed state to up
*Mar 14 20:04:29: %CRYPTO_ENGINE-5-KEY_ADDITION: A key named TP-self-signed-2471666016.server has been generated or imported by crypto-engine
*Mar 14 20:04:31: %SYS-5-CONFIG_P: Configured programmatically by process EPM CREATE DEFAULT CWA URL ACL from console as console
*Mar 14 20:04:40: %RADIUS-4-RADIUS_DEAD: RADIUS server  1812,1813 is not responding.
*Mar 14 20:04:40: %RADIUS-4-RADIUS_ALIVE: RADIUS server  :1812,1813 is being marked alive.
*Mar 14 20:04:49: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/5, change state to up
*Mar 14 20:04:50: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/5, changed state to up
*Mar 14 20:04:54: %DOT1X-5-FAIL: Switch 1 R0/0: sessmgrd: Authentication failed for client (0068.ebf2.43d7) with reason (AAA Server Down) on Interface Gi1/0/7 AuditSessionID 0A2BF0020000000C89D160C8 Username: 
*Mar 14 20:04:54: %DOT1X-5-FAIL: Switch 1 R0/0: sessmgrd: Authentication failed for client (0068.ebf2.43d5) with reason (AAA Server Down) on Interface Gi1/0/8 AuditSessionID 0A2BF0020000000D89D16107 Username: 
*Mar 14 20:04:58: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1000, changed state to up
*Mar 14 20:04:58: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan3220, changed state to up
*Mar 14 20:04:58: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan3553, changed state to up
*Mar 14 20:04:58: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan3886, changed state to up
*Mar 14 20:04:58: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2220, changed state to up
*Mar 14 20:04:58: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2553, changed state to up
*Mar 14 20:04:58: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2886, changed state to up
*Mar 14 20:05:02: %OSPF-5-ADJCHG: Process 2, Nbr 2 on Vlan3553 from LOADING to FULL, Loading Done
*Mar 14 20:05:02: %OSPF-5-ADJCHG: Process 3, Nbr 1 on Vlan3886 from LOADING to FULL, Loading Done
*Mar 14 20:05:02: %OSPF-5-ADJCHG: Process 1, Nbr  on Vlan3220 from LOADING to FULL, Loading Done
*Mar 14 20:05:02: %OSPF-5-ADJCHG: Process 3, Nbr 1 on Vlan2886 from LOADING to FULL, Loading Done
*Mar 14 20:05:02: %OSPF-5-ADJCHG: Process 2, Nbr  on Vlan2553 from LOADING to FULL, Loading Done
*Mar 14 20:05:02: %OSPF-5-ADJCHG: Process 1, Nbr  on Vlan2220 from LOADING to FULL, Loading Done
*Mar 14 20:05:05: %RADIUS-4-RADIUS_DEAD: RADIUS server :1812,1813 is not responding.
*Mar 14 20:05:05: %RADIUS-4-RADIUS_ALIVE: RADIUS server :1812,1813 is being marked alive.
*Mar 14 20:05:04: %SESSION_MGR-5-FAIL: Switch 1 R0/0: sessmgrd: Authorization failed or unapplied for client (0068.e2.43d5) on Interface GigabitEthernet1/0/8 AuditSessionID 0A2BF0020000000D89D16107. Failure reason: Authc fail. Authc failure reason: AAA Server Down.
*Mar 14 20:05:04: %SESSION_MGR-5-FAIL: Switch 1 R0/0: sessmgrd: Authorization failed or unapplied for client (0068.eb.43d7) on Interface GigabitEthernet1/0/7 AuditSessionID 0A2BF0020000000C89D160C8. Failure reason: Authc fail. Authc failure reason: AAA Server Down.
*Mar 14 20:05:04: %SESSION_MGR-5-FAIL: Switch 1 R0/0: sessmgrd: Authorization failed or unapplied for client (000d.f.1fc8) on Interface GigabitEthernet1/0/20 AuditSessionID 0A2BF0020000000E89D18389. Failure reason: Authc fail. Authc failure reason: AAA Server Down.
*Mar 14 20:05:04: %SESSION_MGR-5-FAIL: Switch 1 R0/0: sessmgrd: Authorization failed or unapplied for client (008.ebf2.435) on Interface GigabitEthernet1/0/8 AuditSessionID 0A2BF0020000000D89D16107. Failure reason: Authc fail. Authc failure reason: AAA Server Down.
*Mar 14 20:05:04: %SESSION_MGR-5-FAIL: Switch 1 R0/0: sessmgrd: Authorization failed or unapplied for client (0068.ebf3d7) on Interface GigabitEthernet1/0/7 AuditSessionID 0A2BF0020000000C89D160C8. Failure reason: Authc fail. Authc failure reason: AAA Server Down.
*Mar 14 20:05:09: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan100, changed state to up
*Mar 14 20:05:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan200, changed state to up
*Mar 14 20:05:27: %SMART_LIC-5-END_POINT_RESET: End Point list reset
*Mar 14 20:05:28: %SMART_LIC-5-SYSTEM_CLOCK_CHANGED: Smart Agent for Licensing System clock has been changed
Mar 14 20:06:14: %DOT1X-5-FAIL: Switch 1 R0/0: sessmgrd: Authentication failed for client (00.f803.1fc8) with reason (No Response from Client) on Interface Gi1/0/20 AuditSessionID 0A2BF0020000000E18389
Mar 14 20:06:15: %DOT1X-5-FAIL: Switch 1 R0/0: sessmgrd: Authentication failed for client (7074.6826) with reason (Cred Fail) on Interface Gi1/0/22 AuditSessionID 0A2BF0020000001889D2E81C Username: WLAN_802.1x
Mar 14 20:06:27: %DOT1X-5-FAIL: Switch 1 R0/0: sessmgrd: Authentication failed for client (0020f5) with reason (No Response from Client) on Interface Gi1/0/10 AuditSessionID 0A2BF0020000001089B5AF
Mar 14 20:07:02: %DOT1X-5-FAIL: Switch 1 R0/0: sessmgrd: Authentication failed for client (000d.1d1a) with reason (No Response from Client) on Interface Gi1/0/18 AuditSessionID 0A2BF00200000011824003
Mar 14 20:15:56: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: svcCiscoPrimeCLI] [Source: 172.28.1.171] [localport: 22] at 20:15:56 MET Mon Mar 14 2022
Mar 14 20:16:01: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: svcCiscoPrimeCLI] [Source: 172.28.1.171] [localport: 22] at 20:16:01 MET Mon Mar 14 2022
Mar 14 20:16:37: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: svcCiscoPrimeCLI] [Source: 172.28.1.171] [localport: 22] at 20:16:37 MET Mon Mar 14 2022
Mar 14 21:10:31: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: svcCiscoPrimeCLI] [Source: 172.28.1.171] [localport: 22] at 21:10:31 MET Mon Mar 14 2022
Mar 14 22:31:12: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: cwadm] [Source: 10.117.16.53] [localport: 22] at 22:31:12 MET Mon Mar 14 2022
Mar 14 22:55:36: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: svcCiscoPrimeCLI] [Source: 172.28.1.171] [localport: 22] at 22:55:36 MET Mon Mar 14 2022
Mar 14 22:56:01: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: svcCiscoPrimeCLI] [Source: 172.28.1.171] [localport: 22] at 22:56:01 MET Mon Mar 14 2022
Mar 14 22:56:58: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: svcCiscoPrimeCLI] [Source: 172.28.1.171] [localport: 22] at 22:56:58 MET Mon Mar 14 2022
Mar 15 01:11:56: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: svcCiscoPrimeCLI] [Source: 172.28.1.171] [localport: 22] at 01:11:56 MET Tue Mar 15 2022
Mar 15 05:13:09: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: svcCiscoPrimeCLI] [Source: 172.28.1.171] [localport: 22] at 05:13:09 MET Tue Mar 15 2022
Mar 15 07:50:49: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: aki05095] [Source: 10.117.18.22] [localport: 22] at 07:50:49 MET Tue Mar 15 2022
Mar 15 07:55:27: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: aki05095] [Source: 10.117.18.22] [localport: 22] at 07:55:27 MET Tue Mar 15 2022