deploying and managing ip over wdm networks - Index of

Recommendations

Info

174 Deploying and Managing IP over WDM Networks 9.6.2 SNMP The simplicity of SNMP has been a major factor in its success leading to a rapid adoption by manufacturers and a huge base of agreed MIB definitions. There are a number of sophisticated products such as HP OpenView (e.g., network node manager), which offer powerful facilities for the management of SNMPbased networks. From a user’s point of view, SNMP offers the benefit of wide industry support and comparative cheapness. However, SNMP suffers from a number of deficiencies: • The protocol is very inefficient when large quantities of information have to be retrieved from a managed system. • There is poor support for event-driven management. • There is, in effect, no security. The last point is the most serious one, and it reduces SNMP to a monitoring rather than a management protocol. SNMPv2 was intended to remedy the principal deficiencies of SNMP and be largely backwards compatible with it. Unfortunately the adoption of SNMPv2 and later versions has not been widespread. 9.6.3 The WINMAN Implementation The WINMAN interface specification is written entirely in CORBA IDL and the component-specification language (CSL) used by the DSC framework. The CSL is based on the CORBA component model specification. The DSC CSL is the language used to describe the components that client objects call and object implementations provide. A CSL component provides the information needed to develop clients that use the component’s operations. Clients are not written in CSL, which is purely a descriptive language, but in languages for which mappings from CSL concepts have been defined—for the WINMAN implementation, this is Java. The CSL can specify static compound components and list per subcomponent which of its interfaces are to be exported. Per component, it lists generated and accepted notifications, exported and required interfaces, and component properties. Also, the CSL lists per interface generated and accepted notifications and interface-specific properties. Supported interfaces can be specified to be dynamic or static. 9.7 Connectivity Interface Protocols There is a broad spectrum of communication protocols available for conveying management information. One of the oldest is SNMP. As already pointed out,
the simplicity of SNMP has been a major factor in its success but this same simplicity was also one of the reasons for needing a more robust management protocol. Therefore, a protocol stack based on CMIP and common management information service element (CMISE) was specified. Although these protocols provide a good method for describing the management information, there was no large penetration of the market. A good alternative between these extremes is CORBA. It provides both a safe environment and is far less complex then CMIP/CMISE. Alternatives like XML (which is seen by some as the successor for CORBA IDL) were not taken into account, as these alternatives are not yet mature and still have to prove their value as management protocols. 9.7.1 Connection and Service Management Information Model Today’s telecommunications world is dealing with all types of services. This situation has led to a business approach of a quick and easy service creation, taking into account the impact of network faults on services and having visibility of the problems on several layers. These goals led to the creation of the CaSMIM approach.The CaSMIM goal is to create a standard model to automate service provisioning and end-to-end monitoring across multitechnology, multivendor, and multilayered networks. This involves translation of service requests issued by the SMS into network connection provisioning actions. Another goal is to be service oriented but technology independent, and so be flexible to cater for connectivity setup across networks using current and future technologies. Figure 9.4 shows the CaSMIM protocol between network layers. CaSMIM sees its usage in the following scenarios: • Service provisioning. This is for automatic provisioning of service whatever the underlying technology implied. • Service assurance. This is to be used to export the visibility of a given network layer and to show the impact of a given network failure on the service. 9.7.2 Multitechnology Network Management Technologies and Tools 175 The objective of the MTNM specification is to detail, with the usage of UML, the interface between entities that reside in the NML with entities of the EML. The successful fulfillment of the above goal provides for a scalable and nonproprietary network management solution, where multivendor, multitechnology (ATM, SONET/SDH, WDM) management systems interoperate in an open architecture. Examples of the management business scenarios that the MTNM
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: 124 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 249 and 250: Integration of IP over WDM: The LIO
Page 251 and 252:
Integration of IP over WDM: The LIO
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?