Configuring syslog and SNMP on Cisco Integrated Service Router (ISR)

Unanswered Question
Aug 14th, 2007

Greetings,

Configuring Cisco integrated Service router is a little bit trivial. For instance, you have to configure the backplane logical interface with Ip address in order to session to EtherSwitch module.

The ES module is configured as pure layer two, therefore a router port is trunked to ES port 802.1Q. This is working perfectly because by default all ports and vlans are allowed through the trunk.

Router config:

logging source-interface Vlan81

logging 10.5.9.73

logging 10.5.6.13

snmp-server engineID:XXXX

What is the purpose of engineID configuration and where to locate and change the engine ID octet string.

snmp-server community xxxxx RO 2

snmp-server community xxxxx RW 3

snmp-server community xxx view v1default RO

snmp-server trap-source Vlan81

snmp-server location Lab

snmp-server contact xxxxxx

snmp-server enable traps snmp linkdown linkup

snmp-server enable traps config

snmp-server enable traps hsrp

snmp-server enable traps rtr

snmp-server enable traps syslog

snmp-server host 10.5.6.13 xxxxx

snmp-server host 10.55.9.73 xxxxxx

ETHERSWITCH CONFIG:

no logging console

no logging monitor

snmp-server engineID local xxx (the same id as router)

snmp-server community xxxx RO 2

snmp-server community xxxx RW 3

snmp-server community xxxview v1default RO

snmp-server trap-source Vlan81

snmp-server location xxxx

snmp-server contact xxxxxx

snmp-server enable traps snmp linkdown linkup

snmp-server enable traps config

snmp-server enable traps hsrp

snmp-server enable traps rtr

snmp-server enable traps syslog

snmp-server host 10.5.6.13 inform version 2c xxxx snmp

snmp-server host 10.5.9.73 inform version 2c xxxx udp-port 1620 snmp

snmp-server host 10.5.6.13 version 2c xxxx snmp

snmp-server host 10.5.9.73 version 2c xxx udp-port 1620 snmp

snmp-server host 10.5.6.13 xxxx

snmp-server host 10.5.9.73 xXXX

You may be wondering why port 1620. that was fat-fingered. when I tried to remove the it, it refused to be removed.

Only the router interfaces are sending traps to remote NMS. The goal is to configure syslog and snmp to send link up/down and line protocol down/up messages to the servers.

I must be missing something.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Wed, 08/15/2007 - 09:56

I don't see any logging server and trap configuring on the ES module. You will need the same logging config on the ES module that you have on the router. In fact, you should duplicate the same SNMP trap configuration on the ES module as well. Sure, you may want to enable additional traps on the ES module, but the trap hosts should be the same lines.

Actions

This Discussion