deploying and managing ip over wdm networks - Index of

Recommendations

Info

148 Deploying and Managing IP over WDM Networks the entire WINMAN server as a single component. In this way, the GUI has one point of contact to the WINMAN server, regardless of the required functionality or the viewed domain. As shown in Figure 8.6, the view manager has a published interface with generic operations that allow the GUI to retrieve data from the server, update the data in the server when the operator entered data manually, and start a provisioning process by creating an object. These operations allow the GUI to interface with the inventory, the provisioning manager and the policy manager without knowing in which specific system they are. Another important role of the view manager is to unify the object structure. The GUI uses a flat object that has only one level of hierarchy, while the WINMAN server uses nested objects. The view manager gets the WINMAN objects (flat ones) from the GUI, recreates the nested structure, and sends them to the WINMAN server components, and vice versa. The view manager gets the nested objects from the inventory and creates the flat WINMAN objects for the GUI. In order to keep these two mapping mechanisms (mapping to the server components and mapping the server-nested objects) and allow them to be Provisioning Manager: IViewManager Figure 8.6 The view manager interfaces. IViewManager ViewManager IPolicyManager IInventory
Management System Design and Implementation Issues 149 augmented without any code changes, the view manager uses extended markup language (XML) files to describe them. There are two types of files: 1. Input files. Mapping the GUI request to the server-related component. It maps the GUI flat object to the server-nested objects. 2. Output files. Mapping the server response to the GUI. It maps the server-nested object to the GUI flat object. In order to allow the GUI to connect to the IP-NMS and to the WDM-NMS, there is a view manager component for each domain. However, these components are identical. There are no changes of behavior between the IP view manager and the WDM view manager. In the same way, the view manager component is an independent component and can be connected to any other domain type. At the INMS level, the view manager has another role; if the request from the GUI needs to be forwarded to the technology-dependent inventories, it communicates directly to the INMS southbound interface for retrieving the data. This behavior is also defined in the XML mapping files, and therefore the INMS view manager component can be the same as in the IP and WDM systems. 8.7 Northbound Interface Manager A focus point of the WINMAN architecture is to provide NMSs in multivendor and multitechnology environments. This goal is attained by having multiple instances of NMS systems, one for every different domain managed by the WINMAN solution. In order to provide access to network services in a technology-agnostic style, the functionality of each domain-specific NMS is accessed through the INMS system. In order to have a simple implementation of such a design, the communication between each of the various cross-domain managers (IP-NMS and WDM-NMS for the current implementation) must be based on a generic interface that provides isolation from the specifics of each technology. This interface is implemented by the northbound interface manager (NIM) component. The primary role of the northbound interface is to provide a single entry point to clients that wish to gain access to the services provided by the NMS in a way that is independent of the underlying technologies. These requirements are in line with concept of the TMF CaSMIM standard [2]. The CaSMIM is a set of CORBA interfaces that enables the user to provide connection services across diverse technologies. The implementation of the NIM component exports a CORBA set of interfaces that implement the
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: 98 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 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: for any of the three WINMAN NMSs. T
Page 185: Management System Design and Implem
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:
268 Deploying and Managing IP over
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

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

Delete template?

Save as template?