If the LE server is in another cluster (NNI links):
1. The NNI network-side/user-side definition rules have not been applied.
Check that one side of the NNI link is defined as user, and that the other side is
defined as network.
2. No logical-link has been defined for the NNI port.
Define the logical link, using the SET LOGICAL_LINK command.
3. The peer logical links do not match (bad vpi, cluster, or bandwidth match).
Check that the logical links on both sides do match, and if necessary, clear
those logical links are re-define them.
4. No static route has been defined, if the ONcore hub and the LE server are in
different ATM subnetworks.
Define the static routes using the SET STATIC_ROUTE command.
5. A static route was badly configured.
Check the static routes, using the SHOW STATIC_ROUTE command.
6. The VP-tunnel is defective.
Ask your VP-tunnel provider to test it.
Cause Codes: 16/31
Explanation: The connection has been voluntarily rejected the LE server. The reason
depends on LE server implementation.
Cause Codes: 18/102
Explanation: The LE server is present, but not started.
Cause Code: 47
Explanation: There may be a lack resources on the LE server side preventing
connection to it.
7-32 ONcore ATM Switch/Control Module: Installation and User's Guide
