Ping and Traceroute for GMPLS LSPs in Non-Packet Switched Networks draft-ali-ccamp-gmpls-lsp-ping-traceroute-00.txt Zafar Ali, Cisco Systems T. Otani(KDDI R - PowerPoint PPT Presentation

Loading...

PPT – Ping and Traceroute for GMPLS LSPs in Non-Packet Switched Networks draft-ali-ccamp-gmpls-lsp-ping-traceroute-00.txt Zafar Ali, Cisco Systems T. Otani(KDDI R PowerPoint presentation | free to download - id: 1e60c1-ZDc1Z



Loading


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation
Title:

Ping and Traceroute for GMPLS LSPs in Non-Packet Switched Networks draft-ali-ccamp-gmpls-lsp-ping-traceroute-00.txt Zafar Ali, Cisco Systems T. Otani(KDDI R

Description:

MPLS traceroute displays an entire tunnel as a single MPLS hop. Route taken by GMPLS LSP cannot be traced using MPLS Traceroute. ... – PowerPoint PPT presentation

Number of Views:121
Avg rating:3.0/5.0
Slides: 15
Provided by: cis957
Learn more at: http://www.ietf.org
Category:

less

Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: Ping and Traceroute for GMPLS LSPs in Non-Packet Switched Networks draft-ali-ccamp-gmpls-lsp-ping-traceroute-00.txt Zafar Ali, Cisco Systems T. Otani(KDDI R


1
Ping and Traceroute for GMPLS LSPs in Non-Packet
Switched Networks draft-ali-ccamp-gmpls-lsp-ping
-traceroute-00.txt Zafar Ali, Cisco
Systems T. Otani(KDDI RD Laboratories, Inc.)
2
Outline
  • Scope of the Draft
  • Applicability of MPLS OAM to GMPLS
  • GMPLS OAM Solutions Proposed in this draft
  • Next Steps

3
Scope of the Draft
  • The document is particularly applicable to data
    plane technologies where the data plane does not
    otherwise provide the OAM functions.
  • Use of OAM functionality provided by the data
    planes is RECOMMENDED and procedures described in
    this draft are only assumed to be applied when
    OAM mechanisms are not supported by the data
    plane or are deficient.
  • The draft addresses some GMPLS OAM requirements
    stated in the draft-ietf-ccamp-gmpls-oam-requireme
    nts-00.txt

4
Outline
  • Scope of the Draft
  • Applicability of MPLS OAM to GMPLS
  • GMPLS OAM Solutions Proposed in this draft
  • Next Steps

5
MPLS Ping over a GMPLS tunnel
  • GMPLS FA appears as single hop in MPLS LSP Ping/
    Traceroute.
  • Failures can be localized to a GMPLS tunnel, but
    cannot be localize to which leg of the GMPLS LSP
    is broken.
  • This limited coverage also requires LSP
    end-points to be PSC.

O4
O2
1
O3
1
R3
R6
O1
O5
R5
Optical Region
R4
R2
R1
R7
R8
R0
  • Ability to Ping LSP with non-PSC endpoints is a
    requirement.
  • Ability to detected which leg of GMPLS LSP is
    broken is a requirement.

6
MPLS Traceroute Over a GMPLS Tunnel
  • MPLS traceroute displays an entire tunnel as a
    single MPLS hop
  • Route taken by GMPLS LSP cannot be traced using
    MPLS Traceroute.
  • This limited coverage also requires LSP
    end-points to be PSC.

O4
O2
1
O3
R3
R6
O1
O5
R5
Optical Region
R4
R2
R7
R1
R8
R0
Mechanism to trace GMPLS LSPs is a Requirement.
7
Outline
  • Scope of the Draft
  • Applicability of MPLS OAM to GMPLS
  • GMPLS OAM Solutions Proposed in this draft
  • Next Steps

8
Use of LMP Link Verification for GMPLS LSP Ping
LMP
LMP
LMP
None-PSC Node2
PXC1
PXC2
None-PSC Node1
9
Challenges in Tracing GMPLS LSP
Control Network (IP-based)
...
...
R1
R2
PXC1
PXC2
  • Control network and data network topologies are
    completely independent of each other.
  • PXC1 is one hop away from R1 in data plane, but
    two hops away in control plane.
  • PXC2 is two hops away from R1 in data plane, but
    one hop away in control plane.
  • We cannot just simply use LSP Ping in the control
    network/ plane to trace GMPLS LSP.

Solution for tracing GMPLS tunnel route needs to
be developed
10
Sending Echo Request Packets via GRE or IP-in-IP
tunnel
Control Network (IP-based)
MPLS Echo Response
...
...
R1
R2
PXC1
PXC2
  • Use of GRE or IP-in-IP encapsulation of MPLS
    Echo request messages.
  • MPLS echo request is a labeled as IPv4 or IPv6
    UDP packet.

11
Tracerouting GMPLS LSP
  1. The Ingress (Egress) LSR finds optical nodes that
    are one hop away in data plane. This can be done
    using control plane state of the LSP being
    traced.
  2. The Ingress (Egress) LSR sends MPLS echo Request
    packet with TTL1 and encapsulates it using GRE
    to the node that it finds in Step 1.
  3. Receiver node examines the FEC contained in the
    MPLS Echo request, and sends an echo reply back
    to the ingress (Egress) LSR if it has a
    crossconnect for the FEC under test. The node
    also returns the control plane address of the
    next hop node in the echo reply.
  4. Upon receiving the Echo reply, Ingress (Egress)
    nodes prepares a Echo Request packet with TTL 1
    and encapsulates it using GRE to the node that it
    learned via Echo reply in step 3.
  5. The Ingress (Egress) LSR repeats the same
    procedure for nodes that it learns from step 4
    until it learns destination (source) node and
    repeats step 4 for destination (source) node.

12
Outline
  • Scope of the Draft
  • Applicability of MPLS OAM to GMPLS
  • GMPLS OAM Solutions Proposed in this draft
  • Next Steps

13
Next Steps
  • This work is within CCAMP Charter.
  • The draft addresses some GMPLS OAM requirements
    stated in the draft-ietf-ccamp-gmpls-oam-requireme
    nts-00.txt.
  • We already received some comments on and off the
    list. We need to address these comments.
  • One of the comments is to divide this draft into
    two
  • One for applicability of LMP for GMPLS LSP Ping,
  • The other for GMPLS tracerouting.
  • At this point we are looking for more feedback
    and next steps for this work.

14
  • Thank You.
About PowerShow.com