XYLAN-FRAME-RELAY-MIB

All MIBs › XYLAN-FRAME-RELAY-MIB

Category: Xylan OmniSwitch

Description: Covers Frame Relay PVCs on Xylan OmniSwitch equipment, including configuration, DLCI status, and traffic shaping parameters.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock 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.

What Is XYLAN-FRAME-RELAY-MIB?

XYLAN-FRAME-RELAY-MIB is a private enterprise MIB from Xylan (whose OmniSwitch product line was later absorbed into Alcatel/Alcatel-Lucent) that manages Frame Relay permanent virtual circuit (PVC) configuration on OmniSwitch devices. It is expected to expose per-DLCI objects covering circuit configuration, administrative and operational status, and traffic-shaping parameters such as committed information rate and burst size, following the xylan-prefixed table/entry naming convention seen across other Xylan MIBs. Its monitoring value lies in confirming whether configured Frame Relay PVCs are administratively enabled and operationally up, and whether traffic-shaping parameters match provisioned service levels — a fault/configuration-status check for WAN connectivity. It likely complements or parallels concepts from the standard Frame Relay DTE MIB (RFC 1315) but implements them as Xylan-specific objects. It would be deployed on Xylan OmniSwitch devices terminating Frame Relay WAN circuits, where network operations monitor PVC/DLCI health. Operators tracking down the XYLAN-FRAME-RELAY-MIB MIB definition usually do so to confirm the exact object names for a specific OmniSwitch firmware version.

IPNetwork Monitor allows you to monitor SNMP objects defined in XYLAN-FRAME-RELAY-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.

Supported Devices

Xylan OmniSwitch device (Frame Relay PVC/DLCI configuration)

Monitoring Examples

No sample objects were included for this specific module, but consistent with the xylan-prefixed naming convention seen in sibling MIBs (e.g., xylanIpRipFilterTable), a likely Frame Relay PVC table would carry a DLCI identifier, administrative/operational status, and shaping parameters like committed burst size. An operator would poll such a table to confirm a PVC's operational status is up and that its configured DLCI and shaping values match the carrier's provisioned service, with a down operational status flagging a WAN link fault. This description is inferred from naming convention rather than confirmed sample objects for this exact module.

What Can Be Monitored

PVC/DLCI administrative status
PVC/DLCI operational status
traffic shaping parameters (CIR/burst)

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter

From RFC1213-MIB

DisplayString

From XYLAN-BASE-MIB

xylanFrArch

OBJECT-IDENTITY

OIDs

