BCN-COMMANDSERVER-MIB :: bcnCommandServerSerOperState

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › BCN-COMMANDSERVER-MIB › bcnCommandServerSerOperState

bcnCommandServerSerOperState

Module: BCN-COMMANDSERVER-MIB

OID (symbolic): BCN-COMMANDSERVER-MIB::bcnCommandServerSerOperState

OID (numeric): 1.3.6.1.4.1.13315.3.1.7.2.1.1

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: Operational state of the Service. The possible states are: running(1) The service is running normally. notRunning(2) The service is stopped either intentionally (i.e.: the service is not supposed to run on this node) or unintentionally (a problem has occurred). starting(3) The service is in the process of starting, either for the first time of after an event occurred. stopping(4) The service is in the process of stopping. Stopping a service might be necessary after a configuration change. fault(5) An error has been detected and the state is undefined.

What is bcnCommandServerSerOperState?

Reports the current operational state of the BCN Command Server service, indicating whether it is running normally or has stopped. A state of notRunning may signal either an intentional shutdown or an unexpected failure requiring attention.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.13315.3.1.7.2.1.1
snmpwalk -v2c -c public <target> BCN-COMMANDSERVER-MIB::bcnCommandServerSerOperState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.13315.3.1.7.2.1.1.1
snmpget -v2c -c public <target> BCN-COMMANDSERVER-MIB::bcnCommandServerSerOperState.1

Start monitoring BlueCat Networks DNS/DHCP/IPAM appliances with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the BCN-COMMANDSERVER-MIB::bcnCommandServerSerOperState OID value, configure state conditions and alerts, and monitor any BlueCat Networks DNS/DHCP/IPAM appliances from a single console.

How to Use in IPNetwork Monitor

Select a BlueCat Networks DNS/DHCP/IPAM appliance as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type bcnCommandServerSerOperState into the Find box to locate it in the OID tree, then select it and click OK. The operational state of this service — running, notRunning (stopped), starting, stopping, or fault. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the value is 'fault', or it stays in 'starting'/'stopping' longer than a normal transition takes. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (9 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
1.3.6.1.4.1.13315bluecatnetworksBLUECATNETWORKS-MIB
1.3.6.1.4.1.13315.3bcnMgmtBCN-SMI-MIB
1.3.6.1.4.1.13315.3.1bcnServicesBCN-SMI-MIB
Numeric OIDNameModule
1.3.6.1.4.1.13315.3.1.7bcnCommandServerBCN-COMMANDSERVER-MIB
1.3.6.1.4.1.13315.3.1.7.2bcnCommandServerObjectsBCN-COMMANDSERVER-MIB
1.3.6.1.4.1.13315.3.1.7.2.1bcnCommandServerServiceStatusBCN-COMMANDSERVER-MIB
1.3.6.1.4.1.13315.3.1.7.2.1.1bcnCommandServerSerOperStateBCN-COMMANDSERVER-MIB