NETI-DTM-MIB: View SNMP OID List / Download MIB

The Net Insight DTM MIB. The MIB implements objects for managing the DTM configuration in a network element.

The table of addressing information relevant to this entity's DTM addresses.

The addressing information for one of this entity's DTM addresses.

An arbitrary index in the link table.

The DTM address to which this entry's addressing information pertains.

Indicates if this address is the network address for this entity. There is only one network address for each entity. Values: true(1) This address is an alias. false(2) This address is the 'real' address for this entity.

Indicates the type of address. This type is derived from the prefixes defined below, so this is really just a more user-friendly manner of presenting the address type. unspecified(1) The unspecified address; does not really belong in the address table. Prefix 00.00.00.00.00.00.00.00-64. loopback(2) The loopback address; always assigned to the local node. Prefix 00.00.00.00.00.00.00.01-64. local(3) Site local addresses, prefix 00.00.00.00.00.00.00.00-16 (except the unspecified and loopback addresses). multicast(4) Multicast addresses, prefix FF.00.00.00.00.00.00.00-8. global(5) Global addresses, all other prefixes. Enumeration: 'global': 5, 'multicast': 4, 'local': 3, 'unspecified': 1, 'loopback': 2.

See SNMPv2-TC.

The table of addressing information relevant to this entity's DTM addresses.

The addressing information for one of this entity's DTM addresses.

An arbitrary index in the hosts database table.

The DTM address to which this hosts name is mapped.

The hosts name representing the DTM address. The host name is a text string up to 64 characters drawn from the alphabet (A-Z, a-z), digits (0-9), and minus sign (-). No blank or space characters are permitted as part of a name. No distinction is made between upper and lower case. The first character must be an alpha character. The last character must not be a minus sign or period.

See SNMPv2-TC. The following values are supported: createAndGo(4). A new conceptual row is created representing the mapping between DTM address and DTM host name. destroy(6). The conceptual row is deleted.

A conceptual table containing with DTM interfaces.

An entry in the DTM interface table.

Index in to the table.

The interface name, on the form :, for example 'dtm4:1'. Should correlate to what it says on the front of the actual hardware.

The interfaces DTM physical address, i.e. a MAC identity.

The upper transmit capability (in slots) for this interface. Set to 0 if not known.

The transmit capability (in slots) used for control traffic (when dedicated control channels are used). See also dtmIfreducedCtrlCapacity.

The start slot for owned transmit capability (in slots) for this interface. Valid range is between 1 and the upper transmit capacity of the interface - 1.

The owned transmit capability (in slots) for this interface. Total capacity for use is Owned + Borrowed - Lent. Set to 0 if not known.

The borrowed transmit capability (in slots) for this interface. Set to 0 if not known.

The maximum amount of transmit capability (in slots) that this interface will lend to other interfaces. Set to 0 if not known.

The lent transmit capability (in slots) for this interface. Set to 0 if not known.

The transmit capability (in slots) used for data traffic for this interface.

The upper receive capability (in slots) for this interface. Set to 0 if not known.

The receive capability (in slots) used for data traffic for this interface.

Index in to the MIB-II ifTable. Set to 0 if not known.

The desired state of the interface. The administrative status controls whether the interface should be active or not. Enumeration: 'down': 2, 'up': 1.

The actual state of the interface. The value should follow the state of the Administrative Status (dtmIfAdminStatus) unless something fails, or be `absent' if the interface is absent. Enumeration: 'down': 2, 'absent': 3, 'lowerLayerDown': 4, 'up': 1.

See SNMPv2-TC.

Indicates that a configured interface can not be activated because there are no hardware resources. This happens if the dtmIfAdminStatus is set to `up', and the interface is absent.

Indicates Loss Of Signal from the DTM domain.

Indicates that the node has not been able to allocate dedicated capacity for control traffic.

The lower end of the transmit capability range (in slots) for this interface.

The upper end of the transmit capability range (in slots) for this interface.

The route metric used by the DTM Routing Protocol (DRP) when calculating cost for routing through this interface. The value zero (0) indicates that the DRP protocol shall be disabled for this interface and no routing information shall be exchanged.

The link class controls the behavior of a link when a failure is detected on the link or on the node connected to the remote end of the link. The link class decides which values the dtmLinkStateNodeStatus object can take. A link is monitored with the following mechanisms: - The underlying trunk interface will detect when the signal on the receiving interface disappears or is impossible to use due to errors. This is called a Signal Failure. - The communication with the node at the remote end of the link is monitored by periodically sending messages, and expecting responses. If no response is received within a reasonable time, a failure is assumed. This is called a Supervision Failure. The error detection mechanisms can detect failures in one or both directions of a bi-directional link. If a failure is detected in only one direction of a bi-directional link and there is another fully working link in the opposite direction, the remaining working links will all have status `up'. The link classes are: normal(1) If either a Signal Failure or Supervision Failure is detected on the link, the link is considered as `down' and its entry is removed from the dtmLinkStateTable. persistent(2) If a Signal Failure is detected on the link, the link is considered as `down' and its entry is removed from the dtmLinkStateTable. If a Supervision Failure is detected on the link, the object dtmLinkStateIfNodeStatus for the link is assigned `noControl'. nailed(3) If a Signal Failure is detected on the link, the object dtmLinkStateIfNodeStatus for the link is assigned `downKeep'. If a Supervision Failure is detected on the link, the object dtmLinkStateIfNodeStatus for the link is assigned `noControl'. Enumeration: 'nailed': 3, 'persistent': 2, 'normal': 1.

