CE+T Power T2S-ETH, Руководство пользователя

Страница: 46 / 96

9. SNMP
9.1 SNMP Configuration
9.1.1 Introduction
This document describes the Management Information Base (MIB) schema design for standalone T2S ETH for SNMP
v1 configuration and T2S ETH with Catena for SNMP V2C and V3 configuration. A MIB schema describes the structure
of information served by a Simple Network Management Protocol Subsystem (SNMP) agent.
9.1.2 General NMS, SNMP Agent and MIB Role
This section describes the Management Information Base’s (MIB’s) and SNMP Agent’s roles.
9.1.2.1 NMS Role
SNMP’s purpose is to report operational status information about networked computing devices to a centralized
Network Management System (NMS) endpoint. The status information is typically polled from an SNMP Agent on
regular intervals by a Network Management System (NMS) Endpoint. Internal status can also be checked by the SNMP
Agent on regular intervals, and when status of certain metrics falls outside pre-defined acceptable tolerances, an
asynchronous Notification is transmitted to the NMS. This notification is termed as a Trap.
9.1.2.2 MIB Role
The MIB file describes the specific format of data provided by the SNMP agent running within the subsystem. The
data is grouped in terms of high level objects, and therefore models a top-down hierarchical design. There exist a high
level object defined in a TOP LEVEL MIB file they are CET-TSI-MIB and CET-TSI-SMI
9.1.2.3 SNMP Agent Role
An agent is a network-management software module that resides on a managed device. An agent has local knowledge
of management information and translates that information to or from an SNMP-specific form. A network management
station (NMS) executes applications that monitor and control managed devices. As mentioned above, the SNMP agent’s
purpose is report data elements to a Network Management System tool, such as MG Soft, I reasoning on a periodic
basis. Also, if the system is exhibiting non-ideal behavior, Notifications can be distributed to the NMS on a per incident
basis called the Traps. After Notifications that denote non-conforming or malfunctioning behavior are triggered, the
system may further distribute Notifications indicating the system is back to its normal state.
9.1.3 MIB General Design
This section describes the general design for the T2S ETH and Catena products
9.1.3.1 Industry Identification
The private CET MIB shall be represented by the object identifier 1.3.6.1.4.1.12551, or iso.org.dod.internet.private.
enterprise.cetMIB.
The TSI MIB shall be named cetTSI and will be located as a child object of the cetMIB, using object identifier
1.3.6.1.4.1.12551.4, taking the next available spot at the top level of the cet MIB’s Products node.
46 – Monitoring T2S - ETH User Manual – v1.4
SNMP