deploying and managing ip over wdm networks - Index of

Recommendations

Info

128 Deploying and Managing IP over WDM Networks • CS. The CS is the basic service delivered by the IP-MPLS or WDM network and managed by WINMAN. The service is delivered either by the IP-MPLS network meeting some QoS goals, resembling a connection-oriented circuit, or by the WDM network. • EMS. The EMS represents the abstraction of the subnetworks managed by the technology-dependent management system. • Termination point (TP). A TP is a logical abstraction of an end point (actual or potential) of a topological (physical) link or a subnetwork connection. The TP is contained within a managed element (ME), an entity that is described later. • Physical termination point (PTP). A termination point that is an actual or potential end point of a topological (physical) link shall be abstracted as a PTP. Essentially, this is a representation of a physical port. • Connection termination point (CTP). A CTP is an actual or potential end point of a subnetwork connection. • Topological link. A topological link is a physical link between two PTPs. A topological link has a name and references to the two PTPs. A topological link reported by an EMS to a NMS will be between two MEs managed by the same EMS. Depending on the capabilities of the EMS and the MEs, the autodiscovery of topological links may or may not be allowed by the EMS. • Link connection. A link connection represents the transparent capacity of transfer information characterized by a given signal identification between two fixed points. • SNC. An SNC relates CTPs. An SNC provides a transparent end-toend connection through or within a subnetwork. The SNC may be created, deleted, or modified by the INMS or by domain-specific NMS and is implemented by means of one or several EMSs. The SNC is contained in the subnetwork. • Route. The route of a subnetwork connection shall be represented as an ordered series of CTP names through which the subnetwork connection traverses, including the working and the protection route. The protection route is optional. • ME. An ME is an abstraction used to represent network elements visible across the interfaces. 7.3.2 Mapping Between the Model Entities and the Managed Resources The WINMAN domain model is generic, thus providing an abstraction of the physical elements of the IP over WDM network by capturing in a uniform
The WINMAN System Architecture 129 representation the relevant attributes, for management purposes, of any network entity. While this abstraction enables technology-agnostic processing, it is based on a mapping that is specific for each of the three management levels considered in WINMAN. Table 7.1 summarizes this mapping. Table 7.1 Mapping of the Model Entities to Physical Resources Entity IP-NMS WDM-NMS INMS CS MPLS LSP between two end points of an IP subnetwork EMS IP-EMS and the IP subnetwork it manages Optical channel path between two end points of a WDM subnetwork WDM-EMS and the WDM subnetwork it manages MPLS LSP between two customer-facing end points; also referred as an ICS Not present TP PTPs and CTPs represent different resources PTP Router interface OXC or OADM port Router interfaces and OXC/OADM ports CTP FEC assigned to a LSP Wavelength at a OXC or OADM port Not used Topological link IP point-to-point link between two adjacent routers Fiber span between two adjacent OXCs/OADMs Link connection Not present Single channel of a WDM signal in a topological link SNC An LSP segment or an end-to-end LSP Route Sequence of IP router interfaces Path between any two WDM CTPs Sequence of port/ wavelength pairs Fiber span between a router and a OXC/OADM (interdomain link) Not present LSP between two end points of an IP network, or optical channel between two end points of a WDM network Sequence of IP router interfaces ME IP router OXC or OADM IP router (WDM network elements are not visible at this layer)
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 204 and 205:
178 Deploying and Managing IP over
Page 206 and 207:
Page 208 and 209:
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?