Baseline

Read-only (RO): gives read-only access to

the MIB objects which is safer and preferred
to other method.

The process of recording network traffic

and performance, and saving the data for
Read-write (RW): gives read and write
future reference or reviewing it for
access to the MIB objects. This method
network performance analysis
allows SNMP Manager to change the
configuration of the managed
SNMP
router/switch.
Simple Network Management Protocol
SNMPv3 major features
(SNMP) is the protocol developed to
manage nodes (servers, workstations,
routers, switches and hubs etc.) on an IP Message integrity: ensuring that a
packet has not been modified in transit.
network
SNMP Manager (Network
Management System)
a software runs on the device of the
network administrator (in most case, a
computer) to monitor the network.

Authentication: by using password

hashing (based on the HMAC-MD5 or
HMAC-SHA algorithms) to ensure the
message is from a valid source on the
network.

SNMP Agent

Privacy (Encryption): by using encryption

(56-bit DES encryption, for example) to
encrypt the contents of a packet

a software runs on network devices that

we want to monitor (router, switch,
server)

Disaster Recovery Planning

Management Information Base (MIB)

is collection of managed objects. This
component makes sure that the data
exchange between the manager and the
agent remains structured
Get: retrieve information from the SNMP
Agents
GET-NEXT: retrieves the value of the
next object in the MIB
GET-RESPONSE: used by the SNMP
Agents to reply to GET and GET-NEXT
messages.
SET: are used by the SNMP Manager to
modify or assign the value to the SNMP
Agents.
TRAP: initiated from the SNMP Agents to
inform the SNMP Manager on the
occurrence of an event

assist the organization/business to continue

functioning even though normal operations
are disrupted in the event of a systems
disruption.
DRP Procedures

Backup
Monitoring
Duplicate services
On-site inventory
Automatic system recovery

DRP Failure Reasons

Ill-defined scope
Ambiguous objectives
Never had real commitment
Budget constraints
Unrealistic target dates
Lack of accountability
Poor communication
Lack of technical expertise
Inadequate testing

SNMPv2c:
updated the original protocol and offered
some enhancements. One of the
noticeable enhancement is the
introduction of INFORM and GETBULK

Poor maintenance

Five Steps to Disaster Recovery

Step
Step
Step
Step
Step

1:
2:
3:
4:
5:

Develop the Budget

Consider the Issues
Create a Procedure
Test the Procedure
Keep Pace With Changes