deploying and managing ip over wdm networks - Index of

Recommendations

Info

228 Deploying and Managing IP over WDM Networks coexist with permanent setup schemes. We will later show how this can be achieved by our approach. The approach described earlier allows vendors to reuse implementations of management functionality already developed. For network operators, the advantage is that the management functionality can be aligned to well-known procedures of existing transport networks, and hence the need to adapt the operational processes can be minimized. The next section describes the information model developed in LION for ASTN management. This description will show how the separation of ASTN management and transport network management works practically and how it influences the design of the ASTN information model. 12.3.3 Management Information Model A management information model in general describes all information and functionality needed to manage the network. It consists of a structured set of managed objects. The managed objects represent a software abstraction of the resources to be managed and carry the management information and functionality. For ASTNs, the main focus of management functionality is configuration and supervision of OLCs. All further management functionality is in effect important only for supporting this task. For this reason, the most important aspect of the information model is to be able to represent, from a management point of view, the OLC and its supporting resources that reside in the network element. The management interfaces specified for existing transport networks with their different technologies [9–11] are (more or less directly) derived from a technology-independent interface specification called M.3100 [12]. This recommendation describes objects such as a trail (which represents the supervised end-to-end connectivity) and connections (which model the individual sections making up the trail). As M.3100 is a widely accepted basis for the modeling of connection-oriented networks, we have based the design of our ASTN information model on M.3100. In Figure 12.5, the most important managed objects are depicted. This figure shows what the conceptual split into transport and CP means. As can be seen from the figure, an ASTN-enabled optical node is considered to be composed by a CP network element (CpNE) and a transport network element (TnwNE). Regarding networks, the overall network is considered to be made up of a CP network and a transport network. The ASTN information model (highlighted in Figure 12.5 by the shaded area) only comprises resources that are part of the CP network (with other words that are directly linked to the CpNE).
ClientCTP Integration of IP over WDM: The LION Project Approach 229 ClientNE ClientNE CpNE TnwNE AstnTTP AstnCTP AstnConnection NniTTP NniTrail Transport network trail Transport network connection Terminating transport network TTP with switching capability (e.g., OchTTP) ClientConnection AstnTrail TnwNE From an operational perspective, the most important resource in the ASTN network is the end-to-end connectivity in the ASTN. Following M.3100, we call this resource AstnTrail. The AstnTrail represents a switched or soft-permanent monitored OLC. In other words, it provides end-to-end data transport functionality between a pair of TnwNEs controlled by CpNEs and supervision of the quality and integrity of the signal (e.g., by mechanisms of end-to-end connectivity and continuity supervision of the CP such as LMP [13]). An AstnTrail is made up of several AstnConnections. An AstnConnection provides data transport functionality and NNI signal transport functionality between a pair of TnwNEs controlled by CpNEs. Switched or soft-permanent OLCs (AstnTrails) are made up from several AstnConnections. Each AstnConnection object has a related transport network connection object in the respective transport network MIB. The NniTrail provides monitored data transport functionality between a pair of TnwNEs controlled by CpNEs. In contrast to the related transport network trail object, the supervision is done on a per link basis using ASTN mechanisms such as those provided (e.g., by LMP [13]) rather than the trail monitoring mechanisms of the transport layer. A NniTrail acts as a server for one or more AstnConnections. CpNE AstnCrossConnection Transport network CTP with switching capability (e.g., OchCTP) Figure 12.5 Overview on transport and CP managed resources. CpNE TnwNE ASTN information model Transport NW. information model TnwNE/CpNE: Transport network/control plane network element
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: 178 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 253: Integration of IP over WDM: The LIO
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 291: Future Developments and Challenges
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

Create successful ePaper yourself

Delete template?

Save as template?