In the Name of the

Most High

Network Management Tools and

Systems

1
NM Tools and Systems
 Network Management Tools
 Network Statistics Measurement Systems
 Enterprise Management Systems

2
 Network Management Tools
Network
Management
NOC Tools
Tools (RFC 1470)

Network
Operating
Functional Resources / Mechanism Acquisition
Environment
Components

Examples : Examples: Examples: Examples: Free

Alarm Bridge NMS DOS
Manager Ethernet Ping Windows NT Library
Security IP SNMP Sun
Traffic NFS X Unix Sourcelib

Figure 12.1 NOC Tool Categories (RFC 1470)

3
 Network Monitoring Tools
 Useful list of network monitoring tools
 http://www.slac.stanford.edu/xorg/nmtf/nmtf-tools.htm
l
 http://www.snmplink.org/Tools.html
 http://www.simpleweb.org/software/

4
 Status Monitoring Tools

Table 12.5 Status Monitoring Tools

NAME OPERATING DESCRIPTION
SYSTEM
Ifconfig UNIX Obtains and configures networking interface parameters
and status
ping UNIX Checks the status of node / host
Windows
nslookup UNIX Looks up DNS for name-IP address translation
Windows NT
dig UNIX Queries DNS server
host UNIX Displays information on Internet hosts / domains

5
 UNIX
ifconfig

Used to assign/read an address to/of an

interface
Option -a is to display all interfaces
Notice two interface loop-back (lo0) and
Ethernet (le0)

6
Ping
Most basic tool for internet management
Available on all TCP/IP stacks
Useful for measuring
Connectivity
Packet loss rate
Round trip time
Can do auto-discovery of TCP/IP equipped stations
on single segment

7
nslookup

An interactive program for querying Internet

Domain Name System servers
Converts a hostname into an IP address and
vice versa querying DNS
Useful to identify the subnet a host or node
belongs to
Lists contents of a domain, displaying DNS
record

8
 Traffic Monitoring Tools
Table 12.6 Traffic-Monitoring Tools
Name Operating Description
System
ping UNIX Used for measuring roundtrip packet loss
Windows
bing UNIX Measures point-to-point bandwidth of a link
etherfind UNIX Inspects Ethernet packets
snoop UNIX Captures and inspects network packets
tcpdump UNIX Dumps traffic on a network
getethers UNIX Acquires all host addresses of an Ethernet LAN segment
iptrace UNIX Measures performance of gateways

9
 Packet Loss Measurement

netman: ping -s mit.edu

PING mit.edu: 56 data bytes
64 bytes from MIT.MIT.EDU (18.72.0.100): icmp_seq=0. time=42. ms
64 bytes from MIT.MIT.EDU (18.72.0.100): icmp_seq=1. time=41. ms
64 bytes from MIT.MIT.EDU (18.72.0.100): icmp_seq=2. time=41. ms
64 bytes from MIT.MIT.EDU (18.72.0.100): icmp_seq=3. time=40. ms
64 bytes from MIT.MIT.EDU (18.72.0.100): icmp_seq=4. time=40. ms

----mit.edu PING Statistics----

5 packets transmitted, 5 packets received, 0% packet loss
round-trip (ms) min/avg/max = 40/40/42

10
 ping
Usage: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS]
[-r count] [-s count] [[-j host-list] | [-k host-
list]]
[-w timeout] destination-list

Options:
-t Ping the specified host until stopped.
To see statistics and continue –
type Control-Break;
To stop - type Control-C.
-a Resolve addresses to hostnames.
-n count Number of echo requests to send.
-l size Send buffer size.
-f Set Don't Fragment flag in packet.
-i TTL Time To Live.
-v TOS Type Of Service.
-r count Record route for count hops.
-s count Timestamp for count hops.
-j host-list Loose source route along host-list.
-k host-list Strict source route along host-list.
-w timeout Timeout in milliseconds to wait for each reply.

11
C:\>ping -n 10 -l 256 www.hinet.net

