Network management

Alright last big chapter.

Network management is done at the last two stages.
Operate,   then based on the data accumulated the network will be
optimized...


Statistics will be grabbed on
link utilization -  to see if the link needs upgrading
CPU utilization -  to see if the device will need upgrading
interface utilization - to see traffic patterns

Cisco Works can centralize configuration changes.

FCAPS is the acronym for this chapter.
Fault management
Configuration management
Accounting Management
Performance management
Security management

This is all done using.
NMS - Network management Systems.  This is not a product but a framework for Network management.
In order to run this management the NMS will need.

Network management protocols and standards.  - These will be SNMP, RMON,

The NMS will manage devices  -  these will be the     "managed devices"

Inside each device that is being managed there will be a diplomat a "Management Agent".
Snmp Agent
RMON Agent








Netflow can be used instead of RMON.
Syslog can accumulate data from all the devices instead of storing the logs/data locally on each.



SNMP RFC1157
Runs over UDP.

The data in each device is stored in it.
The storage is arranged in a  TRee format.
MIB.
The MIB can be queried for the data in the cell/branch by referencing its locations
either by name  or number.

Name
Syntax   - interger or string
Encoding

Normal Tree would give you basic data like the interface packets.
Cisco has some "private" MIB which will give you the small, med , larg packets.


SNMPv1
Request and Respond mainly.
Get request -        let's see get CPU usage              -  (get response 60%)

Get Request    -     let's see get route table                  -(get response 10.0.0.0/24 next-hop 15.15.15.1)
Get Next  Request                                                    -  get response 20.0.0.0/24 next-hop 16.16.16.1) 

when the agent   responds    to the   requests    he will send a      Get response 

okay so far we have been reading the fields
Set Request   -      will enable you to write to a field.     set request mib3.3.3.4.5  contactname Saar
pretty useless, I can't find any real implementations of this.

Trap -   this is a setting on the agent.  When a certain item on the device happens it will try to send an
alert about it to the NMS.
For example on linkdown  send   to NMS.



SNMPv2
added getbulk       that way you don't have to repeat the getnext requests
added inform request        basically an improved trap  with Confirmation.


SNMPv3
This one finally adds  Security.
noAuthnoPriv     no authentication at all    and   no privacy  (which means no encryption)
authNoPriv         ok, authentication is ok    but no privacy. (no encryption)
AuthPriv         authentication and Privacy.
Great!!!!

Authentication is MDAC
Encryption is   DES, 3DES, AES


RMON
Network Nodes are needed for this.
Can't avoid it.
They are expensive. I think the leader in this is  NetScout.
Looks at MAC Layer 2 data.

RMONv1  grabs data from the Layer 1-2
RMONv2  grabs it from the layer 3-7

Netflow is a higher level of the above.
It grabs.
Accounting is the data grabbing
Collectors  will grab the data physically.
Analazyers will give you the reporting and GUI for this.

The netflows can be used for billing.
Network planning
Planning for user actions
or Application actions.


CDP
this is a Cisco protocol.
Cisco Discovery Protoocl.
It is helpful for troubleshooting
It runs on Layer 2 level.

syslog allows you to get information from multiple sources.
You can accumulate it all on the Syslog device and then use that to get data.
The levels go from the lowest
Which is the most critical.
0  Emergency
to 6 infomrational
7 debug