Creating LSPs and Tunnels Using an NMS


The detailed steps we've described for creating LSPs and tunnels are manual in nature. An NMS would substantially reduce the workload involved in creating these objects. We now describe a possible workflow for both cases:

  1. Open a topology map containing the MPLS nodes in Figure 8-2.

  2. Click on the two edge nodes, selecting each as a connection endpoint.

  3. Select the connection type (LSP or tunnel).

  4. If the tunnel type is selected, then the GUI should allow the creation of an ERO.

  5. Optionally request a path computation (trivial in Figure 8-2 but more difficult when hundreds, thousands, or even hundreds of thousands of nodes are involved) between the two end nodes.

  6. Select the required resources (bandwidth, maximum burst size, etc.).

  7. View the computed path and modify it if necessary.

  8. Accept the path and send the connection for provisioning

At this point, all the necessary MIB tables are updated by NMS provisioning software. For the case of the tunnel, just the ingress node (Edge Router 1) MIB needs to be updated, with the remainder being signaled. For the LSP, if no signaling is used, then the NMS provisioning code must painstakingly update the MIBs of all the nodes in the path (Edge Router 1, Core Router 1, and Edge Router 2). Finally, the NMS should then report on the success or failure of the overall operation. Beyond this, the NMS should then start to manage the created connections as owned objectsobjects that it created. This differentiates between connections provisioned using the EMS (i.e., outside the NMS, using the CLI) rather than the NMS.



Network Management, MIBs and MPLS
Network Management, MIBs and MPLS: Principles, Design and Implementation
ISBN: 0131011138
EAN: 2147483647
Year: 2003
Pages: 150

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net