deploying and managing ip over wdm networks - Index of

Recommendations

Info

140 Deploying and Managing IP over WDM Networks GUI XML Main component Supporting component Supporting service View manager Provisioning manager Each component will be individually described. Within each description we also present a UML diagram depicting the environment in which each component is operating, the interfaces that it supports towards the other components, and, if needed, the interfaces that are being used from other components. Finally, where the description of a given component of the generic NMS is complete and major enhancements or adaptations of the generic component are needed to fulfill the specific requirements of the INMS, the IP-NMS, or the WDM-NMS, these adaptations are described in separate subsections. The chapter is structured in 10 sections. Besides this introduction and the summary ending the chapter, a section is devoted to each of the eight NMS system components. 8.2 Provisioning Manager Higher level applications CaSMIM Northbound interface manager End- to- end routing manager Network inventory manager Southbound interface manager CaSMIM MTNM Lower level applications Figure 8.1 Detail of the WINMAN generic NMS architecture. Generic NMS Policy manager Timer service Database access and transaction service Directory and naming service Subsystem administration Event and notification service The process of provisioning new services or connections in communication networks tends to be complex and error prone. The large number and the variety of network elements involved, most often with different and sometimes conflicting capabilities, demands that special care be taken in all of the actions carried out to fulfill a provisioning request. The efficiency of this process can be improved if a single entity takes care of the coordination of all necessary activities. In WINMAN, the provisioning manager assumes this role.
Management System Design and Implementation Issues 141 The main function of the provisioning manager is hence to control the provisioning of connectivity services in the WINMAN-managed IP over WDM network. This component receives the requests issued from the WINMAN operator through the GUI or from the SMS application through the northbound interface and triggers, via the southbound interface, the required configuration actions on lower level applications to activate the services. According to Chapter 6, there can be three types of connectivity requests: provide ICS/CS, modify ICS/CS, and delete ICS/CS. These requests are passed to the provisioning manager using the proper operations defined in the TMF connection and service management information model (CaSMIM) interface [2], designed as a technology-agnostic interface suitable for its use between SMSs and network management systems, and between interdomain management systems and technology-specific management systems. As shown in Figure 8.2, separate interfaces have been defined for northbound requests from the SMS (INorthboundInterface) and for GUI requests from the WINMAN operator (IViewManager) to better cope with the specific characteristics of each type of request. However, the same information model has been adopted and the same set of functions is supported. Providing a connection means selecting the resources that will be allocated to that connection and configuring those resources in the network to physically IEndToEnd Routing IToPolicy Manager IPMSouthbound Interface IPolicy Manager Figure 8.2 The Provisioning manager context. INorthbound Interface Provisioning manager IView Manager IConnection ITreeView Object IInventory
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: 90 Deploying and Managing IP over W
Page 126 and 127: 100 Deploying and Managing IP over
Page 165: 8 Management System Design and Impl
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: Management System Design and Implem
Page 185: Management System Design and Implem
Page 216 and 217:
190 Deploying and Managing IP over
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?