15.12.2012 Views

deploying and managing ip over wdm networks - Index of

deploying and managing ip over wdm networks - Index of

deploying and managing ip over wdm networks - Index of

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

48 Deploying <strong>and</strong> Managing IP <strong>over</strong> WDM Networks<br />

3.5.4 MPLS Tools<br />

Apart from these tools, the IETF working groups are proposing some MPLSspecific<br />

tools for monitoring <strong>and</strong> carrying out basic operations <strong>and</strong> maintenance<br />

(OAM) <strong>of</strong> MPLS-enabled <strong>networks</strong>. Most proposed diagnostic tools rely upon<br />

IP (e.g., the LSP ping [29] <strong>and</strong> the generic tunnel tracing [30]).<br />

3.5.4.1 LSP Ping<br />

LSP ping is a simple <strong>and</strong> efficient mechanism to detect or diagnose data plane<br />

failures in MPLS LSPs, specific to reservation protocol with traffic engineering<br />

extensions (RSVP-TE) <strong>networks</strong>.<br />

Ingress LSR sends ICMP echo_request messages <strong>over</strong> the LSP, which<br />

should be returned by the egress LSR. If after a defined time period ICMP messages<br />

are not returned, then ingress LSR sends a LSP-ping probe packet<br />

(RSVP-TE extension) to the egress LSR <strong>over</strong> the LSP under test. Egress LSR<br />

acknowledges rece<strong>ip</strong>t <strong>of</strong> the probe packet by returning the LSP_ECHO object<br />

in the RSVP Resv message back to the ingress LSR.<br />

If the ingress LSR does not receive a Resv message from the egress LSR<br />

that consists <strong>of</strong> an LSP_ECHO object within a period <strong>of</strong> time, it declares the<br />

LSP as down. At this point, the ingress LSR should apply the necessary procedures<br />

to fix the LSP. This may include generating a message to a networkmanagement<br />

console, tearing down <strong>and</strong> rebuilding the LSP, <strong>and</strong> rerouting user<br />

traffic to a backup LSP.<br />

3.5.4.2 Generic Tunnel Tracing<br />

This tool helps to reduce the time <strong>of</strong> detecting or diagnosing failures within a<br />

tunneled network. It solves some missing functionality in traditional traceroute<br />

comm<strong>and</strong>. Its main features are:<br />

• Trace path through generic tunnels (e.g., MPLS, IP-in-IP);<br />

• Support heterogeneous nested tunnels (e.g., IP-in-IP <strong>over</strong> MPLS);<br />

• Trace through forwarding plane or control plane.<br />

This tool requires a protocol that supports these applications. This<br />

protocol reveals the path between two points in an IP network. When access<br />

policy allows it, the protocol also reveals tunnel details, including type <strong>of</strong> tunnel.<br />

The protocol supports traceProbe <strong>and</strong> traceResponse messages carried <strong>over</strong><br />

UDP.<br />

Another interesting proposal for MPLS-OAM can be found in [31].

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!