deploying and managing ip over wdm networks - Index of

Recommendations

Info

116 Deploying and Managing IP over WDM Networks (including addition and removal of network elements) by the WINMAN operator. This interaction is done through the appropriate graphical user interface (GUI) representations of the current network configuration map. • Add IP node and delete IP node UCs. The add IP node and the delete IP node UCs are used by the configure network UC when new IP nodes need to be added or deleted to or from the WINMAN system, respectively. • Add WDM node and delete WDM node UCs. These UCs create or delete a WDM node by adding or removing it in the WINMAN inventory. • Add WDM link and delete WDM link UCs. These UCs create or delete a WDM link entity in the WINMAN inventory. • Modify WDM link UC. This UC modifies the characteristics of a WDM link in the WINMAN inventory. • Add EMS and delete EMS UCs. These UC are intended to modify the network configuration (updating the WINMAN inventory) by adding or removing EMS information through an established communication link at the WINMAN southbound interface. 6.4.2.5 NM&R The NM&R UCs support the WINMAN fault management functionality. This refers to the processing of alarm notifications and to the execution of actions triggered by such alarm processing. The WINMAN operator is the actor intended to acknowledge or clear alarms. Figure 6.11 depicts the NM&R UCs considered by WINMAN. The NM&R UCs are: • Recover network UC. This UC is used for rerouting all connections, bypassing faulty parts of the network. • Revert network UC. This UC comes back to the original routing status, as it was before the recover network UC invocation. • Open alarm UC. This UC handles alarms issued by an EMS, by an internal WINMAN application like the performance management, or by the topology manager when the network element status is changed. • Clear alarm UC. This UC clears an alarm and removes it from the list of active alarms. • Provide alarm reports UC. This UC creates reports based on selected attributes carried on the alarm notifications.
SMS (from actors) WINMAN operator (from actors) IP EMS (from actors) WDM EMS (from actors) Figure 6.11 NM&R UCs. The WINMAN Management System Concept 117 Provide alarm reports (from "included " use cases) Open alarm (from "included " use cases) Clear alarm (from "included " use cases) Revert network (from "included " use cases) Recover network (from "included " use cases) Synchronize alarms (from "included " use cases) Acknowledge alarm (from "included" use cases) Configure network (from "included " use cases) Identify affected connection (from "included " use cases) Identify root cause (from "included " use cases) Execute policy (from "included " use cases) • Identify affected connections UC. This UC finds all active connections affected by a given alarm. • Identify root cause UC. This UC identifies the root or primary cause in a set of alarms. • Synchronize alarms UC. This UC queries the EMSs for their open alarms for resynchronization of the active alarms in the WINMAN system. As a consequence of the execution of this UC, the alarms reflected in the WINMAN system will be the same as those existing in the corresponding EMS. • Acknowledge alarm UC. This UC changes the status of an alarm to the acknowledged status. 6.4.2.6 Network Data Management The network data management (NDM) UCs incorporate the functionality intended for performance management. These are the UCs providing means to collect and analyze performance data. The operator can request reports and configure the way WINMAN collects performance information. The configuration
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: Management of the WDM Network Layer
Page 95 and 96: 4.4.4 Management Interfaces Managem
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 192 and 193:
166 Deploying and Managing IP over
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
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

Create successful ePaper yourself

Delete template?

Save as template?