TELDAT-MON-FEATURES-TIDP-MASTER-MIB

All MIBs › TELDAT-MON-FEATURES-TIDP-MASTER-MIB

Category: Teldat Router Management

Description: Monitors Teldat router TIDP master feature operational status, session state, and protocol activity counters.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is TELDAT-MON-FEATURES-TIDP-MASTER-MIB?

This MIB module is part of Teldat's proprietary TELDAT-MON-* monitoring family for Teldat routers, covering the router's internal TIDP (Teldat traffic-distribution/data-path) feature in its master role. It exposes operational status data for the feature's session state and protocol activity counters, letting an administrator see whether the TIDP master role is active and how many protocol events it has processed. It is a software-status monitor: it reveals whether the feature process is running, its current session state, and cumulative activity counts, which reveal stalls or restarts rather than any temperature/power hardware data. As a Teldat-proprietary MON MIB it shares the vendor's common enterprise MIB tree structure with the other TELDAT-MON-* modules rather than depending on any external IETF standard. It is deployed on Teldat router families running feature-rich firmware in enterprise or carrier networks where TIDP-based traffic distribution is configured. Engineers can download the TELDAT-MON-FEATURES-TIDP-MASTER-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TELDAT-MON-FEATURES-TIDP-MASTER-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Teldat router

Monitoring Examples

An administrator would poll the session-state and status objects under the TIDP master feature branch to confirm the feature is active rather than standby or failed, and would track protocol activity counters to see event throughput over time. A sudden counter freeze combined with a status change to a non-operational state would indicate the TIDP master process has crashed or lost its peer session. Because no explicit object names were captured for this module, polling in practice would target its *Status and *Counter style leaf objects under the TIDP master feature branch.

What Can Be Monitored

TIDP master operational status
session state
protocol activity counters
feature active/standby state

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

IpAddress

From RFC1213-MIB

DisplayString

From TELDAT-SW-STRUCTURE-MIB

telProdNpMonFeatures

OBJECT-IDENTITY

OIDs

OID symbolic	OID numeric	Type	Access	Description
telProdNpMonFeatTidpMaster	1.3.6.1.4.1.2007.4.1.2.4.5
tidpMasterGlobalGroup	1.3.6.1.4.1.2007.4.1.2.4.5.1
INT tidpMasterGlobalStatus	1.3.6.1.4.1.2007.4.1.2.4.5.1.1	INTEGER	read-only	Indicates whether the TIDP MASTER function is enabled or not. Possible values are: (1) enabled or (2) disabled.
INT tidpMasterGlobalMaxStations	1.3.6.1.4.1.2007.4.1.2.4.5.1.2	INTEGER	read-only	Maximum number of managed stations (routers).
INT tidpMasterGlobalUsedEntries	1.3.6.1.4.1.2007.4.1.2.4.5.1.3	INTEGER	read-only	Number of used entries.
STR tidpMasterGlobalHostnameIsHere	1.3.6.1.4.1.2007.4.1.2.4.5.1.4	DisplayString	read-write	Hostname whose position index is required. This variable is used in conjunction with tidpMasterGlobalEquipmentPosition.
INT tidpMasterGlobalEquipmentPosition	1.3.6.1.4.1.2007.4.1.2.4.5.1.5	INTEGER	read-only	Position index in the table of the equipment entry associated to the hostname specified in tidpMasterGlobalHostnameIsHere (0 if not present).
STR tidpMasterGlobalSerialIsHere	1.3.6.1.4.1.2007.4.1.2.4.5.1.6	DisplayString	read-write	Serial number whose position index is required. This variable is used in conjunction with tidpMasterGlobalEquipmentPosition.
tidpMasterEquipmentTable	1.3.6.1.4.1.2007.4.1.2.4.5.2		not-accessible	This table includes the routers being managed or trying to manage. The maximum number of items in the table is limited by tidpMasterGlobalMaxStations.
tidpMasterEquipmentEntry	1.3.6.1.4.1.2007.4.1.2.4.5.2.1		not-accessible	Each entry contains information about the equipment being managed.
INT tidpMasterEquipmentIndex	1.3.6.1.4.1.2007.4.1.2.4.5.2.1.1	INTEGER	read-only	Table index: order number of the entry or equipment being managed by the TIDP Master.
INT tidpMasterEquipmentStatus	1.3.6.1.4.1.2007.4.1.2.4.5.2.1.2	INTEGER	read-only	Entry status: (0) initial: no operation is being performed. (1) waiting: the management process has begun and is running and the TIDP Master is waiting to get reachability to the remote equipment. (2) managing: the remote equipment is ready to be managed; its IP address is now readable in tidpEquipmentAddress. (3) reset: a reset command has been sent to the remote equipment.
INT tidpMasterEquipmentCommand	1.3.6.1.4.1.2007.4.1.2.4.5.2.1.3	INTEGER	read-write	Command to be performed: (1) manage: begin management process (write-only). (2) delete: end management process (write-only). (3) ok: last command has been performed gracefully (read-only). (4) undefined: last command not finished (read-only). (5) error: last command has not been performed properly (read-only). (6) reset: send a reset to the remote end (write-only).
STR tidpMasterEquipmentHostname	1.3.6.1.4.1.2007.4.1.2.4.5.2.1.4	DisplayString	read-write	Hostname of the equipment being managed. The management process can be performed using hostname or serial number. If it is going to be based on hostname, this variable must be set with the apropriate value before launch the management process. Otherwise, this variable takes a realiable value only when tidpMasterEquipmentStatus is managing(2).
IP tidpMasterEquipmentAddress	1.3.6.1.4.1.2007.4.1.2.4.5.2.1.5	IpAddress	read-only	Router IP address. This variable is readable when tidpMasterEquipmentStatus is managing(2). Otherwise its value is 0.0.0.0 (until the managed router is reachable).
STR tidpMasterEquipmentSerial	1.3.6.1.4.1.2007.4.1.2.4.5.2.1.6	DisplayString	read-write	Serial number of the equipment being managed. The management process can be performed using hostname or serial number. If it is going to be based on serial number, this variable must be set with the apropriate value before launch the management process. Otherwise, this variable takes a realiable value only when tidpMasterEquipmentStatus is managing(2).
INT tidpMasterEquipmentManagementType	1.3.6.1.4.1.2007.4.1.2.4.5.2.1.7	INTEGER	read-write	Management type: (1) manual: manual operation. (2) automatic: automatic operation.
STR tidpMasterEquipmentManagerIdentifier	1.3.6.1.4.1.2007.4.1.2.4.5.2.1.8	DisplayString	read-write	Manager identifier. It is usually the IP address of the management station that requested the router management.
INT tidpMasterEquipmentError	1.3.6.1.4.1.2007.4.1.2.4.5.2.1.9	INTEGER	read-only	If the value of this variable is not 0 (none, not error) when the variable tidpMasterEquipmentStatus takes the value 2 (managing) something went wrong during management process. Before management process begins, this value will be 3 (connection-lost) initially and it will change to 4 (netification-received) when the TIDP master receives a notification packet from the equipment which is trying to be managed.

RFC description

Monitoring MIB for Teldat IP Discovery Protocol (TIDP) master service, managing remote device discovery and error notification.

Start monitoring Teldat routers with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download TELDAT-MON-FEATURES-TIDP-MASTER-MIB

What Is TELDAT-MON-FEATURES-TIDP-MASTER-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description