Newbie - VSP4000 square mesh cluster with base license possible?

[yeopaul]

Hi guys,

I am new to avaya. I was given 4 vsp4000 with Version : Build 4.1.0.0 , base license as cores, 4850gts and 3524 as edge.

The task given was to have all 4 vsp4000 to be able to act as router for all vlans in the event of failures, so I am thinking of using smlt/mlt with vrrp .

I tried to use simplified vIST in place of IST following avaya's campus design guide, however I was unable to add vlan to the vIST link.

My questions:

1) Will the design works, as in vsp4000 cores with full mesh?
2) if it doesn't, do I have any other options to make it works?
3) can base license support vIST, mlt, smlt, rsmlt, ospf, rip, vrrp?

regards,
paul

[Øyvind Nikolaisen]

Unfortunately, clusters are limited to two members at this time. Don't necessarily see the need for more, but I may be mistaken... 

Depending on your topology, you should set up two and two as two separate cluster using vIST - use proper vIST instead of the simplified one. Why? That's what you'll find most people familiar with if you need help... There are some considerations with regards to PIM when using simplified vIST, but I can't remember those details right now, I'm afraid. Edge switches should then connect with an SMLT/MLT to both VSP4000s in a cluster for load-sharing and redundancy. You ought to read the Network Design Reference for VSP4000 - http://downloads.avaya.com/css/P8/documents/101007438 as well as the Campus Technical Solution Guides from Avaya. You will find lots of useful information and configuration examples.

You can, of course, set up routing on all VSPs for all vlans using VRRP Backup Master. All routing will have to be in the GRT since you don't have a license for VRFs/L3VSNs, but traffic will be routed as soon as it hits a VSP4000.

One thing, get an upgrade to at least 4.2.1.1. All 4.x releases prior to that has a not so minor bug that causes a VSP4850 to reboot every 320 days and every VSP4450 every 426 days. VSP7200/8000 reboots every 284 days, whereas VSP9000 reboots every 320 days. Interesting bug... 

Best regards,
Øyvind

[yeopaul]

Hi Øyvind,

 I appreciate a lot on your advice especially i am still fresh on a lot of concepts. i have gone through your suggestions, well :> i hope i get them all.

I did the design as attached. for normal IST, you can add vlans to it. however, since I can't do the normal vIST, i have to use the simplified vIST, I just wonder how we add vlans to the simplified vIST links? or  since the link is 802.1q encapsulated, will simplified vIST trunk a trunk all for all vlans?


below is the example for the normal IST link configuration, and you are adding vlan to the IST:

5 Add VLANs 4, 5 and 2000 to the IST:
Core-A:1(config)# vlan mlt 4 1
Core-A:1(config)# vlan mlt 5 1
Core-A:1(config)# vlan mlt 2000 1
Core-A:1(config)# vlan mlt 4 1
Core-A:1(config)# vlan mlt 5 1
Core-A:1(config)# vlan mlt 2000 1

Below is the example i paste from vsp4000 documentation : Configuring IP Multicast Routing Protocols on Avaya VSP 4000


enable
configure terminal
no boot config flags spbm-config-mode
Save the configuration and reboot the switch.
virtual-ist peer-ip 50.1.1.14 vlan 50
mlt 3 enable
mlt 3 member 1/35,1/36
interface mlt 3
smlt
exit
mlt 5 enable
mlt 5 member 2/15,2/17
mlt 5 encapsulation dot1q
interface mlt 5
virtual-ist enable
exit
vlan create 50 type port-mstprstp 0
interface vlan 50
ip address 50.1.1.15 255.255.255.0 1
exit
vlan create 100
vlan mlt 100 3
interface vlan 100
ip address 100.1.1.15 255.255.255.0 2
exit
interface vlan 100
ip pim enable (or ip igmp snooping)
exit
interface vlan 50
ip pim enable
exit
ip pim enable