deploying and managing ip over wdm networks - Index of

Recommendations

Info

176 Deploying and Managing IP over WDM Networks (i) Simple network (ii) Complex network SMS DM specification caters for are: inventory discovery, connection provisioning, equipment provisioning, and performance management. The MTNM specification consists of the documents referenced as [3–5]. The [5] contains an implementation of the specified interface using the IDL notation of CORBA, while [3] defines the problem, requirements and use cases that the MTNM specification solves and [4] contains the information model that is used in order to represent the managing network. 9.7.3 The WINMAN Implementation CaSMIM Figure 9.4 The CaSMIM protocol between network layers. SMS To achieve vendor- and technology-independent NML-EML communication, the WINMAN system followed the MTNM specification. Although the adoption of this specification means that the WDM technology domain is covered, as it is inherently supported by the MTNM, the WINMAN system also requires IP domain communication functionality. This problem was solved, in a consistent manner to the specification, utilizing the existing generic fields and operations in order to pass IP-specific information, without requiring any major modifications. This successful application of the MTNM specification to the IP technology domain, which was not considered by the TMF, qualifies the correctness of our choice. The CaSMIM interface was used for implementing the interfaces between the IP NMS and the WDM NMS to the INMS and further between the INMS and the SMS. The WINMAN NMSs northbound component implemented the DM
CaSMIM protocol and thus created a public interface between the WINMAN system and the SMS. 9.8 Databases When associations among files or records cannot be expressed by links, relational databases are used; a simple flat list becomes one row of a table, or relation, and multiple relations can be mathematically associated to yield desired information. The user must have an understanding of how data is structured within the database in order to retrieve, insert, update, or delete records. However, it is much simpler to understand than hierarchical models, and it provides extremely useful tools for database administration. On the other hand, object-oriented databases store and manipulate more complex data structures, called objects, which are organized into hierarchical classes that may inherit properties from higher classes in the chain; this database structure is the most flexible and adaptable. 9.8.1 The WINMAN Implementation WINMAN used a relational database because this is the state of the art as used in the network management industry. Because our software used an objectoriented data model, we had to do an object-to-relational mapping. The methodology we used is the simplest that maps each object to a table, each structure or list to a table, and each parent/abstract object to a table. This was done to enable the retrieval of the basic (and most often queried) information stored in the abstract objects in one database query. 9.9 User Interface Tools The term user interface refers to the methods and devices that are used to accommodate interaction between machines and the human beings who use them (users). Among the properties of the GUIs are intuitiveness, consistency, simplicity, prevention, forgiveness, and aesthetics. 9.9.1 Hypertext Markup Language Technologies and Tools 177 HTML was introduced in the mid 1980s as a subset of standard generalized markup language (SGML). SGML was a metalanguage defined by IBM in the early 1970s as a method for describing text and documents that were not specific to any device or application. Based on this concept, W3C originally introduced HTML as a presentation mechanism for hypertext documents exchanged
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:
Page 126 and 127:
100 Deploying and Managing IP over
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153: 126 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 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 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 253 and 254:
Integration of IP over WDM: The LIO
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?