Each port is associated with a port group. Typically, a port will belong to
a port group of one and the value of this object will be the same as the
port index for this instance. That is, this port will point to itself.
The intent of this object is to help manage ports that have hierarchical
relationships. For example, an ATM port typically has a physical port and
multiple logical ports (e.g. each logical port corresponding to an instance of
an emulated LAN). In this case, each LANE instance would refer to the
instance of the physical port associated with the ATM front-end.
Another example is an FDDI DAS type port. In this case, there is a logical
port associated with the FDDI switch port which is connected to the two
FDDI physical port connectors. The physical FDDI ports both point to
the logical instance of an FDDI port.
Parsed from file ProminetMib.txt
Company: None
Module: PROMINET-MIB
Each port is associated with a port group. Typically, a port will belong to
a port group of one and the value of this object will be the same as the
port index for this instance. That is, this port will point to itself.
The intent of this object is to help manage ports that have hierarchical
relationships. For example, an ATM port typically has a physical port and
multiple logical ports (e.g. each logical port corresponding to an instance of
an emulated LAN). In this case, each LANE instance would refer to the
instance of the physical port associated with the ATM front-end.
Another example is an FDDI DAS type port. In this case, there is a logical
port associated with the FDDI switch port which is connected to the two
FDDI physical port connectors. The physical FDDI ports both point to
the logical instance of an FDDI port.
Parsed from file PROMINET-MIB.mib
Module: PROMINET-MIB
Vendor: Prominet Corporation
Module: PROMINET-MIB
[Automatically extracted from oidview.com]
promPortGroupBinding OBJECT-TYPE SYNTAX ResourceId ACCESS read-only STATUS mandatory DESCRIPTION "Each port is associated with a port group. Typically, a port will belong to a port group of one and the value of this object will be the same as the port index for this instance. That is, this port will point to itself. The intent of this object is to help manage ports that have hierarchical relationships. For example, an ATM port typically has a physical port and multiple logical ports (e.g. each logical port corresponding to an instance of an emulated LAN). In this case, each LANE instance would refer to the instance of the physical port associated with the ATM front-end. Another example is an FDDI DAS type port. In this case, there is a logical port associated with the FDDI switch port which is connected to the two FDDI physical port connectors. The physical FDDI ports both point to the logical instance of an FDDI port." ::= { promPortEntry 10 }
promPortGroupBinding OBJECT-TYPE SYNTAX ResourceId ACCESS read-only STATUS mandatory DESCRIPTION "Each port is associated with a port group. Typically, a port will belong to a port group of one and the value of this object will be the same as the port index for this instance. That is, this port will point to itself. The intent of this object is to help manage ports that have hierarchical relationships. For example, an ATM port typically has a physical port and multiple logical ports (e.g. each logical port corresponding to an instance of an emulated LAN). In this case, each LANE instance would refer to the instance of the physical port associated with the ATM front-end. Another example is an FDDI DAS type port. In this case, there is a logical port associated with the FDDI switch port which is connected to the two FDDI physical port connectors. The physical FDDI ports both point to the logical instance of an FDDI port." ::= { promPortEntry 10 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2167.3.6.1.1.1.1 | promPortIndex | 0 | 0 | An index that uniquely identifies this port. Typically, ports are child resources of the module that contains them. In these c… |
| 1.3.6.1.4.1.2167.3.6.1.1.1.2 | promPortName | 0 | 0 | The user-assigned name for this port. Note that setting this object for an internal(1) port results in an error. |
| 1.3.6.1.4.1.2167.3.6.1.1.1.3 | promPortType | 0 | 0 | An internal(1) port does not have an external connection. An ether-ten-oneHundred(2) port is an Ethernet port which can be switc… |
| 1.3.6.1.4.1.2167.3.6.1.1.1.4 | promPortBaseType | 0 | 0 | The base type of this port. This object may be useful to help manage new port types that are similar in nature to legacy port t… |
| 1.3.6.1.4.1.2167.3.6.1.1.1.5 | promPortMode | 0 | 0 | The mode of this port. When set to enable(1), this port passes data. When set to disable(2), the port does not receive or trans… |
| 1.3.6.1.4.1.2167.3.6.1.1.1.6 | promPortStatus | 0 | 0 | The status of this port. Disabled(1) means that this port has been disabled through management action. Okay(2) indicates that … |
| 1.3.6.1.4.1.2167.3.6.1.1.1.7 | promPortConnector | 0 | 0 | The connector type associated with this port. |
| 1.3.6.1.4.1.2167.3.6.1.1.1.8 | promPortSpeedState | 0 | 0 | The data rate of this port in bits per second. For example, a standard Ethernet port (e.g. 10BASE-T) would indicate a value of … |
| 1.3.6.1.4.1.2167.3.6.1.1.1.9 | promPortDuplexState | 0 | 0 | The value of this object indicates whether this port is operating in full- or half-duplex mode. The value under-negotiation(3) in… |
| 1.3.6.1.4.1.2167.3.6.1.1.1.11 | promPortFlowControlState | 0 | 0 | The value of this object indicates whether this port is operating using flow control. The value under-negotiation(3) indicates th… |