deploying and managing ip over wdm networks - Index of

Recommendations

Info

212 Deploying and Managing IP over WDM Networks 11.5.2 Experiment Results This section describes WINMAN system reaction observed while executing the experiments for functional and nonfunctional attributes. Evaluation of the experiment results against the required functionality for both functional and nonfunctional attributes is summarized in the tables hereafter. 11.5.2.1 Experiments Validating Functional Attributes All of the experiments defined in the previous section were completed successfully. 11.5.2.2 Experiments Validating Nonfunctional Attributes The experiments validating nonfunctional attributes were executed explicitly or implicitly. Modularity, flexibility, portability, and openness are nonfunctional attributes that are inherently supported by the WINMAN solution architecture and the core technologies that were used in order to implement it. The choice of using standard interfaces, like CaSMIM and MTNM, gives the WINMAN system the desired openness. Moreover, the WINMAN solution is implemented using Java programming language, which is highly platform independent. Additionally, the implementation is encapsulated in components that are provided by the component-based platforms that were employed—DSC and NETRAC. DSC uses CORBA middleware as the core communication mechanism between components, which brings along all of the valuable attributes of this technology. We can add components to the WINMAN solution imposing minimal alterations to the existing functional system in a time-efficient way for both development and integration. These new components can support new entities (applications, network nodes, new types of interfaces, and new functionality). These components can also replace malfunctioning components without affecting functionality that directly makes use of them. More specifically, the results from the experimentation regarding nonfunctional attributes are: • Portability. During execution of the experiments, we installed the DSC platform on a Solaris machine as well as on a Windows NT machine without any side effects on WINMAN overall behavior. Moreover, we managed to run the GUI smoothly from both UNIX and Windows machines. • Flexibility and modularity. During the experiments, we started, stopped, replaced, and recompiled several components (specifically, provisioning manager, routing, and the policy manager) without the need for rebuilding the entire WINMAN system.
Evaluation of IP over WDM Management Solutions 213 • Robustness and scalability. We did not stress the system to its limits because it is in the development phase, and some minor communication issues between components are still under investigation. Moreover, the autodiscovery of new network elements was not available, so it was impossible to create many network elements by means of an emulator. • Openness. To test that WINMAN is open to other, higher level management systems, we sent SMS commands using tcl/tk scripts [3]. The results were completely satisfactory. 11.5.2.3 Result Sheets The results of the experiments are summarized in Tables 11.3 and 11.4. Table 11.3 Results of the Functional Attributes Validation Experiment Status Result Comments Create optical path Executed Optical path between node-2 and node-3 was established. Create IP/MPLS path Executed IP/LSP path was established after removing the negative authorization policy. The experiment was executed using the DSC actors. The result was confirmed by observing the status of the specific equipment (the green LEDs were on) and the GUI. The process of setting up the path took up to 15 minutes, with all debugging features activated. The experiment was performed using the DSC actors. The result was confirmed by multimedia traffic. ICS provisioning Executed ICS was created. All of the correct steps involved in ICS creation were taken. However, they were performed as separate actions and not as one go. The initiation was performed through the WINMAN northbound interface. Network inventory consistency to its network infrastructure Executed Inventory was notified of newly created links and the GUI map was updated accordingly.
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: 162 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 237: 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 289 and 290:
Future Developments and Challenges
Page 291:
Future Developments and Challenges
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?