Pinging www.hinet.net [61.219.38.89] with 256 bytes of data:

Reply from 61.219.38.89: bytes=256 time=7ms TTL=242

Reply from 61.219.38.89: bytes=256 time=6ms TTL=242
Reply from 61.219.38.89: bytes=256 time=9ms TTL=242
Reply from 61.219.38.89: bytes=256 time=6ms TTL=242
Reply from 61.219.38.89: bytes=256 time=6ms TTL=242
Reply from 61.219.38.89: bytes=256 time=6ms TTL=242
Reply from 61.219.38.89: bytes=256 time=9ms TTL=242
Reply from 61.219.38.89: bytes=256 time=6ms TTL=242
Reply from 61.219.38.89: bytes=256 time=6ms TTL=242
Reply from 61.219.38.89: bytes=256 time=37ms TTL=242

Ping statistics for 61.219.38.89:

Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 37ms, Average = 9ms

12
bing bing 163.22.18.110 203.64.255.90

bing L1 L2

Used to determine throughput of a link

Uses icmp_echo utility
Knowing packet size and delay, calculates
bandwidth
bing L1 and L2 and the difference yields the
bandwidth of link L1-L2

13
snoop
Puts a network interface in promiscuous mode
Logs data on
 Protocol type
 Length
 Source address
 Destination address
 Reading of user data limited to super-user

14
 Network Routing Tools
Table 12.7 Route-Monitoring Tools
Name Operating System Description
netstat UNIX / Windows Displays the contents of various network-
related data structures
arp UNIX, Windows Displays and modifies the Internet-to-Ethernet
95/x/00NT address translation tables
traceroute UNIX Traces route to a destination with routing
tracert Windows delays

15
 netstat
C:\>netstat -n -a
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:21 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1234 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1235 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1236 0.0.0.0:0 LISTENING
TCP 163.31.153.68:1234 163.22.3.4:80 ESTABLISHED
TCP 163.31.153.68:1235 163.22.4.67:80 ESTABLISHED
TCP 163.31.153.68:1236 163.22.4.67:80 SYN_SENT
UDP 0.0.0.0:135 *:*
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:38037 *:*
UDP 127.0.0.1:1230 *:*
UDP 163.31.153.68:500 *:*

16
NETSTAT [-a] [-b] [-e] [-n] [-o] [-p proto] [-r] [-s] [-v] [interval]

-a Displays all connections and listening ports.

-e Displays Ethernet statistics. This may be combined with the -s
option.
-n Displays addresses and port numbers in numerical form.
-p proto Shows connections for the protocol specified by proto; proto
may be TCP or UDP. If used with the -s option to display
per-protocol statistics, proto may be TCP, UDP, or IP.
-r Displays the routing table.
-s Displays per-protocol statistics. By default, statistics are
shown for TCP, UDP and IP; the -p option may be used to
specify
a subset of the default.
interval Redisplays selected statistics, pausing interval seconds
between each display. Press CTRL+C to stop redisplaying
statistics. If omitted, netstat will print the current
configuration information once.

17
C:\>netstat -s -p TCP

TCP Statistics for IPv4

Active Opens = 904

Passive Opens = 13
Failed Connection Attempts = 25
Reset Connections = 189
Current Connections = 3
Segments Received = 61946
Segments Sent = 53891
Segments Retransmitted = 249

