From: jsaxe@xxxxxxxxxxxxxxx
Date: Fri Aug 23 2002 - 17:10:52 GMT-3
Hmm. I run a network in which we just recently put in MSFC2's in an existing
6509-based LAN. We have all dot1q trunks as well (as Ajith said, I started
with the standards so I skipped ISL). The legacy was to have all traffic in
VLAN 1, and so of course at the start all the switch (mostly 2900XL's)
management interfaces were in this VLAN, and most still are. But we most
definitely have HSRP groups in that VLAN; at first it was one HSRP group
composed of two routers, then composed of three routers, and now we have two
independent HSRP groups, group 1 and group 99, both in VLAN 1. All with no
problems.
I'm guessing that the admonishment in the article y'all referenced is to not
be running HSRP on the switch itself! I.e., if you can currently telnet to
the switch on 10.1.1.1/24, in VLAN 1, and you're about to move the
management interface by trunking to a big LAN, creating and un-shutting VLAN
50, and giving an IP address of 10.1.50.1/24, you should not have "standby"
commands under VLAN 50 right there on the 2950. (And the only reason I can
think of to run HSRP on a switch at all is to have a backup cluster
commander for a switch cluster. Otherwise, if one switch dies, who the heck
is going to take on its role in any meaningful way?)
I don't think the 2950 would care if you had "standby" commands on other
routers also on VLAN 50, either a couple of MSFC's or any other router. At
least that's the way I read the document, and that's my experience
personally. As Chuck said, management interfaces are basically just hosts.
-----Original Message-----
From: Chuck Church [mailto:cchurch@MAGNACOM.com]
Sent: Friday, August 23, 2002 9:55 AM
To: 'Gregory W. Posey Jr.'; Chuck Church; 'Abraham Ajith'; 'Phil';
ccielab@groupstudy.com
Subject: RE: OT: Strange DHCP result with MSFC2
Did you find a reason why they don't want you to use HSRP with a management
vlan? Management vlan is really just a concept of putting your switch mgmt
interfaces in a separate vlan. It doesn't necessarily imply they're tagged
or untagged. Any idea why? HSRP uses IP multicast, not really sure why
this would affect switch mgmt interfaces, which are really just hosts.
Chuck Church
CCIE #8776, MCNE, MCSE
Sr. Network Engineer
Magnacom Technologies
140 N. Rt. 303
Valley Cottage, NY 10989
845-267-4000
-----Original Message-----
From: Gregory W. Posey Jr. [mailto:gposey@uaes.org]
Sent: Wednesday, August 21, 2002 4:20 PM
To: 'Chuck Church'; 'Abraham Ajith'; 'Phil'; ccielab@groupstudy.com
Subject: RE: OT: Strange DHCP result with MSFC2
And I quote...
" Before changing the management VLAN on your switch network, make sure
you follow these guidelines:
The new management VLAN should not have a Hot Standby Router Protocol
(HSRP) standby group configured on it."
From:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat2950/1219ea1/scg/
swvlan.htm#xtocid3
(watch the word wrap)
I just happen to be implementing the same solution for a customer, and
was very unhappy to see this little note in the online doc CD.
Anyone know any workarounds (besides just NOT having HSRP in the
management VLAN)?
Thank you,
Greg Posey Jr.
CCIE #7981
CSS1, CCSE
CCNP - Voice Access
M.S. EE
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:35 GMT-3