You are on page 1of 16

HELSINKI METROPOLIA UNIVERSITY OF APPLIED SCIENCES

Network Management in IP Networks

Lab 1: Network Management Tasks

Topology

SNMP Agent

Router2 DCE
Serial 0/0/0 Serial 0/0/1
DCE
Serial 0/0/0 Serial 0/0/1

SNMP Agent SNMP Agent

Router1 Router3

Fa 0/0 Fa 0/0 10.10.10.0/24


192.168.10.0/24

Fa 0/24 Fa 0/24

SNMP Agent SNMP Agent

SW1 SW2

Fa 0/5 Fa 0/6 Fa 0/18

PC 3
Observium
PC 1 PC 2
VM

Page 1 of 16
HELSINKI METROPOLIA UNIVERSITY OF APPLIED SCIENCES

Addressing Table

Device Interface IP Address Subnet Mask Gateway


PC1 NIC 192.168.10.10 255.255.255.0 192.168.10.254
PC2 NIC 192.168.10.11 255.255.255.0 192.168.10.254
Observium VM NIC 192.168.10.12 255.255.255.0 192.168.10.254
PC3 NIC 10.10.10.10 255.255.255.0 10.10.10.254
SW1 VLAN1 192.168.10.253 255.255.255.0 192.168.10.254
SW2 VLAN1 10.10.10.253 255.255.255.0 10.10.10.254
R1 Fa 0/0 192.168.10.254 255.255.255.0 NA
Serial 0/0/0 172.16.10.1 255.255.255.252 NA
R2 Serial 0/0/0 172.16.10.2 255.255.255.252 NA
Serial 0/0/1 172.16.10.5 255.255.255.252 NA
R3 Fa 0/0 10.10.10.254 255.255.255.0 NA
Serial 0/0/1 172.16.10.6 255.255.255.252 NA

Objective

The objective of this lab is to get a practical view of different network management tasks and
information provided by NMS software.

Page 2 of 16
HELSINKI METROPOLIA UNIVERSITY OF APPLIED SCIENCES

Background

Functional areas of network management tasks are Fault Management, Configuration Management,
Accounting Management, Performance Management and Security Management. Functional Layers
include Network Element Management, Network Management, Service Management and Business
Management.

Equipment and Tools

The following equipment and tools are needed to perform the laboratory exercises:
3 SNMP manageable routers (Cisco 2811)
2 SNMP manageable switches (Cisco 2960)
3 PCs
Cables
Observium software running on a virtual machine on PC2
cpustres.exe simulation tool

Page 3 of 16
HELSINKI METROPOLIA UNIVERSITY OF APPLIED SCIENCES

Working

Network Setup and SNMP Configuration

1. Set up a network as shown in the picture. Make sure that the start-up configuration file is
empty on each device. Copy the device configurations provided at the end of this
document. Verify the network connectivity (for example ping between PC3 and PC1)
and confirm the different networks from the routing table of R1 and R3 at least.

2. Power ON the virtual machine Ubuntu Observium on PC2.


User is "student", password is "student123" to access the VM from the command line.
The virtual machine running Ubuntu Observium is the management station. The network
adapter of the virtual machine should be set to Bridged mode (Player > Manage >
Virtual Machine Settings > Network Adapter). Click on Configure Adapters and check
that only Intel network adapter is chosen. Uncheck the check box on the other network
adapters. Make sure that the VM has the correct IP settings
ip address
ifconfig
ip route

3. Set the correct IP address if needed. See the Addressing table for IP addresses.
Verify connectivity to the virtual machine using ping.

4. Open a browser from any of the PCs and got to http://192.168.10.12. You should see the
web Observium web interface.
Log in as user1 with password user1pass

Page 4 of 16
HELSINKI METROPOLIA UNIVERSITY OF APPLIED SCIENCES

5. Configure all switches and routers to support SNMP with the default community string
"public". Use commands:
snmp-server community ?
snmp-server location ?

Use snmpwalk to verify the SNMP configuration of each device.

Snmpwalk is a part of net-snmp package, which is designed to perform a sequence of


chained GETNEXT requests. "The command takes a single OID, and will display a list
of all the results which lie within the subtree rooted on this OID." [The Net-SNMP
Wiki]

For example, you can use the following command (run in console on the virtual
machine) to request the device name via SNMP
snmpwalk -v 1 -c public <IP address> 1.3.6.1.2.1.1.5

As the output of this command, you should get the device name. Do not proceed, if you
do not get a correct reply. Verify your configuration and make sure that you get correct
replies from each switch and router.

6. Install and configure SNMP agent on Windows PCs.


Go to Start > Control Panel > Programs and Features > Turn Windows features on or off

Select Simple Network Management Protocol (SNMP), turn it on.


