ATM Configuration and Troubleshooting Guide

Supported Standards

Internet RFCs

Chapter 12 321

Address Registration Support

The only functionality based on ILMI on the user-side UME is the

address registration facility. This means that no proprietary extensions

are deﬁned.

The address registration procedures as speciﬁed in UNI 3.0/3.1 section

5.8, and ILMI 4.0 section 9 are supported, with the following

implementation-speciﬁc choices:

• Only private ATM address formats are supported.

• Only User Side UME is supported (refer to UNI 3.0/3.1 section

5.8.5.2). This means the address registration procedures do not work

in back-to-back conﬁgurations.

• Only one ESI (End System Identiﬁer, or MAC address) is supported

for each ATM adapter. No mechanism is provided to dynamically add

or delete other “User Parts.”

• More than one network preﬁx is supported. This means that the

network can register several preﬁxes and that the “User Part” (ESI +

Selector) will be registered with all the preﬁxes. The user-side UME

rejects preﬁxes with the public E164 format.

• The Address Registration entity does not periodically check correct

registration of addresses at the network-side UME (refer to UNI

3.0/3.1 section 5.8.5.2).

• As soon as the Address Registration entity is started, it continuously

tries to complete the initial address registration sequence by sending

appropriate SNMP requests and traps.

NOTE There are various reasons why the initial address registration

sequence might not be completed. Some of these are a disconnected

link; a switch that does not support UNI 3.0, 3.1, or 4.0; a switch port

conﬁgured for a different version of UNI than the ATM adapter to

which it is connected; or a back-to-back connection. If the initial

address registration sequence is not completed, the network

preﬁx(es) is (are) unknown. Consequently, the whole ATM address is

unknown. This can affect ATM components that need ATM

addresses (such as signaling, ATM ARP, and conﬁguration).