deploying and managing ip over wdm networks - Index of

Recommendations

Info

234 Deploying and Managing IP over WDM Networks transponder cards, which adapt the client signal to the transport layer. Two different kinds of tributary ports are available: 2R transponders, digitally transparent up to 2.5 Gbps, and 3R transponders with G.709 framing (digital wrapper) for client signals up to 2.5 Gbps. All of the equipment has been realized in a previous project and has been enhanced adding the G.709 interfaces and ASON/GMPLS CP and NNI signaling. In particular, the CP being developed for the OXC is in line with the ITU-T Rec. G.8080 from which it differs for the absence of minor functionalities not related to the project objectives (i.e., mechanisms of authentication and encryption and the traffic-policing component). A more detailed description of the CP architecture is matter of a following paragraph. 12.4.1.2 SICN Equipment TransXpress OSN managed optical distribution frame (MODIF)/OXC is the Siemens OXC platform based on microelectromechanic systems (MEMS) technology. The OXC is embedded in the MODIF. The combined TransXpress OSN MODIF/OXC concept grants an easier, faster, and manageable configuration, commissioning, and provisioning of OXCs. The core component of the TransXpress OSN MODIF/OXC solution is the OXC. It is embedded physically together with the MODIF in one system. The OXC is (like the MODIF) a transparent system, which can be used in any type of network architecture. It is bit-rate and protocol transparent and is adequate for all kind of optical signals in the 1.3 and 1.5-µm wavelength range, such as SDH/SONET, ATM, IP, and Ethernet signals, at any bit rate. The OXC switches the optical signals with the aid of optical mirrors based on MEMS. The MEMS-based switches are high-speed, low-loss optical switches (micromechanic mirrors) on silicon chips. The switching of the OXC is controlled by an ASON controller. The ASON controller provides a SNMP interface to the TMN. A second management interface (Q3) makes it possible to manage the OXC directly without ASON functionality with the help of a local craft terminal (LCT). Siemens provides two TransXpress OSN MODIF/OXCs, which are both configured as transparent OXCs. Each OXC has a 16 × 16-switching matrix and provides two line interfaces with three single-fiber channels each. For connecting clients, two tributary interfaces are available. The tributary interfaces are equipped with separate 2R transponders. Because the whole testbed is located in a single room, additional optical amplifiers are not necessary and are not being provided. Instead of WDM equipment, multiple fiber connections are used between the OXCs for the same reason. Additionally, for each fiber connected to an OXC, a loss of signal detector is provided that alarms a loss of signal to the ASON controller of the OXC.
12.4.1.3 Tellium Equipment Integration of IP over WDM: The LION Project Approach 235 The Aurora 128 is a smaller version of Tellium’s Aurora optical switch and supports 320 Gbps of bidirectional traffic for an equivalent of 128 2.5-Gbps ports or 32 10-Gbps ports. It has the same five different shelf types as the Aurora optical switch and is housed in two EIA-standard 7-ft bays. The Aurora 128 bay configuration contains one TR bay and one receiver (SR) bay. The Aurora switches support two types of transceivers over single mode fiber: 2.5 Gbps and 10 Gbps. Both transceivers meet SONET SR specifications and can be configured in SONET or SDH format, in either channelized or concatenated mode. The Aurora switches utilize wideband receivers (1,280 nm to 1,600 nm) and standard transmit lasers on all transceivers, making wavelength translation extremely flexible and simple. The STM-16 transmitter (TR) output at 1,310 nm, and the STM-64 TRs output at 1,550 nm. The Aurora 128 has a strictly nonblocking 128 × 128 three-stage CLOS matrix at 2.5-Gbps granularity. The entire matrix is implemented using four FTS and four MSS modules. The working and protection switch matrixes on the Aurora 128 are located in the same switch matrix shelf. The Aurora switches provide equipment-protection switching: the working switch matrix is 1+1 protected by a protection switch matrix. The ingress transceiver bridges the incoming signals to both the working and protection switch matrixes. The two signals are independently switched and arrive at the egress transceivers. The egress transceiver selects the better of the two signals. Network Protection Recovery at the optical layer is fundamental to the effective design and utilization of today’s high-availability core network. Optical recovery is by far the fastest recovery technology; typically, recovery at the IP layer is several orders of magnitude slower than optical layer recovery. The Aurora switches handle multiplex section protection (MSP) on the client (access) side and mesh restoration schemes via emerging standards (utilizing unused and unassigned SONET/SDH overhead bytes) on the network side. Intelligence is built into the switches to perform subsecond restoration. Connection priorities are also built into the mesh restoration algorithms. Protection switching performance depends on the protection-switching algorithm that is being used. On the access side, Aurora switches support MSP based on G.841 (or 1+1 per GR-253-CORE) for 50-ms restoration times. On the network side, Aurora switches support StarNet dedicated mesh protection (1+1 with route diversity) for 50-ms restoration time and StarNet shared mesh restoration with a restoration objective of less than 200 ms. • StarNet dedicated mesh protection for both equipment and network protection. StarNet dedicated mesh protection implements path-based 1+1
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: 184 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: 12.4.1.1 TILAB Equipment Integratio
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 291: Future Developments and Challenges
Page 303: About the Editors Joan Serrat recei
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?