deploying and managing ip over wdm networks - Index of

Recommendations

Info

150 Deploying and Managing IP over WDM Networks CaSMIM standard. The incoming CaSMIM calls are then translated by the interface component into technology-specific method invocations that are compatible with the current NMS system. The interfaces of CaSMIM are organized in a set of profiles. The methods are grouped in these sets according to the functionality they provide. The profiles currently defined are the following: • Basic. The basic profile must be supported by all conforming implementations. It specifies the basic functionality that is needed for providing connectivity and connection handling. • Performance. The performance profile is optionally available only in conjunction with the fine grain profile, but clients may gain significant performance improvements when using it. • Monitor. The monitor profile is required for clients who desire realtime monitoring of the health or status of connections. • Topology. The topology profile is provided by implementations that expose information about their supporting subnetworks or network element implementations. • Customer. The customer profile includes support for handling customer-related information on connections. This can be useful for establishing links to customer service OSSs. However, the information is not used for actual connection management. • Schedule. The schedule profile includes information and operations for implementations offering scheduling and historical records. • Fine grain. The fine grain profile represents connections, links, access groups, and terminations as CORBA objects, in addition to their representation as second-class objects (coarse grain model). • Completion. The completion profile gathers functions that are typically not included in other profiles. To claim conformance to the completion profile, all other profiles except the fine grain profile have to be supported. For the current implementation of the NIM, a subset of the aforementioned profiles was used: the basic, customer, monitor, and topology. Moreover, the implementation contains methods from the classes listed in Table 8.2. All of the interfaces listed in Table 8.2 are subclassed by Casmim::Subnetwork. This means that the northbound manager, as it is depicted in Figure 8.7, implements part of the methods defined in this interface.
Management System Design and Implementation Issues 151 Table 8.2 CaSMIM Interfaces Used in the NIM Casmim::AccessGroup2 Casmim::AdministeredObject2 Casmim::Connection2 Casmim::ManagedObject2 Casmim::Link2 Casmim::Subnetwork2 Casmim::Termination2 ITreeViewObject Subnetwork Figure 8.7 The northbound manager context. NorthBoundManager IInventory IConnection INorthboundInterface The current implementation also supports receiving and sending of notifications through the Common::Notification::Generator and the Common::Notification::GeneratorFactory interfaces. According to the standard [2], there can be two ways of implementing the CaSMIM interface—the fine grain and the coarse grain approach. In the first, each network element in the system is represented by a discrete CORBA object. While this approach is straightforward in its implementation, it results in a large performance overhead because all of the representations of network elements must be mapped in the memory regardless of whether they are currently used or not. In the coarse grain approach, currently used in WINMAN, each object is represented by a unique CaSMIM identifier. While this approach provides
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 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 175: Management System Design and Implem
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

Create successful ePaper yourself

Delete template?

Save as template?