Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

syslogs from rsm, cat3548, cat 2950 etc via snmp port 162


Could you please tell how i could get the syslog from rsm, cat 2950 and 3548 to our nms-station. It seems that those devices send syslogs to udp port 514 and our nms-station listens only udp 162.

rsm does not have

snmp-server enable traps syslog -option.

Its version is



rsm uptime is 52 weeks, 13 hours, 17 minutes

System restarted by reload at 22:53:14 eetdst Tue Jul 17 2001

System image file is "slot0:c5rsm-isv-mz.120-15"

However we are receiving syslog messages from 7200 (ver slot1:c7200-js-mz.120-16) and 3640 flash:c3640-is-mz.113-10.T.bin.

Those have snmp-server enable traps syslog -option .

I Thank you in advance,

Best Regards,


  • Other Network Infrastructure Subjects

Re: syslogs from rsm, cat3548, cat 2950 etc via snmp port 162

The standrad port for Syslog is 512. 162 is the standard port for traps. The command 'snmp-server enable traps syslog' enables the syslog traps on your router and sends error message notifications (Cisco Syslog MIB). Specify the level of messages to be sent with the logging history level command (traps use port 162). You're confusing traps with syslog here. Refer to: which explains how to setup traps and what each mean. As for your question on how to setup the devices to send syslog messages, refer to the section 'How to Configure Cisco Devices for Syslog' at: for the steps.

New Member

Re: syslogs from rsm, cat3548, cat 2950 etc via snmp port 162

Hello !

Thank your for your answer. I am afraid my english is not so good . maybe i did not explain clear enough.

Our syslogserver (cisco works 2000) listens to syslog port 514 (standard syslog port) and it is receiving those syslog messages. We would need to get those messages as syslog traps only to our nms-station. The problem is that I cant configure the rsm to send syslog traps to snmp trap port 162. the rsm does not know the command 'snmp server-server enable traps syslog'.

rsm(config)#snmp-server enable traps syslog


% Invalid input detected at '^' marker.

rsm(config)#snmp-server host asdfgh ?

bgp Allow BGP state change traps

bstun Allow bstun event traps

config Allow SNMP config traps

dlsw Allow dlsw traps

dspu Allow dspu event traps

entity Allow SNMP entity traps

frame-relay Allow SNMP frame-relay traps

isdn Allow SNMP ISDN traps

rsrb Allow rsrb event traps

rtr Allow SNMP Response Time Reporter traps

sdlc Allow sdlc event traps

sdllc Allow sdllc event traps

snmp Allow SNMP-type notifications

stun Allow stun event traps

tty Allow TCP connection traps

udp-port The notification host's UDP port number

x25 Allow x25 event traps

rsm(config)#snmp-server enable traps ?

atm Enable SNMP atm traps

bgp Enable BGP state change traps

config Enable SNMP config traps

dlsw Enable SNMP dlsw traps

entity Enable SNMP entity traps

frame-relay Enable SNMP frame-relay traps

isdn Enable SNMP isdn traps

rtr Enable SNMP Response Time Reporter traps

snmp Enable SNMP traps

rsm#sh logging

Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)

Console logging: level debugging, 507 messages logged

Monitor logging: level debugging, 60 messages logged

Logging to: vty2(1)

Buffer logging: level debugging, 507 messages logged

Trap logging: level notifications, 511 message lines logged

Logging to, 511 message lines logged

However logging history shows the following ( I wonder why this says that

"SNMP notifications not enabled ")

rsm#sh logging history

Syslog History Table:1 maximum table entries,

saving level warnings or higher

72 messages ignored, 0 dropped, 0 recursion drops

447 table entries flushed

SNMP notifications not enabled

entry number 448 : STANDBY-3-DUPADDR

Duplicate address xxx.xx.xx.xx on Vlan5, sourced by 0000.0c07.ac05

timestamp: -1146845367

Neither do cat 3548's or 2950's know the command 'snmp-server enable traps syslog. Neither do they know the command 'logging history level'.

Referring to my previous messages, i was able to configure our 3640 and 7200 to send syslog traps. also our 5509's send syslog traps to our nms-station

Best Regards,


New Member

Re: syslogs from rsm, cat3548, cat 2950 etc via snmp port 162

ok resolved the issue with the help of tac-pages. (thak you tac !)

our ios-version (ip-subset or whatever) does not support syslog-mib.

IP PLUS and Enterprise versions do have the support for syslog-mib.

Also 2900/3500 xl do not support syslog-mib but 2950 does

Best Rgds,