All MIBs › RFC1285-MIB › snmpFddiPORTPathsRequested
snmpFddiPORTPathsRequested
Module: RFC1285-MIB
OID (symbolic): RFC1285-MIB::snmpFddiPORTPathsRequested
OID (numeric): 1.3.6.1.2.1.10.15.4.2.1.8
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: A value that indicates the desired association(s) of the port with a station PATH. The 'Primary' Path is the default. The value of 'Secondary' is only meaningful for S (slave) or M (master) PORT PC-Types. This value effects the setting of the CF_Insert_S, and CF_Insert_L flags (refer to ANSI Section 9.4.3). If the 'Primary' PATH is present, then the Primary PATH (the default PATH) is selected. If the 'Secondary' PATH is present and the 'Primary' PATH is not present, then the CF_Insert_S flag is set. If the 'Local' PATH is sent and neither the 'Primary' or 'Secondary' PATHs are sent, then the CF_Insert_L flag is set.
The value is a sum. This value initially takes the value zero, then for each type of PATH desired, 2 raised to a power is added to the sum. The powers are according to the following table:
Path Power Primary 0 Secondary 1 Local 2 Isolated 3
What is snmpFddiPORTPathsRequested?
A read-write bitmask sum indicating which station path (Primary, Secondary, Local, Isolated) this port should try to associate with, defaulting to Primary. Admins set this to Secondary on an M or S port when the topology design calls for that port to insert onto the secondary ring instead of the default primary.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.10.15.4.2.1.8 snmpwalk -v2c -c public <target> RFC1285-MIB::snmpFddiPORTPathsRequested
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.10.15.4.2.1.8.1 snmpget -v2c -c public <target> RFC1285-MIB::snmpFddiPORTPathsRequested.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.2.1.10.15.4.2.1.8.1 i <value>
Start monitoring vendor-neutral, standards-based MIB, FDDI ring stations, concentrators, and router FDDI interfaces with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RFC1285-MIB::snmpFddiPORTPathsRequested OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, FDDI ring stations, concentrators, and router FDDI interfaces from a single console.
OID Breakdown
Upper-level ancestors (8 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.2 | mgmt | APERTUS-NPG-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| 1.3.6.1.2.1.10 | transmission | CHECKPOINT-MIB-2 |
| 1.3.6.1.2.1.10.15 | fddi | FDDI-SMT73-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.10.15.4 | snmpFddiPORT | RFC1285-MIB |
| 1.3.6.1.2.1.10.15.4.2 | snmpFddiPORTTable | RFC1285-MIB |
| 1.3.6.1.2.1.10.15.4.2.1 | snmpFddiPORTEntry | RFC1285-MIB |
| 1.3.6.1.2.1.10.15.4.2.1.8 | snmpFddiPORTPathsRequested | RFC1285-MIB |