ILPOWER-3-CONTROLLER_ERR:

My syslog server is blowing up with "ILPOWER-3-CONTROLLER_ERR: Controller error, controller number 0-4: accessing failed" messages from my 3550/3560-24/48-PWR-SMI switches running 12.2(46)SE.  The Error Message Decoder was no help and I've been unable to find any docs with troubleshooting steps or bugs identified.  The switches are both supplying and not supplying inline power to VoIP Phones and etc. 
If anyone could point me to a troubleshooting guide or Cisco documentation that identifies that the alerts are non-impacting to the switch’s inline power capabilities that would be grand. Oh and possibly how to disable the alerts if that is the case. 

The only instances of these messages I see in TAC service requests point to a true controller failure requiring an RMA of new hardware to fix.

Similar Messages

  • Need information on CSCeb24148 & CSCea40671

    Hello;
        Could you please provide the information on the following bugs
    1. CSCeb24148
    2. CSCea40671
    I checked in the bus toolkit. But no information is available.
    Thanks & Regards
    Sreejith R

    CSCeb24148 is a duplicate of  CSCea40671
    The Release note is:
    Symptom:
    When a Cisco Catalyst 3550-24PWR interface receives an Electostatic Discharge
    (ESD), from a powered IP Phone, for example, some interfaces go down and no
    longer provide power.
    Workaround:
    Issues shutdown and then no shutdown on the affected interfaces.
    Also, version 12.1(14)EA1 or later provides an ESD recovering mechanism.
    Please upgrade to at least 12.1(14)EA1.
    Another variant of the release note:
    Symptom:
    The following message is displayed on a Catalyst 3550-24PWR:
    %ILPOWER-3-CONTROLLER_ERR: Controller error, Controller number 3: has been reset unexpectedly or s2w bus err
    The interfaces might go down as a result, and the user must issue the interface commands
    shutdown and no shutdown on the affected interfaces.
    Condition:
    The Catalyst 3550-24PWR received an Electro Static Discharge (ESD) event.
    Workaround:
    Make sure that the devices are correctly grounded.
    Also, version 12.1(14)EA1 or later provides an ESD recovering mechanism.
    Please upgrade to at least 12.1(14)EA1.
    We will investigate why they are not published on Bug Toolkit.  They should be.

  • LMS add events?

    So recently we've had some 3750 controller failures.  to be exact, today's issue is:
    Nov  1 10:31:39: %ILPOWER-3-CONTROLLER_ERR: Controller error, Controller number 8: accessing failed
    So I was thinking of how I could send out alerts on LMS.  Keep in mind - when a controller goes bad, that log is generated every minute - I really dont want 600 pages before the issue's resolved (if I were to use " automated syslog action" notifications)
    looking at the switch on LMS - it shows no events/alerts  - so that issue is not part of any event set.
    My question is - could I create user-defined events/event sets, or is there any other way of LMS paging once when it receives the first syslog, then a resolution alert when the issues fixed?
    details:
    lms 4.1 - soft appliance
    syslogs and traps are being sent from switch to lms server
    LMS did indeed receive the controller logs
    switch with issue is one WS-C3750-48P out of a stack of 4 WS-C3750-48P's

    You want to create a raise and clear for this type of event but there is only a syslog that can raise.
    So it can't be done like that
    All you can do is create an automated action that does something when this syslog appears
    Cheers,
    Michel

  • %ILPOWER-3-CONTROLLER_PORT_ERR: on 3750x POE

    Hi,
    can someone explain me what does it means? on my 3750x is a continuous log like this
    Nov 24 13:19:36: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/26: Power Controller reports power Tstart error detected
    and with this command i saw this:
    #show power inline
    Gi1/0/26     auto     faulty     0.0 n/a n/a     30.0
    how can i fix this?, and what is the problem?

    Thank you for the answer
    i found the problem. Yesterday after the post
    i had disabled the electrical supply on the port
    Gi1/0/26 auto off 0.0 n/a n/a 30.0
    And i had received a:
    %SPANTREE-2-BLOCK_BPDUGUARD: Received BPDU on port Gi1/0/26 with BPDU Guard enabled. Disabling port.
    Nov 24 14:00:50: %PM-4-ERR_DISABLE: bpduguard error detected on Gi1/0/26, putting Gi1/0/26 in err-disable state
    After this i went on the interested area
    The user make a loop with the rj45 outline of the ip/phone on another point of connection.
    Users can be very dangerous! :D
    Only for the case study i have test the cable like you had required:
    Interface Speed Local pair Pair length        Remote pair Pair status
    Gi1/0/26  100M  Pair A     N/A                Pair B      Normal
                                 Pair B     N/A                Pair A      Normal
                                 Pair C     N/A                Pair D      Normal
                                 Pair D     N/A                Pair C      Normal
    now all it's ok
    Gi1/0/26  disponibile        notconnect   200          full    100 10/100/1000BaseTX
    Gi1/0/26  auto   on         4.0     Ieee PD             1     30.0

  • Ask for help :( "%ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/17: Power given, but Power Controller does not report Power Good"

    This question is used a translator.... 
    Current conditions 
     - SW1 ----- Power injector ------ AP(cisco is not another model)
     - Port, AP, Power injector, Switch <-> Injector UTP cable  Problems occur even after replacement
     - Power injector <->AP UTP canle No exchange
     - Poe was OFF the function. This is because it is being used for Power Injector. -> Do not generate failure logs
     - But even if another AP is turned ON POE function, no error messages.
    SW1#show logging (5 mins cycle persists)
    May  4 10:37:32.527: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/17: Power given, but Power Controller does not report Power Good
    May  4 10:37:42.556: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to down
    May  4 10:37:43.562: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17, changed state to down
    May  4 10:37:50.032: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17, changed state to up
    May  4 10:37:52.046: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to up
    May  4 10:38:03.238: %ILPOWER-7-DETECT: Interface Gi1/0/17: Power Device detected: IEEE PD
    SW1#show cable-diagnostics tdr interface gi 1/0/17    <----- Issues AP         
    TDR test last run on: May 04 10:49:14
    Interface Speed Local pair Pair length        Remote pair Pair status
    Gi1/0/17  1000M Pair A     84   +/- 10 meters Pair B      Normal              
                                Pair B     84   +/- 10 meters Pair A      Normal              
                                Pair C     84   +/- 10 meters Pair D      Normal              
                                Pair D     84   +/- 10 meters Pair C      Normal              
    SW1#show cable-diagnostics tdr interface gigabitEthernet 1/0/18    <--------- Normal AP
    TDR test last run on: May 04 11:01:04
    Interface Speed Local pair Pair length        Remote pair Pair status
    Gi1/0/18  1000M Pair A     92   +/- 10 meters Pair B      Normal              
                               Pair B     92   +/- 10 meters Pair A      Normal              
                               Pair C     92   +/- 10 meters Pair D      Normal              
                               Pair D     92   +/- 10 meters Pair C      Normal  
    SW1#show cable-diagnostics tdr interface gigabitEthernet 1/0/1   <--------- Normal AP
    TDR test last run on: May 04 11:01:56
    Interface Speed Local pair Pair length        Remote pair Pair status
    Gi1/0/1   1000M Pair A     79   +/- 10 meters Pair B      Normal              
                               Pair B     79   +/- 10 meters Pair A      Normal              
                               Pair C     79   +/- 10 meters Pair D      Normal              
                               Pair D     79   +/- 10 meters Pair C      Normal              
    SW1#show power inline    <-------- (Check every 5 seconds)
    Module   Available     Used     Remaining
                   (Watts)     (Watts)    (Watts) 
    1              370.0      200.2       169.8
    Interface Admin  Oper       Power     Device                           Class   Max
                                                (Watts)                            
    SW1#show power inline | in 17
    Gi1/0/17  auto     off        0.0                 n/a                               n/a   30.0 
    SW1#show power inline | in 17
    Gi1/0/17  auto     on         15.4             Ieee PD                         0     30.0 
    SW1#show power inline | in 17
    Gi1/0/17  auto     on         15.4             Xirrus XR2426, 1.0G     0     30.0 
    SW1#show power inline | in 17
    Gi1/0/17  auto     faulty     0.0              n/a                                 n/a   30.0 
    SW1#show power inline | in 17
    Gi1/0/17  auto     off        0.0                n/a                                  n/a   30.0

    Plug the Xirrus AP directly to the switch port and see if the logs go away or not.

  • ILPOWER-3-CONTROLLER_PORT_ERR:

    Getting Error on cisco WS-C3650-24PD switch
    Jun  9 13:39:51.152: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/6: Power Controller reports Short detected
    the problem is this port is connected to a UPS network management card, so this port should not be trying to engage PoE at all on this port. I turned off PoE on this port manually and this message stopped. is this possibly an issue with the switch hardware or do you think it might be more or a software bug?

    i swapped out the cable and set the port back to auto for PoE. i have not received that error since the cable swap, however after reissuing the command i get the same output
    S-BAY-CORE1#sh cable tdr interface G1/0/6
    TDR test last run on: June 11 09:57:47
    Interface Speed Local pair Pair length        Remote pair Pair status
    Gi1/0/6   100M  Pair A     0    +/- 1  meters Pair B      Normal
                    Pair B     0    +/- 1  meters Pair A      Normal
                    Pair C     1    +/- 1  meters N/A         Short
                    Pair D     2    +/- 1  meters N/A         Short
    Now keep in mind the network interface connected to the port is only 10/100

  • Cisco 3650 Issue with 1231 AP

    hi all,
    i've got an issue with a new cisco 3650 48 port wherein older AP 1231 keeps on disconnecting.
    the connection is just a simple trunk.
    #sh run int g1/0/47
    Building configuration...
    Current configuration : 62 bytes
    interface GigabitEthernet1/0/47
     switchport mode trunk
    end
    1231 is working fine on a 3560.
    could someone advice if anything else need to do on 3650?
    *Apr 21 09:32:33.243: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to down
    *Apr 21 09:32:34.255: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to down
    *Apr 21 09:32:37.369: %ILPOWER-7-DETECT: Interface Gi1/0/47: Power Device detected: IEEE PD
    *Apr 21 09:32:40.406: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/47: PD removed
    *Apr 21 09:32:40.407: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/47: Power given, but Power Controller does not report Power Good
    *Apr 21 09:32:48.994: %ILPOWER-7-DETECT: Interface Gi1/0/47: Power Device detected: Cisco PD
    *Apr 21 09:32:49.473: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/47: Power granted
    *Apr 21 09:32:53.355: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to up
    *Apr 21 09:32:55.356: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to up
    *Apr 21 09:34:27.142: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/47: PD removed
    *Apr 21 09:34:27.142: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/47: Power Controller reports power Imax error detected
    *Apr 21 09:34:27.847: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to down
    *Apr 21 09:34:28.855: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to down
    *Apr 21 09:34:39.384: %ILPOWER-7-DETECT: Interface Gi1/0/47: Power Device detected: Cisco PD
    *Apr 21 09:34:40.235: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/47: Power granted
    *Apr 21 09:34:43.875: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to up
    *Apr 21 09:34:45.874: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to up

    pre,
    i don't think it's a cable issue. correction on the working AP, it's supposed to be a AIR-SAP1602E.
    this AP is working on the 3650.
    i've searched and i think the AIR-AP1231 isn't supported on this switch platform.
    http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3650/software/release/3e/release_notes/OL3264701.html#18425
    this new switch isn't friendly. first, i had the issue with PVLAN and now this :(

  • Impossible to use mAb with Alcatel phone

    Hello
    I try to configure mab authentication with alcatel Phone "ipTouch".
    The radius is an ISE version 1.2.1
    It is impossible to autenticate with mab.
    On the Ise the error is:
        "Event  5434 Endpoint conducted several failed authentications of the same scenario"
        " Failure Reason  11514 Unexpectedly received empty TLS message; treating as a rejection by the client"
    On the switch the error message is:
    2960-09#
    Dec 15 11:13:50.090: %AUTHMGR-5-START: Starting 'mab' for client (0080.9fc8.a9eb) on Interface Gi1/0/11 AuditSessionID
    0A0A510A0000010A2E95860F
    Dec 15 11:13:50.125: %MAB-5-FAIL: Authentication failed for client (0080.9fc8.a9eb) on Interface Gi1/0/11 AuditSessionID
    0A0A510A0000010A2E95860F
    Dec 15 11:13:50.125: %AUTHMGR-7-RESULT: Authentication result 'no-response' from 'mab' for client (0080.9fc8.a9eb) on
    Interface Gi1/0/11 AuditSessionID 0A0A510A0000010A2E95860F
    Dec 15 11:13:50.125: %AUTHMGR-7-FAILOVER: Failing over from 'mab' for client (0080.9fc8.a9eb) on Interface Gi1/0/11
    AuditSessionID 0A0A510A0000010A2E95860F
    2960-09#
    Dec 15 11:13:50.125: %AUTHMGR-5-START: Starting 'dot1x' for client (0080.9fc8.a9eb) on Interface Gi1/0/11 AuditSessionID
    0A0A510A0000010A2E95860F
    Here is the switch config
    +++++++++++++++++
    interface GigabitEthernet1/0/11
     description HOST PORT WITH AUTHENTICATION
     switchport access vlan 68
     switchport mode access
     switchport nonegotiate
     switchport voice vlan 78
     authentication event server dead action reinitialize vlan 68
     authentication event server dead action authorize voice
     authentication host-mode multi-auth
     authentication order mab dot1x
     authentication priority dot1x mab
     authentication port-control auto
     authentication periodic
     authentication timer restart 300
     authentication timer reauthenticate server
     authentication timer inactivity server
     mab
     dot1x pae authenticator
     dot1x timeout tx-period 5
     spanning-tree portfast
    end
    global switch config
    +++++++++++++++
    aaa new-model
    aaa authentication login default local group radius
    aaa authentication dot1x default group radius
    aaa authorization exec default local group radius
    aaa authorization network default group radius
    aaa accounting dot1x default start-stop group radius
    aaa server radius dynamic-author
     client 10.1.30.11 server-key 7 023201575A080B34080F
     client 10.1.30.12 server-key 7 122D001B430508116E6A
    dot1x system-auth-control
    dot1x critical eapol
    radius-server attribute 6 on-for-login-auth
    radius-server attribute 8 include-in-access-req
    radius-server attribute 25 access-request include
    radius-server dead-criteria time 1 tries 3
    radius-server host 10.1.30.11 auth-port 1812 acct-port 1813 key 7 0030160A55550F134B60
    radius-server host 10.1.30.12 auth-port 1812 acct-port 1813 key 7 0030160A55550F134B60
    radius-server deadtime 1
    radius-server vsa send accounting
    radius-server vsa send authentication
    Could you please help me.
    Michel Misonne

    Hi
    Yes the mac is in the Identity endpoint.
    During this night, the Phone reboot and now it is OK  !!!
    I do not know why ?
    I changed nothing !
    But here is the debug.
    Also the ise is configured with authentication protocol  Pap-Ascii = Enable
    and "Calling stat id"  and "Check pass" checked."
    The onfig of the phone is
    -Mac to login
    -MD5 profile = OFF
    -Tls Profile OFF
    Her is te debug. ( when it works well)
    conf t
    Enter configuration commands, one per line.  End with CNTL/Z.
    2960-09(config)#endshutdown int gigabitEthernet 1/0/11
    2960-09(config-if)#no shu
    2960-09(config-if)#no shutdown
    2960-09(config-if)#
    2960-09(config-if)#
    2960-09(config-if)#
    2960-09(config-if)#
    2960-09(config-if)#end
    2960-09#
    Dec 16 08:33:54.962: %ILPOWER-7-DETECT: Interface Gi1/0/11: Power Device detected: IEEE PD
    Dec 16 08:33:56.157: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/11: Power granted
    2960-09#
    2960-09#
    2960-09#
    2960-09#
    2960-09#
    2960-09#
    2960-09#
    Dec 16 08:33:56.241: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/11, changed state to down
    Dec 16 08:33:56.322: %SYS-5-CONFIG_I: Configured from console by admin on vty0 (10.10.68.4)
    2960-09#
    Dec 16 08:34:02.924: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/11, changed state to up
    Dec 16 08:34:03.924: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/11, changed state to up
    2960-09#
    Dec 16 08:34:05.088: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/11, changed state to down
    2960-09#
    Dec 16 08:34:06.095: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/11, changed state to down
    2960-09#
    Dec 16 08:34:09.800: %AUTHMGR-5-START: Starting 'mab' for client (0080.9fc8.a9eb) on Interface Gi1/0/11 AuditSessionID 0A0A510A0000011E3329AE1E
    Dec 16 08:34:09.800: RADIUS/ENCODE(0000025F):Orig. component type = Dot1X
    Dec 16 08:34:09.804: RADIUS(0000025F): Config NAS IP: 0.0.0.0
    Dec 16 08:34:09.804: RADIUS(0000025F): Config NAS IPv6: ::
    Dec 16 08:34:09.804: RADIUS/ENCODE(0000025F): acct_session_id: 597
    Dec 16 08:34:09.804: RADIUS(0000025F): sending
    Dec 16 08:34:09.804: RADIUS/ENCODE: Best Local IP-Address 10.10.81.10 for Radius-Server 10.1.30.11
    Dec 16 08:34:09.804: RADIUS(0000025F): Sending a IPv4 Radius Packet
    Dec 16 08:34:09.804: RADIUS(0000025F): Send Access-Request to 10.1.30.11:1812 id 1645/198,len 249
    Dec 16 08:34:09.804: RADIUS:  authenticator D3 5F 99 C6 EE 9F 9F 96 - 7C 1B A1 B9 32 1C 78 61
    Dec 16 08:34:09.804: RADIUS:  User-Name           [1]   14  "00809fc8a9eb"
    Dec 16 08:34:09.804: RADIUS:  User-Password       [2]   18  *
    Dec 16 08:34:09.804: RADIUS:  Service-Type        [6]   6   Call Check                [10]
    Dec 16 08:34:09.804: RADIUS:  Vendor, Cisco       [26]  31 
    Dec 16 08:34:09.804: RADIUS:   Cisco AVpair       [1]   25  "service-type=Call Check"
    Dec 16 08:34:09.804: RADIUS:  Framed-IP-Address   [8]   6   10.10.78.250             
    Dec 16 08:34:09.804: RADIUS:  Framed-MTU          [12]  6   1500                     
    Dec 16 08:34:09.804: RADIUS:  Called-Station-Id   [30]  19  "F0-9E-63-E7-E1-8B"
    Dec 16 08:34:09.804: RADIUS:  Calling-Station-Id  [31]  19  "00-80-9F-C8-A9-EB"
    Dec 16 08:34:09.804: RADIUS:  Message-Authenticato[80]  18 
    Dec 16 08:34:09.804: RADIUS:   5F 60 06 35 54 F6 CB 60 3A D6 A9 87 92 F0 0D 70           [ _`5T`:p]
    Dec 16 08:34:09.804: RADIUS:  EAP-Key-Name        [102] 2   *
    Dec 16 08:34:09.804: RADIUS:  Vendor, Cisco       [26]  49 
    Dec 16 08:34:09.807: RADIUS:   Cisco AVpair       [1]   43  "audit-session-id=0A0A510A0000011E3329AE1E"
    Dec 16 08:34:09.807: RADIUS:  NAS-Port-Type       [61]  6   Ethernet                  [15]
    Dec 16 08:34:09.807: RADIUS:  NAS-Port            [5]   6   50111                    
    Dec 16 08:34:09.807: RADIUS:  NAS-Port-Id         [87]  23  "GigabitEthernet1/0/11"
    Dec 16 08:34:09.807: RADIUS:  NAS-IP-Address      [4]   6   10.10.81.10              
    Dec 16 08:34:09.807: RADIUS(0000025F): Started 5 sec timeout
    Dec 16 08:34:09.856: RADIUS: Received from id 1645/198 10.1.30.11:1812, Access-Accept, len 283
    Dec 16 08:34:09.856: RADIUS:  authenticator BC 72 21 F4 37 7D BE B1 - 03 A7 CE F3 3A DB EE DA
    Dec 16 08:34:09.856: RADIUS:  User-Name           [1]   14  "00809fc8a9eb"
    Dec 16 08:34:09.856: RADIUS:  State               [24]  40 
    Dec 16 08:34:09.856: RADIUS:   52 65 61 75 74 68 53 65 73 73 69 6F 6E 3A 30 41  [ReauthSession:0A]
    Dec 16 08:34:09.856: RADIUS:   30 41 35 31 30 41 30 30 30 30 30 31 31 45 33 33  [0A510A0000011E33]
    Dec 16 08:34:09.856: RADIUS:   32 39 41 45 31 45            [ 29AE1E]
    Dec 16 08:34:09.856: RADIUS:  Class               [25]  54 
    Dec 16 08:34:09.856: RADIUS:   43 41 43 53 3A 30 41 30 41 35 31 30 41 30 30 30  [CACS:0A0A510A000]
    Dec 16 08:34:09.859: RADIUS:   30 30 31 31 45 33 33 32 39 41 45 31 45 3A 6D 65  [0011E3329AE1E:me]
    Dec 16 08:34:09.859: RADIUS:   67 61 74 72 6F 6E 2F 32 30 37 35 39 38 39 38 34  [gatron/207598984]
    Dec 16 08:34:09.859: RADIUS:   2F 34 31 30              [ /410]
    Dec 16 08:34:09.859: RADIUS:  Message-Authenticato[80]  18 
    Dec 16 08:34:09.859: RADIUS:   51 E9 8C 07 61 A4 F0 02 0C DC DF 1F 25 BE 39 A3              [ Qa?9]
    Dec 16 08:34:09.859: RADIUS:  Vendor, Cisco       [26]  34 
    Dec 16 08:34:09.859: RADIUS:   Cisco AVpair       [1]   28  "device-traffic-class=voice"
    Dec 16 08:34:09.859: RADIUS:  Vendor, Cisco       [26]  75 
    Dec 16 08:34:09.859: RADIUS:   Cisco AVpair       [1]   69  "ACS:CiscoSecure-Defined-ACL=#ACSACL#-IP-PERMIT_ALL_TRAFFIC-537cb1d6"
    Dec 16 08:34:09.859: RADIUS:  Vendor, Cisco       [26]  28 
    Dec 16 08:34:09.859: RADIUS:   Cisco AVpair       [1]   22  "profile-name=Unknown"
    Dec 16 08:34:09.859: RADIUS(0000025F): Received from id 1645/198
    Dec 16 08:34:09.859: RADIUS/DECODE: parse unknown cisco vsa "profile-name" - IGNORE
    Dec 16 08:34:09.859: %MAB-5-SUCCESS: Authentication successful for client (0080.9fc8.a9eb) on Interface Gi1/0/11 AuditSessionID 0A0A510A0000011E3329AE1E
    Dec 16 08:34:09.863: %AUTHMGR-7-RESULT: Authentication result 'success' from 'mab' for client (0080.9fc8.a9eb) on Interface Gi1/0/11 AuditSessionID 0A0A510A0000011E3329AE1E
    Dec 16 08:34:09.894: RADIUS/ENCODE(00000000):Orig. component type = Invalid
    Dec 16 08:34:09.894: RADIUS(00000000): Config NAS IP: 0.0.0.0
    Dec 16 08:34:09.898: RADIUS(00000000): sending
    Dec 16 08:34:09.957: RADIUS/ENCODE: Best Local IP-Address 10.10.81.10 for Radius-Server 10.1.30.11
    Dec 16 08:34:09.957: RADIUS(00000000): Sending a IPv4 Radius Packet
    Dec 16 08:34:09.957: RADIUS(00000000): Send Access-Request to 10.1.30.11:1812 id 1645/199,len 147
    Dec 16 08:34:09.957: RADIUS:  authenticator 1B D7 D2 13 EF 69 36 E2 - 87 4D A9 69 2A F7 29 4D
    Dec 16 08:34:09.957: RADIUS:  NAS-IP-Address      [4]   6   10.10.81.10              
    Dec 16 08:34:09.957: RADIUS:  User-Name           [1]   41  "#ACSACL#-IP-PERMIT_ALL_TRAFFIC-537cb1d6"
    Dec 16 08:34:09.957: RADIUS:  Vendor, Cisco       [26]  32 
    Dec 16 08:34:09.957: RADIUS:   Cisco AVpair       [1]   26  "aaa:service=ip_admission"
    Dec 16 08:34:09.961: RADIUS:  Vendor, Cisco       [26]  30 
    Dec 16 08:34:09.961: RADIUS:   Cisco AVpair       [1]   24  "aaa:event=acl-download"
    Dec 16 08:34:09.961: RADIUS:  Message-Authenticato[80]  18 
    Dec 16 08:34:09.961: RADIUS:   E7 15 BB FB 7B 5B 1A C4 50 FC E7 0E 10 AC 22 36             [ {[P"6]
    Dec 16 08:34:09.961: RADIUS(00000000): Started 5 sec timeout
    Dec 16 08:34:09.968: RADIUS: Received from id 1645/199 10.1.30.11:1812, Access-Accept, len 209
    Dec 16 08:34:09.968: RADIUS:  authenticator FA 03 DD C1 D2 87 6B 58 - 99 65 EE 96 FF D5 76 FD
    Dec 16 08:34:09.968: RADIUS:  User-Name           [1]   41  "#ACSACL#-IP-PERMIT_ALL_TRAFFIC-537cb1d6"
    Dec 16 08:34:09.968: RADIUS:  State               [24]  40 
    Dec 16 08:34:09.968: RADIUS:   52 65 61 75 74 68 53 65 73 73 69 6F 6E 3A 30 61  [ReauthSession:0a]
    Dec 16 08:34:09.971: RADIUS:   30 31 31 65 30 62 30 30 30 30 30 30 37 38 35 34  [011e0b0000007854]
    Dec 16 08:34:09.971: RADIUS:   38 46 45 45 38 31            [ 8FEE81]
    Dec 16 08:34:09.971: RADIUS:  Class               [25]  54 
    Dec 16 08:34:09.971: RADIUS:   43 41 43 53 3A 30 61 30 31 31 65 30 62 30 30 30  [CACS:0a011e0b000]
    Dec 16 08:34:09.971: RADIUS:   30 30 30 37 38 35 34 38 46 45 45 38 31 3A 6D 65  [00078548FEE81:me]
    Dec 16 08:34:09.971: RADIUS:   67 61 74 72 6F 6E 2F 32 30 37 35 39 38 39 38 34  [gatron/207598984]
    Dec 16 08:34:09.971: RADIUS:   2F 34 31 31              [ /411]
    Dec 16 08:34:09.971: RADIUS:  Message-Authenticato[80]  18 
    Dec 16 08:34:09.971: RADIUS:   A4 02 84 1E 1A 97 E9 E9 DE 46 93 D6 30 C4 52 99               [ F0R]
    Dec 16 08:34:09.971: RADIUS:  Vendor, Cisco       [26]  36 
    Dec 16 08:34:09.971: RADIUS:   Cisco AVpair       [1]   30  "ip:inacl#1=permit ip any any"
    Dec 16 08:34:09.971: RADIUS(00000000): Received from id 1645/199
    Dec 16 08:34:10.069: %AUTHMGR-5-SUCCESS: Authorization succeeded for client (0080.9fc8.a9eb) on Interface Gi1/0/11 AuditSessionID 0A0A510A0000011E3329AE1E
    Dec 16 08:34:10.069: RADIUS/ENCODE(0000025F):Orig. component type = Dot1X
    Dec 16 08:34:10.069: RADIUS(0000025F): Config NAS IP: 0.0.0.0
    Dec 16 08:34:10.069: RADIUS(0000025F): Config NAS IPv6: ::
    Dec 16 08:34:10.073: RADIUS(0000025F): sending
    Dec 16 08:34:10.073: RADIUS/ENCODE: Best Local IP-Address 10.10.81.10 for Radius-Server 10.1.30.11
    Dec 16 08:34:10.073: RADIUS(0000025F): Sending a IPv4 Radius Packet
    Dec 16 08:34:10.073: RADIUS(0000025F): Send Accounting-Request to 10.1.30.11:1813 id 1646/240,len 423
    Dec 16 08:34:10.073: RADIUS:  authenticator 6C 75 45 C7 B7 66 2F 4D - 04 01 C6 CE A5 16 68 9B
    Dec 16 08:34:10.073: RADIUS:  Acct-Session-Id     [44]  10  "00000255"
    Dec 16 08:34:10.073: RADIUS:  Calling-Station-Id  [31]  19  "00-80-9F-C8-A9-EB"
    Dec 16 08:34:10.073: RADIUS:  Vendor, Cisco       [26]  49 
    Dec 16 08:34:10.073: RADIUS:   Cisco AVpair       [1]   43  "audit-session-id=0A0A510A0000011E3329AE1E"
    Dec 16 08:34:10.073: RADIUS:  Framed-IP-Address   [8]   6   10.10.78.250             
    Dec 16 08:34:10.073: RADIUS:  User-Name           [1]   14  "00809fc8a9eb"
    Dec 16 08:34:10.073: RADIUS:  Vendor, Cisco       [26]  32 
    Dec 16 08:34:10.073: RADIUS:   Cisco AVpair       [1]   26  "connect-progress=Call Up"
    Dec 16 08:34:10.073: RADIUS:  Vendor, Cisco       [26]  21 
    Dec 16 08:34:10.073: RADIUS:   Cisco AVpair       [1]   15  "lldp-tlv=    "
    Dec 16 08:34:10.073: RADIUS:  Vendor, Cisco       [26]  25 
    Dec 16 08:34:10.073: RADIUS:   Cisco AVpair       [1]   19  "lldp-tlv=        "
    Dec 16 08:34:10.073: RADIUS:  Vendor, Cisco       [26]  23 
    Dec 16 08:34:10.073: RADIUS:   Cisco AVpair       [1]   17  "lldp-tlv=      "
    Dec 16 08:34:10.073: RADIUS:  Vendor, Cisco       [26]  28 
    Dec 16 08:34:10.073: RADIUS:  Vendor, Cisco       [26]  28 
    Dec 16 08:34:10.073: RADIUS:  Tunnel-Packets-Lost [86]  101 1852075890               
    Dec 16 08:34:10.076: RADIUS:  Nas-Identifier      [32]  32  "             
    Dec 16 08:34:10"
    Dec 16 08:34:10.076: data_left 15
    2960-09#
    Dec 16 08:34:10.076: RADIUS(0000025F): Started 5 sec timeout
    Dec 16 08:34:10.090: RADIUS: Received from id 1646/240 10.1.30.11:1813, Accounting-response, len 20
    Dec 16 08:34:10.090: RADIUS:  authenticator 91 9F CE 71 1C 4B 45 93 - 49 86 52 C8 C3 44 40 B8
    2960-09#
    Dec 16 08:34:11.485: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/11, changed state to up
    Dec 16 08:34:12.485: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/11, changed state to up
    2960-09#
    2960-09#
    2960-09#
    2960-09#
    2960-09#
    2960-09#
    2960-09#sh auth
    2960-09#sh authentication ses
    2960-09#sh authentication sessions int gi
    2960-09#sh authentication sessions int gigabitEthernet 1/ /0/11
                Interface:  GigabitEthernet1/0/11
              MAC Address:  0080.9fc8.a9eb
               IP Address:  10.10.78.250
                User-Name:  00809fc8a9eb
                   Status:  Authz Success
                   Domain:  VOICE
           Oper host mode:  multi-auth
         Oper control dir:  both
            Authorized By:  Authentication Server
                  ACS ACL:  xACSACLx-IP-PERMIT_ALL_TRAFFIC-537cb1d6
          Session timeout:  N/A
             Idle timeout:  N/A
        Common Session ID:  0A0A510A0000011E3329AE1E
          Acct Session ID:  0x00000255
                   Handle:  0x3600011F
    Runnable methods list:
           Method   State
           mab      Authc Success
           dot1x    Not run
    2960-09#

  • 802.1X authentication not happening in Voice Domain for IP Phone

    I am trying to lab as many scenarios as I can for 802.1x.  I seem to have hit a problem with IP Phones running EAP-MD5 authentication.  The phone sare always being authenticated in the Data Domain.  This is regardless of whether or no the port configuration is in: host-mode multi-auth  ,or, host-mode multi-domain.  After a while of both ports appearing to authenticate in the data VLAN, neither the PC or Phone will work
    I have checked that my ACS5.1 server is sending the appropriate AV pair of "device-traffic-class=voice" as I can see it in a wireshark trace.
    What other aspects might i need to check to get the phone to authenticate itself properly?
    The problem shows itself as:
    C3750G#sh authentication sessions int gi 1/0/16
                Interface:  GigabitEthernet1/0/16
              MAC Address:  001d.452d.53e0
               IP Address:  Unknown
                User-Name:  CP-7942G-SEP001D452D53E0
                   Status:  Authz Success
                   Domain:  DATA
          Security Policy:  Should Secure
          Security Status:  Unsecure
           Oper host mode:  multi-domain
         Oper control dir:  both
            Authorized By:  Authentication Server
               Vlan Group:  N/A
          Session timeout:  N/A
             Idle timeout:  N/A
        Common Session ID:  C0A8FE2500000014000F6B8F
          Acct Session ID:  0x00000036
                   Handle:  0xC8000014
    Runnable methods list:
           Method   State
           dot1x    Authc Success
                Interface:  GigabitEthernet1/0/16
              MAC Address:  0014.c209.896f
               IP Address:  192.168.10.2
                User-Name:  TEST\TestAdmin
                   Status:  Running
                   Domain:  UNKNOWN
          Security Policy:  Should Secure
          Security Status:  Unsecure
           Oper host mode:  multi-domain
         Oper control dir:  both
          Session timeout:  N/A
             Idle timeout:  N/A
        Common Session ID:  C0A8FE2500000013000F5A42
          Acct Session ID:  0x00000034
                   Handle:  0x27000013
    Runnable methods list:
           Method   State
           dot1x    Running
    My port config is:
    interface GigabitEthernet1/0/16
    description * 802.1x Multi Domain (1Phone + 1PC) *
    switchport access vlan 10
    switchport mode access
    switchport voice vlan 11
    priority-queue out
    authentication host-mode multi-domain
    authentication port-control auto
    udld port aggressive
    mls qos trust dscp
    dot1x pae authenticator
    spanning-tree portfast
    end

    For information, the debugs you request are:
    Jan 29 10:58:46.317: %ILPOWER-7-DETECT: Interface Gi1/0/16: Power Device detected: IEEE PD
    Jan 29 10:58:46.770: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/16: Power granted
    Jan 29 10:58:50.377: AAA/BIND(0000001D): Bind i/f
    Jan 29 10:58:52.373: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/16, changed state to up
    Jan 29 10:58:53.380: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/16, changed state to up
    Jan 29 10:58:54.789: %AUTHMGR-5-START: Starting 'dot1x' for client (001d.452d.53e0) on Interface Gi1/0/16 AuditSessionID C0A                                                     8FE2500000018002FB1D0
    Jan 29 10:58:56.920: AAA/AUTHEN/8021X (0000001D): Pick method list 'default'
    Jan 29 10:58:56.920: RADIUS/ENCODE(0000001D):Orig. component type = DOT1X
    Jan 29 10:58:56.920: RADIUS(0000001D): Config NAS IP: 192.168.254.37
    Jan 29 10:58:56.920: RADIUS/ENCODE(0000001D): acct_session_id: 54
    Jan 29 10:58:56.920: RADIUS(0000001D): sending
    Jan 29 10:58:56.920: RADIUS(0000001D): Send Access-Request to 192.168.254.51:1645 id 1645/52, len 237
    Jan 29 10:58:56.920: RADIUS:  authenticator 89 81 92 2C AA 6B E6 E6 - CA 2C 3A 0D E1 C5 28 ED
    Jan 29 10:58:56.928: RADIUS:  User-Name           [1]   26  "CP-7942G-SEP001D452D53E0"
    Jan 29 10:58:56.928: RADIUS:  Service-Type        [6]   6   Framed                    [2]
    Jan 29 10:58:56.928: RADIUS:  Framed-MTU          [12]  6   1500
    Jan 29 10:58:56.928: RADIUS:  Called-Station-Id   [30]  19  "30-37-A6-AB-8E-90"
    Jan 29 10:58:56.928: RADIUS:  Calling-Station-Id  [31]  19  "00-1D-45-2D-53-E0"
    Jan 29 10:58:56.928: RADIUS:  EAP-Message         [79]  31
    Jan 29 10:58:56.928: RADIUS:   02 01 00 1D 01 43 50 2D 37 39 34 32 47 2D 53 45 50 30 30 31 44  [CP-7942G-SEP001D]
    Jan 29 10:58:56.928: RADIUS:   34 35 32 44 35 33 45 30          [ 452D53E0]
    Jan 29 10:58:56.928: RADIUS:  Message-Authenticato[80]  18
    Jan 29 10:58:56.928: RADIUS:   83 AF F8 DB 44 0D 0A 46 70 2F 1E 8D 67 CE BC DD             [ DFp/g]
    Jan 29 10:58:56.928: RADIUS:  EAP-Key-Name        [102] 2   *
    Jan 29 10:58:56.928: RADIUS:  Vendor, Cisco       [26]  49
    Jan 29 10:58:56.928: RADIUS:   Cisco AVpair       [1]   43  "audit-session-id=C0A8FE2500000018002FB1D0"
    Jan 29 10:58:56.928: RADIUS:  NAS-Port-Type       [61]  6   Ethernet                  [15]
    Jan 29 10:58:56.928: RADIUS:  NAS-Port            [5]   6   50116
    Jan 29 10:58:56.928: RADIUS:  NAS-Port-Id         [87]  23  "GigabitEthernet1/0/16"
    Jan 29 10:58:56.928: RADIUS:  NAS-IP-Address      [4]   6   192.168.254.37
    Jan 29 10:58:56.928: RADIUS(0000001D): Started 4 sec timeout
    Jan 29 10:58:56.928: RADIUS: Received from id 1645/52 192.168.254.51:1645, Access-Challenge, len 76
    Jan 29 10:58:56.928: RADIUS:  authenticator DA 45 B9 F8 80 48 A0 4B - F7 99 9B 1F DE 4F B2 9E
    Jan 29 10:58:56.928: RADIUS:  State               [24]  30
    Jan 29 10:58:56.937: RADIUS:   32 35 53 65 73 73 69 6F 6E 49 44 3D 41 43 53 2F  [25SessionID=ACS/]
    Jan 29 10:58:56.937: RADIUS:   38 35 36 37 30 35 31 38 2F 33 33 3B      [ 85670518/33;]
    Jan 29 10:58:56.937: RADIUS:  EAP-Message         [79]  8
    Jan 29 10:58:56.937: RADIUS:   01 51 00 06 0D 20                [ Q ]
    Jan 29 10:58:56.937: RADIUS:  Message-Authenticato[80]  18
    Jan 29 10:58:56.937: RADIUS:   3C F4 D9 93 82 EA FB 25 A7 9D C4 8F 14 3F 33 4F             [ <??3O]
    Jan 29 10:58:56.937: RADIUS(0000001D): Received from id 1645/52
    Jan 29 10:58:56.937: RADIUS/DECODE: EAP-Message fragments, 6, total 6 bytes
    Jan 29 10:58:57.046: AAA/AUTHEN/8021X (0000001D): Pick method list 'default'
    Jan 29 10:58:57.046: RADIUS/ENCODE(0000001D):Orig. component type = DOT1X
    Jan 29 10:58:57.046: RADIUS(0000001D): Config NAS IP: 192.168.254.37
    Jan 29 10:58:57.046: RADIUS/ENCODE(0000001D): acct_session_id: 54
    Jan 29 10:58:57.046: RADIUS(0000001D): sending
    Jan 29 10:58:57.046: RADIUS(0000001D): Send Access-Request to 192.168.254.51:1645 id 1645/53, len 244
    Jan 29 10:58:57.046: RADIUS:  authenticator BE 9B 32 59 45 BF 15 45 - E4 43 02 B5 B5 D7 ED 83
    Jan 29 10:58:57.046: RADIUS:  User-Name           [1]   26  "CP-7942G-SEP001D452D53E0"
    Jan 29 10:58:57.046: RADIUS:  Service-Type        [6]   6   Framed                    [2]
    Jan 29 10:58:57.046: RADIUS:  Framed-MTU          [12]  6   1500
    Jan 29 10:58:57.054: RADIUS:  Called-Station-Id   [30]  19  "30-37-A6-AB-8E-90"
    Jan 29 10:58:57.054: RADIUS:  Calling-Station-Id  [31]  19  "00-1D-45-2D-53-E0"
    Jan 29 10:58:57.054: RADIUS:  EAP-Message         [79]  8
    Jan 29 10:58:57.054: RADIUS:   02 51 00 06 03 04                 [ Q]
    Jan 29 10:58:57.054: RADIUS:  Message-Authenticato[80]  18
    Jan 29 10:58:57.054: RADIUS:   E0 B5 99 82 7E 9E 35 0F 78 D9 BD 4B 96 97 34 47            [ ~5xK4G]
    Jan 29 10:58:57.054: RADIUS:  EAP-Key-Name        [102] 2   *
    Jan 29 10:58:57.054: RADIUS:  Vendor, Cisco       [26]  49
    Jan 29 10:58:57.054: RADIUS:   Cisco AVpair       [1]   43  "audit-session-id=C0A8FE2500000018002FB1D0"
    Jan 29 10:58:57.054: RADIUS:  NAS-Port-Type       [61]  6   Ethernet                  [15]
    Jan 29 10:58:57.054: RADIUS:  NAS-Port            [5]   6   50116
    Jan 29 10:58:57.054: RADIUS:  NAS-Port-Id         [87]  23  "GigabitEthernet1/0/16"
    Jan 29 10:58:57.054: RADIUS:  State               [24]  30
    Jan 29 10:58:57.054: RADIUS:   32 35 53 65 73 73 69 6F 6E 49 44 3D 41 43 53 2F  [25SessionID=ACS/]
    Jan 29 10:58:57.054: RADIUS:   38 35 36 37 30 35 31 38 2F 33 33 3B      [ 85670518/33;]
    Jan 29 10:58:57.054: RADIUS:  NAS-IP-Address      [4]   6   192.168.254.37
    Jan 29 10:58:57.054: RADIUS(0000001D): Started 4 sec timeout
    Jan 29 10:58:57.054: RADIUS: Received from id 1645/53 192.168.254.51:1645, Access-Challenge, len 95
    Jan 29 10:58:57.054: RADIUS:  authenticator D9 62 B7 27 8F 55 E9 88 - 41 01 D0 83 52 DF 36 29
    Jan 29 10:58:57.054: RADIUS:  State               [24]  30
    Jan 29 10:58:57.054: RADIUS:   32 35 53 65 73 73 69 6F 6E 49 44 3D 41 43 53 2F  [25SessionID=ACS/]
    Jan 29 10:58:57.063: RADIUS:   38 35 36 37 30 35 31 38 2F 33 33 3B      [ 85670518/33;]
    Jan 29 10:58:57.063: RADIUS:  EAP-Message         [79]  27
    Jan 29 10:58:57.063: RADIUS:   01 52 00 19 04 10 AA 6A A2 BC 63 1A C0 93 B8 58 67 F7 1A A5 FD 45 41 43 53         [ RjcXgEAC                                                     S]
    Jan 29 10:58:57.063: RADIUS:  Message-Authenticato[80]  18
    Jan 29 10:58:57.063: RADIUS:   29 D2 66 87 4A 2F B3 9E B5 EC F9 4E 9F 62 82 5E           [ )fJ/Nb^]
    Jan 29 10:58:57.063: RADIUS(0000001D): Received from id 1645/53
    Jan 29 10:58:57.063: RADIUS/DECODE: EAP-Message fragments, 25, total 25 bytes
    Jan 29 10:58:57.079: AAA/AUTHEN/8021X (0000001D): Pick method list 'default'
    Jan 29 10:58:57.079: RADIUS/ENCODE(0000001D):Orig. component type = DOT1X
    Jan 29 10:58:57.079: RADIUS(0000001D): Config NAS IP: 192.168.254.37
    Jan 29 10:58:57.079: RADIUS/ENCODE(0000001D): acct_session_id: 54
    Jan 29 10:58:57.079: RADIUS(0000001D): sending
    Jan 29 10:58:57.079: RADIUS(0000001D): Send Access-Request to 192.168.254.51:1645 id 1645/54, len 284
    Jan 29 10:58:57.079: RADIUS:  authenticator 91 F4 7C C1 4E 79 27 AB - 2F 36 20 A8 9C 3F A9 76
    Jan 29 10:58:57.079: RADIUS:  User-Name           [1]   26  "CP-7942G-SEP001D452D53E0"
    Jan 29 10:58:57.088: RADIUS:  Service-Type        [6]   6   Framed                    [2]
    Jan 29 10:58:57.088: RADIUS:  Framed-MTU          [12]  6   1500
    Jan 29 10:58:57.088: RADIUS:  Called-Station-Id   [30]  19  "30-37-A6-AB-8E-90"
    Jan 29 10:58:57.088: RADIUS:  Calling-Station-Id  [31]  19  "00-1D-45-2D-53-E0"
    Jan 29 10:58:57.088: RADIUS:  EAP-Message         [79]  48
    Jan 29 10:58:57.088: RADIUS:   02 52 00 2E 04 10 45 2F B1 FC 60 CF 09 08 7B C4 F9 56 74 AF 44 E9 43 50 2D 37 39 34 32  [R.E/                                                     `{VtDCP-7942]
    Jan 29 10:58:57.088: RADIUS:   47 2D 53 45 50 30 30 31 44 34 35 32 44 35 33 45  [G-SEP001D452D53E]
    Jan 29 10:58:57.088: RADIUS:   30                 [ 0]
    Jan 29 10:58:57.088: RADIUS:  Message-Authenticato[80]  18
    Jan 29 10:58:57.088: RADIUS:   45 42 58 9F 75 14 09 A1 FC DD CD 26 B4 88 42 CF            [ EBXu&B]
    Jan 29 10:58:57.088: RADIUS:  EAP-Key-Name        [102] 2   *
    Jan 29 10:58:57.088: RADIUS:  Vendor, Cisco       [26]  49
    Jan 29 10:58:57.088: RADIUS:   Cisco AVpair       [1]   43  "audit-session-id=C0A8FE2500000018002FB1D0"
    Jan 29 10:58:57.088: RADIUS:  NAS-Port-Type       [61]  6   Ethernet                  [15]
    Jan 29 10:58:57.088: RADIUS:  NAS-Port            [5]   6   50116
    Jan 29 10:58:57.088: RADIUS:  NAS-Port-Id         [87]  23  "GigabitEthernet1/0/16"
    Jan 29 10:58:57.088: RADIUS:  State               [24]  30
    Jan 29 10:58:57.088: RADIUS:   32 35 53 65 73 73 69 6F 6E 49 44 3D 41 43 53 2F  [25SessionID=ACS/]
    Jan 29 10:58:57.088: RADIUS:   38 35 36 37 30 35 31 38 2F 33 33 3B      [ 85670518/33;]
    Jan 29 10:58:57.088: RADIUS:  NAS-IP-Address      [4]   6   192.168.254.37
    Jan 29 10:58:57.088: RADIUS(0000001D): Started 4 sec timeout
    Jan 29 10:58:57.222: RADIUS: Received from id 1645/54 192.168.254.51:1645, Access-Accept, len 126
    Jan 29 10:58:57.222: RADIUS:  authenticator 7B A5 E0 B2 D6 15 90 26 - 8F 8F 64 B0 E6 94 D8 C7
    Jan 29 10:58:57.222: RADIUS:  User-Name           [1]   26  "CP-7942G-SEP001D452D53E0"
    Jan 29 10:58:57.222: RADIUS:  Class               [25]  22
    Jan 29 10:58:57.222: RADIUS:   43 41 43 53 3A 41 43 53 2F 38 35 36 37 30 35 31  [CACS:ACS/8567051]
    Jan 29 10:58:57.222: RADIUS:   38 2F 33 33              [ 8/33]
    Jan 29 10:58:57.222: RADIUS:  EAP-Message         [79]  6
    Jan 29 10:58:57.222: RADIUS:   03 52 00 04                 [ R]
    Jan 29 10:58:57.222: RADIUS:  Message-Authenticato[80]  18
    Jan 29 10:58:57.222: RADIUS:   E8 2E 9B FD C2 A8 D7 5E 86 DD 3C 67 FF 37 75 02            [ .^Jan 29 10:58:57.222: RADIUS:  Vendor, Cisco       [26]  34
    Jan 29 10:58:57.222: RADIUS:   Cisco AVpair       [1]   28  "device-traffic-class=voice"
    Jan 29 10:58:57.222: RADIUS(0000001D): Received from id 1645/54
    Jan 29 10:58:57.222: RADIUS/DECODE: EAP-Message fragments, 4, total 4 bytes
    Jan 29 10:58:57.222: AAA/AUTHOR (0000001D): Method list id=0 not configured. Skip author
    Jan 29 10:58:57.222: %DOT1X-5-SUCCESS: Authentication successful for client (001d.452d.53e0) on Interface Gi1/0/16 AuditSess                                                     ionID
    Jan 29 10:58:57.222: %AUTHMGR-7-RESULT: Authentication result 'success' from 'dot1x' for client (001d.452d.53e0) on Interfac                                                     e Gi1/0/16 AuditSessionID C0A8FE2500000018002FB1D0
    Jan 29 10:58:57.239: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to up
    Jan 29 10:58:58.262: %AUTHMGR-5-SUCCESS: Authorization succeeded for client (001d.452d.53e0) on Interface Gi1/0/16 AuditSess                                                     ionID C0A8FE2500000018002FB1D0

  • Limit syslog email alerting

    I have syslog sev1 and Sev2 email alerts enabled in my Prime LMS4.2.2. Is there a way to limit the alerts so that only one email gets sent for every 100 or 500 duplicate alerts etc.
    There are some instances where I received 5000 emails in one night for one of the following error.
    Sep 18 09:31:38.742: %ILPOWER-7-DETECT: Interface Gi2/18: Power Device detected: IEEE PD
    Sep 18 09:31:50.982: %C6K_POWER-SP-1-PD_HW_FAULTY: The device connected to port 2/18 has a hardware problem. Power is turned off on the port.
    Sep 18 09:31:54.494: %ILPOWER-7-DETECT: Interface Gi2/18: Power Device detected: IEEE PD
    Sep 18 09:32:06.762: %C6K_POWER-SP-1-PD_HW_FAULTY: The device connected to port 2/18 has a hardware problem. Power is turned off on the port.
    Sep 18 09:32:09.790: %ILPOWER-7-DETECT: Interface Gi2/18: Power Device detected: IEEE PD
    Sep 18 09:32:22.018: %C6K_POWER-SP-1-PD_HW_FAULTY: The device connected to port 2/18 has a hardware problem. Power is turned off on the port.
    Sep 18 09:32:25.502: %ILPOWER-7-DETECT: Interface Gi2/18: Power Device detected: IEEE PD
    Sep 18 09:32:37.834: %C6K_POWER-SP-1-PD_HW_FAULTY: The device connected to port 2/18 has a hardware problem. Power is turned off on the port.
    Sep 18 09:32:40.902: %ILPOWER-7-DETECT: Interface Gi2/18: Power Device detected: IEEE PD
    Sep 18 09:32:53.216: %C6K_POWER-SP-1-PD_HW_FAULTY: The device connected to port 2/18 has a hardware problem. Power is turned off on the port.

    Currently the Automated Action is a straight forward action in terms of sending email notification. It acts somehow dumb, so as what you configure, it will act as per it. No further properties can be modifed to set the email rate or set LMS to send one consolidated email.

  • 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.

  • POE controller on 3560

    I have a remote 3560X switch which has produced the following error messages. Nothing is connected to port 22, none of the other devices require POE from the switch. Port 21 came back online, but not 23 or 24. Any ideas what this refers to and whether it can be corrected remotely or needs to be replaced.
    Nov 25 08:21:06: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi0/21: Power Controller reports power supply VEE under voltage and lockout
    Nov 25 08:21:06: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi0/22: Power Controller reports power supply VEE under voltage and lockout
    Nov 25 08:21:06: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi0/23: Power Controller reports power supply VEE under voltage and lockout
    Nov 25 08:21:06: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi0/24: Power Controller reports power supply VEE under voltage and lockout
    Nov 25 08:21:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/24, changed state to down
    Nov 25 08:21:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/23, changed state to down
    Nov 25 08:21:08: %LINK-3-UPDOWN: Interface GigabitEthernet0/24, changed state to down
    Nov 25 08:21:08: %LINK-3-UPDOWN: Interface GigabitEthernet0/23, changed state to down
    Nov 25 08:21:16: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/21, changed state to down
    Nov 25 08:21:18: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/21, changed state to up

    I have never seen an error message like this before.
    1.  What is the IOS version you are using?
    2.  Have you tried erasing the configuration of both ports and determine if the error message returns?
    3.  Post the output to the command "sh power inline".
    4.  Have you tried to "shut/no shutdown" the port?
    5.  Have you tried to reboot the switch?

  • C3750X get power supply errors

    Hi, I got a problem with some phones connected to a C3750X-48PS. Phones are Polycom SoundPoint 560. Ports most critical: gig 1/0/9 & 1/0/31.
    Actually, the C3750X belongs to a stack, with the IOS: 12.2(55)SE3.  The environment conditions: power supply working ok, temperature level: ok. (show env all). Physically the LEDs are in green, and the room does not have temperature issues.
    Also, the phones present a humming noise (high pitch). The noise keeps happening even if the phones are plugged in other ports of a stack. It was attempted to connect the phones directly to the stack ports instead of the ports in the cubicules, and the issue keeps happening.
    The Stack presents also sudden fan to spin up / spin down for a couple of minutes, and within a couple of minutes from working on and off.
    Customer has another facility with the same switches but with IOS12.2(55)SE1, in there the same phones were tested and they are working fine.
    A reboot was performed, but now the C3750X show these messages:
    %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/9: Power Controller reports power Tstart error detected
    %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/31: Power Controller reports power Tstart error detected
    Thanks!

    I've found it!  In case anyone is wondering, a lot of server information is available by querying with the iLO xml tag "GET_EMBEDDED_HEALTH".
    This returns, buried way down in the results, information about power supplies (section POWER_SUPPLIES).
    While there doesn't seem to ask for just information on the power supplies, this works!

  • WS-C3850-48P reboots with %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache)

    The Cisco 3850 reboot after a couple of hours in operations. This has happened after the switch IOS has been upgraded from 3.2.1 to 3.3.1 however the rest of the 3850 seems to be OK except this naught one.
    Below is the logs from the switch:
    HOSTNAME#sh ver
    Cisco IOS Software, IOS-XE Software, Catalyst L3 Switch Software (CAT3K_CAA-UNIVERSALK9-M), Version 03.03.01SE RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2013 by Cisco Systems, Inc.
    Compiled Thu 05-Dec-13 10:15 by prod_rel_team
    Cisco IOS-XE software, Copyright (c) 2005-2013 by cisco Systems, Inc.
    All rights reserved. Certain components of Cisco IOS-XE software are
    licensed under the GNU General Public License ("GPL") Version 2.0. The
    software code licensed under GPL Version 2.0 is free software that comes
    with ABSOLUTELY NO WARRANTY. You can redistribute and/or modify such
    GPL code under the terms of GPL Version 2.0.
    (http://www.gnu.org/licenses/gpl-2.0.html) For more details, see the
    documentation or "License Notice" file accompanying the IOS-XE software,
    or the applicable URL provided on the flyer accompanying the IOS-XE
    software.
    ROM: IOS-XE ROMMON
    BOOTLDR: CAT3K_CAA Boot Loader (CAT3K_CAA-HBOOT-M) Version 1.2, RELEASE SOFTWARE (P)
    --More--        
    HOSTNAME uptime is 14 hours, 59 minutes
    Uptime for this control processor is 15 hours, 1 minute
    System returned to ROM by reload at 09:03:48 GMT Wed Dec 11 2013
    System restarted at 18:08:23 GMT Wed Jan 29 2014
    System image file is "flash:packages.conf"
    Last reload reason: reload
    This product contains cryptographic features and is subject to United
    States and local country laws governing import, export, transfer and
    use. Delivery of Cisco cryptographic products does not imply
    third-party authority to import, export, distribute or use encryption.
    Importers, exporters, distributors and users are responsible for
    compliance with U.S. and local country laws. By using this product you
    agree to comply with applicable laws and regulations. If you are unable
    to comply with U.S. and local laws, return this product immediately.
    A summary of U.S. laws governing Cisco cryptographic products may be found at:
    http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
    If you require further assistance please contact us by sending email to
    --More--         [email protected].
    License Level: Ipbase
    License Type: Permanent
    Next reload license Level: Ipbase
    cisco WS-C3850-48P (MIPS) processor with 4194304K bytes of physical memory.
    Processor board ID FOCXXXXXXX
    2 Virtual Ethernet interfaces
    104 Gigabit Ethernet interfaces
    8 Ten Gigabit Ethernet interfaces
    2048K bytes of non-volatile configuration memory.
    4194304K bytes of physical memory.
    250456K bytes of Crash Files at crashinfo:.
    1609272K bytes of Flash at flash:.
    0K bytes of Dummy USB Flash at usbflash0:.
    0K bytes of at webui:.
    Base Ethernet MAC Address         : XX:XX:XX:XX:XX:XX
    Motherboard Assembly Number       : 73-XXXXX-XX
    Motherboard Serial Number         : FOCXXXXXXXX
    Model Revision Number             : L0
    Motherboard Revision Number       : C0
    --More--         Model Number                       : WS-C3850-48P
    System Serial Number              : FOCXXXXXXXX
    Switch Ports Model             SW Version       SW Image             Mode  
    *   2 56   WS-C3850-48P       03.03.01SE       cat3k_caa-universalk9 INSTALL
    Configuration register is 0x102
    HOSTNAME# sh log
    Syslog logging: enabled (0 messages dropped, 1 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)
    No Active Message Discriminator.
    No Inactive Message Discriminator.
       Console logging: level debugging, 166 messages logged, xml disabled,
                         filtering disabled
       Monitor logging: level debugging, 0 messages logged, xml disabled,
                         filtering disabled
       Buffer logging: level debugging, 167 messages logged, xml disabled,
                       filtering disabled
       Exception Logging: size (4096 bytes)
       Count and timestamp logging messages: disabled
       File logging: disabled
       Persistent logging: disabled
       Trap logging: level debugging, 171 message lines logged
           Logging to 10.XX.XX.XX (udp port 514, audit disabled,
                 link up),
                 170 message lines logged,
    --More--                       0 message lines rate-limited,
                 0 message lines dropped-by-MD,
                 xml disabled, sequence number disabled
                 filtering disabled
           Logging Source-Interface:       VRF Name:
           VlanXXX                        
    --More--        
    Log Buffer (16384 bytes):
    OWN: Line protocol on Interface GigabitEthernet2/0/20, changed state to up
    *Jan 29 18:09:18 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/48, changed state to up
    *Jan 29 18:09:18 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan100, changed state to up
    *Jan 29 18:09:18 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/6, changed state to up
    *Jan 29 18:09:19 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/11, changed state to up
    *Jan 29 18:09:19 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/6, changed state to up
    *Jan 29 18:09:20 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/16, changed state to up
    *Jan 29 18:09:20 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/18, changed state to up
    *Jan 29 18:09:20 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/11, changed state to up
    *Jan 29 18:09:20 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/34, changed state to up
    *Jan 29 18:09:20 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/40, changed state to up
    --More--         *Jan 29 18:09:21 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/33, changed state to up
    *Jan 29 18:09:21 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/16, changed state to up
    *Jan 29 18:09:21 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/18, changed state to up
    *Jan 29 18:09:21 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/34, changed state to up
    *Jan 29 18:09:21 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/40, changed state to up
    *Jan 29 18:09:22 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/33, changed state to up
    *Jan 29 18:09:23 GMT: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 10.2.0.91 port 514 started - reconnection
    *Jan 29 18:09:32 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/8, changed state to up
    *Jan 29 18:09:33 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/8, changed state to up
    Jan 29 18:21:15 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/33, changed state to down
    Jan 29 18:21:16 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/33, changed state to down
    Jan 29 18:23:08 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/33, changed state to up
    --More--         Jan 29 18:23:09 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/33, changed state to up
    Jan 29 18:24:03 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/33, changed state to down
    Jan 29 18:24:04 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/33, changed state to down
    Jan 29 18:24:59 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/33, changed state to up
    Jan 29 18:25:00 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/33, changed state to up
    Jan 29 18:31:23 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2d6114a8
    Jan 29 18:39:32 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/18, changed state to down
    Jan 29 18:39:33 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/18, changed state to down
    Jan 29 18:39:48 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/11, changed state to down
    Jan 29 18:39:49 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/11, changed state to down
    Jan 29 19:28:28 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 29 19:36:30 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/40, changed state to down
    --More--         Jan 29 19:36:31 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/40, changed state to down
    Jan 29 20:00:27 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/8, changed state to down
    Jan 29 20:00:29 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/8, changed state to up
    Jan 29 20:57:18 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 29 21:02:15 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/33, changed state to down
    Jan 29 21:02:16 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/33, changed state to down
    Jan 29 21:20:18 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048e1, core 2/cpu 2, cp0_errorepc == 2d8f68b4
    Jan 29 21:28:12 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == ffffffff81295c98
    Jan 29 21:29:18 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 560c48a8
    Jan 29 21:39:20 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 58347c9c
    Jan 29 21:44:24 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b1, core 2/cpu 2, cp0_errorepc == 2b666b04
    Jan 29 21:49:37 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 58347cb4
    --More--         Jan 29 22:00:44 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 29 22:10:11 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 29 22:22:56 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 29 23:37:18 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2d6114a8
    Jan 29 23:48:01 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048e1, core 2/cpu 2, cp0_errorepc == 2d8f68b4
    Jan 30 00:04:29 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == ffffffff812660b4
    Jan 30 00:12:07 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 560c489c
    Jan 30 00:36:04 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 00:41:56 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 58347c98
    Jan 30 00:48:43 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 00:55:03 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 00:55:03 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    --More--         Jan 30 01:07:42 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 01:07:51 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2d6114b0
    Jan 30 01:14:01 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 01:48:51 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 01:57:03 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 560c48a8
    Jan 30 02:33:17 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 02:36:04 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 560c489c
    Jan 30 02:38:55 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 02:55:29 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 03:05:02 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 03:14:28 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 03:19:17 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 58347c9c
    --More--         Jan 30 03:33:09 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 560c489c
    Jan 30 03:49:26 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 03:49:26 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 03:52:33 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 03:52:33 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 04:11:15 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b1, core 2/cpu 2, cp0_errorepc == 2b666b04
    Jan 30 04:18:10 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b1, core 2/cpu 2, cp0_errorepc == 2b666b04
    Jan 30 04:26:18 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 58347ca0
    Jan 30 04:52:43 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 04:59:08 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 04:59:08 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 04:59:08 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    --More--         Jan 30 05:00:17 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/8, changed state to down
    Jan 30 05:00:18 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/8, changed state to down
    Jan 30 05:00:33 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/8, changed state to up
    Jan 30 05:00:34 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/8, changed state to up
    Jan 30 05:53:40 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 58347ca0
    Jan 30 05:56:11 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 05:59:24 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 05:59:24 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 05:59:50 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/33, changed state to up
    Jan 30 05:59:51 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/33, changed state to up
    Jan 30 06:05:44 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 06:08:50 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    --More--         Jan 30 06:12:53 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == ffffffff815654a8
    Jan 30 06:15:59 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 583d14b8
    Jan 30 06:21:11 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/15, changed state to up
    Jan 30 06:21:12 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/15, changed state to up
    Jan 30 06:21:25 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/15, changed state to down
    Jan 30 06:21:27 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/15, changed state to up
    Jan 30 06:27:55 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 06:29:00 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/18, changed state to up
    Jan 30 06:29:01 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/18, changed state to up
    Jan 30 06:29:03 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/18, changed state to down
    Jan 30 06:29:04 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/18, changed state to down
    Jan 30 06:29:08 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/18, changed state to up
    --More--         Jan 30 06:29:09 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/18, changed state to up
    Jan 30 06:38:33 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/11, changed state to up
    Jan 30 06:38:34 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/11, changed state to up
    Jan 30 06:50:32 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 58347c98
    Jan 30 06:59:22 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == ffffffff812a60b0
    Jan 30 07:06:00 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 07:24:30 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048e1, core 2/cpu 2, cp0_errorepc == 2d8f68b4
    Jan 30 07:24:58 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 07:31:24 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 07:50:24 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 07:56:43 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 08:03:02 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    --More--         Jan 30 08:03:03 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 08:26:17 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 58347ca0
    Jan 30 08:37:26 GMT: %ILPOWER-7-DETECT: Interface Gi2/0/29: Power Device detected: IEEE PD
    Jan 30 08:37:29 GMT: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi2/0/29: PD removed
    Jan 30 08:37:29 GMT: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi2/0/29: Power given, but Power Controller does not report Power Good
    Jan 30 08:44:20 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 08:44:20 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 08:53:53 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 08:53:53 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0
    Jan 30 08:57:01 GMT: %IOSXE-3-PLATFORM: 2 process kernel: EDAC DEVICE0: CacheErr (Icache):2521ff00000048b9, core 2/cpu 2, cp0_errorepc == 2cd694b0

    Thankx Rasikanayanajith,
    I have downgraded the IOS from 03.03.01 to 03.02.03 and it has been running for 8+ hours straight now with no reboots since and seem very stable. There is load on the switch. However, I did get some error msg just recently (posted below):
    Feb  3 12:42:03 GMT: Core2: 1 kernel:  Cache error exception:
    Feb  3 12:42:03 GMT: cp0_errorepc == ffffffff812ab4b0 1 kernel:
    Feb  3 12:42:03 GMT: CacheErr (Icache) == 2521ff00000048b9 1 kernel:
    Feb  3 12:58:11 GMT: Core2: 1 kernel:  Cache error exception:
    Feb  3 12:58:11 GMT: cp0_errorepc == ffffffff812ab8a8 1 kernel:
    Feb  3 12:58:11 GMT: CacheErr (Icache) == 2521ff00000048b9 1 kernel:
    Feb  3 13:10:06 GMT: Core2: 1 kernel:  Cache error exception:
    Feb  3 13:10:06 GMT: cp0_errorepc == ffffffff812ab4b0 1 kernel:
    Feb  3 13:10:06 GMT: CacheErr (Icache) == 2521ff00000048b9 1 kernel:
    Feb  3 13:20:50 GMT: Core2: 1 kernel:  Cache error exception:
    Feb  3 13:20:50 GMT: cp0_errorepc == ffffffff812ab4b0 1 kernel:
    Feb  3 13:20:50 GMT: CacheErr (Icache) == 2521ff00000048b9 1 kernel:
    Feb  3 13:47:58 GMT: Core2: 1 kernel:  Cache error exception:
    Feb  3 13:47:58 GMT: cp0_errorepc == ffffffff812ab8a8 1 kernel:
    Feb  3 13:47:58 GMT: CacheErr (Icache) == 2521ff00000048b9 1 kernel:
    Feb  3 18:11:11 GMT: Core2: 1 kernel:  Cache error exception:
    Feb  3 18:11:11 GMT: cp0_errorepc == ffffffff812ab8a8 1 kernel:
    Feb  3 18:11:11 GMT: CacheErr (Icache) == 2521ff00000048b9 1 kernel:
    thankx
    Joe Chross

  • Syslog server for Monitoring Cisco devices

    I am looking for Syslog server to log all logs from Cisco devices. We have more than 800 cisco devices. Can anyone tell me what syslog server should i use to log these files.
    Thank you.

    Has anyone used the Cisco recommendation of Buliding Scalable Syslog Solutions?
    http://www.cisco.com/en/US/technologies/collateral/tk869/tk769/white_paper_c11-557812.html#wp9000318
    I used this in another organaztion and we were very successful, we currenlty use Netcool that feeds from a syslog and we get several non-actionable alarms and it's very time consuming for 13,000 devices.  I would only like to alert on 0-5 Cisco Syslog messages.  Below is the response from my Netcool Administrator (What are your thoughts?):
    From my Netcool Administrator:
    Regarding, using the Cisco syslog severity for alert control, I feel that is not the best way to control the work in Netcool.
    1. -- Cisco is not consistent with the use of this value.
        Examples:
            In this case the important message is the lower severity alert: I would consider the BGP-3-NOTIFICATION of a 6 level of Informational
            Aug  4 03:10:01 rtgara02r01m04-lb0.us.bank-dns.com 001458: Aug  4 03:10:01: %BGP-5-ADJCHANGE: neighbor 10.93.69.106 Down BGP Notification sent
            Aug  4 03:10:02 rtgara02r01m04-lb0.us.bank-dns.com 001459: Aug  4 03:10:01: %BGP-3-NOTIFICATION: sent to neighbor 10.93.69.106 4/0 (hold time expired) 0 bytes   
            This one is near the top level of serverity per Cisco but not all that severe in reality, further this syslog has a bug where the threshold is not even exceeded
            %ENVMON-1-CPU_WARNING_OVERTEMP: Critical Warning: CPU temperature 107C exceeds threshold 110C.  Please resolve system cooling immediately to prevent system damage
            This one is reporting a standard condition:
            %ILPOWER-5-POWER_GRANTED: Interface Fa0/24: Power granted
            Here is an example of a 1 where the voice group says that nothing is wrong:
            Aug  4 13:08:42 rtgcaa75u01-01.sw.us.bank-dns.com 047489: Aug  4 11:08:41: %IVR-1-APP_PARALLEL_INVALID_LIST: Call terminated.  Huntgroup \'1\' does not contain enough valid SIP end-points to proceed with a parallel call.

Maybe you are looking for

  • How do i sync my notes from my mac to iCloud?

    Hi there, I've been trying to sync my notes between my iphone, ipad and macbook.  I'm able to sync them between my ipad, iphone and icloud, but I can't do it from my macbook.  That's really what the whole point of this exercise is - there are a lot o

  • How to enter a new Date and Time each day in a Numbers Spreadsheet...

    Hi... I have finally decided to move away from Excel and really give Numbers a shot... I have an application where each day I first enter the current date and time into a particular cell of a new row and then I enter some data in cells adjacent (in t

  • Error while using RUN_REPORT_OBJECT thru Menu in Developer 10g

    Hi All: I am trying to call the Oracle Report desinged in Oracle Reports 10g from Menu. I wrote the following coding in Menu Item: declare repid report_object; v_rep varchar2(100); rep_status varchar2(20); begin repid:=FIND_REPORT_OBJECT('Exportsvess

  • PDF Dynamic Watermark - Not working

    Hi, We are using Oracle UCM 10gR3 (Stellent) with IIS 6. Ghost script 8.63 for conversion We have configured Watermark Templates and set rule for displaying Watermark dynamically on the footer based on dDocAuthor. Static watermark is appearing with o

  • PS/NVision problem since upgrading to PeopleTool 8.53.13

    We are busy upgrading from PeopleTools 8.49.18 to PeopleTools 8.53.13 on HCM 9.0. Since the upgrade the "Run Report" button on the PS/nVision "Define Report Request" page is missing. I have:- 1) Checked security 2) Run a trace and see the instruction