MIOX25-MIB: View SNMP OID List / Download MIB

VENDOR: INTERNET-STANDARD


 Home MIB: MIOX25-MIB
Download as:   
SNMPv2-CONF, RFC1316-MIB, IF-MIB, RFC1381-MIB, SNMPv2-SMI, RFC1382-MIB, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 miox 1.3.6.1.2.1.10.38
       mioxPle 1.3.6.1.2.1.10.38.1
           mioxPleTable 1.3.6.1.2.1.10.38.1.1 no-access
This table contains information relative to an interface to an X.25 Packet Level Entity (PLE).
               mioxPleEntry 1.3.6.1.2.1.10.38.1.1.1 no-access
These objects manage the encapsulation of other protocols within X.25.
                   mioxPleMaxCircuits 1.3.6.1.2.1.10.38.1.1.1.1 integer read-write
The maximum number of X.25 circuits that can be open at one time for this interface. A value of zero indicates the interface will not allow any additional circuits (as it may soon be shutdown). A value of 2147483647 allows an unlimited number of circuits.
                   mioxPleRefusedConnections 1.3.6.1.2.1.10.38.1.1.1.2 counter read-only
The number of X.25 calls from a remote systems to this system that were cleared by this system. The interface instance should identify the X.25 interface the call came in on.
                   mioxPleEnAddrToX121LkupFlrs 1.3.6.1.2.1.10.38.1.1.1.3 counter read-only
The number of times a translation from an Encapsulated Address to an X.121 address failed to find a corresponding X.121 address. Encapsulated addresses can be looked up in the mioxPeerTable or translated via an algorithm as for the DDN. Addresses that are successfully recognized do not increment this counter. Addresses that are not recognized (reflecting an abnormal packet delivery condition) increment this counter. If an address translation fails, it may be difficult to determine which PLE entry should count the failure. In such cases the first likely entry in this table should be selected. Agents should record the failure even if they are unsure which PLE should be associated with the failure.
                   mioxPleLastFailedEnAddr 1.3.6.1.2.1.10.38.1.1.1.4 octet string read-only
The last Encapsulated address that failed to find a corresponding X.121 address and caused mioxPleEnAddrToX121LkupFlrs to be incremented. The first octet of this object contains the encapsulation type, the remaining octets contain the address of that type that failed. Thus for an IP address, the length will be five octets, the first octet will contain 204 (hex CC), and the last four octets will contain the IP address. For a snap encapsulation, the first byte would be 128 (hex 80) and the rest of the octet string would have the snap header.
                   mioxPleEnAddrToX121LkupFlrTime 1.3.6.1.2.1.10.38.1.1.1.5 timeticks read-only
The most recent value of sysUpTime when the translation from an Encapsulated Address to X.121 address failed to find a corresponding X.121 address.
                   mioxPleX121ToEnAddrLkupFlrs 1.3.6.1.2.1.10.38.1.1.1.6 counter read-only
The number of times the translation from an X.121 address to an Encapsulated Address failed to find a corresponding Encapsulated Address. Addresses successfully recognized by an algorithm do not increment this counter. This counter reflects the number of times call acceptance encountered the abnormal condition of not recognizing the peer.
                   mioxPleLastFailedX121Address 1.3.6.1.2.1.10.38.1.1.1.7 x121address read-only
The last X.121 address that caused mioxPleX121ToEnAddrLkupFlrs to increase.
                   mioxPleX121ToEnAddrLkupFlrTime 1.3.6.1.2.1.10.38.1.1.1.8 timeticks read-only
The most recent value of sysUpTime when the translation from an X.121 address to an Encapsulated Address failed to find a corresponding Encapsulated Address.
                   mioxPleQbitFailures 1.3.6.1.2.1.10.38.1.1.1.9 counter read-only
The number of times a connection was closed because of a Q-bit failure.
                   mioxPleQbitFailureRemoteAddress 1.3.6.1.2.1.10.38.1.1.1.10 x121address read-only
The remote address of the most recent (last) connection that was closed because of a Q-bit failure.
                   mioxPleQbitFailureTime 1.3.6.1.2.1.10.38.1.1.1.11 timeticks read-only
The most recent value of sysUpTime when a connection was closed because of a Q-bit failure. This will also be the last time that mioxPleQbitFailures was incremented.
                   mioxPleMinimumOpenTimer 1.3.6.1.2.1.10.38.1.1.1.12 positiveinteger read-write
