From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Tue Aug 19 2003 - 19:03:31 GMT-3
Ken,
It is not legacy syntax, but syslog and snmp are mutually
exclusive. The 'logging' command applies to console, monitor, buffer,
and syslogging. The '[no] logging on' command enables/disables
syslogging. The 'snmp-server' command applies exclusively to snmp
polling and trapping.
HTH,
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-334-8987
Direct: 708-362-1418 (Outside the US and Canada)
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Kenneth Wygand
Sent: Tuesday, August 19, 2003 3:22 PM
To: ccielab@groupstudy.com
Subject: Syslog / SNMP configuration
Hello Everyone,
I am trying to configure a router to send syslog/SNMP messages to a
Ciscoworks Workstation (IP = 1.2.3.4)
I included the following configuration:
snmp-server community PUBLIC RO 1
snmp-server community PRIVATE RW 1
snmp-server trap-source FastEthernet0
snmp-server host 1.2.3.4 traps public
snmp-server enable traps
access-list 1 permit host 1.2.3.4
Do I need any of the following configuration:
logging on
logging trap information
Are these two commands a legacy way of configuring a syslog server and
possibly has now been replaced by the snmp-server commands? I'm
researched the DOC CD but haven't had too much luck.
Thanks in advance,
Kenneth E. Wygand
Systems Engineer, Project Services
CISSP #37102, CCNP, CCDP, MCP 2000, CNA 5.1, Network+, A+
Custom Computer Specialists, Inc.
"It's not just about ending up where you want to be, it's about making
the most of the trip there."
-Anonymous
This archive was generated by hypermail 2.1.4 : Tue Sep 02 2003 - 18:54:03 GMT-3