cc/td/doc/product/wanbu/bpx8600/9_3_1
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Configuring BME Multicasting

Configuring BME Multicasting

This chapter presents an overview of multicasting, a description of the BME card used on the BPX switch for multicasting for PVCs, and configuration instructions:

The BME provides multicast services in the BPX switch. It is used in conjunction with a two-port OC-12 backcard.

Multicasting point-to-multipoint services meets the demands of those requiring virtual circuit replication of data (Frame Relay and ATM) performed within the network. Some examples of functions benefiting from multicasting are:

BME Standards are:

Multicasting point-to-multipoint connections benefits include:

BME Features

BME Requirements

BME Restrictions

Address Criteria

For example, if 12.1.50.0 is added on port 1, then the leaves should be:

12.2.50.50
12.2.50.100
12.2.50.101 and so on.

Similarly, if a root 12.2.60.0 is added on port 2, then the leaves should be

12.1.60.101
12.1.60.175, and so on.

Connection Management Criteria

Root connections and leaf connections can be added in any order:

Root and leaf connections can be deleted in any order.

Root can be deleted and replaced with a new root.

Connection Management with Cisco WAN Manager

Cisco WAN Manager management includes these functions:

BME Operation

Cables are connected between port 1 and port 2 of the backcard, transmit to receive and receive to transmit.


Note   Removing the physical loopback cables or placing line 1 or 2 into loopback will prevent the cells from the root reaching the leaves.

BME Cell Replication

Figure 26-1 shows a BME with a single root input multicasting with 3 leaves. The root connection can be added at a BPX switch (BPX switch A) distant from where the traffic is replicated by the BME card (BPX switch F) and routed through a number of BPX nodes. Similarly, the leaves can be routed from the multicasting node through a number of nodes before reaching their destination.


Figure 26-1: Replication of a Root Connection into Three Leaves


Cell Replication Stats

As an example of how traffic appears on the BME, if there is one root at port 1 with two leaves at port 2, and traffic is passed on the root at 500 cells per sec, then one should see an egress port stat of 1000 cells per sec on port 1 and an ingress port stat of 1000 cells per sec on port 2, as shown in Figure 26-2.


Figure 26-2: Example of Traffic, One Root and Two Leaves


Adding Connections

Two multicasting groups are shown in Figure 26-3. For purposes of the illustration only a few leaves are shown for each connection. However, as described previously, each multicasting group could contain up to 8064 connections.

In this example, the two connections with a VCI of 0 each define a multicasting root connection. Their VPI defines a broadcasting group.

One group is defined by 2.1.70.0, where the VCI of zero defines the root connection to a BME, and the VPI of 70 defines a group. All the leaves in that group are of the form 2.2.70.x.

The other group is defined by 2.2.80.0, where the VCI of zero defines the root connection to a BME, and the VPI of 80 defines a group. All the leaves in that group are of the form 2.1.80.x.

Group 2.1.70.x Action Command

at bpx switch_F,

add input to root

addcon 2.1.70.0 bpx switch_A 1.1.80.100 c 500 * * *

at bpx switch_F,

add leaf 1

addcon 2.2.70.101 bpx switch_D 6.1.100.50 c 500 * * *

at bpx switch_F,

add leaf 2

addcon 2.2.70.100 bpx switch_C 4.3.50.60 c 500 * * *

at bpx switch_F,

add leaf 3

addcon 2.2.70.102 bpx switch_G 3.4.55.75 c 500 * * *

Group 2.2.80.x

at bpx switch_F,

add input to root

addcon 2.2.80.0 bpx switch_B 10.1.233.400 v 4000 * * *

at bpx switch_F,

add leaf 1

addcon 2.1.80.201 bpx switch_E 13.1.78.900 v 4000 * * *

at bpx switch_F,

add leaf 2

addcon 2.1.80.100 bpx switch_E 14.1.100.40 v 4000 * * *


Figure 26-3: Adding Multicasting Connections


Multisegment Multicast Connections

Figure 26-4 shows an example of a multisegment multicast connection where a leaf connection from one BME can become a root connection for another BME. This capability allows the users to configure multisegment, multicast tree topologies.


Figure 26-4: Multi-Segment Multicast Connections


Multicast Statistics

Channel statistics are available for leaf connections on the BME end. However, channel statistics are not available for the root connection on the BME end.

For the example in Figure 26-5, execute the following commands to display channel statistics for the leaf connections:

For the example in Figure 26-5, the following command will not display channel statistics (because 5.1.75.0 is a root connection):


Figure 26-5: Statistics Collection


Policing

Policing is supported on all leaf connections on the BME end.

All policing types available on the BXM are available on the BME leaves.

No policing functionality is available on the root connection on the BME end.

Hot Standby Backup

BME cards can be set up to provide hot standby backup. Both cards are set up with port 1 connected to port 2 on the same card to provide the multicasting connection, transmit to receive and receive to transmit. There is no Y-cabling connection between the cards, and they do not have to be adjacent to each other.

Use the addyred command to enable hot standby backup between the cards.


Note   The addyred command must be used before any connections are added to the active card. The command will be rejected if used after connections have been added to the active card.

Configuration

If the multicast tree has a large number of leaf connections, for example, 3000, then the cnfportq command should be used to configure the Qbin threshold to be greater than needed for half the number of leaves so as to assure that the multicast group will have no discards. The Qbin default depth is about 1200 cells.

The following is a Qbin example using the cnfportq command:

j4b VT SuperUser ~ BPX 15 9.3 March 24 2000 16:59 PST Port: 3.2 [ACTIVE ] Interface: LM-BXM Type: NNI Speed: 1412830 (cps) SVC Queue Pool Size: 0 CBR Queue Depth: 1200 CBR Queue CLP High Threshold: 80% CBR Queue CLP Low Threshold: 60% CBR Queue EFCI Threshold: 80% VBR Queue Depth: 10000 UBR/ABR Queue Depth: 40000 VBR Queue CLP High Threshold: 80% UBR/ABR Queue CLP High Threshold: 80% VBR Queue CLP Low Threshold: 60% UBR/ABR Queue CLP Low Threshold: 60% VBR Queue EFCI Threshold: 80% UBR/ABR Queue EFCI Threshold: 30% This Command: cnfportq 3.2 SVC Queue Pool Size [0]: Virtual Terminal CD


hometocprevnextglossaryfeedbacksearchhelp
Posted: Fri Jul 27 17:53:42 PDT 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.