Table of Contents

F Commands

The commands shown in this chapter apply to the Catalyst 8540 MSR, Catalyst 8510 MSR, and LightStream 1010 ATM switch routers. Where an entire command or certain attributes of a command have values specific to a particular switch or switch router, an exception is indicated by the following callouts:

Refer to Appendix D of this command reference for a detailed list of commands that have been removed, changed or replaced.

facility-alarm (Catalyst 8540 MSR)

To configure the temperatures so that the ATM switch router declares a major or minor alarm condition, use the facility-alarm command. You can configure explicit threshold temperatures
(in degrees Celsius [° C]) to override the defaults for major and minor alarms. Use the no form of this command to disable alarms for that threshold and reset the threshold to the default value.

facility-alarm core-temperature {major [temperature] | minor [temperature]}

no facility-alarm core-temperature {major [temperature] | minor [temperature]}

Syntax Description

Defaults

major is 53° C.
minor is 45° C.

Command Modes

Global configuration

Command History

Usage Guidelines

You cannot disable or adjust the system critical alarms threshold. A "critical" alarm is standard Telco terminology for the alarm just before the system powers itself off.

Examples

The following example shows how to configure facility alarms to 50° C for major alarms, and 38° C for minor alarms.

Related Commands

failed-attempts

To configure the writing of records for initial connection attempts, use the failed-attempts ATM accounting file subcommand. To disable this feature, use the no form of this command.

failed-attempts [none | [regular | soft]]

no failed-attempts

Syntax Description

Defaults

regular and soft

Command Modes

ATM accounting file

Command History

Examples

The following example shows entering the ATM accounting file configuration mode and configuring failed-attempts to record failed attempts for SVC/SVP connections in the accounting file.

Related Commands

fdl (Catalyst 8510 MSR and LightStream 1010)

To enable the FDL capability provided on the T1 board, use the fdl interface configuration command. To restore the default, use the no form of this command.

fdl {ansi | att}

no fdl

Syntax Description

Defaults

Both ansi and att are disabled.

Command Modes

Interface configuration

Command History

Usage Guidelines

The T1 board responds to requests in both ANSI and ATT format, but is only able to gather the remote end data in ANSI format. The T1 board complies to ANSI standard T1.403

FDL packets are used to collect data from the remote end. To enable the FDL capability, it is necessary to know whether the remote end supports FDL functionality.

The mode selected depends upon which mode is supported on the remote end.

Examples

The following example shows how to enable FDL capabilities in both ANSI and ATT mode.

The following example shows how to disable FDL capabilities in both ANSI and ATT mode.

Related Commands

None

format

To format Flash memory, use the format privileged EXEC command.

format device1: [[device2:] [monlib-filename]]

Caution    The following formatting procedure erases all information in the Flash memory. To prevent the loss of important data, proceed carefully.

Syntax Description

Defaults

The default monlib file is the one bundled with the system software.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

Use the format command to format internal Flash memory (bootflash) or your Flash memory cards.

In some cases, you might need to insert a new PCMCIA Flash memory card and load images or backup configuration files onto it. Before you can use a new Flash memory card, you must format it.

Flash memory cards have sectors that can fail. You can reserve certain Flash memory sectors as "spares" for use when other sectors fail. Use the format command to specify between 0 and 16 sectors as spares. If you reserve a small number of spare sectors for emergencies, you do not waste space because you can use most of the Flash memory card. If you specify zero spare sectors and some sectors fail, you must reformat the Flash memory card and thereby erase all existing data.

The monlib file is the ROM monitor library. The ROM monitor uses the monlib file to access files in the Flash file system.

In the command syntax, device1 is the device to format, and device2 contains the monlib file to use. When you omit the [[device2:][monlib-filename]] argument, the system formats device1 using the monlib file that is bundled with the system software. When you omit device2 from the [[device2:][monlib-filename]] argument, the system formats device1 using the named monlib file from the device specified by the cd command. When you omit monlib-filename from the [[device2:][monlib-filename]] argument, the system formats device1 using device2's monlib file. When you specify the whole [[device2:][monlib-filename]] argument, the system formats device1 using the specified monlib file from the specified device. Note that you can specify device1's own monlib file in this argument. When the system cannot find a monlib file, the system terminates the formatting process.

Examples

The following example shows the format command that formats a Flash memory card inserted in slot 0 of the route processor card.

When the switch returns you to the EXEC prompt, the new Flash memory card is successfully formatted and ready for use.

Related Commands

frame-relay bc-default

To configure the committed burst size for ABR or UBR soft VCs terminating on an interface, use the frame-relay bc-default interface configuration command. To disable the committed burst size, use the no form of this command.

frame-relay bc-default bc_default