OID symbolic	OID numeric	Type	Access	Description
INT frxPortDefaultBridgingMode	1.3.6.1.4.1.800.2.8.1.1.1.10	INTEGER	read-write	The default Briding Mode, 0 = BRIDGE_ALL, 1 = ETHERNET ONLY
INT frxPortDefaultBridgingServiceNumber	1.3.6.1.4.1.800.2.8.1.1.1.5	INTEGER	read-write	If non-zero, this is the unique service number which unconfigured Bridging Virtual Circuits are added to if frxPortDefaultBridgingVLAN is non zero (set to a VLAN ID) and frxPortDefaultBridgingGrouping is set to groupVCsIntoOneVport. This allows an unconfigured VC to be added to an existing configured bridging service virtual circuit group. If zero, then unconfigured VCs will be added to a newly created (dynamic) Briding Service instance (i.e. a new virtual port is created dynamically).
INT frxPortDefaultBridgingVLAN	1.3.6.1.4.1.800.2.8.1.1.1.4	INTEGER	read-write	The default VLAN for new PVCs that have not been configured for the Bridging Service. A value of zero(0) indicates that unconfigured VCs will not perform a bridging service and will discard all bridged format frames received or transmitted. A non-zero value indicates the bridging VLAN to be used if the network informs the port of a new VC.
INT frxPortDefaultCompressionAdminStatus	1.3.6.1.4.1.800.2.8.1.1.1.7	INTEGER	read-write	This object controls whether or not an unconfigured virtual circuit will attempt (enable) or not attempt (disable) to negotiate for compression.
INT frxPortDefaultCompressionPRetryCount	1.3.6.1.4.1.800.2.8.1.1.1.9	INTEGER	read-write	The default P-Retry-Count for negotiating mode 1 compression as described in Frame Relay Forum Data Compression Implementation Agreement FRF.9 This object controls the default value for P-Retry-Count for an unconfigured (dynamic) virtual circuit. This object represents the number of retries before giving up on the negotiation phase and not running compression on the virtual circuit.
INT frxPortDefaultCompressionPRetryTime	1.3.6.1.4.1.800.2.8.1.1.1.8	INTEGER	read-write	The default P-Retry-Time for negotiating mode 1 compression as described in Frame Relay Forum Data Compression Implementation Agreement FRF.9. This object controls the default value for P-Retry-Time for an unconfigured (dynamic) virtual circuit. This object represents the time in seconds between retransmission of Data Compression Negotiation Control messages.
INT frxPortDefaultRoutingVLAN	1.3.6.1.4.1.800.2.8.1.1.1.6	INTEGER	read-write	The default VLAN for new PVCs that have not been configured for a routing Service. A value of zero(0) indicates that unconfigured VCs will not perform a routing service and will discard all routed format frames received or transmitted. A non-zero value indicates the routing VLAN to be used if the network informs the port of a new VC.
STR frxPortDescription	1.3.6.1.4.1.800.2.8.1.1.1.3	DisplayString	read-write	A description for this Frame Relay port.
frxPortEntry	1.3.6.1.4.1.800.2.8.1.1.1		not-accessible	An entry in the table, containing information about the physical layer of a UNI interface.
frxPortGroup	1.3.6.1.4.1.800.2.8.1
INT frxPortPortIndex	1.3.6.1.4.1.800.2.8.1.1.1.2	INTEGER	read-only	A unique value which identifies this WSM submodule port.
INT frxPortSlotIndex	1.3.6.1.4.1.800.2.8.1.1.1.1	INTEGER	read-only	A unique value which identifies this HSM board slot.
frxPortTable	1.3.6.1.4.1.800.2.8.1.1		not-accessible	A table of port layer status and parameter information for the UNI's physical interface.
INT frxServiceAdminStatus	1.3.6.1.4.1.800.2.8.3.1.1.8	INTEGER	read-write	The service adminstration status.
INT frxServiceBridgingMode	1.3.6.1.4.1.800.2.8.3.1.1.11	INTEGER	read-write	The default Briding Mode, 0 = BRIDGE_ALL, 1 = ETHERNET ONLY
STR frxServiceDescription	1.3.6.1.4.1.800.2.8.3.1.1.5	DisplayString	read-write	A description for this Frame Relay service.
frxServiceEntry	1.3.6.1.4.1.800.2.8.3.1.1		not-accessible	An entry in the table, containing information about the Frame Relay services.
frxServiceGroup	1.3.6.1.4.1.800.2.8.3
INT frxServiceNumber	1.3.6.1.4.1.800.2.8.3.1.1.3	INTEGER	read-only	The unique service number for this particular slot/port.
INT frxServiceOperStatus	1.3.6.1.4.1.800.2.8.3.1.1.7	INTEGER	read-only	The service operational status.
INT frxServicePortIndex	1.3.6.1.4.1.800.2.8.3.1.1.2	INTEGER	read-write	A unique value which identifies this WSM submodule port.
INT frxServiceSlotIndex	1.3.6.1.4.1.800.2.8.3.1.1.1	INTEGER	read-write	A unique value which identifies this HSM board slot.
frxServiceTable	1.3.6.1.4.1.800.2.8.3.1		not-accessible	A table of Frame Relay services status and parameter information.
INT frxServiceTableEntryType	1.3.6.1.4.1.800.2.8.3.1.1.4	INTEGER	read-write	The type of table entry for this Frame Relay Serivce. A static entry is one that is stored in non-volatile memory. A dynamic entry is one that is automatically created for an unconfigured virtual circuit based on the the type of service (bridging or routing) and whether a default VLAN is defined for the type of service. Changing the value via a write command from dynamic to static will cause the table entry to be stored into non-volatile memory. Setting a value of dynamic is not allowed.
INT frxServiceType	1.3.6.1.4.1.800.2.8.3.1.1.6	INTEGER	read-write	The service type.
OCT frxServiceVirtualCircuits	1.3.6.1.4.1.800.2.8.3.1.1.9	OCTET STRING	read-write	The virtual circuits for this service. Interpret this as a 16 bit field per connection: Trunking 1, Bridging 1..255, IP 1..255.
OCT frxServiceVlans	1.3.6.1.4.1.800.2.8.3.1.1.10	OCTET STRING	read-write	The Vlans for this service. Interpret this as a 16 bit field per vlan: Trunking 1-32, Bridging 1, IP 1
INT frxVcControlBridgingInUse	1.3.6.1.4.1.800.2.8.2.1.1.8	INTEGER	read-write	Determine for NMS Manager to see whether VC is already in-use. 1=InUse, 0=Free.
INT frxVcControlCompressionAdminStatus	1.3.6.1.4.1.800.2.8.2.1.1.4	INTEGER	read-write	This object controls whether or not the virtual circuit will attempt (enable) or not attemp (disable) to negotiate for compression. The current state of compression for the virtual circuit is indicated in frxVcControlCompressionOperStatus
INT frxVcControlCompressionOperPhase	1.3.6.1.4.1.800.2.8.2.1.1.5	INTEGER	read-only	This object reports the current phase (state) of compression for this virtual circuit if the Compression Admin Status is set to enable. If the compression Admin status is set to disabled, then this object will report as disabled. Otherwise the value reflects whether compression is currently inactive or failed negotiation (disabled) is under negotiation (initialization) or active (operation). Possible causes of disabled are a failed negotiation, virtual circuit inactive, the other side not supporting compression, etc. For a description of the phases (states), see Frame Relay Forum Implementation aggreement on Data Compression (FRF.9)
INT frxVcControlCompressionPRetryCount	1.3.6.1.4.1.800.2.8.2.1.1.7	INTEGER	read-write	The default P-Retry-Count for negotiating mode 1 compression as described in Frame Relay Forum Data Compression Implementation Agreement FRF.9 This object represents the number of retries before giving up on the negotiation phase and not running compression on the virtual circuit.
INT frxVcControlCompressionPRetryTime	1.3.6.1.4.1.800.2.8.2.1.1.6	INTEGER	read-write	The default P-Retry-Time for negotiating mode 1 compression as described in Frame Relay Forum Data Compression Implementation Agreement FRF.9. This object represents the time in seconds between retransmission of Data Compression Negotiation Control messages.
INT frxVcControlDlci	1.3.6.1.4.1.800.2.8.2.1.1.3	INTEGER	read-only	A unique value which identifies this Data Link Connection Identifier (DLCI) for this Frame Relay Virtual Circuit.
frxVcControlEntry	1.3.6.1.4.1.800.2.8.2.1.1		not-accessible	An entry in the table, containing information about the Frame Relay virtual circuit statistics.
frxVcControlGroup	1.3.6.1.4.1.800.2.8.2
INT frxVcControlPortIndex	1.3.6.1.4.1.800.2.8.2.1.1.2	INTEGER	read-only	A unique value which identifies this WSM submodule port.
INT frxVcControlSlotIndex	1.3.6.1.4.1.800.2.8.2.1.1.1	INTEGER	read-only	A unique value which identifies this HSM board slot.
frxVcControlTable	1.3.6.1.4.1.800.2.8.2.1		not-accessible	A table of Frame Relay virtual circuit configuration and control information.
INT frxVcStatsDlci	1.3.6.1.4.1.800.2.8.4.1.1.3	INTEGER	read-only	A unique value which identifies this Data Link Connection Identifier (DLCI) for this Frame Relay Virtual Circuit.
frxVcStatsEntry	1.3.6.1.4.1.800.2.8.4.1.1		not-accessible	An entry in the table, containing information about the Frame Relay virtual circuit statistics.
frxVcStatsGroup	1.3.6.1.4.1.800.2.8.4
INT frxVcStatsPortIndex	1.3.6.1.4.1.800.2.8.4.1.1.2	INTEGER	read-only	A unique value which identifies this WSM submodule port.
CTR frxVcStatsRx8025Frames	1.3.6.1.4.1.800.2.8.4.1.1.23	Counter	read-only	The total number of received 8025 frames on this virtual circuit.
CTR frxVcStatsRx8025Octets	1.3.6.1.4.1.800.2.8.4.1.1.22	Counter	read-only	The total number of received octets (including the Frame Relay Header field) within 8025 frames on this virtual circuit.
CTR frxVcStatsRxBPDUFrames	1.3.6.1.4.1.800.2.8.4.1.1.15	Counter	read-only	The total number of received BPDU frames on this virtual circuit.
CTR frxVcStatsRxBPDUOctets	1.3.6.1.4.1.800.2.8.4.1.1.14	Counter	read-only	The total number of received octets (including the Frame Relay Header field) within BPDU frames on this virtual circuit.
CTR frxVcStatsRxCompressedDiscards	1.3.6.1.4.1.800.2.8.4.1.1.34	Counter	read-only	The total number of received compressed format frames on this virtual circuit that were discarded due to error or lost frames (e.g. out of sequence, decompression errors, etc.)
CTR frxVcStatsRxCompressedFrames	1.3.6.1.4.1.800.2.8.4.1.1.31	Counter	read-only	The total number of received compressed format frames on this virtual circuit.
CTR frxVcStatsRxCompressedOctets	1.3.6.1.4.1.800.2.8.4.1.1.30	Counter	read-only	The total number of received octets (including the Frame Relay Header field) within compressed format frames on this virtual circuit.
CTR frxVcStatsRxDecompressedOctets	1.3.6.1.4.1.800.2.8.4.1.1.33	Counter	read-only	The total number of octets (including the Frame Relay Header field) after decompression of data received within compressed format frames on this virtual circuit.
CTR frxVcStatsRxEthernetFrames	1.3.6.1.4.1.800.2.8.4.1.1.19	Counter	read-only	The total number of received bridged 802.3 format frames on this virtual circuit.
CTR frxVcStatsRxEthernetOctets	1.3.6.1.4.1.800.2.8.4.1.1.18	Counter	read-only	The total number of received octets (including the Frame Relay Header field) within bridged 802.3 format frames on this virtual circuit.
CTR frxVcStatsRxFDDIFrames	1.3.6.1.4.1.800.2.8.4.1.1.27	Counter	read-only	The total number of received FDDI frames on this virtual circuit.
CTR frxVcStatsRxFDDIOctets	1.3.6.1.4.1.800.2.8.4.1.1.26	Counter	read-only	The total number of received octets (including the Frame Relay Header field) within FDDI frames on this virtual circuit.
CTR frxVcStatsRxIPFrames	1.3.6.1.4.1.800.2.8.4.1.1.7	Counter	read-only	The total number of received routed IP format frames on this virtual circuit.
CTR frxVcStatsRxIPOctets	1.3.6.1.4.1.800.2.8.4.1.1.6	Counter	read-only	The total number of received octets (including the Frame Relay Header field) within routed IP format frames on this virtual circuit.
CTR frxVcStatsRxIPXFrames	1.3.6.1.4.1.800.2.8.4.1.1.11	Counter	read-only	The total number of received routed IPX format frames on this virtual circuit.
CTR frxVcStatsRxIPXOctets	1.3.6.1.4.1.800.2.8.4.1.1.10	Counter	read-only	The total number of received octets (including the Frame Relay Header field) within routed IPX format frames on this virtual circuit.
INT frxVcStatsSlotIndex	1.3.6.1.4.1.800.2.8.4.1.1.1	INTEGER	read-only	A unique value which identifies this HSM board slot.
frxVcStatsTable	1.3.6.1.4.1.800.2.8.4.1		not-accessible	A table of Frame Relay virtual circuit statistics information.
CTR frxVcStatsTx8025Frames	1.3.6.1.4.1.800.2.8.4.1.1.21	Counter	read-only	The total number of transmitted 8025 frames on this virtual circuit.
CTR frxVcStatsTx8025Octets	1.3.6.1.4.1.800.2.8.4.1.1.20	Counter	read-only	The total number of transmitted octets (including the Frame Relay Header field) within 8025 frames on this virtual circuit.
CTR frxVcStatsTxBPDUFrames	1.3.6.1.4.1.800.2.8.4.1.1.13	Counter	read-only	The total number of transmitted BPDU frames on this virtual circuit.
CTR frxVcStatsTxBPDUOctets	1.3.6.1.4.1.800.2.8.4.1.1.12	Counter	read-only	The total number of transmitted octets (including the Frame Relay Header field) within BPDU frames on this virtual circuit.
CTR frxVcStatsTxCompressedFrames	1.3.6.1.4.1.800.2.8.4.1.1.29	Counter	read-only	The total number of transmitted compressed format frames on this virtual circuit.
CTR frxVcStatsTxCompressedOctets	1.3.6.1.4.1.800.2.8.4.1.1.28	Counter	read-only	The total number of transmitted octets (including the Frame Relay Header field) within compressed format frames on this virtual circuit.
CTR frxVcStatsTxEthernetFrames	1.3.6.1.4.1.800.2.8.4.1.1.17	Counter	read-only	The total number of transmitted bridged 802.3 format frames on this virtual circuit.
CTR frxVcStatsTxEthernetOctets	1.3.6.1.4.1.800.2.8.4.1.1.16	Counter	read-only	The total number of transmitted octets (including the Frame Relay Header field) within bridged 802.3 format frames on this virtual circuit.
CTR frxVcStatsTxFDDIFrames	1.3.6.1.4.1.800.2.8.4.1.1.25	Counter	read-only	The total number of transmitted FDDI frames on this virtual circuit.
CTR frxVcStatsTxFDDIOctets	1.3.6.1.4.1.800.2.8.4.1.1.24	Counter	read-only	The total number of transmitted octets (including the Frame Relay Header field) within FDDI frames on this virtual circuit.
CTR frxVcStatsTxIPFrames	1.3.6.1.4.1.800.2.8.4.1.1.5	Counter	read-only	The total number of transmitted routed IP format frames on this virtual circuit.
CTR frxVcStatsTxIPOctets	1.3.6.1.4.1.800.2.8.4.1.1.4	Counter	read-only	The total number of transmitted octets (including the Frame Relay Header field) within routed IP format frames on this virtual circuit.
CTR frxVcStatsTxIPXFrames	1.3.6.1.4.1.800.2.8.4.1.1.9	Counter	read-only	The total number of transmitted routed IPX format frames on this virtual circuit.
CTR frxVcStatsTxIPXOctets	1.3.6.1.4.1.800.2.8.4.1.1.8	Counter	read-only	The total number of transmitted octets (including the Frame Relay Header field) within routed IPX format frames on this virtual circuit.
CTR frxVcStatsTxPrecompressedOctets	1.3.6.1.4.1.800.2.8.4.1.1.32	Counter	read-only	The total number of octets (including the Frame Relay Header field) prior to compression of data for transmission within compressed format frames on this virtual circuit.

RFC description

Manages Xylan OmniSwitch Frame Relay PVC configuration, DLCI status, and traffic shaping parameters.

Start monitoring Xylan OmniSwitch device (legacy Frame Relay PVC/DLCI admin-status/traffic-shaping 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.

Download XYLAN-FRAME-RELAY-MIB

What Is XYLAN-FRAME-RELAY-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description