VRRP/ipfc and mgmt on MDS

When you have to access remote MDS via fcip link or fc link, ie., access
FM via that IPFc, here is a design for you!

SAmple Config:


DS9120-A1# show vrrp
Interface VR Status
-------------------------------------------------------
mgmt0 1 backup
MDS9120-A1# show run int mgmt 0

interface mgmt0
ip address 172.16.33.82 255.255.255.128
switchport speed 100
vrrp 1
address 172.16.33.82
address 172.16.33.120 secondary
no shutdown


MDS9216i# show run int mgmt 0
version 2.1(1)

interface mgmt0
ip address 172.16.33.86 255.255.255.128
vrrp 1
address 172.16.33.86
address 172.16.33.120 secondary
no shutdown

MDS9216i# show vrrp
Interface VR Status
-------------------------------------------------------
mgmt0 1 master

the problem is uou have to vrrp address same as that mgmt 0.. It has
been confusing for me.. how does the remote switch know the ip address
of other switche's vrrp enabled address ?
Problem Statement:

a. Customer wants to use ISL link to FM/DM related management in a
Two Switch
Scenario, when one mgmt interface is messed up.

b. also the wants minimum traffic
to ISL and confirmed that no host or storage will talk to the storage or
host on the
remote switch. (localization).

Design:

a. both 9216 will have console access for better recovery.
-configure vrrp on the mgmt interface. , this is to resolve
problem with two static entries for same network. As
static route entries load balances , if there are two paths,
and it does not know when when one path fails.
So we configure only one static entry with vrrp interface 172.16.33.120and
vrrp will take care of routing thro' active path).
( for eg, configuration of 9506 with mgmt of 172.16.33.79
MDS9506-B1-sup1(config)# interface mgmt 0
MDS9506-B1-sup1(config-if)# vrrp 1
MDS9506-B1-sup1(config-if-vrrp)# address 172.16.33.79
MDS9506-B1-sup1(config-if-vrrp)# address 172.16.33.120 secondary
MDS9506-B1-sup1(config-if-vrrp)# no shutdown
MDS9506-B1-sup1# show vrrp

Interface VR Status
-------------------------------------------------------

mgmt0 1 master
and do the same thing for other switch with mgmt ip address 172.16.33.77
MDS9509-B1-sup1(config)# interface mgmt 0
MDS9509-B1-sup1(config-if)# vrrp 1
MDS9509-B1-sup1(config-if-vrrp)# address 172.16.33.77
MDS9509-B1-sup1(config-if-vrrp)# address 172.16.33.120 secondary
MDS9509-B1-sup1(config-if-vrrp)# no shutdown
MDS9509-B1-sup1# show vrrp

Interface VR Status
-------------------------------------------------------

mgmt0 1 backup

So even if mgmt 0 172.16.33.79 goes down, the vrrp 172.16.33.120 will route
thro' 172.16.33.77, so we need only static route path on host or the
router. )
- create ISL (TE port ) between 9216 in vsan 1
- configure ip for each 9216's vsan 1. (config t ; interface vsan 1)
- create vsan 10 with interfaces on one switch and empty vsan 20 on
the same switch.
- create empty vsan 10 on second switch and vsan 20 with interfaces on the
second switch.
- create second default routers with a different metric using vsan 1's ip
addresses.
- configure zoning from a single switch/ you can do either full zoneset to
propagate aliases
as well as non-active zonesets from that switch.
- you can do copy merge or leave it as it is on the second switch.
- if first 9216's mgmt fails, you can login to 9216 cli and connect to other
switche's vsan ip
and correct the problem. or thro' console.
- or configure static route to vsan's network to go via active mgmt (one
of the mgmt should be
up) on the mgmt wkstation and run fabric manager .


Also note that , even without VSAN 1 interface being configured for network,
you can
do zone editing etc thro' normal ISL because it uses FC-CT from one
switch.
Let me know if this suffice your requirements.