ATM Configuration and Troubleshooting Guide

Troubleshooting

Troubleshooting MPOA

Chapter 9 261

E Check for MPS discovery. Use the command mpcarp to see whether

the local gateway/router (whose IP address you used when you issued the

route command [see “B” on page 255]) has been recognized as an

MPOA-capable device (an MPS) by the local ATM host.

Shown below is part of the output of the mpcarp command issued on

host51 in our example. The last section of the output (“MPOA Routers

Table for Primary LEC”) shows the list of MPSs discovered by the

speciﬁed MPOA-capable LAN Emulation interface. In the example

below, one MPS is shown.

host51:/> mpcarp -n el200

MPOA Routers (MPOA Servers) Table for LEC interface el100:

MPOA Routers (MPOA Servers) Table for Primary LEC:

MPS MAC

(MPS Router)

Address Router MPS Address

------------ ------------------------------------------

0000ef03a860 47000580ffe1000000f21c4c21.0000ef03a864.92

If the list of discovered MPSs is empty, you might have a conﬁguration

problem on the device hosting the MPS (most probably the router).

Consult your router’s documentation and check its conﬁguration and

status. If the problem persists, contact HP.

If your MPS is shown in the routers table but all the MPOA VCs are not

established, ﬁrst ensure that the data trafﬁc volume is sufﬁcient to be

considered a data ﬂow (see the list of assumptions after the ﬂowchart

[Figure 9-14 on page 253]).

F Check the routers’ MPOA conﬁguration. Verify the MPOA-related

conﬁguration of your routers. Look for any limitation or incompatibility

in the release notes, if any, published for the routers.

If the destination is an ATM-attached MPOA-capable HP system, repeat

ﬂowchart steps “A” through “E” using the destination system as the data

source, to validate its MPOA conﬁguration.

If the destination is an ATM-attached MPOA-capable non-HP system,

consult the manufacturer’s documentation for MPOA conﬁguration

guidelines.