Configure the new service. Go to Control Panel > Administrative Tools > Services
> SNMP Service > Right click and select Properties:
Set the location of the PC from the Agent tab.
Go to the Security tab. Add a new community name public and leave the
default settings for Community rights
To limit acceptance of SNMP packets, click on the radio button Accept SNMP
packets from these hosts and add the IP address of the management station.
If the Services window was open before, you might need to close it and open again in
order to see all the tabs in the SNMP Service properties.

Verify the SNMP configuration of PCs using snmpwalk.

Familiarization with Observium and Initial Setup

"Observium is... an SNMP based network monitoring platform which includes support for a wide
range of network hardware and operating systems." [Observium web site]
Page 5 of 16
HELSINKI METROPOLIA UNIVERSITY OF APPLIED SCIENCES

7. From the web management interface of Observium and add the devices to Observium
using their names and a community string.
Go to Devices > Add Device.

Use exactly the same device names as given in the Addressing table in this document.
When you add PCs, use names PC1, PC2 and PC3, not their real system names.
This is caused by the specific configuration of hostname mapping in the lab
environment.

After devices have been added to the system, wait for polling to be executed.
Explore which information about the device is available and think how this information
can be useful for a network engineer.

Fault management

"Fault Management... includes proactive prevention or reactive detection, isolation and correction
of abnormal behavior of the network." [Puska 2013]
8. As part of the Fault Management, it is important to detect network failures in time.
Shutdown the routers interface Fa0/0 on R3 (or disconnect the cable).

After the next polling you should see the warning on the main page.
The web page is refreshed automatically every 60 seconds.

Enable the interface again and make sure that the warning disappeared.

Security Management

"Security Management includes controlling access to network resources." [Puska 2013]

9. Servers and network devices keep a log of important events. Logs are useful for
diagnosing problems or examining possible security violations.
Configure the router R1 to send log entries to a Syslog server on the management host.
Use commands: logging ?
Configure an Extended Access List, which permits and logs all telnet sessions to
the Ethernet interface of the router R1. Remember to allow other traffic than telnet as
well in ACL.
Set a password for enable and vty lines on R1. Open a Telnet connection to the router.
Go to Syslog and make sure that your session created a log entry.

Page 6 of 16
HELSINKI METROPOLIA UNIVERSITY OF APPLIED SCIENCES

Performance Management

"Performance Management ensures the network ability to satisfy the needs of multiple users."
[Puska 2013]

10. Monitoring system resources provides timely information for a hardware upgrade, as
well as detects the abnormal system behavior.
Look at the processors, memory and disk usage information.
Health > Memory
Health > Processors
Health > Storage

Simulate CPU load on PC3 using CPUSTRES.exe.


You can find the file from Desktop > NMS folder > Soft
You can run the exe file directly from the folder by just double clicking
CPUSTRESS.EXE. Change the values for the different Thread under activity and
see the changes in both Windows Task Manager and from Observium.
Follow the increasing Processor Usage for PC3 in Observium (notice change of the
color). Take into account that Observium does not show processor load in real time,
but updates values once a minute.

Accounting Management

"Accounting Management measures the usage of network resources." [Puska 2013]

11. Monitoring the network utilization helps to find out the bottleneck and improve network
performance.

Generate traffic by pinging the router R1 continuously from PC3:


ping -t -l 10000 <R1 Serial0/0/0 ip address>
Monitor the network utilization on the Serial0/0/0 port of the router.
Page 7 of 16
HELSINKI METROPOLIA UNIVERSITY OF APPLIED SCIENCES
Devices > All Devices > R1 > Ports > Serial0/0/0

In order to being able to see the port utilization in real time, we need to change the web
page auto refresh interval.

Open the configuration file:


sudo nano /opt/observium/config.php

Find the following line and change the refresh interval to 300 (5 minutes)
$config['page_refresh'] = "60"; ## Refresh the page every 60
seconds

Go to Devices > All Devices > R1 > Ports > Serial0/0/0 > Real Time
Notice traffic spikes caused by SNMP polling every minute.

Configuration management

Configuration management is an important part of network management. It provides tools to collect


device configs automatically or track the config changes.

12. Configure the router R1 to generate a log message for every config change to the syslog
server:
configure terminal
archive
log config
logging enable

notify syslog
hidekeys

Syslog logging was enabled in exercise 8, so we do not need to configure it again.

Make any configuration change. Go to Syslog page in Observium and check that the
corresponding entry appeared there. You might need to refresh the page in order to see
new entries.

References

Observium Web Site, http://www.observium.org


Matti Puska: Network Management in IP Networks. Helsinki Metropolia University of Applied
Sciences, 2013
The Net-SNMP Wiki, http://www.net-snmp.org

Page 8 of 16
HELSINKI METROPOLIA UNIVERSITY OF APPLIED SCIENCES

Device Configurations

R1

