deploying and managing ip over wdm networks - Index of

Recommendations

Info

68 Deploying and Managing IP over WDM Networks • Spurious emission, which usually indicates a laser malfunction and may cause interference with other carriers; • Subsidiary optical carrier parameters (other optical parameters that may affect upon one or several main optical carrier parameters). 4.4.3.2 Signal Quality Supervision Methods The optical spectral analysis technique also has important limitations in its application to the performance management of all-optical transport networks. Its limitations stem from the fact that this method only monitors the optical carrier. Therefore, alternative supervision methods may be required in order to also monitor the optical signal quality itself (i.e., the quality of the modulated signal), while still conforming to the requirements for performance management. The optical modulated signal quality can be affected by several different optical parameters. Some of these parameters are essentially static in nature (i.e., their values change very slowly during the network’s life span). In these cases, the network is engineered so as to guarantee that these parameters fall within acceptable limits. In other cases, hardware countermeasures might be in place in the network to guarantee that the value of these parameters falls within acceptable limits [15, 16]. Nevertheless, in agreement with the third requirement given earlier, supervision of these parameters may be required as their value slowly drifts away (e.g., due to component aging). The relevant parameters affecting the signal quality are: • Dispersion, defined as the spreading of an optical pulse as it propagates along its path; • Crosstalk, which is an interference with the desired signal caused by a spurious signal falling at the same frequency of the signal; • Bit error counting, which consists of applying an error detection pattern to the payload in the transmitter side, which is sent as overhead to the receiver—this error detection pattern will allow the error counting at the receiver side; • Amplitude distribution of the optical signal, which produces a histogram of the distribution of the actual signal amplitudes corresponding to both the logical “one” and “zero” symbols. From the recorded histogram, it is possible to calculate an estimate for the BER of the transmission in a given path [17]. As with fault management in WDM, performance management is further complicated when multilayer networks are involved (e.g., SONET), thus requiring integration of the management functions.
4.4.4 Management Interfaces Management of the WDM Network Layer 69 WDM network elements are not tied to any particular management interface; this is also true for WDM element and network management systems. Possible interfaces may range from proprietary to standardized interfaces. This section will describe a set of frequently used standardized interfaces for managing WDM network elements. The main management interfaces competing on the network element layer are TL1, SNMP, and common management information protocol (CMIP). Also Telcordia’s OSMINE is used in networks as a means to communicate between the OSS and various types of network elements. Transaction language 1 (TL1) [18] is a text-based, command-line, telecommunications protocol for network element management, specified by Bellcore in 1986. A large number of technologies and vendors have network elements that are managed via TL1. General acceptance of TL1 was brought with the reliance of operators on Telcordia operation support system (OSSs) for interfacing with network elements. In today’s large OTNs, TL1 is the dominating protocol, as SNMP is for packet networks. SNMP is the IETF’s standardized network management interface and dominates the packet networks. While the majority of the WDM equipment vendors mainly offer a TL1 interface, some do also offer SNMP. However, limited security [19] is built into SNMP, and it is vulnerable to malicious individuals due to its inconsistent behavior when unexpected input is provided. The OSI network management model proposes a different approach than the one described earlier. Manager and agent communicate by means of the CMIP protocol [20, 21]. This is an alternative that offers richer functionality than TL1 but is more costly to deploy. Unlike TL1, CMIP and SNMP are both based on platform-centric manager-agent paradigms, each with a different information model. This is in contrast to TL1, which does not have any information model concept defined. Different from the previous models, the OSMINE [1] is a process that, according to Telcordia, integrates equipment manufacturer’s products with Telcordia OSSs. OSMINE, that is conforming the TL1 interface, gives network equipment interoperability with Telcordia OSS systems. Telcordia offers this process as a service to optical equipment vendors to certify the equipment. Because Telcordia is in a monopolistic position with the regional Bell operating companies (RBOCS), other vendors’ equipment must be made OSMINE compliant. OSMINE is an ongoing process because Telcordia is the single authority to determine the scope of work for OSMINE certification. Network element vendors that intend to deploy products at multiple service providers may be required to undergo OSMINE certification multiple times. Sometimes the EMS or NMS that come with a vendor’s network element must undergo OSMINE certification also. Moreover, when a new Telcordia OSS system is introduced
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: 18 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 93: Management of the WDM Network Layer
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 126 and 127: 100 Deploying and Managing IP over
Page 144 and 145:
118 Deploying and Managing IP over
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?