Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Frame-Relay Broadcast-Queue


I am needing to implement Frame-Relay Broadcast-Queue in a network I currently manage, however I can’t find any detailed information usage and how to calculate out the correct parameters. It’s a very large network currently suffering from lots of dropped eigrp broadcasts and causing, both eigrp neighbor changes and SIA issues. I’ve read all the Cisco documentation on their website, but no luck. For instance:

Do you apply the Frame-Relay Broadcast-Queue to the parent or sub-interface?

Are the calculations based upon all DLCI’s on the router, or just the parent and related sub-interfaces?

Is their a formula I could use to figure out what numbers to use for the Frame-Relay Broadcast-Queue command?

New Member

Re: Frame-Relay Broadcast-Queue

It's been a while, but I think the broadcast queue is applied to the main interface & the calculation is based on the number of DLCIs/sub-interfaces on that interface.

From the

Cisco - Configuring and Troubleshooting Frame Relay

web page that I saved in 1999

A broadcast queue is given a maximum transmission rate (throughput) limit measured in bytes per second and packets per second. The queue is serviced to ensure that only this maximum is provided. The broadcast queue has priority when transmitting at a rate below the configured maximum, and hence has a guaranteed minimum bandwidth allocation. The two transmission rate limits are intended to avoid flooding the interface with broadcasts. The actual limit in any second is the first rate limit that is reached. Given the transmission rate restriction, additional buffering is required to store broadcast packets. The broadcast queue is configurable to store large numbers of broadcast packets. The queue size should be set to avoid loss of broadcast routing update packets. The exact size depends on the protocol being used and the number of packets required for each update. To be safe, the queue size should be set so that one complete routing update from each protocol and for each data-link connection identifier (DLCI) can be stored. As a general rule, start with 20 packets per DLCI. The byte rate should be less than both of the following:

N/4 times the minimum remote access rate (measured in bytes per second), where N is the number of DLCIs to which the broadcast must be replicated

1/4 the local access rate (measured in bytes per second)

The packet rate is not critical if the byte rate is set conservatively. In general, the packet rate should be set assuming 250-byte packets. The defaults are 64 queue size, 256,000 bytes per second (2,048,000 bps), and 36 pps.