hostname R1
!
no ip domain-lookup
!
interface f0/0
ip address 192.168.10.254 255.255.255.0
no sh
!
interface Serial0/0/0
ip address 172.16.10.1 255.255.255.252
clock rate 64000
no sh
!
router ospf 1
network 172.16.10.0 0.0.0.3 area 0
network 192.168.10.0 0.0.0.255 area 0
!
line con 0
logging synchronous
!
End

Page 9 of 16
HELSINKI METROPOLIA UNIVERSITY OF APPLIED SCIENCES

R2

hostname R2
!
no ip domain lookup
!
interface Serial0/0/0
ip address 172.16.10.2 255.255.255.252
no sh
!
interface Serial0/0/1
ip address 172.16.10.5 255.255.255.252
clock rate 64000
no sh
!
router ospf 1
network 172.16.10.0 0.0.0.3 area 0
network 172.16.10.4 0.0.0.3 area 0
!
line con 0
logging synchronous
!
end

Page 10 of 16
HELSINKI METROPOLIA UNIVERSITY OF APPLIED SCIENCES

R3

!
hostname R3
!
no ip domain lookup
!
interface f0/0
ip address 10.10.10.254 255.255.255.0
no sh
!
interface Serial0/0/1
ip address 172.16.10.6 255.255.255.252
no sh
!
router ospf 1
network 10.10.10.0 0.0.0.255 area 0
network 172.16.10.4 0.0.0.3 area 0
!
line con 0
logging synchronous
!
end

Page 11 of 16
HELSINKI METROPOLIA UNIVERSITY OF APPLIED SCIENCES

SW1

hostname SW1
!
no ip domain-lookup
!
interface FastEthernet0/1
shutdown

!
interface FastEthernet0/2
shutdown
!
interface FastEthernet0/3
shutdown
!
interface FastEthernet0/4
shutdown
!
interface FastEthernet0/5
!
interface FastEthernet0/6
!
interface FastEthernet0/7
shutdown
!
interface FastEthernet0/8
shutdown
!
interface FastEthernet0/9
shutdown
!
interface FastEthernet0/10
shutdown
!
interface FastEthernet0/11
shutdown
!
interface FastEthernet0/12
shutdown
!
Page 12 of 16
HELSINKI METROPOLIA UNIVERSITY OF APPLIED SCIENCES
interface FastEthernet0/13

shutdown
!
interface FastEthernet0/14
shutdown
!
interface FastEthernet0/15
shutdown
!
interface FastEthernet0/16

shutdown
!
interface FastEthernet0/17
shutdown
!
interface FastEthernet0/18
shutdown
!
interface FastEthernet0/19
shutdown
!
interface FastEthernet0/20
shutdown
!
interface FastEthernet0/21
shutdown
!
interface FastEthernet0/22
shutdown
!
interface FastEthernet0/23
shutdown
!
interface FastEthernet0/24
!
interface GigabitEthernet0/1
shutdown
!
interface GigabitEthernet0/2
shutdown
!
Page 13 of 16
HELSINKI METROPOLIA UNIVERSITY OF APPLIED SCIENCES
interface Vlan1

ip address 192.168.10.253 255.255.255.0


!
ip default-gateway 192.168.10.254
!
!
line con 0
logging synchronous
!
end

SW2

hostname SW2
!
no ip domain-lookup
!
interface FastEthernet0/1
shutdown
!
interface FastEthernet0/2
shutdown
!
interface FastEthernet0/3
shutdown
!
interface FastEthernet0/4
shutdown
!
interface FastEthernet0/5
shutdown
!
interface FastEthernet0/6
shutdown
!
interface FastEthernet0/7
shutdown
!
interface FastEthernet0/8
shutdown
!
Page 14 of 16
HELSINKI METROPOLIA UNIVERSITY OF APPLIED SCIENCES
interface FastEthernet0/9

shutdown
!
interface FastEthernet0/10
shutdown
!
interface FastEthernet0/11
shutdown
!
interface FastEthernet0/12
shutdown
!

interface FastEthernet0/13
shutdown
!
interface FastEthernet0/14
shutdown
!
interface FastEthernet0/15
shutdown
!
interface FastEthernet0/16
shutdown
!
interface FastEthernet0/17
shutdown
!
interface FastEthernet0/18
!
interface FastEthernet0/19
shutdown
!
interface FastEthernet0/20
shutdown
!
interface FastEthernet0/21
shutdown
!
interface FastEthernet0/22
shutdown
!
Page 15 of 16
HELSINKI METROPOLIA UNIVERSITY OF APPLIED SCIENCES
interface FastEthernet0/23

shutdown
!
interface FastEthernet0/24
!
interface GigabitEthernet0/1
shutdown
!
interface GigabitEthernet0/2
shutdown
!
interface Vlan1
ip address 10.10.10.253 255.255.255.0

!
ip default-gateway 10.10.10.254
!
line con 0
logging synchronous
!
end

Page 16 of 16

You might also like