The ring (segment) number in use on a 802.5 ring. For
bridges supporting RFC 1525, this value is the same as given
by dot1dSrPortLocalSegment for the bridge port attached to
that ring. When tokenRing VLANs are in use, each 'trNet'
VLAN can/does have a different instance of
dot1dSrPortLocalSegment for each physical port. Note that
access to the particuler instance of dot1dSrPortLocalSegment
requires knowledge of how the agent supports the multiple
'contexts' required to implement RFC 1525 for multiple
VLANs; also note that the assignment of ifIndex values may
be different in different 'contexts'.
Parsed from file CISCO-VTP-MIB.mib
Module: CISCO-VTP-MIB
The ring (segment) number in use on a 802.5 ring. For
bridges supporting RFC 1525, this value is the same as given
by dot1dSrPortLocalSegment for the bridge port attached to
that ring. When tokenRing VLANs are in use, each 'trNet'
VLAN can/does have a different instance of
dot1dSrPortLocalSegment for each physical port. Note that
access to the particuler instance of dot1dSrPortLocalSegment
requires knowledge of how the agent supports the multiple
'contexts' required to implement RFC 1525 for multiple
VLANs; also note that the assignment of ifIndex values may
be different in different 'contexts'.
vtpVlanPortLocalSegment OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The ring (segment) number in use on a 802.5 ring. For
bridges supporting RFC 1525, this value is the same as given
by dot1dSrPortLocalSegment for the bridge port attached to
that ring. When tokenRing VLANs are in use, each rNet
VLAN can/does have a different instance of
dot1dSrPortLocalSegment for each physical port. Note that
access to the particuler instance of dot1dSrPortLocalSegment
requires knowledge of how the agent supports the multiple
contexts required to implement RFC 1525 for multiple
VLANs; also note that the assignment of ifIndex values may
be different in different contexts."
View at oid-info.com
The ring (segment) number in use on a 802.5 ring. For
bridges supporting RFC 1525, this value is the same as given
by dot1dSrPortLocalSegment for the bridge port attached to
that ring. When tokenRing VLANs are in use, each 'trNet'
VLAN can/does have a different instance of
dot1dSrPortLocalSegment for each physical port. Note that
access to the particuler instance of dot1dSrPortLocalSegment
requires knowledge of how the agent supports the multiple
'contexts' required to implement RFC 1525 for multiple
VLANs; also note that the assignment of ifIndex values may
be different in different 'contexts'.
Parsed from file cisco-vtp.mib.txt
Company: None
Module: CISCO-VTP-MIB
The ring (segment) number in use on a 802.5 ring. For
bridges supporting RFC 1525, this value is the same as given
by dot1dSrPortLocalSegment for the bridge port attached to
that ring. When tokenRing VLANs are in use, each 'trNet'
VLAN can/does have a different instance of
dot1dSrPortLocalSegment for each physical port. Note that
access to the particuler instance of dot1dSrPortLocalSegment
requires knowledge of how the agent supports the multiple
'contexts' required to implement RFC 1525 for multiple
VLANs; also note that the assignment of ifIndex values may
be different in different 'contexts'.
vtpVlanPortLocalSegment OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "The ring (segment) number in use on a 802.5 ring. For bridges supporting RFC 1525, this value is the same as given by dot1dSrPortLocalSegment for the bridge port attached to that ring. When tokenRing VLANs are in use, each 'trNet' VLAN can/does have a different instance of dot1dSrPortLocalSegment for each physical port. Note that access to the particuler instance of dot1dSrPortLocalSegment requires knowledge of how the agent supports the multiple 'contexts' required to implement RFC 1525 for multiple VLANs; also note that the assignment of ifIndex values may be different in different 'contexts'." ::= { vtpNotificationsObjects 1 }
vtpVlanPortLocalSegment OBJECT-TYPE SYNTAX INTEGER(0..65535) ACCESS not-accessible STATUS mandatory DESCRIPTION "The ring (segment) number in use on a 802.5 ring. For bridges supporting RFC 1525, this value is the same as given by dot1dSrPortLocalSegment for the bridge port attached to that ring. When tokenRing VLANs are in use, each 'trNet' VLAN can/does have a different instance of dot1dSrPortLocalSegment for each physical port. Note that access to the particuler instance of dot1dSrPortLocalSegment requires knowledge of how the agent supports the multiple 'contexts' required to implement RFC 1525 for multiple VLANs; also note that the assignment of ifIndex values may be different in different 'contexts'." ::= { vtpNotificationsObjects 1 }
Automatically extracted from a file named C-VTP
vtpVlanPortLocalSegment OBJECT-TYPE SYNTAX INTEGER (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The ring (segment) number in use on a 802.5 ring. For bridges supporting RFC 1525, this value is the same as given by dot1dSrPortLocalSegment for the bridge port attached to that ring. When tokenRing VLANs are in use, each 'trNet' VLAN can/does have a different instance of dot1dSrPortLocalSegment for each physical port. Note that access to the particuler instance of dot1dSrPortLocalSegment requires knowledge of how the agent supports the multiple 'contexts' required to implement RFC 1525 for multiple VLANs; also note that the assignment of ifIndex values may be different in different 'contexts'." ::= { vtpNotificationsObjects 1 }
vtpVlanPortLocalSegment OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "The ring (segment) number in use on a 802.5 ring. For bridges supporting RFC 1525, this value is the same as given by dot1dSrPortLocalSegment for the bridge port attached to that ring. When tokenRing VLANs are in use, each 'trNet' VLAN can/does have a different instance of dot1dSrPortLocalSegment for each physical port. Note that access to the particuler instance of dot1dSrPortLocalSegment requires knowledge of how the agent supports the multiple 'contexts' required to implement RFC 1525 for multiple VLANs; also note that the assignment of ifIndex values may be different in different 'contexts'." ::= { vtpNotificationsObjects 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.46.2.1.1.0 | vtpVlanPortLocalSegment | 0 | 0 | None |