no frame-relay bc-default

Syntax Description

Defaults

32768

Command Modes

Interface configuration

Command History

Usage Guidelines

Use the frame-relay bc-default interface parameter to configure the committed burst size
(in bits) on the destination interface of a UBR or ABR soft VC connection.

The configured committed burst size is then effective for any subsequent connections.

Examples

The following example shows how to configure the Frame Relay committed burst size to 16384 for serial interface 11/0/0:1.

Related Commands

frame-relay connection-traffic-table-row

To create a table entry in the Frame Relay connection-traffic table, use the frame-relay connection-traffic table-row global configuration command. To delete an entry, use the no form of this command.

frame-relay connection-traffic table-row [index row-index] cirval bcval pirval [beval]
{abr | vbr-nrt | ubr} [arrow-index]

no frame-relay connection-traffic table-row [index row-index]

Syntax Description

Defaults

See "Syntax Description."

Command Modes

Global configuration

Command History

Usage Guidelines

When you create a connection traffic table row, the Frame Relay parameters are converted into the ATM equivalent parameters and a row is added to the ATM connection-traffic table. The table index values are shared by the Frame Relay connection table and the ATM connection table. If you specify the index in the command, the index value is available in the ATM connection table.

Note   Since the index value is linked to the ATM connection-traffic table, the index values in the Frame Relay connection-traffic table might not be contiguous.

Examples

The following example shows how to create a table entry with a row index of 150, committed information rate of 1024000, committed burst size of 16334, peak information rate of 1024000, excess burst size of 20, and the abr service category with an ATM row index of 250.

Related Commands

frame-relay input-queue

To configure discard marking thresholds on a Frame Relay interface in the input direction, use the frame-relay input queue interface configuration command. Use the no form of the command to revert to default values for the threshold.

frame-relay input-queue {abr | ubr | vbr-nrt} {discard-threshold |
marking-threshold} percent

no frame-relay input-queue {abr | ubr | vbr-nrt} {discard-threshold |
marking-threshold} percent

Syntax Description

Defaults

See "Syntax Description."

Command Modes

Interface configuration

Command History

Usage Guidelines

This command affects all existing connections on the interface, as well as subsequent connections.

Examples

The following example sets the Frame Relay input queue for ABR connects to allow EFCI marking for cells over 75 percent of capacity.

Related Commands

frame-relay intf-type

To configure an interface as DCE or NNI, use the frame-relay intf-type interface configuration command. To disable the configuration, use the no form of this command.

frame-relay intf-type {dce | nni}

no frame-relay intf-type {dce | nni}

Syntax Description

Defaults

nni

Command Modes

Interface configuration

Command History

Usage Guidelines

When you specify DCE, the ATM switch router supports only network-side PVC status
management procedures. When you specify NNI, the ATM switch router supports both user-side
and network-side PVC status management procedures.

Note   Frame Relay DTE is not supported.

Examples

The following example configures serial interface 11/0/0:1 as Frame Relay interface, type DCE.

Related Commands

frame-relay lmi-n391dte

To set a full status polling interval, use the frame-relay lmi-n391dte interface configuration command. To restore the default interval value, use the no form of this command.

frame-relay lmi-n391dte keep-exchanges

no frame-relay lmi-n391dte keep-exchanges

Syntax Description

Defaults

6 keep exchanges

Command Modes

Interface configuration

Command History

Usage Guidelines

To set the full status message polling interval, use this command when the interface is configured
as NNI.

Examples

The following example shows how to set one out of every four status inquiries to request a full status response from the switch. The remaining three status inquiries request only keepalive exchanges.

Related Commands

frame-relay lmi-n392dce

To set the error threshold on DCE and NNI interfaces, use the frame-relay lmi-n392dce interface configuration command. To remove the setting, use the no form of this command.

frame-relay lmi-n392dce threshold

no frame-relay lmi-n392dce threshold

Syntax Description

Defaults

Two errors

Command Modes

Interface configuration

Command History

Usage Guidelines

N392 errors must occur within the number defined by the N393 event count for the link to be down. Therefore, the threshold value for this command must be less than the count value defined in the frame-relay lmi-n393dce command.

Examples

The following example configures serial interface 11/0/0:1 with Frame Relay LMI monitoring event count to four.

Related Commands

frame-relay lmi-n392dte

To set the error threshold on DTE or NNI interfaces, use the frame-relay lmi-n392dte interface configuration command. To remove the setting, use the no form of this command.

frame-relay lmi-n392dte threshold

no frame-relay lmi-n392dte threshold

Syntax Description

Defaults

Three errors

Command Modes

Interface configuration

Command History

Usage Guidelines

