deploying and managing ip over wdm networks - Index of

Recommendations

Info

240 Deploying and Managing IP over WDM Networks the paths before execution of the path setup command. However, they can easily establish new paths to avoid complicated path configurations. 12.4.3 NNI Signaling for Soft-Permanent Connection Setup and Tear Down The current NNI signaling specifications, developed within the project, utilize standards and specifications already available from other organizations or from previous internal documents and have been proposed to OIF as a contribution for the development of a standard NNI. Within the testbed, signaling messages are exchanged over a DCN, using an out-of-fiber approach. This network should not process the signaling messages sent between the OXCs. This could be achieved in different ways (e.g., by non-RSVP-capable DCN routers, by disabling RSVP protocol in the DCN routers, by utilizing NNI messages with the router alert flag disabled, by using an RSVP implementation on the DCN routers that do not process such messages, or by using tunneling techniques between the OXCs). Transport plane data interfaces are grouped into a bundled link. Both the bundled link and the component links are modeled as unnumbered interfaces according to [UNNUM] and [BUNDLE]. For soft-permanent connection, LSP setup is triggered by an NMS sending to the ingress node the appropriate information, such as source and destination node ID, port IDs, and payload type. The NMS could also specify an explicit route to the destination. Ingress node receives this parameter directly from NMS, whereas the egress node is provided with this information by NNI signaling messages. Last subobject of the explicit route object (ERO) in the PATH message is used for this purpose. It is loaded with the node identifier and the port ID to be connected to the client node. The teardown procedure is initiated by NMS, not independently by a node. Two different cases are possible: teardown commands sent to the source node or sent to the destination node. In both cases, NMS sends a message indicating the action to be performed (i.e., “Tear down soft-permanent LSP”) and the necessary parameters (i.e., “Sender address, LSP ID, and Tunnel ID”) to the involved node. When the source node receives such a message from NMS, it sends a PathTear message downstream towards the destination node that releases reserved resources as well as the setup cross connections along the way. If the destination node receives a “Tear down soft-permanent LSP” message from NMS, it sends a ResvTear message upstream towards the source node that releases the setup cross-connections along the way but not the reserved resources. When source node receives the ResvTear message, it will send a PathTear message to the destination node releasing the reserved resources.
At least two other possible solutions could be implemented: 1. Destination node can tear down the LSP and release the resources by a ResvTear message. 2. Destination node can request the source node to tear down the LSP and release the resources by a ResvTear message. In this case, a Resv- Tear message does not change the network state and both the cross connections and the resources will be released with the subsequent PathTear message. 12.4.4 Tests Carried Out Integration of IP over WDM: The LION Project Approach 241 The experimental activities that are being carried out in the testbed are focused basically on interworking aspects investigated in the project and divided mainly into three families of tests: ASON/GMPLS functionality, network resilience, and G.709 interfaces capability. The ASON/GMPLS experiments aim at demonstrating setup/tear down of soft-permanent connections in a multidomain and multivendor network by using NNI signaling. The assessment of both single-layer and multilayer resilience tests is allowed by FRR capability on the IP/MPLS layer and by protection and restoration mechanisms on the ASON/GMPLS layer; the interworking between layers is guaranteed by using hold-off timers on the client layer. Finally, the G.709 testing is focused on the analysis of the performance monitoring capabilities of these interfaces. References [1] ITU-T Recommendation G.8080, “Architecture for the Automatic Switched Optical Network (ASON),” Geneva, October 2001. [2] ITU-T Recommendation G.803, “Architecture of Transport Networks Based on the Synchronous Digital Hierarchy (SDH),” 1997. [3] ITU-T Recommendation G.872, “Architecture of Optical Transport Networks,” Draft 1.4, Geneva, November 2000. [4] National Bank of Poland, www.nbp.pl/statystyka/index.html, December 2002. [5] Bank PBK, www.bph.pl/index_fakty.html, December 2002. [6] Polish Offical Statistics, www.stat.gov.pl/english/index.htm, December 2002. [7] Maesschalck, S. D., et al., “Intelligent Optical Networking for Multilayer Survivability,” IEEE Communications Magazine, Vol. 40, No. 1, January 2002.
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: 190 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 265: Integration of IP over WDM: The LIO
Page 269 and 270: 13 Future Developments and Challeng
Page 271 and 272: Future Developments and Challenges
Page 291: Future Developments and Challenges
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?