All MIBs › JETDIRECT3-MIB › npPortDesiredMode
npPortDesiredMode
Module: JETDIRECT3-MIB
OID (symbolic): JETDIRECT3-MIB::npPortDesiredMode
OID (numeric): 1.3.6.1.4.1.11.2.4.3.13.3
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: The desired (remotely specified) operating mode of the parallel port.
The following map is used to determine mode availability and provides
the definition for each mode:
Available When
npPortDesiredMode Definition
------------------ --------------
1 bitronics always
EX will attempt to retrieve nibble mode back
channel data from the printer. If the printer
does not support bitronics, EX will default
back to compatibility mode.
2 centronics npPortMaxModeAvailable >= 1
EX will only support compatibility (centronics)
mode when talking to the printer
3 ecpWithNibbleMLC npPortMaxModeAvailable >= 1
EX will attempt to talk to the printer across
MLC. This is done by using ECP in the forward
direction and nibble-mode bitronics in the
reverse direction. If the printer does not
support both MLC and ECP, EX will fall back to
regular bitronics, as described above.
4 ecpWithMLC npPortMaxModeAvailable >= 1
EX will attempt to talk to the printer across
MLC. This is done by using ECP in both forward
and reverse directions. If the printer does
not support both MLC and ECP, EX will fall back
to regular bitronics, as described above.
5 ecp npPortMaxModeAvailable >= 1
EX will attempt to talk to the printer using
ECP in both the forward and reverse directions.
If the printer does not support ECP, EX will
fall back to regular bitronics, as described
above.What is npPortDesiredMode?
Writable choice of how the card talks over the parallel port: bitronics(1) tries nibble-mode back channel and falls back to compatibility mode, centronics(2) is forward-only compatibility, and the ECP options use ECP forward and either nibble or ECP back, with or without MLC, falling back to bitronics if the printer lacks support. The source text maps 3 to ecpWithNibbleMLC and 4 to ecpWithMLC, which is the reverse of the enumerated names in the SYNTAX, so verify the behavior on your model before relying on those two values.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.11.2.4.3.13.3 snmpwalk -v2c -c public <target> JETDIRECT3-MIB::npPortDesiredMode
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.11.2.4.3.13.3.1 snmpget -v2c -c public <target> JETDIRECT3-MIB::npPortDesiredMode.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.11.2.4.3.13.3.1 i <value>
Start monitoring HP LaserJet printer with JetDirect print-server card (legacy models) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the JETDIRECT3-MIB::npPortDesiredMode OID value, configure state conditions and alerts, and monitor any HP LaserJet printer with JetDirect print-server card (legacy models) from a single console.
OID Breakdown
Upper-level ancestors (9 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.11 | hp | CLJ8500-MIB |
| 1.3.6.1.4.1.11.2 | nm | CLJ8500-MIB |
| 1.3.6.1.4.1.11.2.4 | interface | HP-UNIX |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.11.2.4.3 | npCard | JETDIRECT3-MIB |
| 1.3.6.1.4.1.11.2.4.3.13 | npPort | JETDIRECT3-MIB |
| 1.3.6.1.4.1.11.2.4.3.13.3 | npPortDesiredMode | JETDIRECT3-MIB |