deploying and managing ip over wdm networks - Index of

Recommendations

Info

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.
AstnTrail AstnTTP NL resource Integration of IP over WDM: The LION Project Approach 231 Subnetwork 0..1 0..* 1 ControlPlaneNetwork 1..* NniControlChannel 1 1 1 1 1 1 0..* 1 1 1..* UniControlChannel UniLink 0..* AstnTrail 1..* ControlPlaneNetworkElement 0..* 1 1 UserNetworkInterface 0..* NniTrail 0..* 0..* ClientConnection AstnConnection 0..* ClientNetworkElement 1..* 1 1 0..* ClientCTP UniCControlChannelTP NEL resource 1 1..* NetworkNodeInterface 1 AstnFabric 1..* 1 1 1 RoutingTable UniTeLinkTP 1..* 1 0..* NniTeLinkTP 0..* UniControlChannelTP 1 1..n AstnCrossConnection NniControlChannelTP 1 1..* UniPort 1 0..* AstnTTP 1 1..* NniTTP 1 0..* AstnCTP Figure 12.6 Overview on the resources of the ASTN information model (draft version). Second, as an optional parameter, the operator may specify some or even all intermediate hops the path should take. This is done by specifying a group of outgoing ports. Then the routing protocol may decide which port (and channel) inside this group will be used for the connection. Furthermore, the required switching type of the connection has to be given, as the nodes (and ports) may support more than one switching type. Also the required encoding type of the optical layer connection has to be specified in the setup request. This is needed to check whether the involved ports support the required encoding type of the OLC. This check should be done by the management system. Finally, in the setup request the management system gives its identifier in a parameter called activatorId. This parameter will go into an attribute of the AstnTrail, to be able to distinguish soft-permanent connections from switched connections. Our requirement that permanent, switched, and soft-permanent connections may coexist has several implications. First, the trail object must carry the information about its ownership, and rules have to be defined regarding who is allowed to access the resource in which way (e.g., get information, modify, or tear down an OLC). 1
Page 3 and 4:
Deploying and Managing IP over WDM
Page 5 and 6:
Deploying and Managing IP over WDM
Page 7 and 8:
Contents Foreword xv Preface xix Ac
Page 9 and 10:
Contents vii 4.2 The WDM Network El
Page 11 and 12:
Contents ix 8 Management System Des
Page 13 and 14:
Contents xi 10.3 The WINMAN Testbed
Page 15:
Contents xiii 13.4.1 Adoption of Op
Page 18 and 19:
xvi Deploying and Managing IP over
Page 21 and 22:
Preface The integration of the Inte
Page 23:
Coauthors of the IST-OPTIMIST proje
Page 27 and 28:
1 Introduction 1.1 The Importance o
Page 29 and 30:
communications. These legacy networ
Page 31:
Within these programs, consortia of
Page 34 and 35:
8 Deploying and Managing IP over WD
Page 36 and 37:
10 Deploying and Managing IP over W
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 81 and 82:
4 Management of the WDM Network Lay
Page 83 and 84:
λ1λ 2 ··· λ w λ1λ 2 ···
Page 85 and 86:
Management of the WDM Network Layer
Page 87 and 88:
• Lightpaths that may be protecte
Page 89 and 90:
• Wavelength continuity. Two conn
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
4.4.4 Management Interfaces Managem
Page 97 and 98:
Page 99 and 100:
5 IP Over WDM Integration Mechanism
Page 101 and 102:
STM1/ATM interface requirements. Fo
Page 103 and 104:
IP router OLA The version of IP ove
Page 105 and 106:
Gigabit Ethernet interface GbE prov
Page 107 and 108:
the IETF extended the MPLambdaS fra
Page 109 and 110:
ASON/ASTN. ITU-T will try to push t
Page 111 and 112:
The proposed management solution is
Page 113:
IP Over WDM Integration Mechanisms
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
100 Deploying and Managing IP over
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 165 and 166:
8 Management System Design and Impl
Page 167 and 168:
Management System Design and Implem
Page 169 and 170:
checking is done at the very beginn
Page 171 and 172:
8.4.1 The Inventory Model The inven
Page 173 and 174:
for any of the three WINMAN NMSs. T
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207: 180 Deploying and Managing IP over
Page 225 and 226: 11 Evaluation of IP over WDM Manage
Page 227 and 228: Evaluation of IP over WDM Managemen
Page 229 and 230: system will still perform without i
Page 241 and 242: 11.5.3.1 General Remarks The manage
Page 243 and 244: 12 Integration of IP over WDM: The
Page 245 and 246: domains with different management t
Page 247 and 248: Integration of IP over WDM: The LIO
Page 255: ClientCTP Integration of IP over WD
Page 259 and 260: 12.4.1.1 TILAB Equipment Integratio
Page 261 and 262: 12.4.1.3 Tellium Equipment Integrat
Page 267 and 268: At least two other possible solutio
Page 269 and 270: 13 Future Developments and Challeng
Page 271 and 272: Future Developments and Challenges
Page 291: Future Developments and Challenges
Page 303: About the Editors Joan Serrat recei
Page 306 and 307:
Page 308 and 309:
Page 310 and 311:
Page 312 and 313:
Page 314:
show all

deploying and managing ip over wdm networks - Index of

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

Delete template?

Save as template?