deploying and managing ip over wdm networks - Index of

Recommendations

Info

42 Deploying and Managing IP over WDM Networks 3.3.3.3 Example of SNMP-Based MPLS Management: A Generic Object-Oriented MPLS-TE Application Programming Interface The example refers to an implementation of MPLS-TE management using SNMP and Java language [9]. The application programming interface (API) uses a generic SNMP Java implementation and builds its functionality from an object-oriented information model of the devices’ configuration (depicted in Figure 3.4). Even though the actual implementation is being used with Cisco routers, it is generic enough to accommodate other vendors’ equipment because the specific parts are template based. Minimum changes are needed to work with different equipment. The MPLS-TE API is able to configure MPLS LSPs with all the functionality provided by the vendors’ equipment. The configuration class abstracts the configuration information (a text file in the case of Cisco routers). This class has several attributes of classes that provide further detail about the configuration; in particular the tunnel class contains the attributes for a given MPLS tunnel configured in a device. The configuration class is generic, not tailored to any vendor. A specialization is needed when parsing the configuration file and writing configuration information to the device. A template with the appropriate vendor’s syntax is used to generate the configuration file that is downloaded to the device by TFTP. Configuration Device: String transaction: String Configuration () addTunnel () activateTunnel () deA ctivateTunnel () delTunnel () addSRoute () delSRoute () addERoute () delERoute () toStrings() 1 +rest 1 OtherConfigPar 1 1 +tunnels 0..n Figure 3.4 MPLS-TE API model. Tunnel Device: String = null tunnelID: String= null routeID: String= null deleted: boolean = false active : boolean = false tunnelString : String= null tunnelTemplate : String= null Tunnel () Tunnel () Tunnel () toStrings () main () 1 +tDescriptors 0..n Fec TrafficDescriptor name: String + StaticRoute tunnelID: String deleted: boolean = false sRouteStrings : String StaticRoute () StaticRoute () StaticRoute () toStrings () +destination _IP +origin _IP +sRoute IP_ address address : String mask : String IP_ address () 1 +fec +e Route [] +QoSAttributes QoSAttributes bandwidth: String = null priority : String = null 0..n 1..n PathOption type : String = null ename: String = null PathOption () 0..n 1 ExpRoute routeID : String deleted : boolean = false eRouteStrings : String eRouteTemplate: String Exp Route () Exp Route () Exp Route () toStrings ()
Another remarkable characteristic of the API is the implementation of the concept of transactions: a configuration change is done completely or it is not done at all. We achieve this goal by transferring the complete configuration file to the device and replacing the active configuration by this new file. The whole process is controlled using a proprietary Cisco MIB for device configuration [10, 11]. This API is extensible to every aspect of the router configuration. This can be achieved by extension of the configuration class and the corresponding templates. A multivendor implementation would need specific templates for each vendor. The method for extending the API is to specialize the class OtherConfigPar, which at the moment contains everything but the MPLS-TE tunnels configuration. The API supports the whole range of SNMP traps and can capture and parse them in order to notify the exception condition to any management system using the API. Performance management functionality is currently under development and is based on standard SNMP meters and the proprietary CISCO- RTTMON-MIB [12] that enables the measurement of one-way delay (synchronization needed), round trip delay, and jitter. More information about this MIB usage can be read at [13]. 3.3.4 Management of MPLS VPNs Based on the successful deployment of the previously mentioned BGP/MPLS model for IP VPNs, many vendors are providing management software for this application. These applications are inherently multivendor because the model is a standard implemented by several IP equipment providers. These tools are mainly centered on performance and configuration management, and they enable service providers to deploy VPN services on their MPLS-enabled backbones. Examples of these tools can be found in the Web sites of major vendors like Cisco [14] and Juniper [15], and some software companies like Orchestream [16] and WANDL [17], among others. Also, a MIB for modeling MPLS/border gateway protocol (BGP) VPN management has been published by the IETF [18]. 3.4 Policy-Based Management Management of the IP Network Layer 43 The aim of policy based network management (PBNM) is to make reality a vertical integration among network-element management, network management, and application management. In fact, PBNM provides a way to abstract the
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 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 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 118 and 119:
92 Deploying and Managing IP over W
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:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?