The minimum time in milliseconds this interface will keep a connection open before allowing it to be closed. A value of zero indicates no timer.
                   mioxPleInactivityTimer 1.3.6.1.2.1.10.38.1.1.1.13 positiveinteger read-write
The amount of time time in milliseconds this interface will keep an idle connection open before closing it. A value of 2147483647 indicates no timer.
                   mioxPleHoldDownTimer 1.3.6.1.2.1.10.38.1.1.1.14 positiveinteger read-write
The hold down timer in milliseconds. This is the minimum amount of time to wait before trying another call to a host that was previously unsuccessful. A value of 2147483647 indicates the host will not be retried.
                   mioxPleCollisionRetryTimer 1.3.6.1.2.1.10.38.1.1.1.15 positiveinteger read-write
The Collision Retry Timer in milliseconds. The time to delay between call attempts when the maximum number of circuits is exceeded in a call attempt.
                   mioxPleDefaultPeerId 1.3.6.1.2.1.10.38.1.1.1.16 instancepointer read-write
This identifies the instance of the index in the mioxPeerTable for the default parameters to use with this interface. The entry identified by this object may have a zero length Encapsulation address and a zero length X.121 address. These default parameters are used with connections to hosts that do not have entries in the mioxPeerTable. Such connections occur when using ddn-x25 IP-X.25 address mapping or when accepting connections from other hosts not in the mioxPeerTable. The mioxPeerEncTable entry with the same index as the mioxPeerTable entry specifies the call encapsulation types this PLE will accept for peers not in the mioxPeerTable. If the mioxPeerEncTable doesn't contain any entries, this PLE will not accept calls from entries not in the mioxPeerTable.
       mioxPeer 1.3.6.1.2.1.10.38.2
           mioxPeerTable 1.3.6.1.2.1.10.38.2.1 no-access
This table contains information about the possible peers this machine may exchange packets with.
               mioxPeerEntry 1.3.6.1.2.1.10.38.2.1.1 no-access
Per peer information.
                   mioxPeerIndex 1.3.6.1.2.1.10.38.2.1.1.1 positiveinteger read-only
An index value that distinguished one entry from another. This index is independent of any other index.
                   mioxPeerStatus 1.3.6.1.2.1.10.38.2.1.1.2 integer read-write
This reports the status of a peer entry. A value of valid indicates a normal entry that is in use by the agent. A value of underCreation indicates a newly created entry which isn't yet in use because the creating management station is still setting values. The value of invalid indicates the entry is no longer in use and the agent is free to delete the entry at any time. A management station is also free to use an entry in the invalid state. Entries are created by setting a value of createRequest. Only non-existent or invalid entries can be set to createRequest. Upon receiving a valid createRequest, the agent will create an entry in the underCreation state. This object can not be set to a value of underCreation directly, entries can only be created by setting a value of createRequest. Entries that exist in other than the invalid state can not be set to createRequest. Entries with a value of underCreation are not used by the system and the management station can change the values of other objects in the table entry. Management stations should also remember to configure values in the mioxPeerEncTable with the same peer index value as this peer entry. An entry in the underCreation state can be set to valid or invalid. Entries in the underCreation state will stay in that state until 1) the agent times them out, 2) they are set to valid, 3) they are set to invalid. If an agent notices an entry has been in the underCreation state for an abnormally long time, it may decide the management station has failed and invalidate the entry. A prudent agent will understand that the management station may need to wait for human input and will allow for that possibility in its determination of this abnormally long period. Once a management station has completed all fields of an entry, it will set a value of valid. This causes the entry to be activated. Entries in the valid state may also be set to makeCall or clearCall to make or clear X.25 calls to the peer. After such a set request the entry will still be in the valid state. Setting a value of makeCall causes the agent to initiate an X.25 call request to the peer specified by the entry. Setting a value of clearCall causes the agent to initiate clearing one X.25 call present to the peer. Each set request will initiate another call or clear request (up to the maximum allowed); this means that management stations that fail to get a response to a set request should query to see if a call was in fact placed or cleared before retrying the request. Entries not in the valid state can not be set to makeCall or clearCall. The values of makeCall and clearCall provide for circuit control on devices which perform Ethernet Bridging using static circuit assignment without address recognition; other devices which dynamically place calls based on destination addresses may reject such requests. An agent that (re)creates a new entry because of a set with createRequest, should also (re)create a mioxPeerEncTable entry with a mioxPeerEncIndex of 1, and a mioxPeerEncType of 204 (hex CC). Enumeration: 'makeCall': 6, 'clearCall': 5, 'invalid': 4, 'underCreation': 3, 'createRequest': 2, 'valid': 1.
                   mioxPeerMaxCircuits 1.3.6.1.2.1.10.38.2.1.1.3 positiveinteger read-write
