ALL ABOUT MULTILAYER

Sedona's Blog

   

Share to Facebook Share to linkedin Share to Twitter Share to Google Plus

Selecting the right IP/optical network controller is critical for end-to-end service delivery. There is no room for capability gaps in the solution and we encourage you to carefully consider your options. We suggest asking suppliers the following questions to determine whether the solution can truly deliver comprehensive, accurate visibility and control in a real-world multilayer, multivendor, multidomain network. 

The questions have been developed as a result of Sedona’s extensive interactions with Tier 1 customers as they deploy our NetFusion IP/Optical Controller in both legacy and SDN-controlled network environments. To understand how NetFusion addresses these requirements, please contact us.

Multilayer

Multilayer is an essential requirement for reliable and optimized service delivery. Without complete multilayer capabilities, the network controller cannot determine the relationships between the layers and therefore, cannot fully analyze the network. For example, without optical awareness and knowledge of multilayer relationships, the network controller cannot know the service repercussions of optical failures and maintenance activities, or how to optimally route services in the IP/MPLS layer. Nor can it achieve full optimization or restoration without complete IP/MPLS knowledge, including available protection schemes.

  1. Is the solution multilayer? Can it automatically detect and correlate IP and optical topology and traffic?
  2. Provide a full breakdown of supported models in the Network and Data Link layers (IP/MPLS). Include further questions to determine if the following are supported.
    • IP links and bundled IP links (including both logical and physical interfaces)
    • LSPs
    • VRFs
    • VLANs
    • L2VPNs
    • L3VPNs
  3. Provide a full breakdown of the supported Optical layers. Include further questions to determine if the following are supported.
    • ODU2
    • ODU4
    • OCh
    • OMS
    • OTS

Multivendor

With a multilayer solution in place, you have a great start, but it must also be vendor agnostic. With today’s abundance of acquisitions and mergers, most networks consist of equipment from multiple vendors and without the ability to see and control all devices, the IP/optical network control solution is incomplete.

  1. Does the solution support multiple vendors?
  2. Which IP/MPLS vendors does the solution support?
  3. Provide a list of supported router operating systems and software versions.
  4. Which optical vendors does the solution support?
  5. What is the estimated time for adding support for a new vendor?
  6. Does adding support for a new vendor require a new release of the solution?
  7. Is the solution vendor also a network hardware vendor? If so, can they confirm that competing hardware vendors will provide open access to, and updates for, their equipment APIs?

Multidomain

Networks are managed by many systems, often by legacy systems with an eye to future control via SDN. Each of these systems and controllers represent a unique management domain. Without full support for the discovery and control of not only each domain, but also of the handoffs between them, you cannot guarantee end-to-end service delivery.

  1. Can the solution automatically map multiple optical domains?
  2. Can the solution automatically map the connectivity between the domains?
  3. Does the solution support native Ethernet handoff between the domains? This is sometimes called “1310 handoffs.”
  4. Does the solution support ODU handoffs between the domains?
  5. Which IP/MPLS EMS/NMS systems and SDN controllers are supported? Example answers could be support for the Juniper NorthStar SDN controller and Nokia SAM management system.
  6. Which optical EMS/NMS systems and SDN controllers are supported? Example answers could be support for the Infinera OTSv SDN controller and Coriant 7194 management system.

Access and Deployment

Only with full knowledge of which network elements and standards the solution supports can you be sure that your network can be fully discovered and controlled.

  1. What are the supported operating systems for the solution?
  2. What are the system requirements?
  3. Does the solution require any external data sources, such as inventory systems?
  4. What northbound and southbound protocols does the solution support?
  5. Does the solution support direct access to routers? If yes, how does it reach the routers?
  6. Does the solution support virtual router configurations that split one physical device into several virtual instances with different configurations?
  7. Does the solution support direct access to optical network elements? If yes, how are they reached?
  8. Provide a list of the supported optical network elements. Does this list include ROADMs, regenerators, amplifiers, and optical wavelength switches?
  9. Does the solution support T-API (Transport API)?
  10. How does the solution’s architecture support migration from legacy equipment, such as older EMS/NMS systems, to next-generation SDN Controller-based systems?
  11. Is new equipment necessary when new apps are added?

Armed with the above questions, service providers have a great foundation to assess IP/optical controllers from multiple software vendors. Requesting comprehensive and detailed answers will quickly expose any discrepancies between marketing claims and real capabilities, and will help to ensure a successful vendor selection and implementation process. 

Please contact us if you have questions or if you would like to learn more about Sedona’s NetFusion IP/Optical controller and how it compares with other vendor’s solutions.