Active Connections
Proto Local Address Foreign Address State
TCP 94ASUS3705:1502 euler.im.ncnu.edu.tw:telnet ESTABLISHED
TCP 94ASUS3705:1976 giant.ccserver.ncnu.edu.tw:epmap TIME_WAIT
TCP 94ASUS3705:1977 giant.ccserver.ncnu.edu.tw:1025 TIME_WAIT
TCP 94ASUS3705:1980 giant.ccserver.ncnu.edu.tw:1025 TIME_WAIT
TCP 94ASUS3705:1981 giant.ccserver.ncnu.edu.tw:1025 TIME_WAIT
TCP 94ASUS3705:1982 giant.ccserver.ncnu.edu.tw:ldap TIME_WAIT
TCP 94ASUS3705:1984 giant.ccserver.ncnu.edu.tw:ldap TIME_WAIT
TCP 94ASUS3705:1985 giant.ccserver.ncnu.edu.tw:microsoft-ds TIME_WAIT
TCP 94ASUS3705:1990 giant.ccserver.ncnu.edu.tw:ldap TIME_WAIT
TCP 94ASUS3705:4558 localhost:4559 ESTABLISHED
TCP 94ASUS3705:4559 localhost:4558 ESTABLISHED 18
C:\>netstat –r C:\>route print

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 12 f0 2b b8 0b ...... Intel(R) PRO/Wireless 2200BG Network Connection
- Packet Scheduler Miniport
0x3 ...00 01 4a 82 13 e8 ...... Intel(R) PRO/100 VE Network Connection - Packet
Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.10.1 192.168.10.40 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.10.0 255.255.255.0 192.168.10.40 192.168.10.40 20
192.168.10.40 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.10.255 255.255.255.255 192.168.10.40 192.168.10.40 20
224.0.0.0 240.0.0.0 192.168.10.40 192.168.10.40 20
255.255.255.255 255.255.255.255 192.168.10.40 192.168.10.40 1
255.255.255.255 255.255.255.255 192.168.10.40 2 1
Default Gateway: 192.168.10.1
===========================================================================
Persistent Routes:
None

19
 traceroute/tracert
tracert www.hinet.net

Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout]

target_name

Options:
-d Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-j host-list Loose source route along host-list.
-w timeout Wait timeout milliseconds for each reply.

20
C:\>tracert www.yahoo.co.jp

Tracing route to www.yahoo.co.jp [203.216.247.225]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms gateway.puli13-10-10.ncnu.edu.tw [10.10.13.254]

2 <1 ms 1 ms <1 ms ip253.puli01.ncnu.edu.tw [163.22.1.253]
3 <1 ms <1 ms <1 ms ip105.puli18-10-10.ncnu.edu.tw [10.10.18.105]
4 <1 ms <1 ms <1 ms ip110.puli18.ncnu.edu.tw [163.22.18.110]
5 2 ms 1 ms 1 ms ip098.puli255-64-203.ncnu.edu.tw [203.64.255.98]
6 6 ms 3 ms 3 ms 140.128.251.38
7 3 ms 3 ms 2 ms 10G-10GE-CHT-P1.TCC-NCHUE.twaren.net
[211.79.60.145]
8 4 ms 4 ms 5 ms 10G-POS-CHT-P1.HCC-TCC.twaren.net [211.79.59.161]
9 6 ms 6 ms 6 ms 10G-POS-CHT-P1.TPC-HCC.twaren.net [211.79.59.154]
10 6 ms 6 ms 6 ms 211.79.59.98
11 56 ms 19 ms 6 ms 202.169.174.58
12 59 ms 60 ms 60 ms 202.169.174.41
13 66 ms 74 ms 70 ms AS9607-2.ix.jpix.ad.jp [210.171.224.205]
14 62 ms 61 ms 62 ms ge-1-0-0.edge09.colo01.bbtower.ad.jp
[211.14.3.200]
15 60 ms 62 ms 61 ms yahoo-7.demarc.colo01.bbtower.ad.jp [211.14.30.1]
16 62 ms 62 ms 60 ms 202.93.95.194
17 60 ms 60 ms 60 ms 203.216.238.154
18 63 ms 60 ms 62 ms f6.top.vip.tnz.yahoo.co.jp [203.216.247.225]

Trace complete.

21
Network Management Tools
 SNMP command tools
 MIB Walk
 MIB Browser
 snmpsniff

22
SNMP Command Tools
snmptest
snmpget
snmpgetnext
snmpset
snmptrap
snmpwalk
snmpnetstat

