deploying and managing ip over wdm networks - Index of

Recommendations

Info

132 Deploying and Managing IP over WDM Networks Client/presentation side Middle tier/business logic side Server/persitency side GUI View manager provisioning processes. This is done in order to enable different rules and algorithms to be plugged into the system. 7.4.1.3 Server/Persistency Side This layer contains the persistency component and the database itself in order to keep the system database independent and to allow different persistence implementations such as relational databases, object databases, or file systems. In Figure 7.5, we can also observe that the WINMAN NMS communicates with its environment through four types of interfaces, as described hereafter. 7.4.2 The Northbound Interface Higher level applications Northbound interface Business logic Southbound interface Lower level applications Figure 7.5 The three-tier architecture of the NMS. This component is a generic interface to the northbound customer applications. This interface enables the WINMAN NMS to stay independent of the type of Persistency Data Metadata
customer application that wants to use and interact with it. This component gets the customer’s commands and requests using a well-known protocol and translates it to the actions inside the WINMAN NMS. From the other end, this interface receives all of the events from the WINMAN NMS and sends them northbound to the customer, using the same communication protocol. The customer of the northbound interface can be an external application like the SMS layer or another higher level NMS like the INMS, with respect to the WDM-NMS or IP-NMS. 7.4.3 The Southbound Interface This component is a generic interface to the NMSs. This interface enables the WINMAN NMS to stay independent of the type of network that it manages. This component gets the events from the EMSs or lower level NMSs using a well-known protocol and presents the events to the WINMAN components. From the other end, this interface gets queries and requests from the WINMAN modules and using the same communication protocol sends them to the EMSs or lower level NMSs. 7.4.4 The View Manager Interface The view manager is a component that links the WINMAN processes to the GUI, in order to keep the GUI as independent as possible from the process in the server/middle tier. This component will get all of the actions initiated by the WINMAN operator in the GUI and will forward them to the relevant component in WINMAN. On the other hand, all of the answers from the WINMAN components are translated by the view manager to a simple structure known by the GUI so that it can process and display the data without knowing the specific structure inside each of the WINMAN components. 7.4.5 The Persistence Layer Interface This interface is responsible of the persistency of the WINMAN data. It gets all of the data processed by the NMS components and stores it. At the same time, this component restores all of the relevant data (and, if needed, all of the relevant metadata) from the storages and brings it to the different components. This component enables the WINMAN solution to stay independent from the storage type, which can be any database or any file system (local or remote). 7.5 The GUI The WINMAN System Architecture 133 The WINMAN-integrated GUI acts as a general-purpose tool, which can be used for:
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 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 185: Management System Design and Implem
Page 208 and 209:
182 Deploying and Managing IP over
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

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

Delete template?

Save as template?