Verify routing config on 6513 SUP-II??

[abatson]

We have a flat network with ~7 class-C subnets that we want to move the the SUP-II with routing function. -Just before we move to VLAN. Is the following config valid, to route between all the subnets listed on the SUP-II? Do I need two IPs from each subnet? One for the interface itself, and one for the "virtual IP"? I want to use the ".1" from each subnet as it's def. GW.

__________________________________________________________

interface Vlan500

description Connection to Flat Network

ip address 198.186.47.2 255.255.255.0

no ip redirects

mls rp management-interface

standby 1 ip 198.186.47.1

standby 1 priority 106

standby 1 preempt

ip address 198.186.44.2 255.255.255.0 secondary

no ip redirects

mls rp management-interface

standby 1 ip 198.186.44.1

standby 1 priority 106

standby 1 preempt

ip address 198.186.45.2 255.255.255.0 secondary

no ip redirects

mls rp management-interface

standby 1 ip 198.186.45.1

standby 1 priority 106

standby 1 preempt

ip address 198.186.46.2 255.255.255.0 secondary

no ip redirects

mls rp management-interface

standby 1 ip 198.186.46.1

standby 1 priority 106

standby 1 preempt

ip address 198.186.43.2 255.255.255.0 secondary

no ip redirects

mls rp management-interface

standby 1 ip 198.186.43.1

standby 1 priority 106

standby 1 preempt

ip address 198.186.59.2 255.255.255.0 secondary

no ip redirects

mls rp management-interface

standby 1 ip 198.186.59.1

standby 1 priority 106

standby 1 preempt

ip address 198.186.61.2 255.255.255.0 secondary

no ip redirects

mls rp management-interface

standby 1 ip 198.186.61.1

standby 1 priority 106

standby 1 preempt

[#2]

After having a look on your configuration, there is nothing wrong in it.

For addtional configurations, you can refer to the following also:

http://www.cisco.com/univercd/cc/td/doc/product/lan/cat5000/rel_5_2/layer3/routing.htm#xtocid302326

[abatson]

My local SE (CCIE) said that I should use different HSRP group numbers for each IP, or MAC addresses might conflict if a fail-over occurs. What do you think?

-

alex

[hbaerten · Accepted solution]

Hi abatson,

if you configure all this one a single vlan interface, it does not make sense to repeat identical commands, and you need to define the hsrp standby addresses (all but one) as secondary as well.

interface Vlan500

description Connection to Flat Network

ip address 198.186.47.2 255.255.255.0

ip address 198.186.44.2 255.255.255.0 secondary

ip address 198.186.45.2 255.255.255.0 secondary

ip address 198.186.46.2 255.255.255.0 secondary

ip address 198.186.43.2 255.255.255.0 secondary

ip address 198.186.59.2 255.255.255.0 secondary

ip address 198.186.61.2 255.255.255.0 secondary

no ip redirects

mls rp management-interface

standby 1 ip 198.186.47.1

standby 1 ip 198.186.44.1 secondary

standby 1 ip 198.186.45.1 secondary

standby 1 ip 198.186.46.1 secondary

standby 1 ip 198.186.43.1 secondary

standby 1 ip 198.186.59.1 secondary

standby 1 ip 198.186.61.1 secondary

standby 1 priority 106

standby 1 preempt

You could use hsrp groups but that would not give you any added value unless you want to have different hsrp parameters (priority, preempt) per group.

But why not implement vlans right away?

Herbert

[abatson]

Thanks for the example. With stations spread across 7 subnets, we need to find out who has what IP address first, which is a fairly manual process. Plus, CIsco Registrar (DHCP) not up yet; we'll use DHCP to plunk people into VLANs....

-Alex