deploying and managing ip over wdm networks - Index of

Recommendations

Info

142 Deploying and Managing IP over WDM Networks establish the connection. As a first step, when the connection entity is created in the system, its route is computed but no actions are performed in the network until the implementation stage. In case of a scarcity of resources, it may happen that a suitable route for satisfying the quality requirements of the connection request cannot be found. The provisioning manager of the INMS reacts to this situation by requesting the activation of new capacity. In an IP over WDM network, capacity is obtained by setting up a new optical path between two IP routers. The provisioning manager will create as many additional optical paths as are needed to satisfy the request quality constraints. While in the creation phase of a connection, the resources are logically reserved, though only in the WINMAN databases. In the implementation stage, all network elements are actually configured to support the service; however, it still cannot carry traffic. The final step of the provisioning process is the activation of the service, after which it becomes fully operational. The provisioning manager supports both step-by-step provisioning and single-request provisioning. It must be noted that typically all steps (creation, implementation, and activation) are done automatically after a single SMS/operator request. The deletion of a service requires traversing the same states in the opposite direction. The deactivation of the connection causes the cancellation of the services delivered over such a connection. Resources are then released both in the network elements and in the NMSs. Finally, all information about the connection is deleted. Modification of a service is done as a sequence of delete and provide operations and always causes service interruption. A more flexible approach, based on the survivability features that IP routers provide, is being considered. It should be noted that in the network provisioning processes of an ICS, more than one provisioning manager instance is involved. In fact, each of the INMS, IP-NMS, and WDM-NMS contains its own instance of the provisioning manager, derived with few modifications from the generic provisioning component. These different instances interact with each other in the described processes. For example, when the INMS provisioning manager decides that a new optical connection is required it delegates on the WDM-NMS provisioning manager, which then coordinates the activation of such a connection. The provisioning manager relies on the end-to-end routing component to support advanced features associated with a service. The provisioning manager receives the required features and transparently forwards them to the routing component, which is then responsible for considering those features while computing the route for the service. In this way, the system can be enhanced with new functionality without affecting the provisioning component. Authorization-support capabilities have been implemented through the policy manager validating all requests before proceeding to honor them. This
checking is done at the very beginning of the provisioning process to prevent further processing of requests that are unacceptable according to the userdefined policies or which are technically inconsistent. Finally, this component is able to receive notifications from lower level applications and to send them upwards to higher level applications, in order to keep synchronized the information about services and their states in all systems within the network management hierarchy. The CORBA notification service is used for this purpose. 8.3 End-to-End Routing Manager This component is in charge of calculating the route between the two end points of the connection [3]. When a provisioning request is received in the system, the end-to-end routing manager makes use of the network graph representing the current network topology to quickly find the most efficient route between two given end points. The necessary network topology information is retrieved from the network inventory manager. Route calculations are only requested by the provisioning manager component. The end-to-end routing manager can base its calculations on ad hoc policies. These policies, for example, can exclude certain links from routing calculations or give preference to others to find more efficient routes in terms of available bandwidth, hop count, economical cost, or even a combination of these factors. Figure 8.3 depicts the end-to-end routing manager context. Table 8.1 presents the main characteristics exhibited by the routing algorithm, explicitly showing those that are generic and those that are system specific. 8.4 NIM Management System Design and Implementation Issues 143 The NIM or inventory component is designed to have a full view of the network. Its responsibility is to know the different elements of the network, their roles, and their connections to other elements. The inventory component should have a full view of all of the subnetworks that the configuration module is managing. The inventory component roles are: • Maintain an updated and persistent view of the network; • Navigate on the network associations between networks and network elements; • Display the network tree view.
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: 92 Deploying and Managing IP over W
Page 126 and 127: 100 Deploying and Managing IP over
Page 165 and 166: 8 Management System Design and Impl
Page 167: Management System Design and Implem
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: Management System Design and Implem
Page 185: Management System Design and Implem
Page 218 and 219:
192 Deploying and Managing IP over
Page 220 and 221:
Page 222 and 223:
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 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
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 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
ClientCTP Integration of IP over WD
Page 257 and 258:
AstnTrail AstnTTP NL resource Integ
Page 259 and 260:
12.4.1.1 TILAB Equipment Integratio
Page 261 and 262:
12.4.1.3 Tellium Equipment Integrat
Page 263 and 264:
Page 265 and 266:
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 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
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

Create successful ePaper yourself

Delete template?

Save as template?