Table Of Contents
frame-relay map bridge broadcast
netbios input-access-filter bytes
netbios input-access-filter host
netbios name-cache proxy-datagram
netbios name-cache query-timeout
netbios name-cache recognized-timeout
netbios output-access-filter bytes
netbios output-access-filter host
rif validate-enable-route-cache
clear bridge
To remove any learned entries from the forwarding database and to clear the transmit and receive counts for any statically or system-configured entries, use the clear bridge command in privileged EXEC mode.
clear bridge bridge-group
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following example shows the use of the clear bridge command:
Router# clear bridge 1Related Commands
bridge address
Filters frames with a particular MAC-layer station source or destination address.
bridge protocol
Defines the type of Spanning Tree Protocol.
clear bridge multicast
To clear transparent bridging multicast state information, use the clear bridge multicast command in user EXEC or privileged EXEC mode.
clear bridge [bridge-group] multicast [router-ports | groups | counts] [group-address] [interface-unit] [counts]
Syntax Description
Defaults
No default behavior or values
Command Modes
User EXEC
Prvileged EXECCommand History
Usage Guidelines
If you do not specify arguments or keywords as part of the command, the command clears router ports, group ports, and counts for all configured bridge groups.
Use the show bridge multicast command to list transparent bridging multicast state information, then use specific pieces of state information in the clear bridge multicast command.
Examples
The following example clears router ports, group ports, and counts for bridge group 1:
Router# clear bridge 1 multicastThe following example clears the group and count information for the group identified as 235.145.145.223, interface Ethernet 0/3 for bridge group 1:
Router# clear bridge 1 multicast groups 235.145.145.223 Ethernet0/3 countsRelated Commands
bridge cmf
Enables CMF for all configured bridge groups.
show bridge multicast
Displays transparent bridging multicast state information.
clear drip counters
To clear duplicate ring protocol (DRiP) counters from the Route Switch Module (RSM) interfaces, use the clear drip counters command in privileged EXEC mode.
clear drip counters
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the clear drip counters command if you want to check whether the router is receiving any packets. The counters will start at 0. If the counters are incrementing, DRiP is active on the router.
Examples
The following example clears DRiP counters:
Router# clear drip countersRelated Commands
interface vlan
Configures a Token Ring or Ethernet interface on the RSM.
show drip
Displays the status of the DRiP database.
clear netbios-cache
To clear the entries of all dynamically learned NetBIOS names, use the clear netbios-cache command in privileged EXEC mode.
clear netbios-cache
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The Cisco IOS software automatically learns NetBIOS names. This command clears those entries. This command will not remove statically defined name cache entries.
Examples
The following example clears all dynamically learned NetBIOS names:
Router# clear netbios-cacheRelated Commands
clear rif-cache
To clear the entire Routing Information Field (RIF) cache, use the clear rif-cache command in privileged EXEC mode.
clear rif-cache
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Some entries in the RIF cache are dynamically added and others are static.
Examples
The following example clears the entire RIF cache:
Router# clear rif-cacheRelated Commands
clear source-bridge
To clear the source-bridge statistical counters, use the clear source-bridge command in privileged EXEC mode.
clear source-bridge
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following example clears the source-bridge statistical counters:
Router# clear source-bridgeRelated Commands
clear bridge
Removes any learned entries from the forwarding database and clears the transmit and receive counts for any statically or system-configured entries.
clear sse
To reinitialize the Silicon Switch Processor (SSP) on the Cisco 7000 series routers with RSP7000, use the clear sse command in privileged EXEC mode.
clear sse
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The silicon switching engine (SSE) is on the SSP board in the Cisco 7000 series routers with RSP7000.
Examples
The following example re initializes the SSP:
Router# clear sseclear vlan statistics
To remove virtual LAN statistics from any statically or system-configured entries, use the clear vlan statistics command in privileged EXEC mode.
clear vlan statistics
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following example clears VLAN statistics:
Router# clear vlan statisticsethernet-transit-oui
To choose the Organizational Unique Identifier (OUI) code to be used in the encapsulation of Ethernet Type II frames across Token Ring backbone networks, use the ethernet-transit-oui command in subinterface configuration mode. Various versions of this OUI code are used by Ethernet/Token Ring translational bridges. To return the default OUI code, use the no form of this command.
ethernet-transit-oui [90-compatible | standard | cisco]
no ethernet-transit-oui
Syntax Description
90-compatible
(Optional) Default OUI form.
standard
(Optional) Standard OUI form.
cisco
(Optional) Cisco's OUI form.
Defaults
The default OUI form is 90-compatible.
Command Modes
Interface configuration
Command History
Usage Guidelines
Before using this command, you must have completely configured your router using multiport source bridging and transparent bridging.
The standard keyword is used when you are forced to interoperate with other vendor equipment, such as the IBM 8209, in providing Ethernet and Token Ring mixed media bridged connectivity.
Table 5 shows the actual OUI codes used, when they are used, and how they compare to Software Release 9.0-equivalent commands.
Specify the 90-compatible keyword when talking to our routers. This keyword provides the most flexibility. When 90-compatible is specified or the default is used, Token Ring frames with an OUI of 0x0000F8 are translated into Ethernet Type II frames and Token Ring frames with the OUI of 0x000000 are translated into Subnetwork Access Protocol (SNAP)-encapsulated frames. Specify the standard keyword when talking to IBM 8209 bridges and other vendor equipment. This OUI does not provide for as much flexibility as the other two choices. The cisco keyword oui is provided for compatibility with future equipment.
Do not use the standard keyword unless you are forced to interoperate with other vendor equipment, such as the IBM 8209, in providing Ethernet and Token Ring mixed media bridged connectivity. Only use the standard keyword only when you are transferring data between IBM 8209 Ethernet/Token Ring bridges and routers running the source-route translational bridging (SR/TLB) software (to create a Token Ring backbone to connect Ethernets).
Use of the standard keyword causes the OUI code in Token Ring frames to always be 0x000000. In the context of the standard keyword, an OUI of 0x000000 identifies the frame as an Ethernet Type II frame. (Compare with 90-compatible, where 0x000000 OUI means SNAP-encapsulated frames.)
If you use the 90-compatible keyword, the router, acting as an SR/TLB, can distinguish immediately on Token Ring interfaces between frames that started on an Ethernet Type II frame and those that started on an Ethernet as a SNAP-encapsulated frame. The distinction is possible because the router uses the 0x0000F8 OUI when converting Ethernet Type II frames into Token Ring SNAP frames, and leaves the OUI as 0x000000 for Ethernet SNAP frames going to a Token Ring. This distinction in OUIs leads to efficiencies in the design and execution of the SR/TLB product; no tables need to be kept to know which Ethernet hosts use SNAP encapsulation and which hosts use Ethernet Type II.
The IBM 8209 bridges, however, by using the 0x000000 OUI for all the frames entering the Token Ring, must take extra measures to perform the translation. For every station on each Ethernet, the 8209 bridges attempt to remember the frame format used by each station, and assume that once a station sends out a frame using Ethernet Type II or 802.3, it will always continue to do so. It must do this because in using 0x000000 as an OUI, there is no way to distinguish between SNAP and Type II frame types. Because the SR/TLB router does not need to keep this database, when 8209 compatibility is enabled with the standard keyword, the SR/TLB chooses to translate all Token Ring SNAP frames into Ethernet Type II frames as described earlier in this discussion. Because every nonroutable protocol on Ethernet uses either non-SNAP 802.3 (which traverses fully across a mixed IBM 8209/ router Token Ring backbone) or Ethernet Type II, this results in correct inter connectivity for virtually all applications.
Do not use the standard keyword OUI if you want SR/TLB to output Ethernet SNAP frames. Using either the 90-compatible or cisco keyword OUI does not present such a restriction, because SNAP frames and Ethernet Type II-encapsulated frames have different OUI codes on Token Ring networks.
Examples
The following example specifies standard OUI form:
interface tokenring 0ethernet-transit-oui standardRelated Commands
source-bridge transparent
Establishes bridging between transparent bridging and SRB.
frame-relay map bridge broadcast
To bridge over a Frame Relay network, use the frame-relay map bridge broadcast command in interface configuration mode. To delete the mapping entry, use the no form of this command.
frame-relay map bridge dlci broadcast
no frame-relay map bridge dlci broadcast
Syntax Description
Defaults
No mapping entry is established.
Command Modes
Interface configuration
Command History
Usage Guidelines
Bridging over a Frame Relay network is supported on networks that do and do not support a multicast facility.
The following example allows bridging over a Frame Relay network:
frame-relay map bridge 144 broadcastRelated Commands
hsma control-sap
To override the default control service access point (SAP) for (hot standby MAC address) HSMA peer communications, use the hsma control-sap command in control adapter configuration mode. To restore the default SAP for peer communications, use the no form of this command.
hsma control-sap sap-address
no hsma control-sap sap-address
Syntax Description
sap-address
SAP address used by the HSMA protocol on the control adapter. This is a hexadecimal value. The allowed range is from 0x4 to 0xFC, and the default is 0xEC.
Defaults
The default SAP address, 0xEC, is used.
Command Modes
Control adapter configuration
Command History
Usage Guidelines
This command allows you to override the default control SAP used for HSMA peer communications. The same value must be configured for both HSMA peers or they will not be able to communicate. This command is valid only on the control adapter.
When the hsma control-sap command is changed, it will take effect only after you restart the interface by using the shutdown and no shutdown commands.
Examples
The following example configures the SAP address E8 on control adapter 26:
interface Channel3/0csna 0190 09lan TokenRing 23source-bridge 330 3 100adapter 9 4043.1313.9009 hsma-partner 4043.1111.001alan TokenRing 31source-bridge 339 9 100adapter 26 4043.3333.001ahsma enablehsma control-sap E8hsma dead-interval
To configure the time interval during which at least one hello packet must be received from the peer (hot standby MAC address) HSMA adapter or else the router declares that neighbor down, use the hsma dead-interval command in peered adapter configuration mode. To restore the default value, use the no form of this command.
hsma dead-interval time-interval
no hsma dead-interval time-interval
Syntax Description
time-interval
Time interval used by the HSMA protocol between the control and peered HSMA adapters. Range: 3 to 180. Default: 10.
Defaults
The time interval is set to the default value of 10 seconds.
Command Modes
Peered adapter configuration
Command History
Examples
The following example configures the time interval on adapter 26 to be 8 seconds:
interface Channel1/0load-interval 30csna 0190 09lan TokenRing 20source-bridge 310 3 100adapter 9 4043.1313.9009 hsma-partner 4043.3333.001ahsma dead-interval 8lan TokenRing 26source-bridge 319 9 100adapter 26 4043.1111.001ahsma enablehsma enable
To enable (hot standby MAC address) HSMA on an adapter, use the hsma enable command in control adapter configuration mode. To disable HSMA, use the no form of this command.
hsma enable
no hsma enable
Syntax Description
This command has no keywords or arguments.
Defaults
HSMA is disabled.
Command Modes
Control adapter configuration
Command History
Usage Guidelines
The hsma enable command instructs HSMA to use the adapter it is configured on as the control adapter. The control adapter is the adapter that is used to send and receive hello updates. HSMA is not enabled on the router until a control adapter is specified by the hsma enable command. The no form of this command is not valid unless all of the HSMA partners have been removed; similarly, the adapter context itself may not be removed unless all of the HSMA partners have been removed.
This command is only valid on the control adapter.
The control adapter can be configured under any LAN Token Ring adapter.
Examples
The following example enables HSMA on control adapter 26:
interface Channel1/0lan TokenRing 20source-bridge 310 3 100adapter 9 4043.1313.9009 hsma-partner 4043.3333.001alan TokenRing 26source-bridge 319 9 100adapter 26 4043.1111.001ahsma enablehsma hello-interval
To configure the time interval between hello messages between the peered (hot standby MAC address) HSMA Cisco Channel Interface Processors (CIPs) or Channel Port Adapters (CPAs), use the hsma hello-interval command in peered adapter configuration mode. To restore the default value, use the no form of this command.
hsma hello-interval time-interval
no hsma hello-interval time-interval
Syntax Description
time-interval
Time interval, in seconds, used by the HSMA protocol between the peered HSMA CIP or CPAs. Range: 1 to 60. Default: 3.
Defaults
The time interval is set to the default value of 3 seconds.
Command Modes
Peered adapter configuration
Command History
Usage Guidelines
The hsma hello-interval is the time interval between hello messages that pass between the peered HSMA CIP or CPAs. The control adapter in the enabled mode sends hello messages to the peered adapter after every 2 seconds.
Examples
The following example configures the interval between hello messages on adapter 26 to be 2 seconds:
interface Channel1/0csna 0190 09lan TokenRing 20source-bridge 310 3 100adapter 9 4043.1313.9009 hsma-partner 4043.3333.001ahsma hello-interval 2lan TokenRing 26source-bridge 319 9 100adapter 26 4043.1111.001ahsma enablehsma preferred
To assign priority to a peer as a control adapter, use the hsma preferred command in peered adapter configuration mode. To allow priority to be set without configuring a peer, use the no form of this command.
hsma preferred
no hsma preferred
Syntax Description
This command has no keywords or arguments.
Defaults
Disabled
Command Modes
Peered adapter configuration
Command History
Usage Guidelines
The hsma preferred command is used in situations when both HSMA peers are becoming active at the same time or both were active because of an interruption of communication between the control adapters. In such situations, the adapter with the hsma preferred command configured becomes the active adapter, and the other adapter is disabled. Sessions that are connected to the disabled adapter will be dropped. If the hsma preferred command is not configured on either peer, the control adapter with the higher MAC address is used.
Examples
The following example disables adapter 9 as the HSMA adapter and enables adapter 26 as the active HSMA adapter:
interface Channel1/0csna 0190 09lan TokenRing 20source-bridge 310 3 100adapter 9 4043.1313.9009 hsma-partner 4043.3333.001ahsma preferredhsma shutdownlan TokenRing 26source-bridge 319 9 100adapter 26 4043.1111.001ahsma enablehsma shutdown
To stop (hot standby MAC address) HSMA on an adapter and hence enable the partner adapter, use the hsma shutdown command. To restart the HSMA adapter, use the no form of this command.
hsma shutdown
no hsma shutdown
Syntax Description
This command has no keywords or arguments.
Defaults
HSMA is not shut down.
Command Modes
Peered adapter configuration
Command History
Usage Guidelines
Use the hsma shutdown command when you wish to force the other adapter of a pair to become active.
Examples
The following example disables adapter 9 as the HSMA adapter and enables adapter 26 as the active HSMA adapter:
interface Channel1/0csna 0190 09lan TokenRing 20source-bridge 310 3 100adapter 9 4043.1313.9009 hsma-partner 4043.3333.001ahsma preferredhsma shutdownlan TokenRing 26source-bridge 319 9 100adapter 26 4043.1111.001ahsma enableinterface bvi
To create the bridge-group virtual interface (BVI) that represents the specified bridge group to the routed world and links the corresponding bridge group to the other routed interfaces, use the interface bvi command in interface configuration mode. To delete the BVI, use the no form of this command.
interface bvi bridge-group
no interface bvi bridge-group
Syntax Description
Defaults
No BVI is created.
Command Modes
Interface configuration
Command History
Usage Guidelines
You must enable integrated routing and bridging (IRB) before attempting to create a BVI.
When you intend to bridge and route a given protocol in the same bridge group, you must configure the network-layer attributes of the protocol on the BVI. Do not configure protocol attributes on the bridged interfaces. No bridging attributes can be configured on the BVI.
Examples
The following example creates a bridge group virtual interface and associates it with bridge group 1:
interface bvi 1Related Commands
bridge irb
Enables the Cisco IOS software to route a given protocol between routed interfaces and bridge groups or to route a given protocol between bridge groups.
interface vlan
To configure a Token Ring or Ethernet interface on the Route Switch Module (RSM), use the interface vlan command in interface configuration mode.
interface vlan vlanid type {trbrf | ethernet}
Syntax Description
vlanid
Unique VLAN ID number used to create a VLAN.
type trbrf
Configures a Token Ring interface on the RSM.
type ethernet
Configures an Ethernet interface on the RSM.
Defaults
The RSM interfaces are not configured.
Command Modes
Interface configuration
Command History
Usage Guidelines
Valid Token Ring VLAN ID numbers are 2 through 1000.
Routing or bridging to a Token Ring VLAN (TrBRF) on the RSM is done by creating a logical interface to a TrBRF VLAN on the RSM with the interface vlan command. The TrBRF VLAN must be defined on the Supervisor module prior to creating the TrBRF interface on the RSM.
Examples
The following example configures an RSM Token Ring interface with VLAN 998:
interface vlan 998 type trbrfip address 10.5.5.1 255.255.255.0Related Commands
clear drip counters
Clears DRiP counters.
show drip
Displays the status of the DRiP database.
lnm alternate
Note
Effective with release 12.3(4)T, the lnm alternate command is no longer available in Cisco IOS software.
To specify the threshold reporting link number, use the lnm alternate command in interface configuration mode. In order for a LAN Reporting Manager (LRM) to change parameters, it must be attached to the reporting link with the lowest reporting link number, and that reporting link number must be lower than this threshold reporting link number. To restore the default of 0, use the no form of this command.
lnm alternate number
no lnm alternate
Syntax Description
Defaults
The default threshold reporting link number is 0.
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
12.3(4)T
This command was removed and is no longer available in Cisco IOS software.
Usage Guidelines
LAN Network Manager (LNM) employs the concepts of reporting links and reporting link numbers. A reporting link is simply a connection (or potential connection) between an LRM and a bridge. A reporting link number is a unique number used to identify a reporting link. An IBM bridge allows four simultaneous reporting links numbered 0 to 3. Only the LRM attached to the lowest number connection is allowed to change any parameters, and then only when that connection number falls below a certain configurable number. In the default configuration, the LRM connected through link 0 is the only LRM allowed to change parameters.
Note
Examples
The following example permits LRMs connected through links 0 and 1 to change parameters:
! provide appropriate global configuration command if not currently in your config.!! permit 0 and 1lnm alternate 1The following example permits all LRMs to change parameters in the Cisco IOS software:
! provide appropriate global configuration command if not currently in your config.!! permit 0, 1, 2, and 3lnm alternate 3Related Commands
lnm crs
Note
To monitor the current logical configuration of a Token Ring, use the lnm crs command in interface configuration mode. To disable this function, use the no form of this command.
lnm crs
no lnm crs
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
12.3(4)T
This command was removed and is no longer available in Cisco IOS software.
Usage Guidelines
The Configuration Report Server service tracks the current logical configuration of a Token Ring and reports any changes to LAN Network Manager (LNM). It also reports on various other activities such as the change of the Active Monitor on a Token Ring.
For more information about the Active Monitor, refer to the IBM Token Ring Architecture Reference Manual or the IEEE 802.5 specification.
Examples
The following example disables monitoring of the current logical configuration of a Token Ring:
interface tokenring 0no lnm crsRelated Commands
lnm rem
Monitors errors reported by any station on the ring.
lnm rps
Ensures that all stations on a ring are using a consistent set of reporting parameters.
lnm disabled
Note
To disable LAN Network Manager (LNM) functionality, use the lnm disabled command in global configuration mode. To restore LNM functionality, use the no form of this command.
lnm disabled
no lnm disabled
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Global configuration
Command History
11.2
This command was introduced.
12.3(4)T
This command was removed and is no longer available in Cisco IOS software.
Usage Guidelines
Under some circumstances, you can disable all LNM server functions on the router without having to determine whether to disable a specific server, such as the ring parameter server or the ring error monitor on a given interface.
This command can be used to terminate all LNM server input and reporting links. In normal circumstances, this command should not be necessary because it is a superset of the functions normally performed on individual interfaces by the no lnm rem and no lnm rps commands.
Examples
The following example disables LNM functionality:
lnm disabledRelated Commands
lnm express-buffer
Note
To enable the LAN Network Manager (LNM) Ring Parameter Server (RPS) express buffer function, use the lnm express-buffer command in interface configuration mode. To disable this function, use the no form of this command.
lnm express-buffer
no lnm express-buffer
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
10.3
This command was introduced.
12.3(4)T
This command was removed and is no longer available in Cisco IOS software.
Usage Guidelines
The RPS express buffer function allows the router to set the express buffer bit to ensure priority service for frames required for ring station initiation. When this function is enabled, the router sets the express buffer bit in its initialize ring station response, which allows Token Ring devices to insert into the ring during bursty conditions.
Examples
The following example enables the LNM RPS express buffer function:
lnm express-bufferlnm loss-threshold
Note
To set the threshold at which the Cisco IOS software sends a message informing all attached LAN Network Manager (LNM)s that it is dropping frames, use the lnm loss-threshold command in interface configuration mode. To return to the default value, use the no form of this command.
lnm loss-threshold number
no lnm loss-threshold
Syntax Description
number
Single number expressing the percentage loss rate in hundredths of a percent. The valid range is from 0 to 9999. The default is
Defaults
10 (0.10 percent)
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
12.3(4)T
This command was removed and is no longer available in Cisco IOS software.
Usage Guidelines
The software sends a message to all attached LNMs whenever it begins to drop frames. The point at which this report is generated (threshold) is a percentage of the number of frames dropped compared with the number of frames forwarded.
When setting this value, remember that 9999 would mean 100 percent of your frames could be dropped before the message is sent. A value of 1000 would mean 10 percent of the frames could be dropped before sending the message. A value of 100 would mean 1 percent of the frames could be dropped before the message is sent.
Examples
In the following example, the loss threshold is set to 0.02 percent:
interface tokenring 0lnm loss-threshold 2lnm password
Note
To set the password for the reporting link, use the lnm password command in interface configuration mode. To return the password to its default value of 00000000, use the no form of this command.
lnm password number string
no lnm password number
Syntax Description
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
12.3(4)T
This command was removed and is no longer available in Cisco IOS software.
Usage Guidelines
LNM employs the concepts of reporting links and reporting link numbers. A reporting link is simply a connection (or potential connection) between a LAN Reporting Manager (LRM) and a bridge. A reporting link number is a unique number used to identify a reporting link. An IBM bridge allows four simultaneous reporting links numbered 0 to 3. Only the LRM attached to the lowest number connection is allowed to change any parameters, and then only when that connection number falls below a certain configurable number. In the default configuration, the LRM connected through link 0 is the only LRM allowed to change parameters.
Each reporting link has its own password. Passwords are used not only to prevent unauthorized access from an LRM to a bridge, but also to control access to the different reporting links. This is important because of the different abilities associated with the various reporting links.
Characters allowable in the string are the following:
•
•
•
Passwords are displayed only through use of the privileged EXEC show running-config command.
Note
Examples
In the following example, the password Zephyr@ is assigned to reporting link 2:
! provide appropriate global configuration command if not currently in your config.!lnm password 2 Zephyr@Related Commands
lnm pathtrace-disabled
Note
To disable pathtrace reporting to LAN Network Manager (LNM) stations, use the lnm pathtrace-disabled command in global configuration mode. To restore pathtrace reporting functionality, use the no form of this command.
lnm pathtrace-disabled [all | origin]
no lnm pathtrace-disabled
Syntax Description
all
(Optional) Disable pathtrace reporting to the LNM and originating stations.
origin
(Optional) Disable pathtrace reporting to originating stations only.
Defaults
Enabled
Command Modes
Global configuration
Command History
11.2
This command was introduced.
12.3(4)T
This command was removed and is no longer available in Cisco IOS software.
Usage Guidelines
Under some circumstances, such as when new hardware has been introduced into the network and is causing problems, the automatic report pathtrace function can be disabled. The new hardware may be setting bit-fields B1 or B2 (or both) of the routing control field in the routing information field embedded in a source-route bridged frame. This condition may cause the network to be flooded by report pathtrace frames if the condition is persistent. The lnm pathtrace-disabled command, along with its options, allows you to alleviate network congestion that may be occurring by disabling all or part of the automatic report pathtrace function within LNM.
Examples
The following example disables all pathtrace reporting:
lnm pathtrace-disabledRelated Commands
lnm rem
Note
To monitor errors reported by any station on the ring, use the lnm rem command in interface configuration mode. To disable this function, use the no form of this command.
lnm rem
no lnm rem
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Interface configuration
Command History