23
Network Status
Command: snmpnetstat host community
Useful for finding status of network connections
% snmpnetstat noc5 public
Active Internet Connections
Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp 0 0 *.* *.* CLOSED
tcp 0 0 localhost.46626 localhost.3456 ESTABLISHED
tcp 0 0 localhost.46626 localhost.3712 ESTABLISHED
tcp 0 0 localhost.46626 localhost.3968 ESTABLISHED
tcp 0 0 localhost.46626 localhost.4224 ESTABLISHED
tcp 0 0 localhost.3456 localhost.46626 ESTABLISHED
tcp 0 0 localhost.3712 localhost.46626 ESTABLISHED
tcp 0 0 localhost.3968 localhost.46626 ESTABLISHED
tcp 0 0 localhost.4224 localhost.46626 ESTABLISHED
tcp 0 0 noc5.41472 noc5.4480 ESTABLISHED
tcp 0 0 noc5.41472 noc5.4736 ESTABLISHED
tcp 0 0 noc5.4480 noc5.41472 ESTABLISHED
tcp 0 0 noc5.4736 noc5.41472 ESTABLISHED

24
SNMP Browser
Command: snmpwalk host community [variable
name]
Uses Get Next Command
Presents MIB Tree

25
SNMP Sniff

snmpsniff -I interface
 A tool in Linux / FreeBSD environment
 Puts the interface in promiscuous mode and
captures snmp PDUs.

26
2 MIB Browser

27
28
Protocol Analyzer
Data
PROTOCOL Capture
ANALYZER Device
Raw data transferred on
Modem / WAN or LAN Link

• Analyzes data packets on any transmission LAN

line including LAN

• MeasurementsFiguremade locally
12.13 Protocol Analyzer or remotely
Basic Configuration
• Probe (data capture device) captures data and
transfers to the protocol analyzer (no storage)
• Data link between probe and protocol analyzer
either dial-up or dedicated link or LAN
• Protocol analyzer analyzes data at all protocol
levels
29
 RMON Probe

PROTOCOL SNMP BACKBONE SNMP RMON

ANALYZER Traffic NETWORK Traffic Probe
Router Router

LAN
 Communication between probe and analyzer
is using SNMP
 Data gathered Figure
and 12.14 stored for
Protocol Analyzer with RMONan
Probe extended period
of time and analyzed later
 Used for gathering traffic statistics and used for
configuration management for performance tuning

30
Network Monitoring with RMON
Probe
Ethernet
Protocol
Probe
Analyzer

Ethernet LAN

Router

Backbone
FDDI LAN
Network
Router

Router Backbone
FDDI Probe Probe

Token Ring
LAN
Token Ring
31
Probe
Network Statistics

 Protocol Analyzers
 RMON Probe / Protocol analyzer
 MRTG (Multi router traffic grouper)
 Home-grown program using tcpdump

32
33
Traffic Load:
Source
HostTopN

Host 1
Host 2
Host 3
Host 4
Host 5
Host 6
Host 7
Host 8
Host 9
Host 10

0 100 200 300 400

Giga Octets
34
Protocol Distribution

35
NMS Deisgn
 Key Requirements:
 Scalability
 Heterogeneity
 Geographic Spread
 Bursty Load
 Real time Response
 Batch Processing
 Diverse Users
 Local and Remote Management
 Ease of Use
 Security
 Data Management

36
NMS Components
Table 12.8 Network Management System Components
Component Service Example
Hardware Processor Sun Sparc
Monitor HP 9000
Mouse and Keyboard PC
Communications
Operating system OS services UNIX
LINUX / FreeBSD
Solaris
MS Windows 95 / 98 / NT
Core application Display OpenView
services GUI SunNet Manager
Database Solstice Enterprise Manager
Report generation MS Windows
Communication services
Common SNMP SNMPv1 messages SNMPc
services SNMPv2 messages OpenView Network Node Manager
MIB management Cabletron Spectrum Enterprise
Basic SNMP applications Manager
3rd party NMS API IBM NetView
SunNet Manager
Solstice Enterprise Manager
Vendor-specific MIB management CiscoWorks
NMS services SNMP applications Transcend
Config. management Spectrum Element Manager /
Physical entity display Spectrum Portable Management
Application