The maximum number of X.25 circuits allowed to this peer.
                   mioxPeerIfIndex 1.3.6.1.2.1.10.38.2.1.1.4 positiveinteger read-write
The value of the ifIndex object for the interface to X.25 to use to call the peer.
                   mioxPeerConnectSeconds 1.3.6.1.2.1.10.38.2.1.1.5 counter read-only
The number of seconds a call to this peer was active. This counter will be incremented by one for every second a connection to a peer was open. If two calls are open at the same time, one second of elapsed real time will results in two seconds of connect time.
                   mioxPeerX25CallParamId 1.3.6.1.2.1.10.38.2.1.1.6 instancepointer read-write
The instance of the index object in the x25CallParmTable from RFC 1382 for the X.25 call parameters used to communicate with the remote host. The well known value {0 0} indicates no call parameters specified.
                   mioxPeerEnAddr 1.3.6.1.2.1.10.38.2.1.1.7 octet string read-write
The Encapsulation address of the remote host mapped by this table entry. A length of zero indicates the remote IP address is unknown or unspecified for use as a PLE default. The first octet of this object contains the encapsulation type, the remaining octets contain an address of that type. Thus for an IP address, the length will be five octets, the first octet will contain 204 (hex CC), and the last four octets will contain the IP address. For a snap encapsulation, the first byte would be 128 (hex 80) and the rest of the octet string would have the snap header.
                   mioxPeerX121Address 1.3.6.1.2.1.10.38.2.1.1.8 x121address read-write
The X.25 address of the remote host mapped by this table entry. A zero length string indicates the X.25 address is unspecified for use as the PLE default.
                   mioxPeerX25CircuitId 1.3.6.1.2.1.10.38.2.1.1.9 instancepointer read-write
This object identifies the instance of the index for the X.25 circuit open to the peer mapped by this table entry. The well known value {0 0} indicates no connection currently active. For multiple connections, this identifies the index of a multiplexing table entry for the connections. This can only be written to configure use of PVCs which means the identified circuit table entry for a write must be a PVC.
                   mioxPeerDescr 1.3.6.1.2.1.10.38.2.1.1.10 displaystring read-write
This object returns any identification information about the peer. An agent may supply the comment information found in the configuration file entry for this peer. A zero length string indicates no information available.
           mioxPeerEncTable 1.3.6.1.2.1.10.38.2.2 no-access
This table contains the list of encapsulations used to communicate with a peer. This table has two indexes, the first identifies the peer, the second distinguishes encapsulation types. The first index identifies the corresponding entry in the mioxPeerTable. The second index gives the priority of the different encapsulations. The encapsulation types are ordered in priority order. For calling a peer, the first entry (mioxPeerEncIndex of 1) is tried first. If the call doesn't succeed because the remote host clears the call due to incompatible call user data, the next entry in the list is tried. Each entry is tried until the list is exhausted. For answering a call, the encapsulation type requested by the peer must be found the list or the call will be refused. If there are no entries in this table for a peer, all call requests from the peer will be refused. Objects in this table can only be set when the mioxPeerStatus object with the same index has a value of underCreation. When that status object is set to invalid and deleted, the entry in this table with that peer index must also be deleted.
               mioxPeerEncEntry 1.3.6.1.2.1.10.38.2.2.1 no-access
Per connection information.
                   mioxPeerEncIndex 1.3.6.1.2.1.10.38.2.2.1.1 positiveinteger read-only
The second index in the table which distinguishes different encapsulation types.
                   mioxPeerEncType 1.3.6.1.2.1.10.38.2.2.1.2 integer read-write
The value of the encapsulation type. For IP encapsulation this will have a value of 204 (hex CC). For SNAP encapsulated packets, this will have a value of 128 (hex 80). For CLNP, ISO 8473, this will have a value of 129 (hex 81). For ES-ES, ISO 9542, this will have a value of 130 (hex 82). A value of 197 (hex C5) identifies the Blacker X.25 encapsulation. A value of 0, identifies the Null encapsulation. This value can only be written when the mioxPeerStatus object with the same mioxPeerIndex has a value of underCreation. Setting this object to a value of 256 deletes the entry. When deleting an entry, all other entries in the mioxPeerEncTable with the same mioxPeerIndex and with an mioxPeerEncIndex higher then the deleted entry, will all have their mioxPeerEncIndex values decremented by one.