-
--- WinAgents MIB Extraction Wizard\r
--- Extracted from rfc1213.txt 16.03.2005 20:20:14\r
-\r
-RFC1213-MIB DEFINITIONS ::= BEGIN\r
-\r
-IMPORTS\r
- mgmt, NetworkAddress, IpAddress, Counter, Gauge,\r
- TimeTicks\r
- FROM RFC1155-SMI\r
- OBJECT-TYPE\r
- FROM RFC-1212;\r
-\r
--- This MIB module uses the extended OBJECT-TYPE macro as\r
--- defined in [14];\r
-\r
-\r
--- MIB-II (same prefix as MIB-I)\r
-\r
-mib-2 OBJECT IDENTIFIER ::= { mgmt 1 }\r
-\r
--- textual conventions\r
-\r
-DisplayString ::=\r
- OCTET STRING\r
--- This data type is used to model textual information taken\r
--- from the NVT ASCII character set. By convention, objects\r
--- with this syntax are declared as having\r
-\r
---\r
--- SIZE (0..255)\r
-\r
-PhysAddress ::=\r
- OCTET STRING\r
--- This data type is used to model media addresses. For many\r
--- types of media, this will be in a binary representation.\r
--- For example, an ethernet address would be represented as\r
--- a string of 6 octets.\r
-\r
-\r
--- groups in MIB-II\r
-\r
-system OBJECT IDENTIFIER ::= { mib-2 1 }\r
-\r
-interfaces OBJECT IDENTIFIER ::= { mib-2 2 }\r
-\r
-at OBJECT IDENTIFIER ::= { mib-2 3 }\r
-\r
-ip OBJECT IDENTIFIER ::= { mib-2 4 }\r
-\r
-icmp OBJECT IDENTIFIER ::= { mib-2 5 }\r
-\r
-tcp OBJECT IDENTIFIER ::= { mib-2 6 }\r
-\r
-udp OBJECT IDENTIFIER ::= { mib-2 7 }\r
-\r
-egp OBJECT IDENTIFIER ::= { mib-2 8 }\r
-\r
--- historical (some say hysterical)\r
--- cmot OBJECT IDENTIFIER ::= { mib-2 9 }\r
-\r
-transmission OBJECT IDENTIFIER ::= { mib-2 10 }\r
-\r
-snmp OBJECT IDENTIFIER ::= { mib-2 11 }\r
-\r
-\r
--- the System group\r
-\r
--- Implementation of the System group is mandatory for all\r
--- systems. If an agent is not configured to have a value\r
--- for any of these variables, a string of length 0 is\r
--- returned.\r
-\r
-\r
-IfEntry ::=\r
- SEQUENCE {\r
- ifIndex\r
- INTEGER,\r
-\r
- ifDescr\r
- DisplayString,\r
- ifType\r
- INTEGER,\r
- ifMtu\r
- INTEGER,\r
- ifSpeed\r
- Gauge,\r
- ifPhysAddress\r
- PhysAddress,\r
- ifAdminStatus\r
- INTEGER,\r
- ifOperStatus\r
- INTEGER,\r
- ifLastChange\r
- TimeTicks,\r
- ifInOctets\r
- Counter,\r
- ifInUcastPkts\r
- Counter,\r
- ifInNUcastPkts\r
- Counter,\r
- ifInDiscards\r
- Counter,\r
- ifInErrors\r
- Counter,\r
- ifInUnknownProtos\r
- Counter,\r
- ifOutOctets\r
- Counter,\r
- ifOutUcastPkts\r
- Counter,\r
- ifOutNUcastPkts\r
- Counter,\r
- ifOutDiscards\r
- Counter,\r
- ifOutErrors\r
- Counter,\r
- ifOutQLen\r
- Gauge,\r
- ifSpecific\r
- OBJECT IDENTIFIER\r
- }\r
-\r
-\r
--- the Address Translation group\r
-\r
--- Implementation of the Address Translation group is\r
--- mandatory for all systems. Note however that this group\r
--- is deprecated by MIB-II. That is, it is being included\r
-\r
--- solely for compatibility with MIB-I nodes, and will most\r
--- likely be excluded from MIB-III nodes. From MIB-II and\r
--- onwards, each network protocol group contains its own\r
--- address translation tables.\r
-\r
--- The Address Translation group contains one table which is\r
--- the union across all interfaces of the translation tables\r
--- for converting a NetworkAddress (e.g., an IP address) into\r
--- a subnetwork-specific address. For lack of a better term,\r
--- this document refers to such a subnetwork-specific address\r
--- as a `physical' address.\r
-\r
--- Examples of such translation tables are: for broadcast\r
--- media where ARP is in use, the translation table is\r
--- equivalent to the ARP cache; or, on an X.25 network where\r
--- non-algorithmic translation to X.121 addresses is\r
--- required, the translation table contains the\r
--- NetworkAddress to X.121 address equivalences.\r
-\r
-\r
-AtEntry ::=\r
- SEQUENCE {\r
- atIfIndex\r
- INTEGER,\r
-\r
- atPhysAddress\r
- PhysAddress,\r
- atNetAddress\r
- NetworkAddress\r
- }\r
-\r
-\r
-\r
-\r
-\r
--- the IP address table\r
-\r
--- The IP address table contains this entity's IP addressing\r
--- information.\r
-\r
-\r
-IpAddrEntry ::=\r
- SEQUENCE {\r
- ipAdEntAddr\r
- IpAddress,\r
- ipAdEntIfIndex\r
- INTEGER,\r
- ipAdEntNetMask\r
- IpAddress,\r
- ipAdEntBcastAddr\r
- INTEGER,\r
- ipAdEntReasmMaxSize\r
- INTEGER (0..65535)\r
- }\r
-\r
-\r
-IpRouteEntry ::=\r
- SEQUENCE {\r
- ipRouteDest\r
- IpAddress,\r
- ipRouteIfIndex\r
- INTEGER,\r
- ipRouteMetric1\r
- INTEGER,\r
- ipRouteMetric2\r
- INTEGER,\r
- ipRouteMetric3\r
- INTEGER,\r
- ipRouteMetric4\r
- INTEGER,\r
- ipRouteNextHop\r
- IpAddress,\r
- ipRouteType\r
- INTEGER,\r
- ipRouteProto\r
- INTEGER,\r
- ipRouteAge\r
- INTEGER,\r
- ipRouteMask\r
- IpAddress,\r
- ipRouteMetric5\r
- INTEGER,\r
-\r
- ipRouteInfo\r
- OBJECT IDENTIFIER\r
- }\r
-\r
-\r
-IpNetToMediaEntry ::=\r
- SEQUENCE {\r
- ipNetToMediaIfIndex\r
- INTEGER,\r
- ipNetToMediaPhysAddress\r
- PhysAddress,\r
- ipNetToMediaNetAddress\r
- IpAddress,\r
- ipNetToMediaType\r
- INTEGER\r
- }\r
-\r
-\r
-\r
-TcpConnEntry ::=\r
- SEQUENCE {\r
- tcpConnState\r
- INTEGER,\r
- tcpConnLocalAddress\r
- IpAddress,\r
- tcpConnLocalPort\r
- INTEGER (0..65535),\r
- tcpConnRemAddress\r
- IpAddress,\r
- tcpConnRemPort\r
- INTEGER (0..65535)\r
- }\r
-\r
-\r
-UdpEntry ::=\r
- SEQUENCE {\r
- udpLocalAddress\r
- IpAddress,\r
- udpLocalPort\r
- INTEGER (0..65535)\r
- }\r
-\r
-\r
-\r
--- the EGP Neighbor table\r
-\r
--- The EGP neighbor table contains information about this\r
--- entity's EGP neighbors.\r
-\r
-\r
-EgpNeighEntry ::=\r
- SEQUENCE {\r
- egpNeighState\r
- INTEGER,\r
- egpNeighAddr\r
- IpAddress,\r
- egpNeighAs\r
- INTEGER,\r
- egpNeighInMsgs\r
- Counter,\r
- egpNeighInErrs\r
- Counter,\r
- egpNeighOutMsgs\r
- Counter,\r
- egpNeighOutErrs\r
- Counter,\r
-\r
- egpNeighInErrMsgs\r
- Counter,\r
- egpNeighOutErrMsgs\r
- Counter,\r
- egpNeighStateUps\r
- Counter,\r
- egpNeighStateDowns\r
- Counter,\r
- egpNeighIntervalHello\r
- INTEGER,\r
- egpNeighIntervalPoll\r
- INTEGER,\r
- egpNeighMode\r
- INTEGER,\r
- egpNeighEventTrigger\r
- INTEGER\r
- }\r
-\r
-\r
-\r
--- the Transmission group\r
-\r
--- Based on the transmission media underlying each interface\r
--- on a system, the corresponding portion of the Transmission\r
--- group is mandatory for that system.\r
-\r
--- When Internet-standard definitions for managing\r
--- transmission media are defined, the transmission group is\r
--- used to provide a prefix for the names of those objects.\r
-\r
--- Typically, such definitions reside in the experimental\r
--- portion of the MIB until they are "proven", then as a\r
--- part of the Internet standardization process, the\r
--- definitions are accordingly elevated and a new object\r
--- identifier, under the transmission group is defined. By\r
--- convention, the name assigned is:\r
---\r
--- type OBJECT IDENTIFIER ::= { transmission number }\r
---\r
--- where "type" is the symbolic value used for the media in\r
--- the ifType column of the ifTable object, and "number" is\r
--- the actual integer value corresponding to the symbol.\r
-\r
-\r
--- the SNMP group\r
-\r
--- Implementation of the SNMP group is mandatory for all\r
--- systems which support an SNMP protocol entity. Some of\r
--- the objects defined below will be zero-valued in those\r
--- SNMP implementations that are optimized to support only\r
--- those functions specific to either a management agent or\r
--- a management station. In particular, it should be\r
--- observed that the objects below refer to an SNMP entity,\r
--- and there may be several SNMP entities residing on a\r
--- managed node (e.g., if the node is hosting acting as\r
--- a management station).\r
-\r
-\r
-END\r
git.stg.codes / stg.git / blobdiff