Top 10 Networking Myths

This Avaya CONNECTED Blog
is also available as an MP3 Audio File

Whether your building out a corporate network, or a brand new ESINet for Public Safety, you need to understand networking, and there are some common myths that will leave you with a poor deployment and huge amounts of capitol investment rusting away in the data center while you try to figure out how to save your career.

10)Cisco continues to be the undisputed leader in networking innovation

It is time to stop living in the 90’s, while I won’t spend time to argue that statement, it is time to look at technology and where the market is heading TODAY. I hate to answer a question with questions, but let me ask:

  • Q: Who was first in delivering Resilient Stacking technology?
  • A: AVAYA
  • Q: Who changed the resiliency model from Active/Standby to Active/Active?
  • A: AVAYA
  • Q: Who introduced Split-Plane technology first to market?
  • A: AVAYA
  • Q: Who introduced hardware based 20ms resiliency?
  • A: AVAYA
  • Q: Who has delivered end to end Ethernet Fabric technology AND drove its standardization with IEEE/IETF?
  • A: AVAYA
  • Q: Who has delivered the most scalable 2 Tier Data Center architecture with lower latency?
  • A: AVAYA
  • Q: Who has delivered Layer 2 and Layer 3 Virtual Services Networks with its Ethernet Fabric Technology?
  • A: AVAYA
  • Q: Who has delivered innovative, scalable, resilient and fast registration for Multicast applications?
  • A: AVAYA
Myth 10

Remember, Innovation does NOT EQUATE TO acquisition, so exactly who is the Innovator and who is the follower?

9)Juniper seems to be the logical alternative to Cisco

Due to the unfortunate situation with Nortel Enterprise, many customers and partners were given no choice but to consider alternative vendors. While it’s clear Avaya has heavily invested in Networking, is Juniper still a logical alternative to Cisco? To me at least, it seems their QFABRIC Data Center strategy was a failure, now it’s based on SDN promises?

It’s time for customers to look back at Avaya’s portfolio and the technological maturity it brings from the heritage of Wellfleet, Synoptics, Bay Networks and Nortel. The technology train never stopped, and they are in the lead for Campus and Fabric architecture…time to reconsider Avaya? Yes indeed as Avaya solves REAL IT CHALLENGES TODAY and is in a unique position for many quarters to come…

8)There’s no different between proprietary and standards-based Fabric solutions

While some may think proprietary Fabric Architecture is ok for the Data Center, aren’t we living in an open system architecture world where best of breed technology should be selected?
How will you extend or leverage your Ethernet Fabric if it is proprietary? The world knows better and there happens to be an IEEE and IETF standard out there, known as SPB (Shortest Path Bridging) or if you prefer IEEE 802.1aq or IETF RFC 6329.

Inter-operabiltiy with other vendors has already been proved and the recent flawless performance of the Core at InterNet 2013 in Las Vegas, demonstrates the maturity and stability of this technology. Avaya is leading, time to look at solving your IT challenges once and for all

7)Wecannot eliminate Spanning Tree

Do people use a bus to try winning a Formula 1 race?

Do people fly airplanes with one of the two engines on standby?

None of this seems logical, does it?

So why is it customers tolerate building a network infrastructure utilizing a protocol that wasn’t built to deliver resiliency?

The market has clearly endorsed Active/Active as the defacto design model now, and it is time for customers to stop accepting sub-optimal solutions for their network and ensure failures won’t be business impacting. Avaya has 12+ years of maturity implementing Active/Active resiliency, and while other vendors are trying to catch up, Avaya keeps moving the dial further ahead, and maintains its position as the undisputed leader of Active/Active resiliency.

6)MPLS is the solution to all of our problems

Customers that wanted to deploy a multi-tenant and multi-services business solution, had no other choice but to eventually consider MPLS as the solution in order to provide Layer 2 and Layer 3 virtualization.

