deploying and managing ip over wdm networks - Index of

230 Deploying and Managing IP over WDM Networks
In order to be able to associate an AstnTrail to a specific client, we have
introduced an object called ClientConnection, which provides end-to-end data
transport functionality between a pair of ASTN client-network elements.
The trail objects mentioned here are terminated by trail termination
points (TTPs); the connections are terminated by CTPs.
The AstnCrossConnection models the flexibility of the optical node and
can connect AstnCTPs with each other and with AstnTTPs.
Obviously, the CP and the transport plane are not completely independent
from each other. The trails configured via the CP (AstnTrails) will bind
resources in the transport network and should therefore be visible to the management
system of the transport network. This means that every time an
AstnTrail is set up in the CP (via soft-permanent or switched scheme), the corresponding
TNW trails and connections have to be created on the transport network
level.
More generally it can be said that each AstnTrail, AstnConnection, and
NniTrail object has a related transport network trail object in the respective
transport network MIB. This is modeled by a mutual pointer relationship
between these objects. By this means, which transport network resource supports
which CP resource can be easily deduced. This is important for finding the
root cause and to assess the impact of a failure in the transport network.
Figure 12.6 gives an overview on the structure of the LION information
model as a UML diagram [14]. This representation shows which managed
object is contained in which other managed object. The ControlPlaneNetwork
contains the ControlPlaneNetworkElements, AstnTrails, AstnConnections,
NniTrails, and ClientConnections described here.
The controlPlaneNetworkElement contains a UserNetworkInterface and
networkNodeInterface to model the UNI and the NNI. These objects contain
the AstnTTP and AstnTTP, where the intermediate objects describe multiplexing
and link bundling. The detailed structure is described in [7, 8]. Furthermore,
the ControlPlaneNetworkElement has a routingTable object which gives
the management system access to the routing table. The AstnFabric models the
switching fabric where the AstnCrossConnections are created. Figure 12.6
depicts further managed objects, which are related to control channel management
and are not described here.
For setting up a soft-permanent OLC, the management system calls a
method of the ControlPlaneNetworkElement called setupSoftpermanentOLC.
In the method call, parameters such as the source and sink of the required connection
UniPort objects have to be specified. In the case of multiplex capable
ports (e.g., WDM ports), the channel (e.g., the wavelength) to be used inside
the port also has to be specified. This information will then go into the creation
of the AstnTTP objects.