NETEXEC-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › NETEXEC-MIB

Category: Network Management

Description: Monitors NetExec network execution and management platform operational parameters.

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 NETEXEC-MIB?

NETEXEC-MIB appears tied to a telecom network element management platform, with object prefixes dsucsu and tyview suggesting a DSU/CSU or digital cross-connect style device family. It exposes a system table describing chassis slot/node identity, system type, software and hardware revision, and channel count, plus network configuration and DACS (Digital Access Cross-connect System) configuration tables. Its monitoring value centers on hardware and software identity/status: dsucsuSysSoftRev and dsucsuSysHardRev let an operator confirm firmware/hardware revisions per slot, dsucsuSysNumChan tracks channel capacity, and the tyviewSysTable/tyviewBroadcastTable likely provide a supervisory view of node status across the platform. As a telecom-oriented MIB it likely coexists with standard IETF interface and physical-layer MIBs, though no explicit dependency is stated in the module description. It is typically deployed in carrier or enterprise telecom equipment rooms managing DSU/CSU or digital cross-connect network elements. Engineers can download the NETEXEC-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in NETEXEC-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

  • DSU/CSU network element
  • digital access cross-connect system (DACS)

Monitoring Examples

An admin would poll dsucsuSysTable/dsucsuSysEntry indexed by dsucsuSysSlot and dsucsuSysNode to inventory each card's dsucsuSysName, dsucsuSysType, and dsucsuSysSoftRev/dsucsuSysHardRev, flagging any slot running an unexpected firmware revision. The dsucsuCfgNetTable/dsucsuCfgNetEntry would be checked against dsucsuCfgNetSlot to confirm network configuration is applied per slot, and dsucsuCfgDacsTable would reveal cross-connect mapping configuration. A slot reporting an unexpectedly low dsucsuSysNumChan could indicate a card fault or misconfiguration.

What Can Be Monitored

  • per-slot software/hardware revision
  • system/node identity
  • channel count
  • per-slot network configuration
  • DACS cross-connect configuration
Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC-1215

TRAP-TYPE

From RFC1155-SMI

Counter
TimeTicks

From RFC1213-MIB

DisplayString
OIDs

RFC description

SNMP MIB module for managing network execution and multiprotocol network operations across distributed systems, providing monitoring and control of remote command execution capabilities.

Start monitoring DSU/CSU network element / digital access cross-connect system (DACS) 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 NETEXEC-MIB