The frame-relay lmi-n392dte and frame-relay lmi-n393dte commands define the condition that causes the link to be declared down. Two "threshold" errors must occur within N393 number of events for the link to be declared down.

Examples

The following example shows how to set the LMI error threshold to six.

Related Commands

frame-relay lmi-n393dce

To set the monitored events count on DCE and NNI interfaces, use the frame-relay lmi-n393dce interface configuration command. To remove the setting, use the no form of this command.

frame-relay lmi-n393dce events

no frame-relay lmi-n393dce events

Syntax Description

Defaults

Two events

Command Modes

Interface configuration

Command History

Usage Guidelines

This command and the frame-relay lmi-n392dce command define the condition that causes the link to be down. In the Cisco implementation, N392 errors must occur within the events count for the link to be down. Therefore, the events value that you define for this command must be greater than the threshold value defined in the frame-relay lmi-n392dce command.

Examples

The following example shows how to set the LMI monitored event count to three.

Related Commands

frame-relay lmi-n393dte

To set the monitored event count on DTE and NNI interfaces, use the frame-relay lmi-n393dte interface configuration command. To remove the setting, use the no form of this command.

frame-relay lmi-n393dte events

no frame-relay lmi-n393dte events

Syntax Description

Defaults

Four events

Command Modes

Interface configuration

Command History

Usage Guidelines

The frame-relay lmi-n393dte and the frame-relay lmi-n392dte commands define the condition that causes the link to be declared down. N392 errors must occur within the events count for the link to be declared down.

Note   The events value defined in this command must be greater than the threshold value defined in the frame-relay lmi-n392dte command.

Examples

The following example shows how to set the LMI monitored events count to three.

Related Commands

frame-relay lmi-t392dce

To set the polling verification timer on DCE and NNI interfaces, use the frame-relay lmi-t392dce interface configuration command. To remove the current setting, use the no form of this command.

frame-relay lmi-t392dce seconds

no frame-relay lmi-t392dce seconds

Syntax Description

Defaults

15 seconds

Command Modes

Interface configuration

Command History

Usage Guidelines

The value for the timer must be greater than the DTE or NNI keepalive timer.

Examples

The following example shows how to set a polling verification timer on a DCE or NNI interface set to 20 seconds.

Related Commands

frame-relay lmi-type

To select the LMI type, use the frame-relay lmi-type interface configuration command. To return to the default LMI type, use the no form of this command.

frame-relay lmi-type [ansi | cisco | q933a]

no frame-relay lmi-type [ansi | cisco | q933a]

Syntax Description

Defaults

cisco

Command Modes

Interface configuration

Command History

Usage Guidelines

The LMI type is set on a per-interface basis. If you want to display the type that is configured,
use the show interfaces EXEC command.

Examples

The following example shows how to configure an interface for the ANSI LMI type.

Related Commands

frame-relay output-queue

To configure discard marking thresholds on a Frame Relay interface in the output direction, use
the frame-relay output-queue interface configuration command. To restore tthe default values for the threshold, use the no form of this command .

frame-relay output-queue {abr | ubr | vbr-nrt} {discard-threshold | marking-threshold} percentage

no frame-relay output-queue {abr | ubr | vbr-nrt} {discard-threshold | marking-threshold} percentage

Syntax Description

Defaults

See "Syntax Description."

Command Modes

Interface configuration

Command History

Usage Guidelines

This command affects all existing connections on the interface, as well as subsequent connections.

Examples

The following example shows how to set the Frame Relay output queue for ABR connects to allow EFCI marking for cells over 65 percent of capacity.

Related Commands

frame-relay overbooking

To set the percentage of CIR overbooking, use the frame-relay overbooking command. To disable CIR overbooking, use the no form of this command.

frame-relay overbooking percent

no frame-relay overbooking

Syntax Description

Defaults

Disabled

Command Modes

Interface configuration

Command History

Usage Guidelines

The allowable overbooking on an access link or interface is a number times the access link or interface speed (access rate), for example, 200 percent of the access rate. The total of all CIRs for all Frame Relay PVCs and Frame Relay soft VCs cannot exceed the CIR overbooking factor times the access rate.

Once configured and used to admit Frame Relay PVCs and Frame Relay soft VCs on an interface, the CIR overbooking factor can only be adjusted within the upper limit and the level which has been overbooked by the existing connections. Disabling the CIR overbooking factor is allowed only when the total of all CIRs for all Frame Relay PVCs and Frame Relay soft VCs does not exceed the interface access rate.

Configuring the CIR overbooking factor increases the available bit rates for the Frame Relay PVC and soft VC but does not increase the actual bandwidth (access rate) and resources available to the Frame Relay interface.

The CIR of a connection is not allowed to ex