Good afternoon all,
I just recently finished another term of WGU, and decided to take a course break as work is requiring some training for the new (partial) Avaya infrastructure. I would like to share my experience here as this exam is somewhat new, and will show to you a little about the newest (We have the latest) Avaya routing/switching infrastructure. Considering I know most of you on this forum are Cisco (As am I), this is what I have learned so far coming from Cisco to Avaya (Even though about 2/3s of our infrastructure is still Cisco):
-Avaya does not support Cisco proprietary protocols i.e. EIGRP, PVST and Rapid PVST, CDP, PaGP, VTP, HSRP, GLBP
-Avaya has an autosave feature and is enabled by default
-Avaya's generic IDF infrastructure (The ERS 4850) supports both stacking and dual PSUs, but has a different software architecture from the VSP 8/9K (ERS uses Baystack while VSP uses VOSS Linux-based code), so the IOS syntax is slightly different, like comparing IOS to NX-OS
-Avaya has both the option of Command line (ACLI) and GUI (EDM). Compared to Cisco's previous attempts for this on IOS, I find it quite simple to navigate the GUI
-Avaya does not support PIM Dense mode (Thankfully)
-Avaya refers to loopbacks as CLIP interfaces
-Avaya uses the term route preference in replacement of Cisco's Administrative distance and route weight in place of route metric
-Avaya's route preferences (or AD) are different than Cisco's defaults and, logically, have different AD for OSPF E1, E2, Internal, and N1/2 routes
-While Avaya does support RSTP and MSTP, it is more common that Nortel's proprietary SMLT (Split Multi-Link trunking) standard is used. This is very similar to vPC in that it uses a peer link (Called an IST) to retain information across both SMLT devices. On the IDF end, either MLT or LACP link aggregation protocols can be used. SMLT load shares traffic based on source/destination IP if it is IP protocol. If not, it uses source/destination MAC. SLPP is used for loop prevention per VLAN
-Avaya supports all standard routing protocols i.e. BGP, OSPF, RIP, static, etc
-While Cisco usually has ECMP enabled by default with a certain number of max paths, Avaya's equipment only is configured for a single path (By default) and requires ECMP manual configuration
-VLACP, an extension to LACP, is a unidirectional link detection mechanism that is recommended to be enabled on SMLT links to prevent black holing traffic.
-Avaya uses LLDP instead of CDP
-Lastly, Avaya's newest equipment supports SPB (Shortest Path bridging). This protocol is similar to Fabricpath in that it uses IS-IS routing protocol for control plane at L2, has TLVs for extensibility. SPB also is capable of MPLS/VPLS type behavior, and is capable of true multicast ECMP using BVLANs within the secondary ethernet header (SPB uses MAC-in-MAC encapsulation). SPB also uses something called a I-SID (Which spans to over 16 million) in the SPB cloud, which is similar to a VLAN tag, but I will leave those interested to read the RFC. If you want a more in-depth look of SPB specific to Avaya, I have a long, technical document on it. PM if interested. This may look complex, but it is extremely simple to configure.
This is just a list of many comparisons. Obviously, Avaya has a list of many other features that are common among all vendors, but I will leave here what you may find useful. My company has provided a year of training for all of the following Avaya Learning courses:
-Avaya routing and switching ERS 4850/VSP 4000/VSP 8000/VSP 9000
-Avaya Identity Engines (Similar to Cisco's ISE)
-Avaya Wireless (Probably not going to look at this one as we're going to Aruba)
-Avaya COM (Configuration and Orchestration Manager. Really cool tool with auto-Visio capability)
-Avaya Fabric Connect Early Adopter Bootcamp
-Lab walkthroughs hosted on a Ubuntu VM.
I am a little skeptical of this new technology but really excited to get this learning going, and if by the end of next year I still like it, I will definitely make it known. So, after this initial post, I will soon be posting the notes I've made so far (in Onenote) to document my experience and make the path for those coming in to this in the near future a little easier.