Solved: different behavior with port-security Cat4500 / Cat3550

From: Oliver Ziltener (ziltener@netcloud.ch)
Date: Fri Aug 01 2003 - 15:04:40 GMT-3


Hello all

please note this:

Cat 4500:
See in this document:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat4000/12_1_19/config/po
rt_sec.htm#1047772

*restrict*?A port security violation restricts data and causes the
SecurityViolation counter to increment and send an SNMP trap notification.
snip..

Cat3550:
http://www.cisco.com/univercd/cc/td/doc/product/lan/c3550/12114ea1/3550scg/sw
trafc.htm#1038501

*restrict*?When the number of secure MAC addresses reaches the limit
allowed on the port, packets with unknown source addresses are dropped
until you remove a sufficient number of secure MAC addresses or increase
the number of maximum allowable addresses. In this mode, you are
notified that a security violation has occurred. Specifically, an SNMP
trap is sent, a syslog message is logged, and the violation counter
increments.

The feature is simply not implemented exactly the same.

Oliver



This archive was generated by hypermail 2.1.4 : Tue Sep 02 2003 - 18:53:51 GMT-3