can't view L1/L2 up/down messages on Cisco 6513 show log

Answered Question
Jun 17th, 2010
User Badges:

I have a Cisco 6513 switch on the network.  I'm trying to view up/down messages on "show log".  The only things I see is when someone executes a write and when soneone clears an interface.  I did try playing around with console/monitor/buffer/trap logging.  I'm currenlty set to "level debugging".


I even compared the "show log" to a Cisco 3750 with no success.


-Manny

Correct Answer by glen.grant about 6 years 9 months ago

Use the "logging event link-status default "   global command , you then see interface up/down events in the log.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
joshiaroon Thu, 06/17/2010 - 12:29
User Badges:

Is the switch running cat os , if yes then try show logging buffer

fibernet570 Thu, 06/17/2010 - 12:32
User Badges:

Its running:

Cisco IOS Software, s72033_rp Software (s72033_rp-IPSERVICES_WAN-M), Version 12.2(33)SXH2a, RELEASE SOFTWARE (fc2)


Show log is:

show log
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)
    Console logging: level debugging, 1458 messages logged, xml disabled,
                     filtering disabled
    Monitor logging: level debugging, 0 messages logged, xml disabled,
                     filtering disabled
    Buffer logging: level debugging, 1458 messages logged, xml disabled,
                    filtering disabled
    Exception Logging: size (4096 bytes)
    Count and timestamp logging messages: disabled
    Trap logging: level debugging, 1493 message lines logged
        Logging to 192.168.11.44, 1430 message lines logged, xml disabled,
               filtering disabled
        Logging to 192.168.11.151, 435 message lines logged, xml disabled,
               filtering disabled


-Mn

joshiaroon Thu, 06/17/2010 - 12:42
User Badges:

try "logging buffered" command. Looks like buffer is not allocated in your switch..

fibernet570 Thu, 06/17/2010 - 12:55
User Badges:

It's already set to buffered "level debugging". this should cover severity 0 to 7 including:

emergencies        System is unusable                (severity=0)

  alerts             Immediate action needed           (severity=1)
  critical           Critical conditions               (severity=2)

  errors             Error conditions                  (severity=3)

warnings           Warning conditions                (severity=4)

notifications      Normal but significant conditions (severity=5)

  informational      Informational messages            (severity=6)
  debugging          Debugging messages                (severity=7)


Let me know if my assesment is correct.


Mn




fibernet570 Thu, 06/17/2010 - 13:00
User Badges:

I did enter "logging buffered", then I bounced a port.  Still don't see the up/down L1/L2 messages in "show log".


Mn

Correct Answer
glen.grant Thu, 06/17/2010 - 17:57
User Badges:
  • Purple, 4500 points or more

Use the "logging event link-status default "   global command , you then see interface up/down events in the log.

Actions

This Discussion