From: itsfortarget iwillgetit (itsfortarget@gmail.com)
Date: Tue Jun 03 2008 - 17:23:29 ART
workaround is to use BIA or use other mac address , but the both is not
recommended by cisco as best solution due to other reason.
On Tue, Jun 3, 2008 at 11:13 PM, Mike Haddad <mike.haddad@hotmail.com>
wrote:
> Hello,
>
> That makes lots of sense and what is the solution in this type of
> situation? Is it to use a aribitrary MAC Address for HSRP?
>
> Thanks,
>
>
>
>
> ------------------------------
> Date: Tue, 3 Jun 2008 22:54:43 +0300
> From: itsfortarget@gmail.com
> To: mike.haddad@hotmail.com
> Subject: Re: HSRP and BIA
> CC: ccielab@groupstudy.com
>
>
> HELLO,
>
>
> When port security is configured on the switch ports that are connected to
> the HSRP enabled routers, it causes a MAC violation, since you cannot have
> the same secure MAC address on more than one interface. A security violation
> occurs on a secure port in one of these situations:
>
> - The maximum number of secure MAC addresses is added to the address
> table, and a station whose MAC address is not in the address table attempts
> to access the interface.
> - An address that is learned or configured on one secure interface is
> seen on another secure interface in the same VLAN.
>
> By default, a port security violation causes the switch interface to become
> error-disabled and to shutdown immediately, which blocks the HSRP status
> messages between the routers.
>
> http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080094afd.shtml#topic5
>
> On Tue, Jun 3, 2008 at 8:59 AM, Mike Haddad <mike.haddad@hotmail.com>
> wrote:
>
> Hello,
>
> When the question says do not use the BIA address for HSRP. Isn't it the
> default behavior of HSRP?
>
> Thanks in advance,
> Regards,
>
> _________________________________________________________________
>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
> ------------------------------
This archive was generated by hypermail 2.1.4 : Tue Jul 01 2008 - 06:23:20 ART