Home/Catalog/ALCATEL-IND1-IPM-VLAN-MIB

ALCATEL-IND1-IPM-VLAN-MIB

AI MIB Summary

The ALCATEL-IND1-IPM-VLAN-MIB manages Alcatel-Lucent IP Media (IPM) devices by configuring VLAN parameters and defining the binding relationships between physical ports, IP addresses, and VLAN identifiers. This module enables the monitoring and control of Layer 2/Layer 3 segmentation policies required for IP media traffic isolation and routing on Alcatel-Lucent hardware.

The parameters for configuration of the IPM Vlan feature, including the association between ports and ipaddresses with vlans. The right to make changes in specification and other information contained in this document without prior notice is reserved. No liability shall be assumed for any incidental, indirect, special, or consequential damages whatsoever arising from or related to this document or the information contained herein. Vendors, end-users, and other interested parties are granted non-exclusive license to use this specification in connection with management of the products for which it is intended to be used. Copyright 1995-2007 Alcatel-Lucent ALL RIGHTS RESERVED WORLDWIDE
Main OID:
alcatelIND1IPMVlanMIB.1.3.6.1.4.1.6486.801.1.2.1.41.1
33
Objects
Active
Status
6
Dependencies

Imported Objects

Objects

33 total
Object Name
alcatelIND1IPMVlanMIBThe parameters for configuration of the IPM Vlan feature, including the association between ports and ipaddresses with vlans. The right to make changes in specification and other information contained in this document without prior notice is reserved. No liability shall be assumed for any incidental, indirect, special, or consequential damages whatsoever arising from or related to this document or the information contained herein. Vendors, end-users, and other interested parties are granted non-exclusive license to use this specification in connection with management of the products for which it is intended to be used. Copyright 1995-2007 Alcatel-Lucent ALL RIGHTS RESERVED WORLDWIDE
MODULE-IDENTITY
.1.3.6.1.4.1.6486.801.1.2.1.41.1
alcatelIND1IPMVlanMIBObjectsBranch For IPM Vlan Managed Objects.
OBJECT IDENTIFIER
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1
alaipmvVlanPort
OBJECT IDENTIFIER
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.1
alaipmvVlanPortTableA table that contains port specific information for the IP Multicast VLAN. An entry is this table is created when a port is configured as a receiver / sender port for a IPMVLAN.
SEQUENCE OF AlaIpmvVlanPortEntry
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.1.1
alaipmvVlanPortEntryA IPMV Port entry.
AlaIpmvVlanPortEntry
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.1.1.1
alaipmvVlanPortIPMVlanNumberThe VLAN number component of this IPMVLAN instance. Valid range from 2 to 4094.ro
INTEGER
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.1.1.1.1
alaipmvVlanPortNumberThe port ifindex of the port which is associated to the IPMVLAN.ro
InterfaceIndex (IF-MIB)
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.1.1.1.2
alaipmvVlanPortTypeThe type of this port associated to the IPMVLAN. receiverPort(1) is the receiver port associated to the IPMVLAN, senderPort(2) is the sender port associated to the IPMVLAN. In the VLAN Stacking environment, these ports are the VLAN Stacking ports. Configuration of IPMVLAN logical/physical receiver port on multiple IPMVlans, that are associated with same IPv4/IPv6 multicast group addresses are not allowed.ro
Enumeration
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.1.1.1.3
alaipmvVlanPortRowStatusThe status of this table entry. The values supported are CreateAndGo(4) and destroy(6), to create or delete the port as a receiver / sender port in an IPMVLAN. Of course the corresponding vlan and port must exist.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.1.1.1.4
alaipmvVlanIpAddr
OBJECT IDENTIFIER
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.2
alaipmvVlanIpAddrTableA list of IP addresses assigned to an IPMVLAN.
SEQUENCE OF AlaIpmvVlanIpAddrEntry
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.2.1
alaipmvVlanIpAddrEntryA IPMVLAN IP address entry.
AlaIpmvVlanIpAddrEntry
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.2.1.1
alaipmvVlanIpAddrVlanNumberThe VLAN number component of this IPMVLAN instance. Valid range from 2 to 4094.ro
INTEGER
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.2.1.1.1
alaipmvVlanIpAddrTypeThe IP address type.ro
InetAddressType
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.2.1.1.2
alaipmvVlanIpAddressThe Multicast IP address based on the address type. This IP multicast group address can be associated to multiple IPMVLANs. Configuration of IPv4/IPv6 Multicast Group address on multiple IPMVlans, that are associated with same physical/logical receiver ports are not allowed.ro
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.2.1.1.3
alaipmvVlanIpAddrRowStatusThis is used to create or delete the Multicast IP address in an IPMVLAN. Of course the corresponding vlan must exist.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.2.1.1.4
alaipmvVlanIpAddrMaskTableA list of IP addresses assigned to an IPMVLAN.
SEQUENCE OF AlaIpmvVlanIpAddrMaskEntry
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.2.2
alaipmvVlanIpAddrMaskEntryA IPMVLAN IP address entry.
AlaIpmvVlanIpAddrMaskEntry
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.2.2.1
alaipmvVlanIpAddrMaskVlanNumberThe VLAN number component of this IPMVLAN instance. Valid range from 2 to 4094.
INTEGER
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.2.2.1.1
alaipmvVlanIpAddrMaskTypeThe IP address type.The allowed values are ipv4(1) and ipv6(2).
InetAddressType
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.2.2.1.2
alaipmvVlanIpAddrMaskAddressThe Multicast IP address based on the address type indicated by alaipmvVlanIpAddrMaskType. This IP multicast group address can be associated to multiple IPMVLANs. alaipmvVlanIpAddrMaskPrefixLen is used to specify a mask. The host bits of the address should be zero.
InetAddress
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.2.2.1.3
alaipmvVlanIpAddrMaskPrefixLenThe Multicast IP address-mask length based on the address type. It must be 0-32 for alaipmvVlanIpAddrMaskType ipv4 and 128 for alaipmvVlanIpAddrMaskType ipv6. The host bits of the address alaipmvVlanIpAddrMaskAddress should be zero.
InetAddressPrefixLength (INET-ADDRESS-MIB)
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.2.2.1.4
alaipmvVlanIpAddrMaskRowStatusThis is used to create or delete the Multicast IP address in an IPMVLAN. Of course the corresponding vlan must exist.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.2.2.1.5
alaipmvVlanCtagT
OBJECT IDENTIFIER
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.3
alaipmvVlanCtagTableA table that contains ipmvlan-ctag association for the IPMV feature.
SEQUENCE OF AlaIpmvVlanCtagEntry
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.3.1
alaipmvVlanCtagEntryA IPMVLAN-Ctag entry.
AlaIpmvVlanCtagEntry
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.3.1.1
alaipmvVlanNumberThe VLAN number component of this IPMVLAN instance. Valid range from 2 to 4094.ro
INTEGER
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.3.1.1.1
alaipmvVlanCtagThe customer vlan id associated to the IPMVLAN. This customer vlan id is unique and can't be associated to more than one IPM Vlanro
INTEGER
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.3.1.1.2
alaipmvVlanCtagRowStatusThe status of this table entry. The supported value for set are createAndGo (4) and destroy(6), to add or remove an IPMVLAN-ctag association.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.3.1.1.3
alaipmvVlanIpAddrMask
OBJECT IDENTIFIER
.1.3.6.1.4.1.6486.801.1.2.1.41.1.1.4
alcatelIND1IPMVlanMIBConformanceBranch For IPM Vlan Conformance Information.
OBJECT IDENTIFIER
.1.3.6.1.4.1.6486.801.1.2.1.41.1.2
alcatelIND1IPMVlanMIBGroupsBranch For IPM Vlan Units Of Conformance.
OBJECT IDENTIFIER
.1.3.6.1.4.1.6486.801.1.2.1.41.1.2.1
alcatelIND1IPMVlanMIBCompliancesBranch For IPM Vlan Compliance Statements.
OBJECT IDENTIFIER
.1.3.6.1.4.1.6486.801.1.2.1.41.1.2.2