While that might be powerful and scalable, its level of complexity just made it extremely difficult for IT departments to retain the skill set required to build and maintain it.

What if there was, today, an alternative provide Layer 2 and Layer 3 Virtualization for both unicast and multicast based services? What if MPLS level scalability was achievable without its associated level of complexity?

What if that same solution gave you network behavior flexibility too, so you no longer have to guess how the network is behaving? What if Avaya was once again in the lead, helping you solve these challenges

5)Deploying services must involve weeks of planning and hours of implementation

Today it takes hours, weeks, months of preparation to deploy a new service across your Enterprise. Why? Simply because of the level of complexity associated with extending a service using existing legacy technology such as VLANs’ to extend such services. This translates into nodal configuration, which despite the qualification of your IT staff, requires proper planning and change management control. There is so much business risk associated with such a deployment, nobody will take a chance on doing it without proper testing and configuration validation.

What if you could, today, provision end to end services, but only have to touch the edge of your network?
Basically provision where the service is to be used, and where its being offered and VOILA, you are done. Let the network SERVICE your application needs.

4)Equipment maintenance and upgrade must be business-impacting

“Sorry Folks! Park’s Closed. The moose out front should have told ya’.”

Myth5.jpgIn the past most applications ran in a non-geo redundant or even in a single data center non-resilient deployment model. Now, you can easily deploy every application in an active/active model and woouldn’t it be even more powerful if you take advantage of various hypervisors virtualization solutions?
The combination of Virtualization, applications running in an Active/Active deployment model, as well as having a Data Center architecture that can extend Layer 2 domains where you need to, gives you the utmost flexibility and agility that your IT staff, and more importantly, your applications were looking for, and needed. Well, you don’t have to wait anymore, it’s here….

3)Multicast is becoming mandatory, but it’s complex, unreliable, and doesn’t scale

Everyone has been suffering through Multicast deployments over the last 15 to 20 years. The level of complexity and limited scalability, often gave no choice but to limit its utilization and size of deployment to known logical limits that did not meet the business needs.

What if you could finally scale multicast to new levels, while also addressing the design complexity?

What if you could no longer have to say “NO” when you are requested to deploy a multicast based application because your multicast network scalability is already saturated?

What if you didn’t have to build a separate infrastructure because the one you have is running at maximum capacity and scalability for multicast?

What if you didn’t have to force usage of unicast anymore? Or, what if you didn’t have application failures or business impacting situations due to the lethargic, slow recovery of multicast applications?

Well, there is a solution to your challenges, It’s called Native Multicast over SPB, and it comes to the rescue to deliver a never-before achieved level of scalability, while delivering 500 milliseconds recovery and 100ms or less registration, and delivering all this without the need for PIM!
That is innovation at its best, while still supporting inter-connectivity to PIM domains.

2)Avaya is a Voice company and doesn’t bring anything to Networking

While Avaya continues to be a leader in Unified Communications, Contact Center and Video conferencing, it is important to note its level of competiveness in the Networking area. Not only do they provide cost effective Ethernet connectivity with or without PoE, they also led the way by solving some complex IT challenges such as E911 location reporting, regardless of the mode of connectivity being used (wired and wireless).

While Avaya has a very strong Voice heritage, it also understands the networking requirement and has focused on delivering best in class innovative solutions which customers and partners need to pay special attention too.
Avaya is about innovative Real Time Collaborations, UC, CC, Video and highly reliable and scalable network.

From Data Center edge all the way to your Branch Edge, Avaya can help you solve these challenges TODAY using industry standard protocols and best practices. How many other competitors can say that? Let me help you out with that one. . . .

Pick a number between ZERO and NONE.

1)The future is all aboutSDN, so you have to wait….

SDN Is gaining momentum in the market, it is like a Tsunami hitting all the IT personnel trying to understand if this is the technology that will finally solve their IT challenges?

While SDN seems to focus on solving relevant IT problems, the question is more “What IT problems is the industry trying to solve, more importantly, what are YOUR business IT challenges”.

