deploying and managing ip over wdm networks - Index of

Recommendations

Info

84 Deploying and Managing IP over WDM Networks In any case, the automatic provisioning of end-to-end IP services is still in a testing phase, as all of these proposals are still in an early stage. As standards are still under development, the interoperability of ONEs belonging to different manufactures is an open issue and is not foreseen to be solved in the coming future. It is obvious that one of the main reasons for these control plane frameworks is the acceleration of the connectivity provisioning. Nevertheless, this is not the case for some of the equipment vendors or telecom operators. Through their sophisticated management systems, they can perform a series of tasks in seconds covering the control plane functionality. In any case, there does not yet seem to be a great need for real-time optical channel provisioning besides grid applications [20], as networks are nowadays overprovisioned and capacity upgrade could be forecasted well in advance with right network planning activities. In addition, interoperability issues among management systems with incompatible or proprietary interfaces were a problem, but the CORBA architecture and open IDL management interfaces of element or network management systems towards the “umbrella” management system have overcome this problem. Finally, features of the control plane such as routing or protection could be integrated in the management systems and the cooperation of control and management plane could bring positive results. The fact that management systems are more mature and ready to offer in the short run services, especially in the optical domain, encourages such cooperation. 5.4 The Management Plane Approach The term management plane is used in the literature to refer to the set of near real-time mechanisms and algorithms related to the system as a whole and to the OAM. It deals mainly with the procedures related to five functional areas, FCAPS. Path provisioning with routing and QoS support in the configuration management area, and automatic recovery of failures or performance degradations in the fault and performance management areas, are the functions more related to the control plane functionality. Besides these three areas, accounting management is more than necessary for an operator planning to bill services such as automatic path setup and recovery. Network management functionality mainly exists independently for the IP-electrical world and the WDM-optical world, rather than for the integration of the two worlds. Chapters 3 and 4 have provided enough background on these technology-specific management systems. The next step in network management is aiming toward an integrated management of IP and WDM and other intermediate layers, if any. Such an intertechnology management solution is the main objective this book and will be briefly outlined here.
The proposed management solution is based on an overlay model, as routing is delegated in a two-layer mechanism. In fact, it is performed in an abstracted way in the integrated IP over WDM environment using only edge access points, and the detailed routing is performed inside the IP and WDM domains having all the internal details. Our management solution also identifies a management system for each technology (i.e., IP/MPLS and WDM accompanied by one intertechnology management system). The focus is on the INMS, the MPLS-capable-IP, and WDM management systems, as ATM and SDH and their integration have been dealt extensively in the past [21]. As far as management functional areas, our solution covers configuration, fault, and performance management, although only the first one is dealt with details in the successive chapters of this book. The work done by TMF will be used as a starting point with the appropriate extensions to support the IP technology. In addition, the WDM and IP NMS will be designed and implemented from scratch, following a technology-neutral internal architecture and providing in turn open interfaces towards the vendor-specific WDM and IP EMSs. The proposed management solution is foreseen only inside one administrative domain for competitive ISPs owning both IP and WDM equipment or for incumbent operator owning multilayer equipment. The main objective of the system is to offer MPLS connectivity services (LSPs), and, as a secondary objective, lambda services (OChs) could be provided to support the required LSPs. 5.5 Summary IP Over WDM Integration Mechanisms 85 Different encapsulation methods have been proposed for the smooth integration of IP over WDM. One such alternative is IP/ATM/SDH/WDM, where IP packets are segmented into ATM cells, which are in turn packet into an SDH frame and transmitted to the optical layer. Another approach considers IP/ATM/WDM, avoiding the SDH layer by means of an ATM cell-based physical layer. More recently, packet over SONET uses encapsulated IP packets that are framed into SDH formats, allowing for a stack like IP/SDH/WDM. Finally, IP over SDL over WDM and IP over GbE over WDM are the most advanced approaches to reach to goal of a simple IP/WDM stack. In fact, most trends in IP-WDM integration propose the removal of intermediate layers, such as ATM and SDH, and propose the direct interaction of the MPLS-capable IP with the optical layer through a thin adaptation layer. Today’s efforts in the telecom industry and the Internet community are characterized by the trend to automate the provisioning of connectivity in terms of OChs in the WDM layer or LSPs in the MPLS layer through the use of signaling protocols. The frameworks working in this direction are the ASON/ASTN
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: 34 Deploying and Managing IP over W
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 95 and 96: 4.4.4 Management Interfaces Managem
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: ASON/ASTN. ITU-T will try to push t
Page 113: IP Over WDM Integration Mechanisms
Page 126 and 127: 100 Deploying and Managing IP over
Page 160 and 161:
134 Deploying and Managing IP over
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:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
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?