deploying and managing ip over wdm networks - Index of

Recommendations

Info

196 Deploying and Managing IP over WDM Networks EMS Factory MLSNW_gr Factory ME proxy ME proxy routers has been developed according to an API whose example is provided in Section 3.3. 10.5 Summary MIB to ME ME proxy From NMS TMF --MTNM Interface TMF- -MTNM Interface TMF -MTNM Interface Façade objects ME proxy Notification dispatcher Not_Disp. interface TMF - MTNM classes (generated by IDL ) Supporting classes (including information model) ME classes Figure 10.6 Structure of WDM-EMS adaptation. HTML generator Routing algorithm Routing algorithm Java+CORBA i/f for Java + Corba HTML HTML HTML page page page From Web browser GUI classes The deployment of an IP over WDM network testbed is instrumental for the validation of the WINMAN integrated management system. Initially, a set of requirements is classified, looking at the management equipment, the testing and verification tools, and the involved transport network infrastructures. The general characteristics of the management platforms to be supplied by the testbed are divided into high-level requirements and functional requirements. High-level requirements are intended to make possible the basic interaction between the NMSs and the managed network. One of these requirements is, for instance, referring to the interconnectability between the testbed and the WINMAN system. On the other hand, the functional requirements refer to the
Testbed Setup for the Evaluation of IP over WDM Management Systems 197 functions that the testbed, and particularly the EMSs, have to exhibit in order to check the management functionality of the NMS prototypes in the three management functional areas for which it has been conceived (i.e., to allow configuration, fault, and performance management). The IP layer of the testbed consists of three MPLS-enabled routers linking three LAN sites. Also belonging to the IP part is the EMS responsible to manage the earlier mentioned routers and the traffic analyzers. Likewise, the WDM testbed consists of a hub and three remote nodes, connected via a two-fiber, counter-rotating ring. On the outer fiber ring, three dedicated wavelengths are used for communication between the hub and the remote nodes, while on the inner fiber ring, each node is provided with a programmable OADM to set up wavelength paths with the other remote nodes or with the hub. Moreover, the WDM part also contains a network element agent per optical node that is connected via RS-232 to the EMS controlling the four agents. Cajun switches that are also part of the WDM testbed provide GbE interfaces. These devices are used to interconnect the routers to the optical nodes because they have GBICs operating at specific wavelengths, thus becoming adapted to the wavelengths needed in the ring. Although the available EMSs provide the management functionality specified for the testbed, they do not support in principle the interface with the NMSs under test. Therefore, an adaptation layer between native testbed platforms and the WINMAN southbound interface is to be introduced. Adaptation of both the WDM-EMS and the IP-EMS is based on international standards and, especially, on the TMF-MTNM interface for EMS to NMS interconnection. References [1] Awduche, D., et al. “Multi-Protocol Lambda Switching: Combining MPLS Traffic Engineering Control With Optical Cross-connects,” draft-awduche-mpls-te-optical-04.txt, April 2002. [2] Nadeau, T., et al., “Multiprotocol Label Switching (MPLS) Management Overview,” draft-ietf-mpls-mgmt-overview-02.txt, work in progress, expires December 2002. [3] Anderson, J., et al., “Protocols and Architectures for Optical Networking,” Bell Labs Technical Journal, January–March 1999, pp. 105–123. [4] Chlamtac, I., A. Ganz, and G. Karmi, “Purely Optical Networks for Terabit Communication,” IEEE INFOCOM, 1989. [5] Strand, J., A. L. Chiu, and R. Tkach, “Issues For Routing In The Optical Layer,” IEEE Communications Magazine, February 2001, pp. 81–87. [6] “High Bandwidth Optical WAN’s,” IEEE Transactions on Communications, July 1992, pp. 1171–1181.
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:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
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 and 176: Management System Design and Implem
Page 185: Management System Design and Implem
Page 188 and 189: 162 Deploying and Managing IP over
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 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 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:
Future Developments and Challenges
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?