37
Multi-NMS Configuration

Vendor 1
NMS
Configuration

Managed Manager
Vendor 2 Fault
Configuration Network of
NMS Performance
Elements Managers

Configuration
Vendor 3
NMS

Figure 12.21 Functional NMS Configuration

38
Network Monitoring

 By polling
 By traps (notifications)
 Failure indicated by pinging or traps
 Ping frequency optimized for network load vs.
quickness of detection
 trap messages: linkdown, linkUp,
coldStart, warmStart, etc.
 Network topology discovered by auto-discovery

39
Node Discovery In a Network

 Node Discovery
 Given an IP Address with its subnet mask, find the
nodes in the same network.
 Two Major Approaches:
 Use ICMP ECHO to query all the possible IP
addresses.
 Use SNMP to query the ARP Cache of a node
known

40
Use ICMP ECHO

 Eg: IP address: 163.25.147.12

Subnet mask: 255.255.255.0
 All possible addresses:
 163.25.147.1 ~ 163.25.147.254
 For each of the above addresses, use ICMP
ECHO to inquire the address
 If a node replies (ICMP ECHO Reply), then it
is found.

41
Use SNMP

 Find a node which supports SNMP

 The given node, default gateway, or router
 Or try a node arbitrarily
 Query the ipNetToMediaTable in MIB-II IP
group
ipNetToMediaPhysAddress ipNetToMediaType
ipNetToMediaIfIndex ipNetToMediaNetAddress

1 00:80:43:5F:12:9A 163.25.147.10 dynamic(3)

2 00:80:51:F3:11:DE 163.25.147.11 dynamic(3)

42
Network Discovery

 Network Discovery
 Find the networks to be managed with their
interconnections
 Given a network, find the networks which
directly connect with it.
 Recall that networks are connected via
routers.
 Major Approach
 Use SNMP

43
 Discovering Networks

163.25.145.0 163.25.146.0

140.112.8.0 140.112.6.0
163.25.148.0
163.25.147.0
163.25.147.0

140.112.5.0

192.168.13.0 192.168.12.0

44
A Network Discovery Algorithm
1. First use a node discovery algorithm to find all the nodes in
the network.
2. For each discovered node, use SNMP to query the ipAddrTable
of MIB-II IP group
3. Query the corresponding entries in ipRouteTable to verify the
above addresses
ipAdEntIfIndex ipAdEntBcastAddr
ipAdEntAddr ipAdEntNetMask
163.25.145.254 1 255.255.255.0 163.25.145.255 …
162.25.146.254 2 255.255.255.0 163.25.146.255 …
162.25.147.254 3 255.255.255.0 163.25.147.255 …

45
ipRouteTable

46
Layer 2 topology discovery

 Useful MIB variables for Layer 2 discovery

(RFC 1493)
 dot1dBase-NumPorts to find the number of ports on each
switch
 dot1dStpPortTable to find the topology of the extended LAN
 dot1dTpFdbTable to find the MAC address of the machines
connected to each port

47
Commercial and Open Source NMSs

 Management functions that must be

supported by NMSs:
 Configuration management
 Fault management
 Performance management
 Accounting management
 Security management

48
Commercial and Open Source NMSs
 Open source NMSs
 OpenNMS
 Currently supports Fault, Performance and parts of Configuration in FCAPS
 Does not have a graphical map for the display of the NEs and their status
 Nagios
 Provides basic network management functions
 It has graphical mapping of network elements
Enterprise NMSs
Hewlett-Packard OpenView
Sun SunNet Manager
IBM Netview
System & Network Management
Computer Associates Unicenter TNG
Tivoli TME / Netview

49