3550 Logging

From: gladston@br.ibm.com
Date: Thu Jul 21 2005 - 18:59:01 GMT-3


Do you know if there is a way to make 3550 logging work with access-list?

In this test there is a vlan map that uses match ip-address 111. It denies dlsw, but logging does not indicate it.

Logging is enabled.

Rack2CAT1#sh logg
Syslog logging: enabled (0 messages dropped, 3 messages rate-limited, 0 flushes, 0 overruns)
    Console logging: level debugging, 180 messages logged
    Monitor logging: level debugging, 0 messages logged
    Buffer logging: level debugging, 183 messages logged
    Exception Logging: size (4096 bytes)
    File logging: disabled
    Trap logging: level informational, 187 message lines logged

Rack2CAT1#sh access-list 111
Extended IP access list 111
    deny tcp any eq 2065 any log-in
    deny tcp any any eq 2065 log-in
    deny tcp any eq 2067 any log-in
    deny tcp any any eq 2067 log-in

The access-list is working; as soon as it permits dlsw, connection is established.



This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:00:30 GMT-3