ATM-FORUM-ADDR-REG

All MIBs › ATM-FORUM-ADDR-REG

Category: ATM

Description: Defines ATM Forum address registration objects for mapping network service access points (NSAPs) to ATM ports.

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 ATM-FORUM-ADDR-REG?

ATM-FORUM-ADDR-REG defines ATM Forum address registration objects for mapping network service access points (NSAPs) to ATM switch ports. It exposes tables for registered network prefixes and end-system ATM addresses per port, along with row status for each registration entry. Its monitoring emphasis is on software/configuration status rather than hardware: the registration row status reveals whether an address or prefix registration remains active and correctly bound to a physical port, which is essential to troubleshoot a signaling failure caused by a stale or missing registration. It is explicitly based on the ATM Forum's UNI signaling specification and complements the standard ATM-MIB (RFC 2515). It is used on ATM switches and edge devices in legacy ATM networks that rely on dynamic address registration for signaling. Engineers can download the ATM-FORUM-ADDR-REG file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in ATM-FORUM-ADDR-REG. 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

vendor-neutral, standards-based MIB (ATM Forum specification), applies to ATM switches and edge devices

Monitoring Examples

atmfNetPrefixTable/atmfNetPrefixEntry exposes atmfNetPrefixPort, atmfNetPrefixPrefix, and atmfNetPrefixStatus, while atmfAddressTable/atmfAddressEntry exposes atmfAddressPort, atmfAddressAtmAddress, and atmfAddressStatus. An administrator would poll atmfAddressStatus to confirm an end system's ATM address registration remains active on its port, and check atmfNetPrefixTable to verify the correct network prefix is bound to that port before troubleshooting a signaling setup failure.

What Can Be Monitored

NSAP prefix-to-port mapping
registered ATM address per port
address registration row status
organizational scope of address registration

Imported Objects

From ATM-FORUM-TC-MIB

AtmAddress
NetPrefix
atmfAddressGroup	OBJECT-IDENTITY
atmfAddressRegistrationAdminGroup	OBJECT-IDENTITY
atmfNetPrefixGroup	OBJECT-IDENTITY

From RFC-1212

OBJECT-TYPE

OIDs

OID symbolic	OID numeric	Type	Access	Description
ADR atmfAddressAtmAddress	1.3.6.1.4.1.353.2.6.1.1.2	AtmAddress	read-only	The ATM address which is in effect on the user side of the ATM UNI port.
atmfAddressEntry	1.3.6.1.4.1.353.2.6.1.1		not-accessible	Information about a single ATM-layer address in effect on the user-side IME. Note that the index variable atmAddressAtmAddress is a variable-length string, and as such the rule for variable-length strings in section 4.1.6 of RFC 1212 applies.
INT atmfAddressOrgScope	1.3.6.1.4.1.353.2.6.1.1.4	INTEGER	read-write	This object indicates the organizational scope for the referenced address. The information of the referenced address shall not be distributed outside the indicated scope. If the user-side IME does not specify a value for the atmfAddressOrgScope object, the network shall set the value of this object to localNetwork(1), if the registered address is an ATM group address, or to global(15), if the registered address is an individual address. Refer to Annex 6.0 of ATM Forum UNI Signalling 4.0 for guidelines regarding the use of organizational scopes. This organization hierarchy may be mapped to ATM network's routing hierarchy such as PNNI's routing level and the mapping shall be configurable in nodes. Use of this object in a public network is for further study. The default values for organizational scope are localNetwork(1) for ATM group addresses, and global(15) for individual addresses.
INT atmfAddressPort	1.3.6.1.4.1.353.2.6.1.1.1	INTEGER	read-only	A unique value which identifies the UNI port for which the ATM address is in effect. The value of 0 has the special meaning of identifying the local UNI.
atmfAddressRegistrationAdminEntry	1.3.6.1.4.1.353.2.11.1.1		not-accessible	An entry in the table, containing Address Registration administrative information for the ATM Interface.
INT atmfAddressRegistrationAdminIndex	1.3.6.1.4.1.353.2.11.1.1.1	INTEGER	read-only	The value of 0 which has the special meaning of identifying the ATM Interface over which this message was received.
INT atmfAddressRegistrationAdminStatus	1.3.6.1.4.1.353.2.11.1.1.2	INTEGER	read-only	An indication of whether or not Address Registration is supported on this ATM Interface. Supported(1) indicates that this ATM Interface supports address registration. Unsupported(2) indicates that this ATM Interface does not support address registration.
atmfAddressRegistrationAdminTable	1.3.6.1.4.1.353.2.11.1		not-accessible	A table of Address Registration administrative information for the ATM Interface.
INT atmfAddressStatus	1.3.6.1.4.1.353.2.6.1.1.3	INTEGER	read-write	An indication of the validity of the ATM address at the user side of the UNI port. To configure a new address in this table, the user-side IME must set the appropriate instance of this object to the value valid(1). To delete an existing address in this table, the user-side IME must set the appropriate instance of this object to the value invalid(2). If circumstances occur on the network-side IME which cause an address to become invalid, the network-side IME modifies the value of the appropriate instance of this object to invalid(2). Whenever the value of this object for a particular address becomes invalid(2), the conceptual row for that address may be removed from the table at any time, either immediately or subsequently.
atmfAddressTable	1.3.6.1.4.1.353.2.6.1		not-accessible	A table implemented by the network-side IME, containing the ATM-layer addresses in effect on the user side of the UNI.
atmfNetPrefixEntry	1.3.6.1.4.1.353.2.7.1.1		not-accessible	Information about a single network-prefix for ATM-layer addresses in effect on the user-side IME. Note that the index variable atmNetPrefixPrefix is a variable-length string, and as such the rule for variable-length strings in section 4.1.6 of RFC 1212 applies.
INT atmfNetPrefixPort	1.3.6.1.4.1.353.2.7.1.1.1	INTEGER	read-only	A unique value which identifies the UNI port for which the network prefix for ATM addresses is in effect. The value of 0 has the special meaning of identifying the local UNI.
NET atmfNetPrefixPrefix	1.3.6.1.4.1.353.2.7.1.1.2	NetPrefix	read-only	The network prefix for ATM addresses which is in effect on the user side of the ATM UNI port.
INT atmfNetPrefixStatus	1.3.6.1.4.1.353.2.7.1.1.3	INTEGER	read-write	An indication of the validity of the network prefix for ATM addresses on the user side of the UNI port. To configure a new network prefix in this table, the network-side IME must set the appropriate instance of this object to the value valid(1). To delete an existing network prefix in this table, the network-side IME must set the appropriate instance of this object to the value invalid(2). If circumstances occur on the user-side IME which cause a prefix to become invalid, the user-side IME modifies the value of the appropriate instance of this object to invalid(2). Whenever the value of this object for a particular prefix becomes invalid(2), the conceptual row for that prefix may be removed from the table at any time, either immediately or subsequently.
atmfNetPrefixTable	1.3.6.1.4.1.353.2.7.1		not-accessible	A table implemented by the user-side IME, containing the network-prefix(es) for ATM-layer addresses in effect on the user side of the UNI.

RFC description

Manages ATM address registration and network prefix configuration at the UNI interface.

Start monitoring ATM switches and edge devices (ATM Forum address registration) 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 ATM-FORUM-ADDR-REG

What Is ATM-FORUM-ADDR-REG?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description