DSwT tunnel auto provisioning (TAP)
...................................................................................................................................................................................................................................
Introduction
Provisioning all the entries in the routing tables of all the nodes can be a considerable
effort and is error prone, particularly when networks comprise hundreds of nodes. It
would be desirable to have a mechanism which reduces some of the necessary
provisioning to alleviate this problem. Such a mechanism has been designed. It is a
Lucent Technologies proprietary mechanism called
tunnel auto provisioning (TAP).
TAP principle
The principle behind TAP is that IP routes known by DSwT nodes at the edge of the
OSI network are advertised across the OSI network to the other DSwT nodes which
can then insert these routes into their own routing tables.
This basic principle is illustrated in the following figure:
Example of two DSwT nodes advertising the IP networks they can reach. Each node
learns the others advertised routes it hears and places them in its routing table.
Notice that the advertising node is not limited to giving one IP prefix but could
provide a list of all the IP prefixes it can reach, if appropriate, each one resulting in a
routing table entry.
120.40.10.0/24
Destination
CLPN-Tunnel
Subnetwork
NSAP(A)
Node
Next Hop
120.40.20.0/24
Destination
CLPN-Tunnel
Subnetwork
NSAP(B)
Node
Next Hop
Routing Table in A
Routing Table in B
NSAP A
120.40.10.0/24
NSAP B
120.40.20.0/24
CLNP Subnetwork
"I am NSAP(B). I can
reach
IP prefix
120.40.20.0 / 24"
"I am NSAP(A). I can
reach IP prefix
120.40.10.0 / 24"
"If
I want to reach
120.40.20.0 / 24, then
I send to NSAP(B)"
"If I want to reach
120.40.10.0 / 24, then
I send to NSAP(A)"
Management communication setup concepts
...................................................................................................................................................................................................................................
365-312-875R5.2
Issue 1, March 2007
Chia sẻ với bạn bè của bạn: