deploying and managing ip over wdm networks - Index of

Recommendations

Info

260 Deploying and Managing IP over WDM Networks can rapidly and flexibly provide existing services on demand as well as develop infrastructure for new value-added services inherent to the reconfigurable optical layer. This need inevitably leads to the development of a new network management model based on a CP that will form the bridge between the current management plane and the optical transport network itself [8]. Under this approach, GMPLS and optical UNI are considered the leaders for practical adoption. They both can be mapped into the ASON model, and they use the same underlying signaling protocols [9]. Furthermore, they have a close relationship with classical MPLS as well as common routing protocols. Hence, they are likely to become the standards for implementation of the optical CP. (See Section 5.3 for the description of GMPLS/ASON approaches.) The development of ASON, GMPLS, and optical-UNI standards is currently progressing at a steady pace, and some vendors have already implemented support of these technologies in their products. The advantages of ASON/GMPLS deployment encompass multiple areas of IP/WDM network management. Most of the important features of IP/WDM networking functionality extended by this deployment are compared with features of the existing functionality in Table 13.2. Automatic on-the-fly provisioning of intercarrier and multivendordomain services, flexible service selection, and dynamic resource allocation and restoration make the approach especially attractive. However, some challenges still exist on the way to further widespread deployment of this model. They belong to such areas as further development/finalization of the standards, persuading carriers to adopt IP technology in the CP, as well as deriving the same economic benefits carriers can get by implementing optical signaling technology. Table 13.2 Features of ASON/GMPLS–Based Networks Versus the Current IP/WDM Existing IP/WDM Networking ASON/GMPLS Deployment Vendor-specific service provisioning Intervendor service provisioning Semimanual nonreal-time domain-by-domain provisioning Real-time end-to-end provisioning on demand Poor information on resource and topology Full network inventory is maintained Billing by ports Billing by LSPs Protection only Link/path protection and dynamic restoration Manual configuration of domains Domains are advertised automatically
Future Developments and Challenges for IP over WDM Network Deployment 261 13.4.2 Possible Deployment Scenarios From a service provider perspective, a shift towards automatically switched optical network services and the development of functionality supporting these services are dependant on the possibility of integrating the optical CP with legacy management systems. Among other issues, this raises a question of allocating the functions between the CP and management plane (e.g., whether the management plane remains responsible for carrying out routing and link management or whether these functions as well as connection processing are done by the CP). The integration of automatically switched and currently deployed systems will be done both within different transport network layers and within transport network partitions (different vendor/carrier domains), as shown in Figure 13.9 and Figure 13.10 [10]. Consider a multivendor network whose administrative area consists of multiple control domains. Optical control plane integration can follow two steps. The first one represents a management-based solution with carrier-specific CPs directly coupled with the network management plane through necessary adaptations (Figure 13.9). While such an approach can be feasible for small-sized networks, its scalability is likely to be difficult, as multiple complex interfaces will be required for the integration when the network has expanded. Additionally, highly dynamic market business requirements make this model expensive to maintain. As the second step, a thin layer above multiple vendor control domains will be provided as mediation between the management plane and vendorspecific domains. This layer will represent a carrier-independent common CP Management plane administrative area Control domain 1 I - NNI Control plane administrative area Carrier-specific integrated control plane API API API I - NNI Control domain 2 Figure 13.9 Carrier-specific CP integration scenario. Control domain 3
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:
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: Evaluation of IP over WDM Managemen
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 285: Future Developments and Challenges
Page 291: Future Developments and Challenges
Page 294 and 295: 268 Deploying and Managing IP over
Page 303: About the Editors Joan Serrat recei
Page 314: 288 Deploying and Managing IP over
show all

deploying and managing ip over wdm networks - Index of

Create successful ePaper yourself

Delete template?

Save as template?