ccna 200 301 practice

ccna 200 301 practice.I want to check the MIB variables to know if GiO/O is in the UP/UP stateFigure 19-2 SNMP for monitoring the network Monitoring CPU utilization on a Cisco router is an excellent example of this type of network management. Thanks to SNMP, NMS can periodically sample this value and display this information for network administrators. This information creates a baseline for administrators so that they can easily see when CPU usage is deviating from the normal values for the network. In addition to continuously polling an SNMP-managed device for information about its MIB variables with SNMP's GET command, the device itself can use SNMP traps (traps) to notify without relying on any outside forces when a problem occurs An NMSO trap is an SNMP message sent by a network device that contains a list of the status of the MIB variables, but because the device sends the message unsolicited without being asked, the NMS reacts differently. For example, assume that the G0/0 interface on Router 1 fails, as shown in step of Figure 19-3. By configuring a trap, the router sends an SNMP trap message to the NMS, and this trap message will mark the unavailable status of the G0/0 interface. The NMS software will then send a paper message to the network support staff, a pop-up window will appear on the NMS screen, the correct router will be set to red on the graphical interface, and so on.Figure 19-3 SNMP for Monitoring the NetworkTo send these unsolicited messages from the managed device to the NMS, SNMP has two approaches. Figure 19-3 shows a trap message. The device sends a trap message to the NMS, but there is no acknowledgement that the NMS has received the message; using protocol terminology, these messages are considered unreliable. A later version of the SNMP protocol (version 3) supports an additional process that contains an informational message and can provide an acknowledgement of whether the message was received, and is therefore considered reliable.(1)d (2)c (3) b (4)c (5)d (6)c (7)d (8)cManagement Information BaseAs mentioned in the earlier discussion, the Management Information Base (MIB) defines the variables that allow management software to monitor/control network devices. Formally, the MIB defines individual variables as an object ID (0ID). o The MIB then organizes the OIDs into OIDs with hierarchies, usually displayed as a tree structure, according to the RFC standard.394 Chapter 19 Managing Network Devices The MIB for any given device will include some branches of the MIB tree, some of which contain variables common to most network devices, and some of which contain variables specific to a particular device. The RFC defines a number of common public variables that are used by almost all devices in the MIB. In addition, network device vendors (such as Cisco) are able to define their own private branches of the tree, providing new variables that are specific to their own devices. Figure 19-4 shows the distribution of the MIB structure, which is defined by Cisco Systems. Notice how the OIDs are described by words or numbers to locate specific variables in the tree structure.Figure 19-4 Management Information Base (M old) As another tool that can be employed in a home lab, the freeware SNMPGET tool allows for quick querying of information from the MIB. In Example 19-1, SNMPGET running on a PC obtains a 5-minute exponential moving average of the percentage of CPU busy from the router. Example 19-1 Using SNMP's GET to Get M Old Values[13:22][cisco@NMS~ ]$ snmpget -v2c -c community 10.250.250.14 1.3.6.1.4.1.9.2.1.58.0 SNMPv2-SMI::enterprises.9.2.1.58.0 =INTEGER: 11