What if Avaya was able to solve these problems for you, TODAY with products, solutions, protocols, etc..that exist NOW in an open system architecture that does not require the wait for some new SDN Protocol to be supported by ALL vendors?

What if Avaya endorsed the SDN concept in addressing key IT business challenges?

What if Avaya offered Orchestration and simplification of Applications Provisioning today?

And more importantly….would you be interested in chatting with one of our Experts?

Avaya continues to innovate, but more importantly, Avaya can solve real IT challenges today by changing the way Networks are being built, without waiting for all sorts of promises to be delivered in the next few years. Giving Avaya an opportunity to show you what we can do TODAY, will be a worth while investment, and we promise not to disappoint you.

Related Articles:

Avaya and IAUG: Coming Together for a Better User Group Experience

Marilyn ShuckMarilyn Shuck serves as a Director on the IAUG Board, president of the Puget Sound Avaya Users Group, and as a UC Engineer at the University of Washington.



The combination of the Avaya Technology Forum (ATF) and the International Avaya Users Group (IAUG) flagship event, Avaya ENGAGE, is generating a lot of buzz. As IAUG members, it’s exciting for us because we’ll be there as Avaya is announcing new products and have better access to Avaya. We’re also looking forward to bringing in more technical expertise, session choice, and potential new members to IAUG.

In the past, ATF was held in February or March, and Avaya ENGAGE was in June. By the time we assembled for Avaya ENGAGE, new product lines would have been out for several months. Now, we’ll get to hear the latest announcements. Since we’re partnering with Avaya, we’ll have much more access to them, getting our questions answered, getting trained, and seeing the new products in action.

We’re also able to offer so many more sessions, some with more technical expertise. ATF has historically been a technical conference, and our IAUG attendees will have a choice of breakout sessions that will add a new dimension to the education they’ll already be receiving.

It also makes sense to hold both of these events under one umbrella. There’s some overlap between ATF attendees and Avaya ENGAGE attendees, and in organizations where travel budgets are tight or where the same person is a technical support specialist and a user, you no longer have to choose which event to attend.

Additionally, we’re excited about the possibility of introducing new members to IAUG. Some ATF attendees may not have known about our existence, but now not only will they have the chance to learn more about us but they can network with us. We can continue to share learning opportunities and even bring a whole new quality of technical users to IAUG.

Make no mistake, the foundation of the event has not changed. This is still planned with the Avaya customer in mind. However, it signals our deepening relationship by aligning all customer events.

This is going to be one of those cases where what happens in Las Vegas won’t stay in Vegas. Avaya and IAUG are aligning, and it’s going to provide valuable education and opportunities for customers, IAUG members, partners, and Avaya. The benefits of attending will resonate throughout your organization, so plan to join us in February to learn, network, and return full of ways to make the most of your Avaya implementations. You can learn more at


Advanced Techniques for Writing Avaya Breeze Snap-ins Using Engagement Designer—Part Four

Welcome to the fourth in my series of videos addressing some of the more advanced Avaya Breeze™ techniques. In Part One I showed you how to catch and process errors inside a Breeze Snap-in. In Part Two I addressed Breeze Connectors. In Part Three I added multimodal communications and parallel gateways. Here in Part four, I show you how to add JavaScript functions to Breeze expressions and data processing.

To start viewing my videos from the beginning watch the introductory series.

Continue with the advanced series:

Part 1: Error Processing and Boundary Events
Part 2: Breeze Connectors
Part 3: SMS Text, Email, and Parallel Gateways
Part 4: Adding JavaScript Functions to Snap-ins

Andrew Prokop is the Director of Vertical Industries at Arrow Systems Integration. Andrew is an active blogger and his widely-read blog, SIP Adventures, discusses every imaginable topic in the world of unified communications. Follow Andrew on Twitter at @ajprokop, and read his blog, SIP Adventures.