A string describing the purpose of the interface. The string is for administrative use.

Controls if the trunk interface on which this interface is stacked on top, can be considered a source for synchronization. disabled(1) The interface shall not be considered. enabled(2). The interface shall be considered. Enumeration: 'disabled': 1, 'enabled': 2.

This is the time the link information table last changed.

The number of entries in the link table.

The link information table.

One entry per discovered link.

An arbitrary index in the link table.

The 'simple' topological type of the link: unknown(1) Type cannot be determined. looped(2) Looped topology; i.e. a ring. open(3) Open topology; i.e. part of a bus. Enumeration: 'unknown': 1, 'looped': 2, 'open': 3.

The name of the local interface that belongs to the link.

The number of entries in the link interface table.

The link interface information table.

One entry for every interface on each link. On each link the interfaces are ordered in downstream order.

An arbitrary index in the link interface table.

The interfaces DTM physical address, i.e. a MAC identity.

The node DTM physical address, i.e. a MAC identity.

The nodes network DTM address. Returns the unspecified address (00.00.00.00.00.00.00.00) if unknown.

The name of the sub-interface that is connected to this link, e.g. 'dtm2:1/rx' for a receiving part of an interface, or dtm2:1/tx for a transmitting part of an interface.

The status of the communication with the neighboring node via this link. The link entry is removed from this table when the link is down. notApplicable(0) This value notApplicable(0) is always set for the entry representing the local node, and never set for any other entry. up(1) The communication with the neighboring node is fully functioning. This is the only state where it is possible to establish new channels over the link. recover(2) The neighboring node is in a recovery state after a node or control function sub-system failure, where it is in the process of recovering the state of all channels. When the process of recovering the channels is completed, the state will change to either up(1) if all channels state were successfully recovered, or limited(3) if the state of any channels failed to be recovered. limited(3) The neighboring node is not or has not been able to recover the state of all its channels after a node or control function sub-system failure. The already existing channels over the link may be fully functional, but the neighboring node is not accepting any channel signaling. The link must be taken down by the neighboring node for its control function sub-system to be able to assume a known state, which typically requires operator intervention. noControl(4) A valid signal is detected from the neighboring node, but the control function sub-system on the neighboring node is not responding, indicating a remote node or control function sub-system failure. Signaling to the neighboring node is thus not possible. Already existing channels over the link may be fully functional. downKeep(5) The bi-directional communication with the neighboring node is lost. The link is not removed because the interface link class is configured as nailed. pending(6) This status is only valid for the entry representing the receiving sub-interface. Indicates that a neighbor has been detected on the receiving part of an interface, but no bi-directional communication has yet been established with the neighboring node. loopback(7) This status is only valid for the entry representing the receiving sub-interface. The link is connected from an interface located on the local node. Enumeration: 'limited': 3, 'loopback': 7, 'noControl': 4, 'up': 1, 'notApplicable': 0, 'downKeep': 5, 'recover': 2, 'pending': 6.

The route metric used by the DTM Routing Protocol (DRP) when calculating cost for routing through this node. The value zero (0) means no cost.

The type of node as seen by the DTM Routing Protocol (DRP). switch(1) The node is to be considered located within the network, where channels may be switched via this node. endNode(2) The node is to be considered located the edge of a network, and channels only originates or terminates on this node. The node does not participate in DRP. Enumeration: 'endNode': 2, 'switch': 1.

The DTM Routing Protocol (DRP) area number. The value zero (0) indicates that the area number is unconfigured.

