Enterprise Network Management Chapter 2

1. Enterprise Network ManagementChapter 2 By: Yilma Tefera May 2006

2. Network Element • High loading can occur when: • Many voice calls are in transit through a PABX • Large numbers of ATM virtual circuits are transporting many ATM cells. • Large numbers of IP packets are in transit a router. • Network topology changes result in routing protocol convergence.

3. Introducing MPLS: First chunck • On a more general note, a good understanding of MPLS is important for appreciating issues such as traffic engineering, network-Qos, and connection oriented IP networks.

4. The Trend towards IP • MPLS allows traffic engineering. • MPLS integrates IP Qos with layer 2 Qos • Many vendors are providing MPLS capability in their devices-for example, Cisco,Juniper, Nortel Networks,and Marconi.

5. MPLS concepts • MPLS is forwarding technology. Its purpose is to receive an incoming traffic type(layer 2 or 3 )at the network edge, it encapsulate it, and then transmit it through an MPLS core or cloud.

6. MPLS Concept • The LSP is created manually or via a signaling protocol • The path taken by the LSP may be either user- specified or computed by LER1. • The LSP may have reserved resources, such as bandwidth, along the path.

7. SNMPv3 Message • The BEGIN keyword indicates the start of the MIB • The IMPORTS keyword introduce descriptors from external MIBs in a similar way to #include in C and import in Java. The IMPORTS statement identifies the descriptor and the module in which it is defined. • The DESCRIPTION keyword provides details about the MIB contente • The REVISION Keyword provides details about the MIB

8. SNMPv3 Message Exchanges SNMPv3 get request SNMPv3 get-NextRequest SNMPv3 getBulkrequest SNMPv3 setRequest SNMPv3 Notifications Access Rights Message Size SNMPv3 Security

9. SNMPv3 Structure • SNMPv3 entity consists of two main components: • An SNMP engine • A collection of SNMP applications

10. The SNMPv3 engine • It made up of four subcomponents: • Dispatcher handles message sending and receiving • Message subsystem handles message processing for SNMPv3, SNMPv2c, SNMPv1, and any other models. • Security subsystem handles security processing for SNMPv3 user-based security model(USM), SNMPv1/v2c community-based security model, and any additional (newly defined) models. • Access control subsystem handles the granting/ rejecting of access to specific managed objects.

11. The two important of engine subcomponents are. • Can hand off the message processing to each other as required. • Are themselves extensible entities.

12. There are five SNMPv3 application • Command generators, create SNMP messages. • Command reponders, respond to SNMP messages. • Notification originators, send trap or inform messages. • Notification receivers, receive and process trap or inform messages. • Proxy forwarders, forward messages between SNMP entity components.

13. The message format divided into four section. • Common data: These fields occur in all SNMPv3 messages. • Security model data: This area has three subsections one general, one for authentication, and one for privacy data. • Context: These two fields are used to provide the correct context in which the protocol data unit (PDU) should be processed. • PDU: This area contains an SNMPv2c PDU.

14. Common Data • Message Version • Message ID • MaxMessageSize • MessageFlags • MessageSecurity

15. Security Model Data • General • EngineID • Engine Boots • Engine Time • UserName

16. Authentication Protocol • MD5 (Message Digest) • SHA (Secure Hash Algorithm)

17. Privacy Protocol • DES Key(Data Encryption Standard)

18. Context • Context Name • ContextID

19. PDU • MessagesFlags

20. Problems with SNMP: • SNMP is not transaction-oriented but instead offers an all-or-nothing style of execution. It is difficult to manipulate very large data sets. • Scalability issues where tables grow to include thousands of rows. • Notifications are not guaranteed to arrive at their destination. Management operations (such as get or set) can time out if the network is congested or the agent host is heavily loaded. • SNMP messages use the UDP protocol (best-effort datagram service).

21. The Different Versions of SNMP. • SNMPv1 • SNMPv2c • SNMPv3

22. SNMP Applications: MIB Browsers • MIB browsers are specialized tools used to examine the values of MIB object instances on a given agent. A MIB browser can be a fully integerated GUI- based application or a simple text-based one.

23. Managed Objects: • Managed objects are the basic unit of exchange between an NMS and Nes. The managed objects are defined in theMIB and deployed in the network.

24. There is only one MIB: • One merit of a standard MIB is ease of extension. As new technologies are invented and deployed, the associated managed objects must be defined in new MIB modules. The latter can then be added to the standard MIB in an orderly fashion, Ex: by using enterprise specific numbers.

25. Some characteristics of intelligent line cards include the following • They can extend the lifespan of the host adding advanced functions such as SNMP and VoIP for a PABX. • They can take a long time to develop. • Operators like to extract the maximum performance from them. Ex: port bandwidth. • They increasingly incorporate numerous layer 1,2, and 3 protocols.

26. Network Elements • An example of an NE is an intelligent line card, which is hosted inside another system, such as a PABX, ATM/MPLS switch, or IP router Command generators create SNMP messages.

27. Analogy for an NMS • MIB modules • Applications-agents and managers • Devices-remote Nes • Soft objects-connections, paths, interfaces, and so on.

28. Analogy for an NMS • In the case of operating systems, some of the abstract objects are: • Files • Applications • Processes • Devices, such as hard disks and network interfaces • Soft objects, such as print jobs and semaphores.