Implementing Advanced AToM Features

Table of contents:

Review Questions

1

Which protocol is used for AToM pseudowire control channel signaling?

2

What are the three steps of AToM pseudowire setup between peer PE routers (assuming an LDP session has not yet been established between PE routers)?

3

An AToM data channel packet typically consists of which elements?

4

Can TDP be used to signal the tunnel LSP? Can TDP be used to signal AToMPW/VC labels?

5

If an AToM HDLC pseudowire is used to transport Frame Relay (Frame Relay port mode), in what way do PE routers participate in LMI?

6

How can Layer 2 traffic to be forwarded between attachment circuits on the same PE router?

   
7

What is one method of configuring RVSP-TE signaled tunnel LSPs to transport AToM pseudowires between PE routers?

8

When transporting ATM cells over an AToM cell relay pseudowire, how is it possible to transport more than one ATM cell per AToM data channel packet?

9

How is it possible to connect dissimilar attachment circuit types over AToM pseudowires?

10

What are the two modes of L2VPN interworking?


Part I: Understanding VPN Technology

What Is a Virtual Private Network?

Part II: Site-to-Site VPNs

Designing and Deploying L2TPv3-Based Layer 2 VPNs

Designing and Implementing AToM-Based Layer 2 VPNs

Designing MPLS Layer 3 Site-to-Site VPNs

Advanced MPLS Layer 3 VPN Deployment Considerations

Deploying Site-to-Site IPsec VPNs

Scaling and Optimizing IPsec VPNs

Part III: Remote Access VPNs

Designing and Implementing L2TPv2 and L2TPv3 Remote Access VPNs

Designing and Deploying IPsec Remote Access and Teleworker VPNs

Designing and Building SSL Remote Access VPNs (WebVPN)

Part IV: Appendixes

Designing and Building SSL Remote Access VPNs (WebVPN)

Appendix B. Answers to Review Questions



Comparing, Designing, and Deploying VPHs
Comparing, Designing, and Deploying VPNs
ISBN: 1587051796
EAN: 2147483647
Year: 2007
Pages: 124
Authors: Mark Lewis

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