Beruflich Dokumente
Kultur Dokumente
NMS on subnet 192.168.252.1 manages the router and the hubs on subnet 172.16.46.1 across the backbone network
Organization Model Describes the components of an NMS and their functions Agent, Manager, Object Information Model Describes the structure and organization of Management Information SMI, MIB Communication Model Management Application processes in the Application Layer Layer Management between Layers Layer Operations within the Layers Functional Model FCAPS
Use an NMS to monitor a Network of multiple vendor NMS as an NMS provided by the same vendor has more capabilities than other vendors NMS. Network Manager receives raw data from the agents and processes them.
Useful when we want temporal data like, data traffic as a function of time Instead of Manager polling, an intermediate agent is inserted between the agent and the manager. RMON (Remote Monitoring) gathers data from MO, analyses the data, and stores the data RMON acts as an agent and a manager; Communicates the statistics to the manager The Manager receives data from the managed object as well as the intermediate agent
Used when it is required to manage non-SNMP Managed objects using SNMP Network elements do not have SNMP agents, eg. legacy systems management, wireless networks The information from these elements are gathered using associated tools Proxy server at a central location converts the non-SNMP data into a set compatible with SNMP Proxy server communicates with the SNMP Manager
Similar to Client-Server Architecture While collecting data from Network elements, acts like a Manager While providing data to another Network Manager, acts like an Agent eg. two telecommunication service providers managing their respective WANs, but needing to exchange information to provide end-t-end services to the customers
Three goals of the Architecture of SNMP: Management functions on the Agent should be minimal and simple Should be flexible to allow expansions Should be independent of the architecture of any particular hosts or gateways SNMP manages the network with 5 messages: 3 Messages from the Manager to the Agent, 2 from the Agent to the Manager
get-request: Sent by manager requesting data from agent get-next-request: Sent by manager requesting data on the next MO to the one specified set-request: Initializes or changes the value of network element get-response: Agent responds with data for get and set requests from the manager Trap - generic trap, specific trap, timestamp: Alarm generated by an agent
Objects by private vendors, if they conform to SMI defined by RFC 1155 and have MIBs specified by RFC 1213, can be managed by SNMP-compatible NMS
Object identifier (OID) is data type, not instance Object instance IP address; Each IP address is an instance of the object All Cisco routers of the same version have identical identifier; they are distinguished by the IP address
internet OBJECT IDENTIFIER ::= {iso standard dod internet} internet OBJECT IDENTIFIER ::= {1 3 6 1}
Any combination of the unique node number and unique name can be used
Any object in the internet MIB will start with the prefix 1.3.6.1 or internet
Examples of OID
OBJECT IDENTIFIER ::= {internet 1} OBJECT IDENTIFIER ::= {internet 2} OBJECT IDENTIFIER ::= {internet 3} OBJECT IDENTIFIER ::= {internet 4} OBJECT IDENTIFIER ::= {1 3 6 1 2}
OCTET STRING
IpAddress Dotted decimal IP Address Used to define IP Address of a Network element. Internally it is an OCTET STRING of length 4 Counter Wraparound non negative incrementing integer, Used for defining values which always increase eg. Input packets received on an interface
Gauge Capped non negative integer, increase or decrease Used for defining values which can increase or decrease eg. No. of interfaces that are active on a hub TimeTicks Non negative integer in hundredths of second units Time measured in 100ths of a second from the time it was initialized to 0 upto the current instant. eg. System Up time Opaque Application wide arbitrary syntax. Used to create data types based on previously defined data types.
SEQUENCE {<type1>, <type2>,.,<typeN>} eg. List: IpAddrEntry::= SEQUENCE { ipAdEntAddr IpAddress ipAdEntIfIndex INTEGER ipAdEntNetMask IpAddress ipAdEntBcastAddr INTEGER ipAdEntReasmMaxSize INTEGER(0..65535) } SEQUENCE OF Table Maker; Makes a table from the list SEQUENCE OF <list> where list is a list made using SEQUENCE eg Table: IpAddrTable ::= SEQUENCE OF IpAddrEntry SET and SET OF are not used in SNMP
SNMPv1 uses Basic Encoding Rules (BER) for encoding the information to be transmitted between the agent and the manager.
Type Length Value
BER uses the tag length value (TLV) notation OBJECT IDENTIFIER SEQUENCE The first octet of the encoding is the tag, IpAddress then the length of the value, then the value. Counter Gauge OID is encoded as an octet string. TimeTicks IP Address is encoded as octet strings Opaque Counter, gauge and TimeTicks are coded as integers Opaque is octet string
Type
Textual name Is mnemonic and starts with a small letter, eg. sysUpTime, sysDescr, etc. Also called OBJECT DESCRIPTOR Syntax Is the ASN.1 definition of the object, eg. OCTET STRING, INTEGER etc. Definition - Textual description of the object Access Type of privilege associated with the object: eg. read-only, read-write or not-accessible Status specifies whether the object is current or obsolete. A managed object once defined can only be made obsolete and not removed or deleted. If it is current, then specify whether its implementation is optional or mandatory eg. sysDescr: {system 1} Syntax: OCTET STRING Definition: A textual description of the entity Access: read-only Status: mandatory
Aggregate Object
An aggregate object is a group of related objects eg. IpAddrEntry::= SEQUENCE{ ipAdEntAddr IpAddress ipAdEntIfIndex INTEGER ipAdEntNetMask IpAddress ipAdEntBcastAddr INTEGER ipAdEntReamMaxSize INTEGER } ipAddrTable::=SEQUENCE OF IpAddrEntry ipAddrTable Syntax Definition Access Status {ip 20} SEQUENCE OF IPAddrEntry .. not-accessible mandatory
1
2 3
123.34.23.1
123.34.23.2 123.34.23.3
1
3 2
255.255.255.0
255.255.255.0 255.255.0.0
0
0 1
12000
12000 12000
ipAdEntAddr OID for Row 3 : {1.3.6.1.2.1.4.20.1.1.123.34.23.3} ipAdEntBcastAddr OID for Row 2 :{1.3.6.1.2.1.4.20.1.4. 123.34.23.2 }
Values
OID INTEGER | SEQUENCE | IpAddress | SEQUENCE OF |
Access
Status Description
A MIB example: Internet MIB Objects that are related are grouped into groups
System Group
Interfaces Group
IfEntry OBJECT-TYPE SYNTAX IfEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "An interface entry containing objects at the subnetwork layer and below for a particular interface." INDEX {ifIndex} ::= {ifTable 1}