COMTEK-VMS-NM-SYSMGR-MIB :: sCfgCritFile

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCOMTEK-VMS-NM-SYSMGR-MIBsCfgCritFile

sCfgCritFile

Module: COMTEK-VMS-NM-SYSMGR-MIB

OID (symbolic): COMTEK-VMS-NM-SYSMGR-MIB::sCfgCritFile

OID (numeric): 1.3.6.1.4.1.597.4.3.5.3

Node type: OBJECT-TYPE

Type: DisplayString

Access: read-write

Description: Name of the file currently being used to identify critical processes. This file is associated with the logical name COMTEK$SYSMGR_CRITPROC. Changing this variable redefines the COMTEK$SYSMGR_CRITPROC logical name. NM*SysMgr must be reinitialized (by setting the variable sCfgReinitSubagent to true) before the new critical process file is used. If a set-request is performed on this variable and the specified file name does not exist, is not accessible by the subagent, or contains invalid data, the file name is not changed, an error is returned, and a sSwErr trap is generated describing the error.

Set-requests: Take effect only after reinitialization (sCfgReinitSubagent)

NOTE: To make changes to this value permanent across system reboots, the definition of this logical name must also be changed in the system startup procedures.

What is sCfgCritFile?

This is the name of the file currently used to identify critical processes, tied to the logical name COMTEK$SYSMGR_CRITPROC. An administrator can change this value to point at a different critical-process definition file, though the subagent must be reinitialized via sCfgReinitSubagent before the new file's contents take effect. For example, an administrator adding a newly deployed service to the critical process list would edit that file and then update sCfgCritFile before reinitializing.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.597.4.3.5.3
snmpwalk -v2c -c public <target> COMTEK-VMS-NM-SYSMGR-MIB::sCfgCritFile

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.597.4.3.5.3.1
snmpget -v2c -c public <target> COMTEK-VMS-NM-SYSMGR-MIB::sCfgCritFile.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.597.4.3.5.3.1 s <value>

Start monitoring Comtek VMS-managed network element with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the COMTEK-VMS-NM-SYSMGR-MIB::sCfgCritFile OID value, configure state conditions and alerts, and monitor any Comtek VMS-managed network element from a single console.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
Numeric OIDNameModule
1.3.6.1.4.1.597comtekCOMTEK-VMS-NM-SYSMGR-MIB
1.3.6.1.4.1.597.4comtekVmsCOMTEK-VMS-NM-SYSMGR-MIB
1.3.6.1.4.1.597.4.3comtekVmsNMSysMgrMibCOMTEK-VMS-NM-SYSMGR-MIB
1.3.6.1.4.1.597.4.3.5sCfgCOMTEK-VMS-NM-SYSMGR-MIB
1.3.6.1.4.1.597.4.3.5.3sCfgCritFileCOMTEK-VMS-NM-SYSMGR-MIB