cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
12936
Views
5
Helpful
7
Replies

interface up down status are not getting logged via console or telnet

blrnetwork
Level 1
Level 1

Hai we use cisco 4506 as access switches.I want to get all logging messages including interface up down status with the mac-address ..But i am not getting the logs for the interface up down status on 4506 switches..

any specific configuration is required for that...

this is my current config for one of my access switch

no logging console

logging trap notifications

logging 10.203.193.112

here logging is disabled via console .but i have configured

logging monitor

which should display the logs via telnet sessions.it's not happening..Pls suggest me a solution.

2 ly i need to to whether mac-notification feature is available in cisco-IOS features..

Regards....

Gokulakrishnan.

7 Replies 7

Try this command

logging synchronous

Hi

I configured "logging synchronous " on line vty 0 15 & line con 0 also and seen the logs it doesn't show any logs about interface up down status....

whether we need to give " logging synchronous level all " instead "logging synchronous "

Regards....

Gokulakrishnan.

n.nandrekar
Level 4
Level 4

hi!

You can try " terminal monitor" in order to get the logging on the telnet session. also try terminal monitor after "logging console"

Is it that you are getting all other logs but just link up/down missing???

In that case, try :

-P(config)#logging event link-status default

Regards,

Niranjan

(pls rate helpful posts)

Hai i tried the above option

I given " terminal monitor " from privilege mode

i didn't get any logs

i tried to configure " logging event link-status default " but i am not able to configure that from global config mode..There is no option for that...

Regards....

Gokulakrishnan.

Hai i tried the above option

I given " terminal monitor " from privilege mode

i didn't get any logs

i tried to configure " logging event link-status default " but i am not able to configure that from global config mode..There is no option for that...

Regards....

Gokulakrishnan.

If you have configured logging monitor - what level did you specify? E.g. wanrnings, notifications, etc.

Also, since it looks like you are logging to a syslog server - are the up/down interface logs turning up there?

I think when the log buffer is full at the switch then all the old logs will get accumulated at the Syslog server,..

but i didn't specify any level in logging monitor" i have just configured " logging monitor "

Is it not possible to monitor all events under the telnet sessions.

also i was monitoring the console logs by disabling the " logging monitor " & " term monitor " and enabling the console monitoring as " logging console " ..

By the above command it should log all the events thru console ....

it 's not happening.....

Only log which i get isattached herewith

bghsgsw601#sh log

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

Console logging: disabled

Monitor logging: level debugging, 3 messages logged, xml disabled,

filtering disabled

Buffer logging: level debugging, 645 messages logged, xml disabled,

filtering disabled

Exception Logging: size (8192 bytes)

Count and timestamp logging messages: disabled

Trap logging: level notifications, 652 message lines logged

Logging to 10.203.193.112, 652 message lines logged, xml disabled,

filtering disabled

Log Buffer (4096 bytes):

19w0d: IP ARP: rcvd req src 10.203.238.50 0060.fb51.c4b7, dst 10.203.238.33 Vlan444

*Jul 8 04:42:34.062 UTC: %SYS-5-CONFIG_I: Configured from console by bgh07668 on vty1 (10.203.237.175)

*Jul 8 04:51:35.406 UTC: %SYS-5-CONFIG_I: Configured from console by bghit on vty0 (10.203.237.167)

*Jul 8 04:56:57.414 UTC: %SYS-5-CONFIG_I: Configured from console by bghit on vty0 (10.203.237.167)

*Jul 8 05:00:49.418 UTC: %SYS-5-CONFIG_I: Configured from console by bghit on vty0 (10.203.237.167)

*Jul 8 06:47:41.313 UTC: %SYS-5-CONFIG_I: Configured from console by bgh17581 on vty0 (10.203.237.171)

*Jul 9 22:21:57.307 UTC: %SYS-5-CONFIG_I: Configured from console by bghit on vty0 (10.203.237.167)

*Jul 9 23:33:45.859 UTC: %SYS-5-CONFIG_I: Configured from console by bghit on vty0 (10.203.237.167)

*Jul 9 23:34:46.995 UTC: %SYS-5-CONFIG_I: Configured from console by bghit on vty0 (10.203.237.167)

*Jul 9 23:46:18.607 UTC: %SYS-5-CONFIG_I: Configured from console by bghit on vty0 (10.203.237.167)

*Jul 9 23:52:49.651 UTC: %SYS-5-CONFIG_I: Configured from console by bghit on vty0 (10.203.237.167)

*Jul 10 01:56:45.535 UTC: %SYS-5-CONFIG_I: Configured from console by bghit on vty1 (10.203.237.167)

*Jul 10 02:08:20.219 UTC: %SYS-5-CONFIG_I: Configured from console by bghit on vty1 (10.203.237.167)

*Jul 10 23:30:21.453 UTC: %SYS-5-CONFIG_I: Configured from console by bghit on vty0 (10.203.237.167)

*Jul 10 23:44:43.529 UTC: %SYS-5-CONFIG_I: Configured from console by bghit on vty0 (10.203.237.167)

*Jul 13 21:50:46.548 UTC: %SYS-5-CONFIG_I: Configured from console by bghit on vty0 (10.203.237.167)

*Jul 14 05:18:16.930 UTC: %SYS-5-CONFIG_I: Configured from console by bgh17581 on vty0 (10.203.237.171)

*Jul 14 05:20:35.846 UTC: %SYS-5-CONFIG_I: Configured from console by bgh17581 on vty0 (10.203.237.171)

*Jul 14 22:04:39.266 UTC: %SYS-5-CONFIG_I: Configured from console by bgh17581 on vty1 (10.203.238.35)

*Jul 14 23:20:10.497 UTC: %SYS-5-CONFIG_I: Configured from console by bgh17581 on vty0 (10.203.237.171)

*Jul 14 23:43:08.117 UTC: %SYS-5-CONFIG_I: Configured from console by bgh17581 on vty0 (10.203.237.171)

*Jul 14 23:51:42.813 UTC: %SYS-5-CONFIG_I: Configured from console by bgh17581 on vty0 (10.203.237.171)

*Jul 14 23:54:30.249 UTC: %SYS-5-CONFIG_I: Configured from console by bgh17581 on vty0 (10.203.237.171)

*Jul 15 00:45:21.657 UTC: %SYS-5-CONFIG_I: Configured from console by bgh17581 on vty0 (10.203.238.35)

bghsgsw601#

Regards.....

Gouklakrishnan.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco