This soft copy for use by IBM employees only.
1 This SHOW DEVICE command was issued when the server was up and the clients have requested to be registered. This command can be used to check the status of each LEC on the IBM 8285, especially if they are registered with an external LES.
2 This line shows the ELAN type and Ethernet type of the LEC. The ethernet/802.3 means the ELAN type is Ethernet and the Ethernet type is 802.3. Don′t make the mistake of thinking that ethernet/802.3 means that both DIX and 802.3 Ethernet types are supported. The LEC on the IBM 8285 can support either of them and the status should be ethernet/DIX when the Ethernet type is DIX.
3 The appropriate values in these fields means that the registration process has been successfully completed since these values are returned by the LES.
The typical reasons a LEC might be unable to register with the LES are as follows:
•ATM switch connection
If the LECs are attached to a different switch, check to see if the connection between the switches has been established.
•Designated LES address
Check if the designated LES ATM address specified for the LEC, especially the SEL field, is correct.
•Max SDU size/ELAN name
Check if the same maximum SDU size and ELAN name are defined on the LEC and LES. If these values don′t match, the registration process fails. And some LECs, such as IBM 8285 internal LEC, don′t have specific values
for itself, but instead gets the values from its LES.
•Registration sequence
Reissue the LANE registration request from the LEC. Several devices have
limited retry counts to issue the registration request and only do so during the initialization phase. Therefore, they won′t register when the LES is
restarted. And the network or the LES congestion may prevent them from the successfully completing the registration process within the allowed period.
For example, PCs using the IBM ATM device driver have retry count limit for the registration request but IBM 8281 and 8285 internal LECs do not.
7.2.4.3 Other Considerations
When the communication between LECs is unable to be established even though both LECs are registered with the LES, the typical reasons are as follows:
•Ethernet type
Check to see if the same Ethernet type is configured for both LECs. For LECs to communicate with each other, they should be configured with the same Ethernet type, 802.3 or DIX/Ethernet V2.
If one of the LECs that is unable to communicate is the IBM 8285′s, you can check the Ethernet type from the console using SET DEVICE command as shown in Figure 45 on page 140.
•IP network number
Chapter 7. IBM 8285 Configuration 143
