All MIBs › TERAWAVE-terasystem-MIB › teraSystemNumOfPCU
teraSystemNumOfPCU
Module: TERAWAVE-terasystem-MIB
OID (symbolic): TERAWAVE-terasystem-MIB::teraSystemNumOfPCU
OID (numeric): 1.3.6.1.4.1.4513.5.25.1
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
What is teraSystemNumOfPCU?
The source DESCRIPTION is empty, so this reading is inferred from the name and syntax. teraSystemNumOfPCU appears to select how many Power/Processor Control Units, 4 or 5, the chassis is configured to expect, matching the physical hardware installed.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4513.5.25.1 snmpwalk -v2c -c public <target> TERAWAVE-terasystem-MIB::teraSystemNumOfPCU
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.4513.5.25.1.1 snmpget -v2c -c public <target> TERAWAVE-terasystem-MIB::teraSystemNumOfPCU.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.4513.5.25.1.1 i <value>
Start monitoring Terawave DSL access system (system clock/event-log status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TERAWAVE-terasystem-MIB::teraSystemNumOfPCU OID value, configure state conditions and alerts, and monitor any Terawave DSL access system (system clock/event-log status) from a single console.
OID Breakdown
Upper-level ancestors (7 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.4513 | terawave | TERAWAVE-teraAccess-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.4513.5 | teraSystem | TERAWAVE-terasystem-MIB |
| 1.3.6.1.4.1.4513.5.25 | teraSystemPCUNumTable | TERAWAVE-terasystem-MIB |
| 1.3.6.1.4.1.4513.5.25.1 | teraSystemNumOfPCU | TERAWAVE-terasystem-MIB |