All MIBs › XYLAN-IP-MIB
Category: Xylan OmniSwitch
Description:
Covers IP routing on Xylan OmniSwitch equipment, including configuration, ARP table entries, and IP interface address assignments.
Imported Objects
What Is XYLAN-IP-MIB?
XYLAN-IP-MIB is a private Xylan enterprise MIB that manages IP routing-related configuration on OmniSwitch devices, including RIP route filtering, ARP table entries, and IP interface address assignments. Its objects, such as the xylanIpRipFilterTable, expose per-filter configuration covering administrative state, target network/netmask, permit/deny mode, and the VLAN/slot/WAN-type context a filter applies to. Its primary monitoring value is configuration/state verification for IP routing policy — confirming whether a specific RIP filter is enabled (xylanIpRipFilterAdminState) and correctly scoped to the intended VLAN and slot — rather than raw traffic counters, making it a routing-configuration health check. It is Xylan-specific but conceptually parallels functionality found in the standard RIP-2 MIB (RFC 1724), reimplemented with switch-specific slot/VLAN/WAN-type context. It would be deployed on Xylan (later Alcatel) OmniSwitch devices acting as Layer 3 switches, where network operations verify RIP filtering and IP interface configuration per slot/VLAN. Engineers referencing the XYLAN-IP-MIB MIB definition can map these RIP filter objects directly to the vendor's slot/VLAN/WAN-type addressing scheme used across the switch line.
IPNetwork Monitor allows you to monitor SNMP objects defined in XYLAN-IP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
What Can Be Monitored
- RIP filter administrative state
- RIP filter target network and netmask
- RIP filter permit/deny mode
- VLAN ID and slot association
- WAN interface type
- ARP table / IP interface address assignment
Supported Devices
- Xylan (Alcatel) OmniSwitch Layer-3 switch device (legacy IP routing configuration)
Monitoring Examples
An administrator can inspect the xylanIpRipFilterTable/xylanIpRipFilterEntry rows, checking xylanIpRipFilterAdminState for a given xylanIpRipFilterNum to confirm whether that RIP filter is active, and xylanIpRipFilterNet/xylanIpRipFilterNetMask together with xylanIpRipFilterMode to see which routes it permits or denies. Cross-referencing xylanIpRipFilterVlanId, xylanIpRipFilterSlot, and xylanIpRipFilterWanType lets the operator confirm the filter applies to the correct VLAN and physical slot/WAN interface. An unexpectedly disabled admin state or mismatched network/mask on a filter would explain why expected routes are being blocked or leaked on that slot.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| xylanIpFilterGroup | 1.3.6.1.4.1.800.2.13.1 | |||
| xylanIpRipFilterTable | 1.3.6.1.4.1.800.2.13.1.1 | not-accessible | The IP Rip Filter Table contains information about all Rip filters that have been defined. | |
| xylanIpRipFilterEntry | 1.3.6.1.4.1.800.2.13.1.1.1 | not-accessible | Each entry corresponds to one filter. | |
| INT xylanIpRipFilterNum | 1.3.6.1.4.1.800.2.13.1.1.1.1 | INTEGER | read-only | The unique number identifying this instance. This number can be used when specifying a filter to delete. This number is used by the implementation to specify the location of this particular filter within the linked-list of all filters; therefore, it will be modified as filters are added/deleted. |
| INT xylanIpRipFilterAdminState | 1.3.6.1.4.1.800.2.13.1.1.1.2 | INTEGER | read-write | The current status of this filter, active (1) means the filter is functioning, delete (2) tells SNMP to delete the filter |
| INT xylanIpRipFilterType | 1.3.6.1.4.1.800.2.13.1.1.1.3 | INTEGER | read-write | The type of filter. The possible types include rip-output (1) or rip-input (2). |
| IP xylanIpRipFilterNet | 1.3.6.1.4.1.800.2.13.1.1.1.4 | IpAddress | read-write | The IP Network Address to filter. An IP Address of 0.0.0.0 is used to denote All Networks. |
| IP xylanIpRipFilterNetMask | 1.3.6.1.4.1.800.2.13.1.1.1.5 | IpAddress | read-write | The IP Network Mask to be used. |
| INT xylanIpRipFilterMode | 1.3.6.1.4.1.800.2.13.1.1.1.6 | INTEGER | read-write | The action defined by this filter. block (2) means packets matching this filter will be blocked, and allow (1) means that packets matching this filter will be allowed. |
| INT xylanIpRipFilterGroupId | 1.3.6.1.4.1.800.2.13.1.1.1.7 | INTEGER | read-write | The GroupId can be used to apply this filter to a particular interface. A GroupId of 0 means that the filter is global. |
| INT xylanIpRipFilterVlanId | 1.3.6.1.4.1.800.2.13.1.1.1.8 | INTEGER | read-write | The VlanId for this filter. |
| INT xylanIpRipFilterWanType | 1.3.6.1.4.1.800.2.13.1.1.1.9 | INTEGER | read-write | If the Vlan has Wan Routing enabled, this object can be used to specify whether this interface is a Frame Relay service or a PPP service. This will be used to determine whether the slot/port/vc or PeerId fields are applicable to this entry. A value of 1 implies that this field is not used. (The interface is not a WAN interface or the filter is not being applied to a specific VC or PeerId.) A value of 2 indicates that this is a Frame Relay service in which case the slot/port/vc fields can be used to apply the filter to a specific VC. A value of 3 indicates that this is a PPP service and the Peer ID field may be used. |
| INT xylanIpRipFilterSlot | 1.3.6.1.4.1.800.2.13.1.1.1.10 | INTEGER | read-write | If the WanType specifies a Frame Relay service, the slot/port/vc can be used to apply this filter to a particular Virtual Circuit (VC). |
| INT xylanIpRipFilterPort | 1.3.6.1.4.1.800.2.13.1.1.1.11 | INTEGER | read-write | If the WanType specifies a Frame Relay service, the slot/port/vc can be used to apply this filter to a particular Virtual Circuit (VC). |
| INT xylanIpRipFilterVc | 1.3.6.1.4.1.800.2.13.1.1.1.12 | INTEGER | read-write | If the WanType specifies a Frame Relay service, the slot/port/vc can be used to apply this filter to a particular Virtual Circuit (VC). |
| INT xylanIpRipFilterPeerId | 1.3.6.1.4.1.800.2.13.1.1.1.13 | INTEGER | read-write | If the WanType specifies a PPP service, the PeerId can be used to apply this filter to a particular Peer. |
| xylanIpMiscGroup | 1.3.6.1.4.1.800.2.13.2 | |||
| xylanIpAssocMacTable | 1.3.6.1.4.1.800.2.13.2.1 | not-accessible | A table of IP addresses and their associated MAC addresses learned. | |
| xylanIpAssocEntry | 1.3.6.1.4.1.800.2.13.2.1.1 | not-accessible | The information for one of this entity's IP addresses. | |
| IP xylanIpAssocAddr | 1.3.6.1.4.1.800.2.13.2.1.1.1 | IpAddress | read-only | The IP address learned from an ARP message's sender IP address. |
| OCT xylanIpAssocMac | 1.3.6.1.4.1.800.2.13.2.1.1.2 | OCTET STRING | read-only | The MAC address learned from an ARP message's sender hardware address. |
| INT xylanIpAssocSlot | 1.3.6.1.4.1.800.2.13.2.1.1.3 | INTEGER | read-only | The slot number (1-based) where ARP message was received. |
| INT xylanIpAssocIntf | 1.3.6.1.4.1.800.2.13.2.1.1.4 | INTEGER | read-only | The interface number (1-based) where ARP message was received. |
| OCT xylanIpAssocDupMac | 1.3.6.1.4.1.800.2.13.2.1.1.5 | OCTET STRING | read-only | If a duplicate IP address is detected, the MAC address associated with this IP address. A value of 0 indicates no duplicate IP address detected. |
| INT xylanIpAssocDupSlot | 1.3.6.1.4.1.800.2.13.2.1.1.6 | INTEGER | read-only | If a duplicate IP address is detected, the slot number (1-based) where this duplicate IP address was learned. |
| INT xylanIpAssocDupIntf | 1.3.6.1.4.1.800.2.13.2.1.1.7 | INTEGER | read-only | If a duplicate IP address is detected, the interface number (1-based) where this duplicate IP address was learned. |
FAQ
What does XYLAN-IP-MIB help verify on a Xylan OmniSwitch acting as a Layer 3 switch?
It exposes the xylanIpRipFilterTable, which reports whether each RIP route filter is enabled (xylanIpRipFilterAdminState), its target network/netmask, permit/deny mode, and which VLAN, slot, and WAN type it applies to -- letting network operations confirm RIP filtering is correctly scoped before trusting the switch's routing behavior.
Would you use XYLAN-IP-MIB to monitor routing traffic volume?
No -- its value is configuration/state verification rather than traffic counters. It's best used as a routing-configuration health check, confirming a given RIP filter is administratively enabled and applied to the intended VLAN/slot, alongside ARP table and IP interface address assignment data.
RFC description
Manages Xylan OmniSwitch IP routing configuration, ARP table, and IP interface address assignments.
Start monitoring Xylan (Alcatel) OmniSwitch Layer-3 switch device (RIP-filter/ARP/IP-interface config status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.