15.12.2012 Views

deploying and managing ip over wdm networks - Index of

deploying and managing ip over wdm networks - Index of

deploying and managing ip over wdm networks - Index of

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

50 Deploying <strong>and</strong> Managing IP <strong>over</strong> WDM Networks<br />

IPNM references include recommendations from other bodies, as well as<br />

contributions from member partic<strong>ip</strong>ants. St<strong>and</strong>ard bodies <strong>and</strong> groups include<br />

ITU-T <strong>and</strong> ETSI, IETF, DMTF DEN. Other source documents are listed<br />

in [33].<br />

3.7 Summary<br />

In the conventional best-effort Internet, there is no network model due to the<br />

characteristic connectionless nature <strong>of</strong> such a network. Therefore we could say<br />

that the IP layer is element-level-management sensitive only. Nevertheless the<br />

deployment <strong>of</strong> MPLS in the IP network has changed that status. IP MPLSenabled<br />

<strong>networks</strong> can be characterized by a network model constituted by the<br />

end-to-end LSPs. These paths can be established under the control <strong>of</strong> a routing<br />

algorithm in the same manner as virtual paths in ATM <strong>networks</strong>. MPLS allows<br />

network administrators to specify the physical path that LSPs take across the<br />

network. More<strong>over</strong> these LSPs can be enforced to meet specific performance<br />

requirements <strong>and</strong> can be monitored during their life span. Therefore, this converts<br />

the IP MPLS-enabled network in a network-level manageable entity like<br />

any connection-oriented network.<br />

Conventional or up-to-date IP network management has been based on<br />

the facilities provided by the SNMP in the areas <strong>of</strong> performance (monitoring)<br />

<strong>and</strong> fault management, whereas configuration management was implemented<br />

by means <strong>of</strong> vendor-specific mechanisms. Management based on SNMP has<br />

been supported by several MIBs, one <strong>of</strong> whose more representative cases is the<br />

MIB-II. This MIB allows for performance management <strong>of</strong> network device interfaces<br />

as well as a very limited functionality in configuration <strong>and</strong> fault management.<br />

On the other h<strong>and</strong>, IP MPLS-enabled <strong>networks</strong> can also be managed<br />

through SNMP thanks to the support <strong>of</strong> several ad hoc defined MIBs. Among<br />

these we mention the MPLS-LDP-MIB, which is intended to manage the LDP,<br />

a protocol used for distributing the labels through the network. Also worthy <strong>of</strong><br />

mention is the MPLS-LSR-MIB <strong>and</strong> the MPLS-TE-MIB, both with functionality<br />

to carry out configuration <strong>and</strong> performance management <strong>of</strong> the LSPs. As an<br />

example <strong>of</strong> the usage <strong>of</strong> the MPLS-TE-MIB, we provide the implementation <strong>of</strong><br />

an API to configure LSPs, making use <strong>of</strong> all the functionality provided by the<br />

device vendor (Cisco in this case).<br />

PBNM has emerged as a new paradigm intended to abstract the service<br />

characteristics from the implementation details, thus allowing for the translation<br />

<strong>and</strong> mapping <strong>of</strong> application-level management statements to device-level management<br />

comm<strong>and</strong>s. Although not restricted to the IP world, PBNM has been<br />

growing in part thanks to the effort <strong>of</strong> the IETF. The IETF-RAP working group<br />

has developed a well-known framework specifying the functional elements <strong>of</strong> a

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!