Académique Documents
Professionnel Documents
Culture Documents
Table of Contents
Network management ............................................................................................................................ 2
Technologies ....................................................................................................................................... 2
Management information base .............................................................................................................. 2
Simple Network Management Protocol ................................................................................................. 3
Overview and basic concepts .......................................................................................................... 3
Protocol details................................................................................................................................ 4
Common Object Request Broker Architecture ....................................................................................... 6
COPS (Common Open Policy Service Protocol)....................................................................................... 8
Mobile IP ................................................................................................................................................. 8
Voice over IP ....................................................................................................................................... 9
Robust Header Compression .............................................................................................................. 9
Vasant Vohra
CSE-D
10315210183
Network management
Network management is the process of administering and managing computer networks.
Various services provided by this discipline include fault analysis, performance
management, provisioning of networks, maintaining the quality of service, and so on. Software
that enables network administrators to perform their functions is called network management
software.
Technologies
A small number of accessory methods exist to support network and network device
management. Network management allows individual IT professional to monitor over the
small network components within large network area.(EXTC VCET) Access methods include
the SNMP, command-line interface (CLI), custom XML, CMIP, Windows Management
Instrumentation (WMI), Transaction Language 1 (TL1), CORBA, NETCONF, and the Java
Management Extensions (JMX).
Schemas include the Structure of Management Information (SMI), WBEM, the Common
Information Model (CIM), and MTOSI amongst others
The seven SNMP PDU types as identified by the PDU-type field are as follows:
GetRequest
A manager-to-agent request to retrieve the value of a variable or list of variables. Desired
variables are specified in variable bindings (the value field is not used). Retrieval of the
specified variable values is to be done as an atomic operation by the agent. A Response with
current values is returned.
SetRequest
A manager-to-agent request to change the value of a variable or list of variables. Variable
bindings are specified in the body of the request. Changes to all specified variables are to be
made as an atomic operation by the agent. A Response with (current) new values for the
variables is returned.
GetNextRequest
A manager-to-agent request to discover available variables and their values. Returns
a Response with variable binding for the lexicographically next variable in the MIB. The entire
MIB of an agent can be walked by iterative application of GetNextRequest starting at OID 0.
Rows of a table can be read by specifying column OIDs in the variable bindings of the request.
GetBulkRequest
A manager-to-agent request for multiple iterations of GetNextRequest. An optimized version
of GetNextRequest. Returns a Response with multiple variable bindings walked from the
variable binding or bindings in the request. PDU specific non-repeaters and max-
repetitions fields are used to control response behavior. GetBulkRequest was introduced in
SNMPv2.
Response
Returns variable bindings and acknowledgement from agent to manager
for GetRequest, SetRequest, GetNextRequest, GetBulkRequest and InformRequest. Error
reporting is provided by error-status and error-index fields. Although it was used as a response
to both gets and sets, this PDU was called GetResponse in SNMPv1.
Trap
Asynchronous notification from agent to manager. While in other SNMP communication, the
manager actively requests information from the agent, these are PDUs that are sent from the
agent to the manager without being explicitly requested. SNMP traps enable an agent to notify
the management station of significant events by way of an unsolicited SNMP message. Trape
PDUs include current sysUpTime value, an OID identifying the type of trap and optional
variable bindings. Destination addressing for traps is determined in an application-specific
manner typically through trap configuration variables in the MIB. The format of the trap
message was changed in SNMPv2 and the PDU was renamed SNMPv2-Trap.
InformRequest
Acknowledged asynchronous notification. This PDU was introduced in SNMPv2 and was
originally defined as manager to manager communication. Later implementations have
loosened the original definition to allow agent to manager communications. Manager-to-
manager notifications were already possible in SNMPv1 (using a Trap), but as SNMP
commonly runs over UDP where delivery is not assured and dropped packets are not reported,
delivery of a Trap was not guaranteed. InformRequest fixes this by sending back an
acknowledgement on receipt.
Common Object Request Broker Architecture
The Common Object Request Broker Architecture (CORBA) is a standard defined by
the Object Management Group (OMG) designed to facilitate the communication of systems
that are deployed on diverse platforms. CORBA enables collaboration between systems on
different operating systems, programming languages, and computing hardware. CORBA uses
an object-oriented model although the systems that use the CORBA do not have to be object-
oriented. CORBA is an example of the distributed object paradigm.
Overview
CORBA enables communication between software written in different languages and running
on different computers. Implementation details from specific operating systems, programming
languages, and hardware platforms are all removed from the responsibility of developers who
use CORBA. CORBA normalizes the method-call semantics between application objects
residing either in the same address-space (application) or in remote address-spaces (same host,
or remote host on a network). Version 1.0 was released in October 1991.
CORBA uses an interface definition language (IDL) to specify the interfaces that objects
present to the outer world. CORBA then specifies a mapping from IDL to a specific
implementation language like C++ or Java. Standard mappings exist
for Ada, C, C++, C++11, COBOL, Java, Lisp, PL/I, Object
Pascal, Python, Ruby and Smalltalk. Non-standard mappings exist
for C#, Erlang, Perl, Tcl and Visual Basic implemented by object request brokers (ORBs)
written for those languages.
The CORBA specification dictates there shall be an ORB through which an application would
interact with other objects. This is how it is implemented in practice:
The application simply initializes the ORB, and accesses an internal Object Adapter, which
maintains things like reference counting, object (and reference) instantiation policies, and
object lifetime policies.
The Object Adapter is used to register instances of the generated code classes. Generated code
classes are the result of compiling the user IDL code, which translates the high-level interface
definition into an OS- and language-specific class base for use by the user application. This
step is necessary in order to enforce CORBA semantics and provide a clean user process for
interfacing with the CORBA infrastructure.
Some IDL mappings are more difficult to use than others. For example, due to the nature of
Java, the IDL-Java mapping is rather straightforward and makes usage of CORBA very simple
in a Java application. This is also true of the IDL to Python mapping. The C++ mapping
requires the programmer to learn datatypes that predate the C++ Standard Template
Library (STL). By contrast, the C++11 mapping is easier to use but requires heavy use of the
STL. Since the C language is not object-oriented, the IDL to C mapping requires a C
programmer to manually emulate object-oriented features.
In order to build a system that uses or implements a CORBA-based distributed object interface,
a developer must either obtain or write the IDL code that defines the object-oriented interface
to the logic the system will use or implement. Typically, an ORB implementation includes a
tool called an IDL compiler that translates the IDL interface into
the target language for use in that part of the system. A
traditional compiler then compiles the generated code to create
the linkable-object files for use in the application. This diagram
illustrates how the generated code is used within the CORBA
infrastructure:
COPS (Common Open Policy Service Protocol) is a proposed standard protocol for
exchanging network policy information between a policy decision point (PDP) in a network
and policy enforcement points (PEPs) as part of overall Quality of Service (QoS) - the
allocation of network traffic resources according to desired priorities of service. The policy
decision point might be a network server controlled directly by the network administrator who
enters policy statements about which kinds of traffic (voice, bulk data, video, teleconferencing,
and so forth) should get the highest priority. The policy enforcement points might be routers
or layer 3 switches that implement the policy choices as traffic moves through the network.
Currently, COPS is designed for use with the Resource Reservation Protocol (RSVP), which
lets you allocate traffic priorities in advance for temporary high-bandwidth requirements (for
example, video broadcasts or multicasts). It is possible that COPS will be extended to be a
general policy communications protocol
In operation, RSVP makes two determinations when an RSVP request arrives at a router
or layer 3 switch. First, it determines whether there are enough resources to satisfy
the bandwidth reservation request. If there are, RSVP determines whether the user is authorized
to make the reservation. The first determination is known as the admission control decision;
the second is known as the policy control decision. COPS allows the router or layer 3 switch
to communicate with the policy decision point about whether the request for the bandwidth
reservation should be permitted. Without COPS, all resources would be reserved on a first
come-first served basis only, and one or more requesters could easily take all the bandwidth.
The current COPS protocol is specified in an Internet-Draft working document of the Internet
Engineering Task Force (IETF).
Mobile IP
The Mobile IP allows for location-independent routing of IP datagrams on the Internet. Each
mobile node is identified by its home address disregarding its current location in the Internet.
While away from its home network, a mobile node is associated with a care-of address which
identifies its current location and its home address is associated with the local endpoint of a
tunnel to its home agent. Mobile IP specifies how a mobile node registers with its home agent
and how the home agent routes datagrams to the mobile node through the tunnel.
Applications
Virtual private network
A virtual private network (VPN) extends a private network across a public network, and
enables users to send and receive data across shared or public networks as if their computing
devices were directly connected to the private network. Applications running across the VPN
may therefore benefit from the functionality, security, and management of the private network
A VPN is created by establishing a virtual point-to-point connection through
the use of dedicated connections, virtual tunneling protocols,
or traffic encryption. A VPN available from the public Internet
can provide some of the benefits of a wide area
network (WAN). From a user perspective, the resources available
within the private network can be accessed remotely.
Voice over IP
Voice over Internet Protocol (also voice over IP, VoIP or IP telephony) is a methodology
and group of technologies for the delivery of voice communications and multimediasessions
over Internet Protocol (IP) networks, such as the Internet. The terms Internet
telephony, broadband telephony, and broadband phone service specifically refer to the
provisioning of communications services (voice, fax, SMS, voice-messaging) over the public
Internet, rather than via the public switched telephone network (PSTN).