ASSIGNMENT #3

CSE-884 ATM
NETWORKS

SUBMITTED TO: SUBMITTED BY:

Mr. Yashpal Harjindar Singh
B.Tech(Hons) CSE
5050070024
ROE115A48
Q2. Why is there 3-way Handshaking in establishment of a point-to-
point SVC in ATM while call release involves 2-way Handshaking?
Ans. Point-to-Point Connection

When an ATM-aware process seeks to connect to another process

elsewhere on the network, it asks the signaling software to establish an
SVC. To do this, the signaling software sends an SVC creation request to
the ATM switch using the ATM adapter and the reserved signaling VC.
Each ATM switch forwards the request to another switch until the request
reaches its destination. An ATM switch determines which switch to send
the request to next based on the ATM address for the connection and the
switch's internal network database (routing tables). Each switch also
determines whether or not the request's service category and Quality of
Service needs can be met. At any point in this process, a switch can
refuse the request.

If all the switches along the path can support the virtual circuit as
requested, the destination endstation receives a packet that contains the
VC number. From that point on, the ATM-aware process can
communicate with the destination process directly by sending packets to
the VPI/VCI that identify the specified VC.

The ATM adapter shapes data traffic for each VC to match the contract
made with the ATM network. If too much data is sent for any reason, the
ATM switch can ignore — and lose — the data in favor of providing
bandwidth to another contract or set of contracts. This is true for the
entire breadth of the network; if bandwidth or speed exceeds the limits
established by the contract, any device, including the ATM adapter, can
simply drop the data. If this happens, the endstations concerned are not
notified of the cell loss.

Call establishment messages: such as CALL PROCEEDING, sent by the

called user to the network or by the network to the calling user to indicate
initiation of the requested call. CONNECT, sent by the called user to the
network and by the network to the calling user to indicate that the called
user accepted the call. CONNECT ACKNOWLEDGE, sent by the
network to the called user to indicate that the call was awarded and by the
calling user to the network. And SETUP, sent by the calling user to the
network and by the network to the calling user to initiate a call.
Call clearing messages: such as RELEASE, sent by the user to request
that the network clear the connection or sent by the network to indicate
that the connection has cleared. RELEASE COMPLETE, sent by either
the user or the network to indicate that the originator has released the call
reference and virtual channel. RESTART, sent by the user or the network
to restart the indicated virtual channel. RESTART ACKNOWLEDGE,
sent to acknowledge the receipt of the RESTART message.

Q3. How a party is added and dropped in a Point-to-Multipoint

connection?
Ans. Point-to-Multipoint messages: such as ADD PARTY, adds a party
to an existing connection. ADD PARTY ACKNOWLEDGE,
acknowledges a successful ADD PARTY. ADD PARTY REJECT,
indicates an unsuccessful ADD PARTY. DROP PARTY, drops a party
from an existing point-to-multipoint connection. DROP PARTY
ACKNOWLEDGE, acknowledges a successful DROP PARTY.

Q5. What are the three functions with the help of which Routing is
accomplished? Discuss Address summarization.
Ans. Routing signals using NI-DAQmx
The NI-DAQmx driver has the ability to implicity route signals from one
device or task to another. (See KnowledgeBase 4B0LUTAC: Internally
Routing Counter Signals in LabVIEW.) You can also explicitly route
signals in NI-DAQmx using the following two techniques:

For LabVIEW developers, you can accomplish explicit signal routing by

using DAQmx Export Signal.vi or DAQmx Connect Terminals.vi and
DAQmx Disconnect Terminals.vi. (See KnowledgeBase 2XSA43RY:
What is the Difference Between the DAQmx Export Signal VI and the
DAQmx Connect/Disconnect Terminals VIs?)

For text-based developers, you can use the DAQmxExportSignal or the

DAQmxConnectTerms and DAQmxDisconnectTerms functions to
accomplish explicit signal routing.

Routing signals using Traditional (Legacy) NI-DAQ

For LabVIEW developers, you can use Route Signal.vi and Counter Set
Attribute.vi to accomplish routing. See the following LabVIEW code
snippet.
Route Summarization

As the result of corporate expansion and mergers, the number of subnets

and network addresses in routing tables is increasing rapidly. This growth
taxes CPU resources, memory, and bandwidth used to maintain the
routing table. Route summarization and CIDR techniques can manage
this corporate growth much like Internet growth has been managed. With
a thorough understanding of route summarization and CIDR, you can
implement a scalable network. This section describes summarization;
CIDR is covered in the later section "Classless Interdomain Routing."
The relationship between summarization and VLSM is also examined.
With VLSM, you break a block of addresses into smaller subnets; in
route summarization, a group of subnets is rolled up into a summarized
routing table entry.

Q6. What are various Security management functions done in OSI

Management framework?

Ans. The 5 areas of function of the model

The OSI network management model categorizes five areas of function,

sometimes referred to as the FCAPS model:

Fault

The goal of fault management is to recognize, isolate, correct and log

faults that occur in the network.

Errors primarily occur in the areas of fault management and configuration

management.

Fault management is concerned with detecting network faults, logging

this information, contacting the appropriate person, and ultimately fixing
a problem. A common fault management technique is to implement an
SNMP-based network management system - such as HP OpenView or
Sun Solstice (formerly Net Manager) - to collect information about
network devices. In turn, the management station can be configured to
make a network administrator aware of problems (by email, paging, or
on-screen messages), allowing appropriate action to be taken.
Configuration

The goals of configuration management are to gather/set/track

configurations of the devices. Configuration management is concerned
with monitoring system configuration information, and any changes that
take place. This area is especially important, since many network issues
arise as a direct result of changes made to configuration files, updated
software versions, or changes to system hardware. A proper configuration
management strategy involves tracking all changes made to network
hardware and software. Examples include altering the running
configuration of a device, updating the IOS version of a router or switch,
or adding a new modular interface card. While it is possible to track these
changes manually, a more common approach is to gather this information
using configuration management software, such as CiscoWorks 2000.

Accounting

The goal is to gather usage statistics for users. Accounting management is

concerned with tracking network utilization information, such that
individual users, departments, or business units can be appropriately
billed or charged for accounting purposes. While this may not be
applicable to all companies, in many larger organizations the IT
department is considered a cost center that accrues revenues according to
resource utilization by individual departments or business units.

Performance

The goal is to both prepare the network for the future, as well as to
determine the efficiency of the current network. Performance
management is focused on ensuring that network performance remains at
acceptable levels. This area is concerned with gathering regular network
performance data such as network response times, packet loss rates, link
utilization, and so forth. This information is usually gathered through the
implementation of an SNMP management system, either actively
monitored, or configured to alert administrators when performance move
above or below predefined thresholds. Actively monitoring current
network performance is an important step in identifying problems before
they occur, as part of a proactive network management strategy etc .....

Security

The goal of security management is to control access to assets in the

network. It uses firewalls to monitor and control external access points to
one's network. Security management is not only concerned with ensuring
that a network environment is secure, but also that gathered security-
related information is analyzed regularly. Security management functions
include managing network authentication, authorization, and auditing,
such that both internal and external users only have access to appropriate
network resources. Other common tasks include the configuration and
management of network firewalls, intrusion detection systems, and
security policies such as access lists.

Security management

Security management is the process of controlling access to assets in the

network. Data security can be achieved mainly with authentication and
encryption. Authorization to it configured with OS and DBMS access
control settings.