Hey group,
T/S an FTP app prob, and I came upon something that made me "ponder".  
Hardware:::
        6509, dual msfc2, 
Software:
        IOS 12.1.(5a)E
        Slot 15: VLAN236 
                10.10.239.12
                standby 236.1 priority 150   [10.10.236.0/22]
        Slot 16: VLAN236
                10.10.239.11
                standby 236.1 priority 125   [and therefore standby]

So I have a client on 10.22.22.22 FTPing to 10.10.236.57.  When I sniffed
the wire [actually the 236.57 port], what I found was that traffic from
22.22 had multiple source-MAC adders.  
So, lets for the sake of brevity say that MAC adders are::
        slot15 is AAA 
        slot16 is BBB
        HSRP is CCC
        & 236.57 is DDD

what I see is:::

AAA (22.22) --> DDD (236.57)
CCC (22.22)  DDD (236.57)
CCC (22.22)  DDD (236.57)  !!!!!!!!!!!!!!
CCC (22.22)  DDD (236.57)
CCC (22.22) <-- DDD (236.57)
etc, you get the idea...

OK, right up front, the conversation from AAA to DDD and then DDD to CCC
"makes sense" to me..  :-)
But why does the back-up mfsc suddenly transmit?  He's not Primary, they
haven't swapped active [did a sh logg].
My thoughts right now:::
HSRP is a listening protocol and not a speaking protocol....but even if that
is true [can't find anything DEFINITIVE at CCO] what makes the back-up
interface suddenly decide to talk?  And it doesn't seem to be a load-balance
thing but rather new-session related... But what does that matter? ie: why
would the secondary mfsc even see this traffic...

Any thoughts? CCO links mucho appreciated if they explain this...
Does the 6500 series automatically session-balance when using HSRP?

Looking forward to your thoughts....
TroyC




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=35892&t=35892
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to