More MIBs from AL-Enterprise

Browse all AL-EnterpriseMIBs →
ALCATEL-IND1-QOS-MIB

The ALCATEL-IND1-QOS-MIB enables monitoring and configuration of Quality of Service (QoS) policies, traffic shaping parameters, and access control list (ACL) filtering rules on Alcatel-Lucent network infrastructure. It provides visibility into queue depths, packet discard rates, and bandwidth allocation statistics to enforce service level agreements and traffic prioritization.

760 objects→
ALCATEL-IND1-SERVICE-MGR-MIB

The ALCATEL-IND1-SERVICE-MGR-MIB provides configuration parameters for the Alcatel-Lucent service manager feature, enabling the management of service provisioning, activation, and lifecycle states on carrier-grade network elements. This module facilitates the monitoring of service instance attributes and operational status to ensure correct delivery of managed services across the infrastructure.

453 objects→
ALCATEL-IND1-FIPS-MIB

The ALCATEL-IND1-FIPS-MIB module enables SNMP-based monitoring of MAC address learning tables and forwarding database states on Alcatel-Lucent Birds of Prey series network switches. It provides enterprise-specific access to layer 2 switching metrics, including learned MAC addresses and their associated port bindings, for traffic analysis and security auditing.

432 objects→
ALCATEL-IND1-BGP-MIB

The ALCATEL-IND1-BGP-MIB enables SNMP-based monitoring and configuration of Border Gateway Protocol (BGP) parameters on Alcatel-Lucent network devices, specifically tracking BGP session states, neighbor relationships, and protocol-specific counters. This module provides visibility into the operational status and performance metrics of BGP routing processes to facilitate network troubleshooting and policy enforcement.

396 objects→
ALCATEL-IND1-DEVICES

The ALCATEL-IND1-DEVICES MIB defines SNMP Object Identifiers for monitoring the physical inventory, chassis status, and module states of Alcatel-Lucent OmniSwitch 4000, 7000, 8000, and 9000 series networking hardware. It enables network management systems to retrieve device topology data, component presence, and hardware health indicators specific to these enterprise switching platforms.

267 objects→
ALCATEL-IND1-AAA-MIB

The ALCATEL-IND1-AAA-MIB provides SNMP access to monitor and manage Authentication, Authorization, and Accounting (AAA) subsystem metrics on Alcatel-Lucent "Birds of Prey" network hardware, specifically tracking user session states, authentication failures, and accounting records.

252 objects→