Defines if the area number shall be detected automatically. true(1) If set to `true', and if the area number (dtmDrpAreaNumber) is unconfigured, then the node will assume the area number of its neighboring nodes. false(2) The area number is not automatically detected.

Defines if the default gateway shall be detected automatically by DTM Routing Protocol (DRP). true(1) The default gateway is automatically detected. false(2) The default gateway is not automatically detected.

This object describes and controls the control function sub-system on the node. up(1) The control function sub-system is fully functioning. This is the only state where it is possible to establish new channels. This is the only value possible to write to this object. When writing this value, the control function sub-system is forced to this state, which may result in all established channels to be removed or re-established. recover(2) The control function sub-system is in the process of recovering the state of all channels after a node or control function sub-system failure, where it is When the process of recovering the channels is completed, the state will change to either up(1) if all channels state were successfully recovered, or limited(3) if the state of any channels failed to be recovered. limited(3) The control function sub-system is not or has not been able to recover the state of all its channels after a node or control function sub-system failure. The already existing channels through the node may be fully functional, but it is not accepting any channel signaling. All link must be taken down for the control function sub-system to be able to assume a known state, which typically requires operator intervention. This state can be exited by writing up(1) to the object. noControl(4) The control function sub-system is failing and is not responding. Signaling to the neighboring node is thus not possible. Already existing channels through the node may still be fully functional, but their state is not known. This state can be exited by writing up(1) to the object. Enumeration: 'limited': 3, 'recover': 2, 'up': 1, 'noControl': 4.

The value of this object is only used if any DTM interface (table dtmIfTable) is configured as persistent (e.g. dtmIfLinkClass is `persistent' or `nailed'). It is controlling what status (dtmNodeStatus) the node shall enter when it reboots or the control function sub-system restarts. Note that the node always enters status `up' at cold-start. true(1) The node shall enter the status (dtmNodeStatus) `up'. All channels are torn down. false(2) The node shall enter the status (dtmNodeStatus) `noControl' or `limited', as applicable.

The physical identity of the node. This is a fixed, unique address for each node.

The physical identity of the node that is the origin of the synchronization of this node, i.e. the node where the timing reference is connected.

The name of the currently used timing source. If the node is synchronized from an interface that is derived from a DTM interface, then this name is the name of the DTM interface.

The physical identity of the node on the peering side of the interface identified by dtmCurrentTimingSourceName. This identifies the neighboring node from where the synchronization is taken. If the node is synchronized from a local interface, i.e. not from a timing source derived from a trunk interface but instead from a connected timing reference or the local oscillator, then the this is the id of the local node (dtmNodeId).

The time scale status of the synchronization clock of this node. notSupported(1) Time Transfer is not supported or not enabled. uninitiated(2) The initial state which indicates that the time of the time scale is not initiated and may not be used for any time keeping. The time scale is however running, so it may be used for relative measures such as those used in round-trip estimates. During the uninitiated state the Time Transfer Control Processing attempts to initiate the TAI/UTC time from either another DTM node in state compensated, or some local UTC source. When the such a source is available, it reassigns the time scale and enters the reassigned state. reassigned(3) When the time scale of this node have a degenerated time-offset from neighbor nodes being compensated, or a local TAI/UTC source, the node reassigns the time scale and enters the reassigned state, during which the time scale may not be used for precision time-keeping. During the reassigned state the Time Transfer Control Processing attempts to retrace the TAI/UTC time from either another DTM node in state compensated, or some local TAI/UTC source. When the retracing have reduced the time error to within defined limits (1 us), it enters the compensated state. compensated(4) When the time scale of the node has been initiated to TAI/UTC, it can be used for time keeping, but the time error of the time scale is too high (and thus stability and precision is limited). During the compensated state the Time Transfer Control Processing will use the TLL to maintain the TAI/UTC time scale from any neighboring nodes in the compensated state. Enumeration: 'uninitiated': 2, 'reassigned': 3, 'notSupported': 1, 'compensated': 4.

The index of the dtmTimeSourceEntry of the time source that is used as calibration reference. The special value 0 is used if the field is not set, and means that the node clock is used as reference.

A conceptual table containing time sources associated to time transfer capable interfaces.

An entry in the time source table.

Index in the dtmTimeSourceTable.

The name of the time source.

The desired state of the interface. The administrative status controls whether the time source should be active or not. Enumeration: 'down': 2, 'up': 1.

The actual state of the time source. The value should follow the state of the Administrative Status (dtmIfAdminStatus) unless something fails (dtmTimeSourceOperStatus=down), `dormant' if another time source is the active time source or be `absent' if the associated interface is not present. Enumeration: 'down': 2, 'absent': 3, 'lowerLayerDown': 4, 'up': 1, 'dormant': 5.

The type of time interface that provides the time source represented by this entry. dsyp(1) A DTM synchronization source (dsyp) represents a DTM interface timing source and the synchronization control information is distributed using the DTM Synchronization Protocol (DSYP). sqc(2) A squelchable clock (sqc) represents a clock interface that squelches its output to announce that it can not provide a source at the expected quality level. ssm(3) An SSM clock (ssm) represents a clock interface that also transports the Quality Level (QL) as a 4-bit Synchronization Signal Marker (SSM). internal(4) An internal clock (internal) represents a holdover clock that is internal to the node. Enumeration: 'dsyp': 1, 'sqc': 2, 'internal': 4, 'ssm': 3.

A reference to the time interface that provides the time source represented by this entry. The value .0.0 is used when no such reference is available.

The round trip time in nanoseconds for sending data to the peer of the time interface providing this time source and back. The value 0 is used, the round trip time is not available.

The time error in nanoseconds of the time source relative the node clock. The value 0 is used when the time error is not available.

The time error in nanoseconds of the time source relative the calibration reference. The value 0 is used when the time error is not available.

The configured calibration offset in ppm compared to the nominal value of of the one-way (i.e. remote to local) to round trip time ratio. The nominal value of the ratio is 1/2, which is equivalent to a value of 0.