VLAN-MIB
AI MIB Summary
The VLAN-MIB enables monitoring and configuration of IEEE 802.1Q virtual LANs and LAN Emulation Client associations on bridging devices by exposing port groupings, filter definitions, and virtual bridge topology parameters.
This module contains definitions for management information for pre-standards IEEE 802.1Q VLANs and their association with a Lan Emulation Client (lec). Devices implementing these pre-standards maintain port groupings and associated filters used to form a 'virtual bridge'.
Main OID:
vlanMIBObjects.1.3.6.1.4.1.326.1.8.1
29
Objects
Active
Status
3
Dependencies
Imported Objects
Objects
29 total| Object Name |
|---|
vlanMIBObjectsThis module contains definitions for management information for pre-standards IEEE 802.1Q VLANs and their association with a Lan Emulation Client (lec). Devices implementing these pre-standards maintain port groupings and associated filters used to form a 'virtual bridge'. MODULE-IDENTITY .1.3.6.1.4.1.326.1.8.1 |
vlanConfGroup OBJECT IDENTIFIER .1.3.6.1.4.1.326.1.8.1.1 |
vlanConfTableA table of VLAN names and characteristics. SEQUENCE OF VlanConfEntry .1.3.6.1.4.1.326.1.8.1.1.1 |
vlanConfEntryA table entry containing VLAN names and characteristics. IMPORTANT: The read-write fields of this table should be modifiable, such that as VLAN characteristics change, the individual parameters in the table can be modified. VlanConfEntry .1.3.6.1.4.1.326.1.8.1.1.1.1 |
vlanNameThe textual name of this VLAN, this is the identifier that the user of a configuration utility will be using. Using a VLAN ID for the index and resolving to a name would be easier for an individual switch. However, the user will not (and should not) use this ID. The problem would then be how to resolve an ID to a Name, given that network manager needs to know this for all devices. Using the name as the index allows a management application to have a list of names and each network device resolves that to a locally significant ID. This means however, if the user configures, via a local interface, two switches with VLANs that have the same name, the network manager will assume that they are the same VLAN. In the future, when the 802.1Q standard comes out, there will be a standard way of maintaining globally unique VLAN IDs because these will be used as the VLAN tag. At that time the index into this table should become the VLAN tag.ro DisplayString .1.3.6.1.4.1.326.1.8.1.1.1.1.1 |
vlanIDThis is the locally significant ID that is used internally by this device to reference this VLAN.ro Integer32 .1.3.6.1.4.1.326.1.8.1.1.1.1.2 |
vlanConfRowStatusThis object is used to create a new row or to modify or delete an existing row in this table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.326.1.8.1.1.1.1.3 |
vlanCreatedByThis object is used to enter a string to identify the management entity that created this entry.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.326.1.8.1.1.1.1.4 |
vlanTypeThe type of vlan, specified as a bitmap. The bitmap indicates all the types of filters that are to be applied to the vlan. The bit locations and meanings are: 0x01 - port-based VLAN 0x02 - MAC-based VLAN 0x04 - protocol-based VLAN 0x08 - IP subnet VLAN for example a VLAN that will look at an incoming port and then apply a MAC filter would use the value 0x03 to indicate both the port and the MAC filters.rw Integer32 .1.3.6.1.4.1.326.1.8.1.1.1.1.5 |
vlanPortGroupInstanceThe index that identifies the the sub tree in the vlanPortGroupTable that should be walked to retrieve the group of ports in this VLAN. IMPORTANT: This table has slightly different semantics than the next three objects because in all 802 VLANs, in the end they all resolve down to a group of ports. Therefore, this object has the following semantic based on its value and the value of vlanType: vlanType vlanPortGroupInstance mode ------------------ ------------------------------- ---- Port-based set points to a user configured Manual set of ports Port-based not set 0 - There are no ports assigned Auto to this VLAN at this time. Port-based not set non zero - points to a system Auto (agent) maintained list of portsrw Integer32 .1.3.6.1.4.1.326.1.8.1.1.1.1.6 |
vlanMacListInstanceIf this is a MAC-based VLAN then this is the index that identifies the sub tree in the vlanMacListTable that should be walked to retrieve the list of MAC address to allow into this VLAN. If this is not a MAC-based VLAN then the value is 0rw Integer32 .1.3.6.1.4.1.326.1.8.1.1.1.1.7 |
vlanProtocolTypeIf this is a protocol-based VLAN then this is the protocol type whose traffic is allowed into this VLAN. If this is not a protocol-based VLAN the value is 'none'.rw Enumeration .1.3.6.1.4.1.326.1.8.1.1.1.1.8 |
vlanProtocolSubtypeIf this is a protocol-based VLAN then this is the protocol subtype whose traffic is allowed into this VLAN. This value is based on the protocol type (vlanProtocolType). If the protocol type is Ethernet V2.0 (ethernetv2) then the value is the value assigned by Xerox (two octets). For example, the value 08-00 is the value for IP. If the protocol type is IEEE 802.3 DSAP then the value is the DSAP value (one octet). For example, the value 224 (0xE0) is the value for IPX. If this is not a protocol-based VLAN the value is a zero length octet string.rw OCTET STRING .1.3.6.1.4.1.326.1.8.1.1.1.1.9 |
vlanIPSubnetAddressIf this is a subnetBased VLAN then this is the subnet whose traffic is allowed into this VLAN. If this is not a subnetBased VLAN then the value is 0.0.0.0rw IpAddress .1.3.6.1.4.1.326.1.8.1.1.1.1.10 |
vlanBridgeNameThe textual name of the bridge that is associated with this VLAN. This is provided for those devices that allow multiple bridge (spanning tree) instances under the management of a single agent. If this value is a NULL string, then the default bridge's name will be applied. See the Fore-Bridge-Extensions-MIB for details on how bridges are managed.rw DisplayString .1.3.6.1.4.1.326.1.8.1.1.1.1.11 |
vlanIPMulticastFilterThis object allows the enabling and disabling of IP multicast filtering on the VLAN.rw Enumeration .1.3.6.1.4.1.326.1.8.1.1.1.1.12 |
vlanPortGroupTableA table of port groupings. The first index breaks down the table into multiple port groups. Then the second index is the port that belongs in the group. This way walking the table, given the first index, will give the list of all ports in that group. This allows the user of this MIB to create many port groupings, and then each VLAN can point to the port grouping they want to associate with a particular VLAN. IMPORTANT: This table depends on RFC 1573 extensions to the interfaces.ifTable. This is because, entries in vlanPort can be virtual interfaces (representing LEC instances) SEQUENCE OF VlanPortGroupEntry .1.3.6.1.4.1.326.1.8.1.1.2 |
vlanPortGroupEntryA table entry containing a port number VlanPortGroupEntry .1.3.6.1.4.1.326.1.8.1.1.2.1 |
vlanPortGroupIndexIndex used so that there can be many different port groups Integer32 .1.3.6.1.4.1.326.1.8.1.1.2.1.1 |
vlanPortThe value of the instance of the ifIndex object, defined in MIB-II, for the interface corresponding to this port. In the case of a non-atm port this is the physical ifIndex of that port, in the case of an atm port it is the virtual ifIndex that represents the LEC. IMPORTANT: By adding a port here, that port will now be part of any VLAN(s) that this port group is associated with. In addition, if the port is a virtual interface that represents a LEC, the ELAN that that LEC represents will also be part of the VLAN that this port group is associated with. Control of the LECs (creating and assignment) is handled by the ATMF Lan Emulation Client MIB, specifically the lecConfigTable in Configuration Group Integer32 .1.3.6.1.4.1.326.1.8.1.1.2.1.2 |
vlanPortGroupRowStatusThis object is used to create a new row or to modify or delete an existing row in this table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.326.1.8.1.1.2.1.3 |
vlanPortStatusThe status of this port relative to the VLAN that points at this port group. The meanings of each value are: autoActive: Means that the port is part of this VLAN because the switch automatically added it. allowed: Means that the port has been configured so that if all other criteria (if any) are met, this port is allowed to be in this VLAN. allowedActive: Means the same as allowed plus the fact that there is a device attached to this port and participating in the VLAN. allowedNotAvail: This value is only needed for devices that don't allow a port to be in more than one VLAN at a time. This value means that this port also exists in some other VLAN(s) and is active in another VLAN. Therefore this port is not available to be used in this VLAN. notAssociated: Means that the Port Group is not currently associated with any VLAN.ro Enumeration .1.3.6.1.4.1.326.1.8.1.1.2.1.4 |
vlanPortGroupNextIndexThe index of the next free row in the table.rw TestAndIncr (SNMPv2-TC) .1.3.6.1.4.1.326.1.8.1.1.3 |
vlanMacListTableA table of MAC Lists. The first index breaks down the table into multiple MAC Lists. Then the second index is the MAC Address that belongs in the group. This way walking the table, given the first index, will give the list of all MAC Addresses in that group. This allows the user of this MIB to create many MAC Lists, and then each VLAN can point to the MAC List they want to associate with a particular VLAN. SEQUENCE OF VlanMacListEntry .1.3.6.1.4.1.326.1.8.1.1.4 |
vlanMacListEntryA table entry containing MAC Addresses VlanMacListEntry .1.3.6.1.4.1.326.1.8.1.1.4.1 |
vlanMacListIndexIndex used so that there can be many different MAC Lists Integer32 .1.3.6.1.4.1.326.1.8.1.1.4.1.1 |
vlanMacAddressThe MAC Address that belongs to this group. Adding a new MAC Address will mean that packets from that MAC are allow to be sent on the VLAN that this MAC List is associated with. MacAddress (SNMPv2-TC) .1.3.6.1.4.1.326.1.8.1.1.4.1.2 |
vlanMacListRowStatusThis object is used to create a new row or to modify or delete an existing row in this table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.326.1.8.1.1.4.1.3 |
vlanMacListNextIndexThe index of the next free row in the table.rw TestAndIncr (SNMPv2-TC) .1.3.6.1.4.1.326.1.8.1.1.4.2 |