Specifications

5-14
Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches
Release 5.2, Part Number OL-6484-01 Rev. C0, September 2005
Chapter 5 AXSM Command Reference
addcon
Limits
The following limitations apply to single-ended connections.
• Continuity checking (-cc option in the addcon command) is not supported.
• AIS is generated at both ends of the connection. However, at the slave endpoint, AIS is visible only
through node-level CLI commands. For example, AIS is not reported to CWM.Termination of a
single-ended connection is supported on most platforms except the following:
– Feeder nodes
– Legacy cards
• You can use the tstdelay command at the master endpoint only.
Characteristics Multicast Operation
Point-to-multipoint (P2MP) connections are added at the master endpoint only. You do not specify an
NSAP in this case. After the connection has been added, you can add multiple parties by using the
addparty command on the PXM on the source node. In the addparty command, you can provide an
NSAP for the remote endpoint (the party). The nature of P2MP connections significantly affects the
connection services that are available to these connections. This section describes these effects.
• Remote endpoints are always non-persistent. Because multicasting involves more than one endpoint,
non-persistent P2P connections cannot override P2MP connections even if the override option has
been enabled for the interface through the cnfpnportcc command.
• P2MP connections are considered for route optimization (or grooming) based on branching. Thus,
PNNI skips P2MP grooming when you use either the optrte, cnfrteopt, or cnfrteopt command. Use
rrtcon to trigger P2MP re-routing. (This branching criterion differs from that of P2P connection
grooming. which is based on the sum of administrative weights along prospective routes.)
• P2MP connections are excluded from the Preferred Route feature. The system blocks any attempt to
assign a preferred route to a P2MP connection.
• For the Priority Routing feature, P2MP connections have the default priority of 8. Cisco suggests
that you not change routing priority for any P2MP connection even though the system lets you do it.
• When PNNI de-routes multiple connections, P2MP connections have the lowest de-routing priority.
• The default, connection-based percent utilization is 100 and is to be used for P2MP connections.
The system ignores any attempt to configure a percent utilization for P2MP connections.If the port
where you add a P2MP connection does not support egress multicast, subsequent addition of a party
is rejected because the port cannot support branches on that port.
• Throughout the duration of a P2MP call, if the port-level subscription option (specified through
cnfpnportcc) originally was disabled, then enabled, and again disabled, the parties become
unequally distributed on that port. The following scenario illustrates this behavior:
– Port 1:1.1:1 currently has one leaf with one party, and the subscription option is disabled.
– Subscription option is enabled through the cnfpnportcc command.
– Subsequent ADDPARTY message creates a leaf. This action results in two leafs (with one party
each) on that P2MP connection on port 1:1.1:1.
– Subscription option is again disabled.
– A subsequent ADDPARTY does not create a leaf although the ADDPARTY is sent. However,
the parties are not equally distributed among the two leaves. Suppose three ADDPARTYs go to
port 1:1.1:1 on that call: all three parties are added to one leaf. The result is one leaf with four
parties and one leaf with just one party.