An Exploration of End-to-End Network Segmentation Part III: Automatic Elasticity

Imagine for a moment: you’re connected to a network via a piece of string. You perform your work, you wind down for the day and you disconnect from the network. When you leave the office, that piece of string stays behind, lying exactly where you last connected—exposed. Wouldn’t you know … the very next person to walk past your office after you leave is a hacker or a malicious employee (remember many attacks start from inside your network) who can now gain access to your open, vulnerable network via your left behind string (for techies, the static VLAN port configuration exposes that service). We all know what happens with the pull of just one thread … things unravel.

Now imagine this same scenario, but instead of your network core being connected by a string, it looks like a ball of rubber bands. When you connect to your network, a rubber band attaches to you, establishing your connection. Same as before, you disconnect when you finish your work day. The difference here is that your rubber band automatically recoils back to the network core (the rubber ball), where it safely rests until you or another user/device reconnects. If a hacker walks by where you’ve just been working, your node (or network connection) is no longer accessible. Similar to native stealth, this automatic elasticity means attackers can’t hack what they can’t connect to—therefore they can’t penetrate your network without the necessary level of authentication (certificates highly recommended).

This is the premise of automatic elasticity—the third core component of end-to-end segmentation (if you missed parts I and II of this series, be sure to catch up).

The Necessity of Elasticity

So, would you rather your network be a bundle of static, inflexible and unsecure strings that anyone can pull at? Or a dynamic, agile and secure elastic that extends to deliver services and retracts to prevent hackers from seeing and touching it?

Automatic elasticity enables businesses to stretch their network services (contained in hyper-segments) to the edge of the network, only as required and only for the duration of a specific application session. As applications terminate (or end-point devices close down or disconnect), those networking services retract from the edge. It’s as simple as that.

Stretching and retracting virtual services in this manner, however, becomes exceedingly difficult for companies operating in a static configuration environment. This is what ultimately led to Target’s massive data breach in 2013. A port had been statically configured to the company’s HVAC system—it did not retract—allowing a hacker to physically gain access to the entire network through that segment. From there, the hacker was able to conduct IP topology and trace IP routes to find the server they wanted and get the information they were after.

In this case, the mistake Target made was that it had no sophisticated methodologies in place to authenticate an end user or device before extending its HVAC port. It remained static, exposed and vulnerable to an attack, which eventually happened.

Without end-to-end segmentation, the only way businesses can truly extend their virtual services is to manually configure each node to simulate their desired level of elasticity. In this case, each node would have to be manually configured to stretch, and then that configuration would have to be removed as soon as the service was finished being used. Just imagine how time-consuming and painstaking this process would be on a large scale. This is illogical.

The bottom line is that automatic elasticity drastically reduces network exposure, and also transforms internal productivity and collaboration. A network access port is no longer statically mapped to a given service or user. Today it can be you, tomorrow a video surveillance camera, the next day a contractor. Agility, flexibility, security all delivered! With the ability to expedite provisioning and dynamically extend services to authenticated end-users or devices, an employee working across the country can quickly gain access to a system to complete a task. If you’re running late to a meeting, you can be authorized to temporarily gain access to a printer in-office to ensure you stay on schedule. The use cases for automatic elasticity are infinite and truly game-changing for businesses today.

In the End

While some still feel comfortable operating within legacy limitations, what’s important is that you now understand current industry standards have evolved to meet today’s next-generation network demands and security needs—something that end-to-end segmentation does flawlessly.

We’re excited to be able to help companies finally deploy end-to-end segmentation without resource-intensive or costly roadblocks. An end-to-end segmentation solution built on hyper-segmentation, native stealth and automatic elasticity is key. To succeed, you need all three of these complementary capabilities. All three share the common goal of maximizing network security. However, they contribute towards this goal in distinctly different yet necessary ways to substantially reduce your business risk exposure with the ever increasing cyber security threats we see and hear about globally.