Source-Route Bridging Commands

Syntax Description

in | out	Either in or out is specified to indicate whether the access expression is applied to packets entering or leaving this interface. You can specify both an input and an output access expression for an interface, but only one of each.
expression	Boolean access list expression, built as explained in the "Usage Guidelines" section.

Defaults

No access expression is defined.

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

An access expression consists of a list of terms, separated by Boolean operators, and optionally grouped in parentheses.

Terms can be grouped in parenthetical expressions. Any of the terms and operators can be placed in parentheses, similar to what is done in arithmetic expressions, to affect order of evaluation.

An "access-expression" type filter cannot exist with a "source-bridge" type filter on the same interface. The two types of filters are mutually exclusive.

Note   The incorrect use of parentheses can drastically affect the result of an operation, because the expression is read left to right.

Related Commands

Command	Description
access-list	Configures the access list mechanism for filtering frames by protocol type or vendor code.

Syntax Description

access-list-number	Integer that identifies the access list. If the type-code wild-mask arguments are included, this integer ranges from 200 to 299, indicating that filtering is by protocol type. If the address and mask arguments are included, this integer ranges from 700 to 799, indicating that filtering is by vendor code.
permit	Permits the frame.
deny	Denies the frame.
type-code	16-bit hexadecimal number written with a leading 0x; for example, 0x6000. Specify either a Link Service Access Point (LSAP) type code for 802-encapsulated packets or a SNAP type code for SNAP-encapsulated packets. (LSAP, sometimes called SAP, refers to the type codes found in the DSAP and SSAP fields of the 802 header.)
wild-mask	16-bit hexadecimal number whose ones bits correspond to bits in the type-code argument. The wild-mask indicates which bits in the type-code argument should be ignored when making a comparison. (A mask for a DSAP/SSAP pair should always be 0x0101 because these two bits are used for purposes other than identifying the SAP code.)
address	48-bit Token Ring address written in dotted triplet form. This field is used for filtering by vendor code.
mask	48-bit Token Ring address written in dotted triplet form. The ones bits in mask are the bits to be ignored in address. This field is used for filtering by vendor code.

Defaults

No access list is configured.

Command Modes

Global configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

For source address filtering, the mask always should have the high-order bit set. This is because the IEEE 802 standard uses this bit to indicate whether a RIF is present, not as part of the source address.

For a list of type codes, refer to the "Ethernet Type Codes" appendix of this manual.

Examples

In the following example, the access list permits only Novell frames (LSAP 0xE0E0) and filters out all other frame types. This set of access lists would be applied to an interface via the source-bridge input-lsap list or source-bridge input-lsap list commands (described later in this chapter).

access-list 201 permit 0xE0E0 0x0101
access-list 201 deny  0x0000 0xFFFF
 

Combine the DSAP/LSAP fields into one number to do LSAP filtering; for example,
0xE0E0—not 0xE0. Note that the deny condition specified in the preceding example is not required; access lists have an implicit deny as the last statement. Adding this statement can serve as a useful reminder, however.

Syntax Description

bridge-group

Number in the range 1 to 9 that you choose to refer to a particular set of bridged interfaces.

Defaults

No bridge group is defined.

Command Modes

Global configuration

Command History

Release	Modification
10.3	This command was introduced.

Examples

The following example specifies bridge 1 to use the automatic spanning-tree function:

bridge 1 protocol ibm

Related Commands

Command	Description
show source-bridge	Displays the current source bridge configuration and miscellaneous statistics.
source-bridge spanning (automatic)	Enables the automatic spanning-tree function for a specified group of bridged interfaces.
source-bridge spanning (manual)	Enables use of spanning explorers.

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

The Cisco IOS software automatically learns NetBIOS names. This command clears those entries.

Examples

The following example clears all dynamically learned NetBIOS names:

clear netbios-cache

Related Commands

Command	Description
netbios enable-name-cache	Enables NetBIOS name caching.
netbios name-cache timeout	Enables NetBIOS name caching and sets the time that entries can remain in the NetBIOS name cache.
show netbios-cache	Displays a list of NetBIOS cache entries.

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

Some entries in the RIF cache are dynamically added and others are static.

Examples

The following example clears the entire RIF cache:

clear rif-cache

Related Commands

Command	Description
rif	Enters static source-route information into the RIF cache. If a Token Ring host does not support the use of IEEE 802.2 TEST or XID datagrams as explorer packets, static information may need to be added to the RIF cache of the router.
rif timeout	Determines the number of minutes an inactive RIF entry is kept. RIF information is maintained in a cache whose entries are aged.
show rif	Displays the current contents of the RIF cache.

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following example clears the source-bridge statistical counters:

clear source-bridge

Related Commands

Command	Description
clear bridge	Removes any learned entries from the forwarding database and clears the transmit and receive counts for any statically or system-configured entries.

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release	Modification
10.3	This command was introduced.

Usage Guidelines

The silicon switching engine (SSE) is on the SSP board in the Cisco 7000 series routers with RSP7000.

Examples

clear sse

Syntax Description

90-compatible	(Optional) Default OUI form.
standard	(Optional) Standard OUI form.
cisco	(Optional) Cisco's OUI form.

Defaults

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.
9.0	This command bridge old-oui replaces and extends the command.

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.

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 while Token Ring frames with the OUI of 0x000000 are translated into 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 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 when you are transferring data between IBM 8209 Ethernet/Token Ring bridges and routers running the 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 interconnectivity for virtually all applications.

Do not use the standard OUI if you want SR/TLB to output Ethernet SNAP frames. Using either the 90-compatible or cisco 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 0
 ethernet-transit-oui standard

Related Commands

Command	Description
ethernet-transit-oui	Chooses the OUI code to be used in the encapsulation of Ethernet Type II frames across Token Ring backbone networks.Various versions of this OUI code are used by Ethernet/Token Ring translational bridges.
source-bridge transparent	Establishes bridging between transparent bridging and SRB.

Syntax Description

number

Threshold reporting link number. It must be in the range 0 to 3.

Defaults

0

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

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   Setting the threshold reporting link number on one interface in a source-route bridge will cause it to appear on the other interface of the bridge, because the command applies to the bridge itself and not to either of the interfaces.

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 1
lnm alternate 1 
 

The 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 3 
lnm alternate 3 

Related Commands

Command	Description
lnm password	Sets the password for the reporting link.

Syntax Description

This command has no arguments or keywords.

Defaults

Enabled

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

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 0
 no lnm crs

Related Commands

Command	Description
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.

Syntax Description

This command has no arguments or keywords.

Defaults

Enabled

Command Modes

Global configuration

Command History

Release	Modification
11.2	This command was introduced.

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 disabled

Related Commands

Command	Description
lnm pathtrace-disabled	Disables pathtrace reporting to LNM stations.
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 snmp-only	Prevents any LNM stations from modifying parameters in the Cisco IOS software.
show lnm bridge	Displays all currently configured bridges and all parameters that are related to the bridge as a whole, not to one of its interfaces.

Syntax Description

number

A single number expressing the percentage loss rate in hundredths of a percent. The valid range is 0 to 9999.

Defaults

10 (.10 percent)

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

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 0
 lnm loss-threshold 2

Syntax Description

number	Number of the reporting link to which to apply the password. This value should be in the range 0 to 3.
string	Password you enter at the keyboard. In order to maintain compatibility with LNM, the parameter string should be a six- to eight-character string of the type listed in the "Usage Guidelines" section.

Defaults

00000000

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

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 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:

• Letters

• Numbers

• Special characters @, #, $, or %

Passwords are displayed only through use of the privileged EXEC show running-config command.

Note   There are two parameters in an IBM bridge that have no corresponding parameter in the Cisco IOS software. This means that any attempt to modify these parameters from LNM will fail and display an error message. The LNM names of these two parameters are route active status and single route broadcast mode.

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

Command	Description
lnm alternate	Specifies the threshold reporting link number. In order for an 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.

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

Release	Modification
11.2	This command was introduced.

Usage Guidelines

Under some circumstances, such as when new hardware has been introduced into the network and is causing problems, the automatic report path trace 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 path trace 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 path trace function within LNM.

Examples

The following example disables all pathtrace reporting:

lnm pathtrace-disabled

Related Commands

Command	Description
lnm disabled	Disables LNM functionality.
lnm pathtrace-disabled	Disables pathtrace reporting to LNM stations.
show lnm bridge	Displays all currently configured bridges and all parameters that are related to the bridge as a whole, not to one of its interfaces.

Syntax Description

This command has no arguments or keywords.

Defaults

Enabled

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

Examples

The following example shows the use of the lnm rem command:

interface tokenring 0
 lnm rem

Related Commands

Command	Description
lnm crs	Monitors the current logical configuration of a Token Ring.
lnm rps	Ensures that all stations on a ring are using a consistent set of reporting parameters.

Syntax Description

This command has no arguments or keywords.

Defaults

Enabled

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

Examples

The following example shows the use of the lnm rps command:

interface tokenring 0
 lnm rps

Related Commands

Command	Description
lnm crs	Monitors the current logical configuration of a Token Ring.
lnm rem	Monitors errors reported by any station on the ring.

Syntax Description

This command has no arguments or keywords.

Defaults

Enabled

Command Modes

Global configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

Configuring a router for LNM support is very simple. It happens automatically as a part of configuring the router to act as a source-route bridge. There are several commands available to modify the behavior of the LNM support, but none of them are necessary for it to function.

Because there is now more than one way to remotely change parameters in the Cisco IOS software, this command was developed to prevent them from detrimentally interacting with each other.

This command does not affect the ability of LNM to monitor events, only to modify parameters in the Cisco IOS software.

Examples

The following command prevents any LNM stations from modifying parameters in the software:

lnm snmp-only 

Syntax Description

milliseconds

Time interval in tens of milliseconds between error messages. The valid range is 0 to 65535.

Defaults

200 ms (2 seconds)

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

All stations on a Token Ring notify the REM when they detect errors on the ring. To prevent an excessive number of messages, error reports are not sent immediately, but are accumulated for a short period of time and then reported. A station learns this value from a router (configured as a source-route bridge) when it first enters the ring.

Examples

The following example changes the error-reporting frequency to once every 5 seconds:

lnm softerr 500 

Related Commands

Command	Description
lnm rem	Monitors errors reported by any station on the ring.

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

There are two solutions. The first involves installing a static RIF entry for every faulty node with which the router communicates. If there are many such nodes on the ring, this may not be practical. The second solution involves setting the MAC address of the Cisco Token Ring to a value that works around the problem.

This command forces the use of a different MAC address on the specified interface, thereby avoiding the Texas Instrument MAC firmware problem. It is up to the network administrator to ensure that no other host on the network is using that MAC address.

Examples

The following example sets the MAC layer address, where xx.xxxx is an appropriate second half of the MAC address to use:

interface tokenring 0
 mac-address 5000.5axx.xxxx

Syntax Description

protocol-keyword	Specifies a protocol; see the keyword list under the "Usage Guidelines" section.
all-routes	Uses all-routes explorers.
spanning	Uses spanning-tree explorers.
all	Enables the multiring for all frames.
other	Enables the multiring for any routed frame not included in the previous list of supported protocols.

Defaults

Disabled

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced
11.1	These keywords were added: all-routes spanning

Usage Guidelines

Level 3 routers that use protocol-specific information (for example, Novell IPX or XNS headers) rather than MAC information to route datagrams also must be able to collect and use RIF information to ensure that they can transmit datagrams across a source-route bridge. The software default is to not collect and use RIF information for routed protocols. This allows operation with software that does not understand or properly use RIF information.

• apollo—Apollo Domain

• appletalk—AppleTalk Phase 1 and 2

• clns—ISO CLNS

• decnet—DECnet Phase IV

• ip—IP

• ipx—Novell IPX

• vines—Banyan VINES

• xns—XNS

Note   When you are configuring DLSw+ over FDDI, the multiring command supports only IP and IPX.

The multiring command was extended in Software Release 8.3 to allow for per-protocol specification of the interface's ability to append RIFs to routed protocols. When it is enabled for a protocol, the router will source packets that include information used by source-route bridges. This allows a router with Token Ring interfaces, for the protocol or protocols specified, to connect to a source-bridged Token Ring network. If a protocol is not specified for multiring, the router can only route packets to nodes directly connected to its local Token Ring.

Note    Previous to Software Release 8.3, the multiring command enabled multiring protocols, in particular, the use of explorers and RIFs, for all routable protocols. This sometimes caused problems when multiring-capable devices speaking one particular protocol were attached to the same ring as a nonmultiring-capable device speaking a different network protocol. If the earlier multiring command (pre-8.3 release) was not specified, nodes speaking one particular protocol would be able to communicate through the router, but nodes speaking other protocols could not. The reverse was true when the multiring capability was specified on the interface. In 8.3 or later releases of the software, the command multiring all is equivalent to the 8.2 and earlier forms of the multiring command.

Examples

The following example enables IP and Novell IPX bridging on a Token Ring interface. RIFs will be generated for IP frames, but not for the Novell IPX frames.

! commands that follow apply to interface token 0
interface tokenring 0
! generate RIFs for IP frames
 multiring ip
! enable the Token Ring interface for IP
 ip address 131.108.183.37 255.255.255.0
! enable the Token Ring interface for Novell IPX 
 novell network 33

Related Commands

Command	Description
clear rif-cache	Clears the entire RIF cache.
rif	Enters static source-route information into the RIF cache. If a Token Ring host does not support the use of IEEE 802.2 TEST or XID datagrams as explorer packets, static information may need to be added to the RIF cache of the router.
rif timeout	Determines the number of minutes an inactive RIF entry is kept. RIF information is maintained in a cache whose entries are aged.
show rif	Displays the current contents of the RIF cache.
xns encapsulation	Elects the type of encapsulation used on a Token Ring interface.

Command Modes

Global configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

For offset pattern matching, the byte pattern must be an even number of hexadecimal digits in length.

The byte pattern must be no more than 16 bytes (32 hexadecimal digits) in length.

As with all access lists, the NetBIOS access lists are scanned in order.

You can specify a wildcard character in the byte string indicating that the value of that byte does not matter in the comparison. This is done by specifying two asterisks (**) in place of digits for that byte. For example, the following command would match 0xabaacd, 0xab00cd, and so on:

netbios access-list bytes marketing permit 3 0xab**cd

Examples

The following example shows how to configure for offset pattern matching:

netbios access-list bytes marketing permit 3 0xabcd
 

In the following example, the byte pattern would not be accepted because it must be an even number of hexadecimal digits:

netbios access-list bytes marketing permit 3 0xabc 

In the following example, the byte pattern would not be permitted because the byte pattern is longer than 16 bytes in length:

netbios access-list bytes marketing permit 3 00112233445566778899aabbccddeeff00
 

The following example would match 0xabaacd, 0xab00cd, and so on:

netbios access-list bytes marketing permit 3 0xab**cd
 

The following example deletes the entire marketing NetBIOS access list named marketing:

no netbios access-list bytes marketing
 

The following example removes a single entry from the list:

no netbios access-list bytes marketing deny 3 0xab**cd
 

In the following example, the first line serves to deny all packets with a byte pattern starting in offset 3 of 0xab. However, this denial would also include the pattern 0xabcd because the entry permitting the pattern 0xabcd comes after the first entry:

netbios access-list bytes marketing deny 3 0xab
netbios access-list bytes marketing permit 3 0xabcd

Related Commands

Command	Description
netbios input-access-filter bytes	Defines a byte access list filter on incoming messages. The actual access filter byte offsets and patterns used are defined in one or more netbios-access-list bytes commands.
netbios output-access-filter bytes	Defines a byte access list filter on outgoing messages.

Syntax Description

name	Name of the access list being defined.
permit	Permits the condition.
deny	Denies the condition.
pattern	A set of characters. The characters can be the name of the station, or a combination of characters and pattern-matching symbols that establish a pattern for a set of NetBIOS station names. This combination can be especially useful when stations have names with the same characters, such as a prefix. The table in the "Usage Guidelines" section explains the pattern-matching symbols that can be used.

Defaults

No access list is assigned.

Command Modes

Global configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

Examples

The following example specifies a full station name to match:

netbios access-list host marketing permit ABCD
 

The following example specifies a prefix where the pattern matches any name beginning with the characters DEFG:

!The string DEFG itself is included in this condition.
netbios access-list host marketing deny DEFG*
 

The following example permits any station name with the letter W as the first character and the letter Y as the third character in the name. The second and fourth character in the name can be any character. This example would allow stations named WXYZ and WAYB; however, stations named WY and WXY would not be allowed because the question mark (?) must match specific characters in the name:

netbios access-list host marketing permit W?Y?
 

The following example illustrates how to combine wildcard characters. In this example the marketing list denies any name beginning with AC that is not at least three characters in length (the question mark [?] would match any third character). The string ACBD and ACB would match, but the string AC would not:

netbios access-list host marketing deny AC?
 

In the following example, a single entry in the marketing NetBIOS access list is removed:

no netbios access-list host marketing deny AC?*
 

In the following example, the entire marketing NetBIOS access list is removed:

no netbios access-list host marketing 

Related Commands

Command	Description
netbios input-access-filter host	Defines a station access list filter on incoming messages. The access lists of station names are defined in netbios access-list host commands.
netbios output-access-filter host	Defines a station access list filter on outgoing messages.

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

Examples

The following example enables NetBIOS name caching for Token Ring interface 0:

interface tokenring 0
 source-bridge proxy-explorer
 netbios enable-name-cache

Related Commands

Command	Description
clear netbios-cache	Clears the entries of all dynamically learned NetBIOS names. Will not remove statically defined name cache entries.
netbios name-cache timeout	Enables NetBIOS name caching and sets the time that entries can remain in the NetBIOS name cache.
show netbios-cache	Displays a list of NetBIOS cache entries.

Syntax Description

name	Name of a NetBIOS access filter previously defined with one or more of the netbios access-list bytes global configuration commands.

Defaults

No access list is defined.

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

The following example applies a previously defined filter named marketing to packets coming into tokenring 1:

interface tokenring 1
 netbios input-access-filter bytes marketing 

Related Commands

Command	Description
netbios access-list bytes	Defines the offset and hexadecimal patterns with which to match byte offsets in NetBIOS packets.
netbios input-access-filter bytes	Defines a byte access list filter on incoming messages. The actual access filter byte offsets and patterns used are defined in one or more netbios-access-list bytes commands.

Syntax Description

name	Name of a NetBIOS access filter previously defined with one or more of the netbios access-list host global configuration commands.

Defaults

No access list is defined.

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following example filters packets coming into tokenring1 using the NetBIOS access list named marketing:

interface tokenring 1
 netbios access-list host marketing permit W?Y?
 netbios input-access-filter host marketing

Related Commands

Command	Description
netbios access-list host	Assigns the name of the access list to a station or set of stations on the network. The NetBIOS station access list contains the station name to match, along with a permit or deny condition.
netbios output-access-filter host	Defines a station access list filter on outgoing messages.

Syntax Description

mac-address	The MAC address.
netbios-name	Server name linked to the MAC address.
interface-name	Name of the interface by which the server is accessible locally.
ring-group	Specifies that the link is accessible remotely.
group-number	Number of the ring group by which the server is accessible remotely. This ring group number must match the number you have specified with the source-bridge ring-group command. The valid range is 1 to 4095.

Defaults

No entry is defined.

Command Modes

Global configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

To specify an entry in the static name cache, first specify a Routing Information Field (RIF) that leads to the server's MAC address. The Cisco IOS software displays an error message if it cannot find a static RIF entry for the server when the NetBIOS name-cache entry is attempted or if the server's type conflicts with that given for the static RIF entry.

Note   The names are case sensitive; therefore "Cc" is not the same as "cC".

Examples

The following example indicates the syntax usage of this command if the NetBIOS server is accessed locally:

source-bridge ring-group 2
rif 0220.3333.4444 00c8.042.0060 tokenring 0
netbios name-cache 0220.3333.4444 DEF tokenring 0
 

The following example indicates the syntax usage of this command if the NetBIOS server is accessed remotely:

source-bridge ring-group 2
 rif 0110.2222.3333 0630.021.0030 ring group 2
 netbios name-cache 0110.2222.3333 DEF ring-group 2

Related Commands

Command	Description
show netbios-cache	Displays a list of NetBIOS cache entries.

Syntax Description

length

Length of the NetBIOS type name. The range is 8 to 16 characters.

Defaults

15 characters

Command Modes

Global configuration

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following example specifies that the name cache will validate 16 characters of the NetBIOS type name:

netbios name-cache name-len 16

Related Commands

Command	Description
netbios enable-name-cache	Enables NetBIOS name caching.
netbios name-cache	Defines a static NetBIOS name cache entry, tying the server with the name netbios-name to the mac-address, and specifying that the server is accessible either locally through the interface-name specified, or remotely through the ring-group group-number specified.
netbios name-cache proxy-datagram	Enables the Cisco IOS software to act as a proxy and send NetBIOS datagram type frames.
netbios name-cache query-timeout	Specifies the "dead" time, in seconds, that starts when a host sends any ADD_NAME_QUERY, ADD_GROUP_NAME, or STATUS_QUERY frame. During this dead time, the Cisco IOS software drops any repeat, duplicate ADD_NAME_QUERY, ADD_GROUP_NAME, or STATUS_QUERY frame sent by the same host. This timeout is only effective at the time of the login negotiation process.
netbios name-cache recognized-timeout	Specifies the "dead" time, in seconds, that starts when a host sends any FIND_NAME or NAME_RECOGNIZED frame. During this dead time, the Cisco IOS software drops any repeat, duplicate FIND_NAME or NAME_RECOGNIZED frame sent by the same host. This timeout is only effective at the time of the login negotiation process.
netbios name-cache timeout	Enables NetBIOS name caching and sets the time that entries can remain in the NetBIOS name cache.

Syntax Description

seconds

Time interval, in seconds, that the software forwards a route broadcast datagram type packet. The valid range is any number greater than 0.

Defaults

There is no default time interval.

Command Modes

Global configuration

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following example specifies that the software will forward a NetBIOS datagram type frame in 20-second intervals:

netbios name-cache proxy-datagram 20

Related Commands

Command	Description
netbios enable-name-cache	Enables NetBIOS name caching.
netbios name-cache	Defines a static NetBIOS name cache entry, tying the server with the name netbios-name to the mac-address, and specifying that the server is accessible either locally through the interface-name specified, or remotely through the ring-group group-number specified.
netbios name-cache query-timeout	Specifies the "dead" time, in seconds, that starts when a host sends any ADD_NAME_QUERY, ADD_GROUP_NAME, or STATUS_QUERY frame. During this dead time, the Cisco IOS software drops any repeat, duplicate ADD_NAME_QUERY, ADD_GROUP_NAME, or STATUS_QUERY frame sent by the same host. This timeout is only effective at the time of the login negotiation process.
netbios name-cache recognized-timeout	Specifies the "dead" time, in seconds, that starts when a host sends any FIND_NAME or NAME_RECOGNIZED frame. During this dead time, the Cisco IOS software drops any repeat, duplicate FIND_NAME or NAME_RECOGNIZED frame sent by the same host. This timeout is only effective at the time of the login negotiation process.
netbios name-cache timeout	Enables NetBIOS name caching and sets the time that entries can remain in the NetBIOS name cache.

Syntax Description

seconds

Dead time period in seconds. Default is 6 seconds.

Defaults

6 seconds

Command Modes

Global configuration

Command History

Release	Modification
10.0	The command was introduced.

Examples

The following example sets the timeout to 15 seconds:

netbios name-cache query-timeout 15

Related Commands

Command	Description
netbios name-cache recognized-timeout	Specifies the "dead" time, in seconds, that starts when a host sends any FIND_NAME or NAME_RECOGNIZED frame. During this dead time, the Cisco IOS software drops any repeat, duplicate FIND_NAME or NAME_RECOGNIZED frame sent by the same host. This timeout is only effective at the time of the login negotiation process.

Syntax Description

seconds

Dead time period in seconds. Default is 6 seconds.

Defaults

6 seconds

Command Modes

Global configuration

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following example sets the timeout to 15 seconds:

netbios name-cache recognized-timeout 15

Related Commands

Command	Description
netbios name-cache query-timeout	Specifies the "dead" time, in seconds, that starts when a host sends any ADD_NAME_QUERY, ADD_GROUP_NAME, or STATUS_QUERY frame. During this dead time, the Cisco IOS software drops any repeat, duplicate ADD_NAME_QUERY, ADD_GROUP_NAME, or STATUS_QUERY frame sent by the same host. This timeout is only effective at the time of the login negotiation process.

Syntax Description

minutes

Time, in minutes, that entries can remain in the NetBIOS name cache. Once the time expires, the entry will be deleted from the cache. Default is 15 minutes.

Defaults

15 minutes

Command Modes

Global configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

This command allows you to establish NetBIOS name caching. NetBIOS name caching can be used only between routers that are running Software Release 9.1 or later. NetBIOS name-caching does not apply to static entries.

Examples

The following example sets the timeout to 10 minutes:

interface tokenring 0
 netbios name-cache timeout 10

Related Commands

Command	Description
show netbios-cache	Displays a list of NetBIOS cache entries.

Syntax Description

name	Name of a NetBIOS access filter previously defined with one or more of the netbios access-list bytes global configuration commands.

Defaults

No access list is defined.

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following example filters packets leaving tokenring 1 using the NetBIOS access list named engineering:

interface tokenring 1
 netbios access-list bytes engineering permit 3 0xabcd 
 netbios output-access-filter bytes engineering

Related Commands

Command	Description
netbios access-list bytes	Defines the offset and hexadecimal patterns with which to match byte offsets in NetBIOS packets.
netbios input-access-filter bytes	Defines a byte access list filter on incoming messages. The actual access filter byte offsets and patterns used are defined in one or more netbios-access-list bytes commands.

Syntax Description

name	Name of a NetBIOS access filter previously defined with one or more of the netbios access-list host global configuration commands.

Defaults

No access list filter is defined.

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following example filters packets leaving tokenring 1 using the NetBIOS access list named engineering:

interface tokenring 1
 netbios access-list host engineering permit W?Y?
 netbios output-access-filter host engineering

Related Commands

Command	Description
netbios access-list host	Assigns the name of the access list to a station or set of stations on the network. The NetBIOS station access list contains the station name to match, along with a permit or deny condition.
netbios input-access-filter host	Defines a station access list filter on incoming messages. The access lists of station names are defined in netbios access-list host commands.

Syntax Description

mac-address	12-digit hexadecimal string written as a dotted triplet; for example, 0010.0a00.20a6.
rif-string	Series of 4-digit hexadecimal numbers separated by a period (.). This RIF string is inserted into the packets sent to the specified MAC address.
interface-name	Interface name (for example, tokenring 0) that indicates the origin of the RIF.
ring-group	Specifies the origin of the RIF is a ring group.
ring	Ring group number that indicates the origin of the RIF. This ring group number must match the number you have specified with the source-bridge ring-group command. The valid range is 1 to 4095.

Defaults

No static source-route information is entered.

Command Modes

Global configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

Syntax Description

minutes

Number of minutes an inactive RIF entry is kept. The value must be greater than 0. Default is 15 minutes.

Defaults

15 minutes

Command Modes

Global configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

A RIF entry is cached based on the MAC address and the interface.

A RIF entry can be aged out even if there is active traffic, but the traffic is fast or autonomously switched.

A RIF entry is refreshed only if a RIF field of an incoming frame is identical to the RIF information of the RIF entry in the cache.

Until a RIF entry is removed from the cache, no new information is accepted for that RIF entry.

Examples

The following example changes the timeout period to 5 minutes:

rif timeout 5

Related Commands

Command	Description
clear rif-cache	Clears the entire RIF cache.
rif validate-enable	Enables RIF validation for entries learned on an interface (Token Ring or FDDI).
show rif	Displays the current contents of the RIF cache.

Syntax Description

seconds

Interval, in seconds, at which a proxy is sent. The valid range is any number greater than 0. Default is 2 seconds.

Defaults

2 seconds

Command Modes

Global configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

If the timer expires before the response is received, the RIF entry or the NetBIOS cache entry is marked as invalid and is flushed from the cache table when another explorer or NAME_QUERY packet is received.

Examples

The following example specifies the interval at which a proxy is sent to be 3 seconds:

rif validate-age 3

Related Commands

Command	Description
rif	Enters static source-route information into the RIF cache. If a Token Ring host does not support the use of IEEE 802.2 TEST or XID datagrams as explorer packets, static information may need to be added to the RIF cache of the router.
rif timeout	Determines the number of minutes an inactive RIF entry is kept. RIF information is maintained in a cache whose entries are aged.

Syntax Description

This command has no arguments or keywords.

Defaults

RIF validation is enabled.

Command Modes

Global configuration

Command History

Release	Modification
11.0	This command was introduced.

Usage Guidelines

A RIF validation algorithm is used for the following cases:

• To decrease convergence time to a new source route path when an intermediate bridge goes down.

• To keep a valid RIF entry in a RIF cache even if a RIF entry is not refreshed either because traffic is fast or autonomously switched, or because there is no traffic.

A directed IEEE TEST command is sent to the destination MAC address. If a response received in the time specified by rif validate-age, the entry is refreshed and is considered valid. Otherwise, the entry is removed from the cache. To prevent sending too many TEST commands, any entry that has been refreshed in less than 70 seconds is considered valid.

Validation is triggered as follows:

• When a RIF entry is found in the cache.

• When a RIF field of an incoming frame and the RIF information of the RIF entry is not identical. If, as the result of validation, the entry is removed from the cache, the RIF field of the next incoming frame with the same MAC address is cached.

• When the RIF entry is not refreshed for the time specified in the rif timeout command.

Note   If the RIF entry has been in the RIF cache for 6 hours, and has not been refreshed for the time specified in the rif timeout command, the entry is removed unconditionally from the cache.

Note   The rif validate-enable commands have no effect on remote entries learned over RSRB.

Examples

The following example enables RIF validation:

rif validate-enable

Related Commands

Command	Description
rif timeout	Determines the number of minutes an inactive RIF entry is kept. RIF information is maintained in a cache whose entries are aged.
rif validate-age	Defines the validation time when the Cisco IOS software is acting as a proxy for NetBIOS NAME_QUERY packet or for explorer frames.
rif validate-enable-age	Enables RIF validation for stations on a source-route bridge network that do not respond to an IEEE TEST command.
rif validate-enable-route-cache	Enables synchronization of the RIF cache with the protocol route cache.

Syntax Description

This command has no arguments or keywords.

Defaults

RIF validation is enabled.

Command Modes

Global configuration

Command History

Release	Modification
11.0	This command was introduced.

Usage Guidelines

You must first issue the rif validate-enable command.

When this command is enabled, a RIF entry is not removed from the cache even if it becomes invalid. If the entry is refreshed, it becomes valid again.

If a RIF field of an incoming frame and the RIF information of the invalid RIF entry are not identical, the old RIF information is replaced by the new information.

Note   The rif validate-enable commands have no effect on remote entries learned over RSRB.

Examples

The following example enables RIF validation:

rif validate-enable-age

Related Commands

Command	Description
rif validate-enable	Enables RIF validation for entries learned on an interface (Token Ring or FDDI).

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled.

Command Modes

Global configuration

Command History

Release	Modification
11.0	This command was introduced.

Usage Guidelines

When a RIF entry is removed from the RIF cache, or the RIF information in the RIF entry is changed, the protocol route caches are synchronized with the RIF cache.

Note   The rif validate-enable commands have no effect on remote entries learned over RSRB.

Examples

The following example synchronizes the RIF cache with the protocol route cache:

rif validate-enable-route-cache

Related Commands

Command	Description
rif validate-enable	Enables RIF validation for entries learned on an interface (Token Ring or FDDI).

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following is sample output from the show controllers token command of a CSC-IR or
CSC-2R card:

Router# show controllers token
 
TR Unit 0 is board 0 - ring 0
 
 state 3, dev blk: 0x1D2EBC, mailbox: 0x2100010, sca: 0x2010000
   current address: 0000.3080.6f40, burned in address: 0000.3080.6f40
   current TX ptr: 0xBA8, current RX ptr: 0x800
 
   Last Ring Status: none
 
 Stats: soft:0/0, hard:0/0, sig loss:0/0
        tx beacon: 0/0, wire fault 0/0, recovery: 0/0
        only station: 0/0, remote removal: 0/0
   Bridge: local 3330, bnum 1, target 3583
     max_hops 7, target idb: 0x0, not local
   Interface failures: 0  -- Bkgnd Ints: 0
   TX shorts 0, TX giants 0
 
   Monitor state: (active)
     flags 0xC0, state 0x0, test 0x0, code 0x0, reason 0x0
 f/w ver: 1.0, chip f/w: '000000.ME31100', [bridge capable]
     SMT form of this command s: 1.01 kernel, 4.02 fastmac
     ring mode: F00, internal enables:  SRB REM RPS CRS/NetMgr
     internal functional: 0000011A (0000011A), group: 00000000 (00000000)
     if_state: 1, ints: 0/0, ghosts: 0/0, bad_states: 0/0
     t2m fifo purges: 0/0
     t2m fifo current: 0, t2m fifo max: 0/0, proto_errs: 0/0
     ring: 3330, bridge num: 1, target: 3583, max hops: 7
 
Packet counts:
       receive total:  298/6197, small: 298/6197, large 0/0
               runts: 0/0, giants: 0/0
               local: 298/6197, bridged: 0/0, promis: 0/0
             bad rif: 0/0, multiframe: 0/0
       ring num mismatch 0/0, spanning violations 0
       transmit total: 1/25, small: 1/25, large 0/0
                runts: 0/0, giants: 0/0, errors 0/0
bad fs: 0/0, bad ac: 0
congested: 0/0, not present: 0/0
     Unexpected interrupts: 0/0,  last unexp. int: 0
 
     Internal controller counts:
    line errors:  0/0, internal errors: 0/0
    burst errors: 0/0, ari/fci errors:  0/0
    abort errors: 0/0, lost frame: 0/0
    copy errors:  0/0, rcvr congestion: 0/0
    token errors: 0/0, frequency errors: 0/0
    dma bus errors: -/-, dma parity errors: -/-
     Internal controller smt state:
    Adapter MAC:     0000.3080.6f40, Physical drop:     00000000
    NAUN Address:    0000.a6e0.11a6, NAUN drop:         00000000
    Last source:     0000.a6e0.11a6, Last poll:         0000.3080.6f40
    Last MVID:       0006,           Last attn code:    0006
    Txmit priority:  0006,           Auth Class:        7FFF
    Monitor Error:   0000,           Interface Errors:  FFFF
    Correlator:      0000,           Soft Error Timer:  00C8
    Local Ring:      0000,           Ring Status:       0000
    Beacon rcv type: 0000,           Beacon txmit type: 0000
    Beacon type:     0000,           Beacon NAUN:       0000.a6e0.11a6
 

In the following line, state 3 indicates the state of the board. The rest of this output line displays memory mapping that is of primary use to our engineers.

 state 3, dev blk: 0x1D2EBC, mailbox: 0x2100010, sca: 0x2010000
 

The following line also appears in show interface token output as the address and burned in address (bia), respectively:

 current address: 0000.3080.6f40, burned in address: 0000.3080.6f40
 

The following line displays buffer management pointers that change by board:

 current TX ptr: 0xBA8, current RX ptr: 0x800
 

The following line indicates the ring status from the controller chip set. This information is used by LAN Network Manager:

 Last Ring Status: none
 

The following line displays Token Ring statistics. See the Token Ring specification for more information:

 Stats: soft:0/0, hard:0/0, sig loss:0/0
        tx beacon: 0/0, wire fault 0/0, recovery: 0/0
        only station: 0/0, remote removal: 0/0
 

The following line indicates that Token Ring communication has been enabled on the interface. If this line of output appears, the message "Source Route Bridge capable" should appear in the show interfaces tokenring display.

 Bridge: local 3330, bnum 1, target 3583
 

The following line is specific to the hardware:

   Interface failures: 0  -- Bkgnd Ints: 0
 

In the following line, TX shorts are the number of packets the interface transmits that are discarded because they are smaller than the medium's minimum packet size. TX giants are the number of packets the interface transmits that are discarded because they exceed the medium's maximum packet size.

   TX shorts 0, TX giants 0
 

The following line indicates the state of the controller. Possible values include active, failure, inactive, and reset.

 Monitor state: (active)
 

The following line displays detailed information relating to the monitor state shown in the previous line of output. This information relates to the firmware on the controller. This information is relevant to our engineers only if the monitor state is something other than active.

     flags 0xC0, state 0x0, test 0x0, code 0x0, reason 0x0
 

The following line displays the version numbers for the kernel and the accelerator microcode of the Madge firmware on the board; this firmware is the LLC interface to the chip set:

SMT form of this command s: 1.01 kernel, 4.02 fastmac
    

The following line displays LAN Network Manager information that relates to ring status:

ring mode: F00, internal enables:  SRB REM RPS CRS/NetMgr
   

The following line corresponds to the functional address and the group address shown in show interfaces tokenring output:

internal functional: 0000011A (0000011A), group: 00000000 (00000000)
 

The following line displays interface board state information that is proprietary:

if_state: 1, ints: 0/0, ghosts: 0/0, bad_states: 0/0
    

The following lines display information that is proprietary. Our engineers use this information for debugging purposes:

t2m fifo purges: 0/0
t2m fifo current: 0, t2m fifo max: 0/0, proto_errs: 0/0
 

Each of the fields in the following line maps to a field in the show source bridge display, as follows: ring maps to srn; bridge num maps to bn; target maps to trn; and max hops maps to max:

ring: 3330, bridge num: 1, target: 3583, max hops: 7
 

In the following lines of output, the number preceding the slash (/) indicates the count since the value was last displayed; the number following the slash (/) indicates count since the system was last booted:

Packet counts:
       receive total:  298/6197, small: 298/6197, large 0/0
 

In the following line, the number preceding the slash (/) indicates the count since the value was last displayed; the number following the slash (/) indicates count since the system was last booted. The runts and giants values that appear here correspond to the runts and giants values that appear in show interfaces tokenring output:

runts: 0/0, giants: 0/0
 

The following lines are receiver-specific information that our engineers can use for debugging purposes:

local: 298/6197, bridged: 0/0, promis: 0/0
bad rif: 0/0, multiframe: 0/0
ring num mismatch 0/0, spanning violations 0
transmit total: 1/25, small: 1/25, large 0/0
runts: 0/0, giants: 0/0, errors 0/0
 

The following lines include very specific statistics that are not relevant in most cases, but exist for historical purposes. In particular, the internal errors, burst errors, ari/fci, abort errors, copy errors, frequency errors, dma bus errors, and dma parity errors fields are not relevant.

Internal controller counts:
 line errors: 0/0,  internal errors: 0/0
 burst errors: 0/0,  ari/fci errors: 0/0
 abort errors: 0/0, lost frame: 0/0
 copy errors: 0/0, rcvr congestion: 0/0
 token errors: 0/0, frequency errors: 0/0
 dma bus errors: -/-, dma parity errors: -/-
 

The following lines are low-level Token Ring interface statistics relating to the state and status of the Token Ring with respect to all other Token Rings on the line:

 Internal controller smt state:
 Adapter MAC:     0000.3080.6f40, Physical drop:     00000000
 NAUN Address:    0000.a6e0.11a6, NAUN drop:         00000000
 Last source:     0000.a6e0.11a6, Last poll:         0000.3080.6f40
 Last MVID:       0006,           Last attn code:    0006
 Txmit priority:  0006,           Auth Class:        7FFF
 Monitor Error:   0000,           Interface Errors:  FFFF
 Correlator:      0000,           Soft Error Timer:  00C8
 Local Ring:      0000,           Ring Status:       0000
 Beacon rcv type: 0000,           Beacon txmit type: 0000

Syntax Description

number

(Optional) Interface number. If you do not provide a value, the command will display statistics for all Token Ring interfaces.

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following is sample output from the show interfaces tokenring command:

Router# show interfaces tokenring
 
TokenRing 0 is up, line protocol is up
Hardware is 16/4 Token Ring, address is 5500.2000.dc27 (bia 0000.3000.072b)
   Internet address is 150.136.230.203, subnet mask is 255.255.255.0
   MTU 8136 bytes, BW 16000 Kbit, DLY 630 usec, rely 255/255, load 1/255
   Encapsulation SNAP, loopback not set, keepalive set (10 sec)
   ARP type: SNAP, ARP Timeout 4:00:00
   Ring speed: 16 Mbps
   Single ring node, Source Route Bridge capable
   Group Address: 0x00000000, Functional Address: 0x60840000
   Last input 0:00:01, output 0:00:01, output hang never
   Output queue 0/40, 0 drops; input queue 0/75, 0 drops
   Five minute input rate 0 bits/sec, 0 packets/sec
   Five minute output rate 0 bits/sec, 0 packets/sec
   16339 packets input, 1496515 bytes, 0 no buffer
        Received 9895 broadcasts, 0 runts, 0 giants
        0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     32648 packets output, 9738303 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets, 0 restarts
     5 transitions
 

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following is sample output from the show lnm bridge command:

Router# show lnm bridge
 
Bridge 001-2-003, Ports 0000.3000.abc4, 0000.0028.abcd
Active Links:  0000.0000.0000  0000.0000.0000  0000.0000.0000  0000.0000.0000
Notification: 0 min, Threshold 00.10%
 

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following is sample output from the show lnm config command for a simple two-port bridge:

Router# show lnm config
 
Bridge(s) currently configured:
 
           From     ring 001, address 0000.3000.abc4
           Across bridge 002
           To       ring 003, address 0000.0028.abcd
 

The following is sample output from the show lnm config command for a multiport bridge:

Router# show lnm config
 
Bridge(s) currently configured:
 
           From     ring 001, address 0000.0028.abc4
           Across bridge 001
           To       ring 008, address 4000.0028.abcd
 
           From     ring 002, address 0000.3000.abc4
           Across bridge 002
           To       ring 008, address 4000.3000.abcd
 
           From     ring 003, address 0000.3000.5735
           Across bridge 003
           To       ring 008, address 4000.3000.5735
 

Syntax Description

type	(Optional) Interface type.
number	(Optional) Interface number.

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

This command is for all types of interfaces, including Token Ring interfaces. If you want information specific to Token Ring, use the show lnm ring command.

Examples

The following is sample output from the show lnm interface command:

router# show lnm interface
 nonisolating error counts
interface  ring   Active Monitor  SET   dec   lost   cong.  fc    freq.token
TokenRing1 0001*  1000.5a98.23a0  00200 00001 00000  00000  00000 0000000002
 
Notification flags: FE00, Ring Intensive: FFFF, Auto Intensive: FFFF
Active Servers: LRM LBS REM RPS CRS
Last NNIN:   never, from 0000.0000.0000.
Last Claim:  never, from 0000.0000.0000.
Last Purge:  never, from 0000.0000.0000.
Last Beacon: never, 'none' from 0000.0000.0000.
Last MonErr: never, 'none' from 0000.0000.0000.
 
                 isolating error counts
station         int ring   loc.   weight line   inter  burst  ac    abort
1000.5a98.23a0  T1  0001   0000   00 - N00000   00000  00000  00000 00000
1000.5a98.239e  T1  0001   0000   00 - N00000   00000  00000  00000 00000
1000.5a6f.bc15  T1  0001   0000   00 - N00000   00000  00000  00000 00000
0000.3000.abc4  T1  0001   0000   00 - N00000   00000  00000  00000 00000
1000.5a98.239f  T1  0001   0000   00 - N00000   00000  00000  00000 00000
 

Related Commands

Command	Description
show lnm ring	Displays all LNM information about a specific Token Ring or all Token Rings. If a specific interface is requested, it also displays a list of all currently active stations on that interface.
show lnm station	Displays LNM-related information about a specific station or all known stations on all rings. If a specific station is requested, it also displays a detailed list of the current MAC-level parameters of that station.

Syntax Description

ring-number

(Optional) Number of a specific Token Ring. It can be a value in the range 1 to 4095.

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

Syntax Description

address

(Optional) Address of a specific LNM station.

Command Modes

Privileged EXEC

Command History

Release	Modification
11.0	This command was introduced.

Examples

The following is sample output from the show lnm station command when a particular address (in this case, 1000.5abc15) has been specified:

Router# show lnm station 1000.5a6f.bc15
 
                                            isolating error counts
    station      int  ring  loc.   weight   line  inter burst   ac  abort
1000.5a6f.bc15    T1  0001  0000   00 - N   00000 00000 00000 00000 00000
 
Unique ID:  0000.0000.0000          NAUN: 0000.3000.abc4
Functional: C000.0000.0000         Group: C000.0000.0000
Physical Location:   00000        Enabled Classes:  0000
Allowed Priority:    00000        Address Modifier: 0000
Product ID:     00000000.00000000.00000000.00000000.0000
Ucode Level:    00000000.00000000.0000
Station Status: 00000000.0000
Last transmit status: 00
 

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following is sample output from the show netbios-cache command:

Router# show netbios-cache
 
  HW Addr          Name            How       Idle      NetBIOS Packet Savings
1000.5a89.449a     IC6W06_B        TR1       6         0
1000.5a8b.14e5     IC_9Q07A        TR1       2         0
1000.5a25.1b12     IC9Q19_A        TR1       7         0
1000.5a25.1b12     IC9Q19_A        TR1       10        0
1000.5a8c.7bb1     BKELSA1         TR1       4         0
1000.5a8b.6c7c     ICELSB1         TR1       -         0
1000.5a31.df39     ICASC_01        TR1       -         0
1000.5ada.47af     BKELSA2         TR1       10        0
1000.5a8f.018a     ICELSC1         TR1       1         0
 

Related Commands

Command	Description
netbios name-cache	Defines a static NetBIOS name cache entry, tying the server with the name netbios-name to the mac-address, and specifying that the server is accessible either locally through the interface-name specified, or remotely through the ring-group group-number specified.
netbios name-cache timeout	Enables NetBIOS name caching and sets the time that entries can remain in the NetBIOS name cache.

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following is sample output from the show rif command:

Router# show rif
 
Codes: * interface, - static, + remote
Hardware Addr  How   Idle (min)  Routing Information Field
5C02.0001.4322 rg5           -   0630.0053.00B0
5A00.0000.2333 TR0           3   08B0.0101.2201.0FF0
5B01.0000.4444 -             -   -
0000.1403.4800 TR1           0   -
0000.2805.4C00 TR0           *   -
0000.2807.4C00 TR1           *   -
0000.28A8.4800 TR0           0   -
0077.2201.0001 rg5          10   0830.0052.2201.0FF0
 

Related Commands

Command	Description
multiring	Enables collection and use of RIF information.

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following is sample output from the show source-bridge command:

Router# show source-bridge
 
Local Interfaces:                           receive     transmit
             srn bn  trn r p s n  max hops     cnt         cnt        drops
TR0            5  1   10 *   *          7    39:1002     23:62923 
 
Ring Group 10:
  This peer: TCP 150.136.92.92
   Maximum output TCP queue length, per peer: 100
  Peers:                 state   lv  pkts_rx  pkts_tx  expl_gn    drops TCP
   TCP 150.136.92.92     -       2       0        0          0     0    0
   TCP 150.136.93.93     open    2*     18       18          3     0    0
Rings:
   bn: 1 rn: 5    local  ma: 4000.3080.844b TokenRing0            fwd: 18
   bn: 1 rn: 2   remote  ma: 4000.3080.8473 TCP 150.136.93.93     fwd: 36
 
Explorers: ------- input -------             ------- output -------
       spanning  all-rings     total      spanning  all-rings     total
  TR0         0          3         3             3          5         8
 
 

The following is sample output from the show source-bridge command when Token Ring LANE is configured.

Router# show source-bridge
 
Local Interfaces:                           receive     transmit
             srn bn  trn r p s n  max hops     cnt         cnt        drops
AT2/0.1     2048  5  256 *   f    7  7  7     5073        5072          0
To3/0/0        1  1  256 *   f    7  7  7     4719        4720          0
 
Global RSRB Parameters:
 TCP Queue Length maximum: 100
 
Ring Group 256:
  No TCP peername set, TCP transport disabled
   Maximum output TCP queue length, per peer: 100
  Rings:
   bn: 5  rn: 2048 local  ma: 4000.0ca0.5b40 ATM2/0.1              fwd: 5181
   bn: 1  rn: 1    local  ma: 4000.3005.da06 TokenRing3/0/0        fwd: 5180
 
Explorers: ------- input -------             ------- output -------
         spanning  all-rings     total      spanning  all-rings     total
AT2/0.1         9          1        10            10          0        10
To3/0/0        10          0        10             9          1        10
 
  Local: fastswitched 20        flushed 0         max Bps 38400
 
         rings      inputs         bursts         throttles     output drops
       To3/0/0          10              0                 0                0
 

Syntax Description

This command has no arguments or keywords.

Command Modes

EXEC

Command History

Release	Modification
10.3	This command was introduced.

Examples

The following is sample output from the show span command:

RouterA> show span
 
Bridge Group 1 is executing the IBM compatible spanning tree protocol
  Bridge Identifier has priority 32768, address 0000.0c0c.f68b
  Configured hello time 2, max age 6, forward delay 4
  Current root has priority 32768, address 0000.0c0c.f573
  Root port is 001A (TokenRing0/0), cost of root path is 16
  Topology change flag not set, detected flag not set
  Times:  hold 1, topology change 30, notification 30
          hello 2, max age 6, forward delay 4, aging 300
  Timers: hello 0, topology change 0, notification 0
Port 001A (TokenRing0/0) of bridge group 1 is forwarding. Path cost 16
   Designated root has priority 32768, address 0000.0c0c.f573
   Designated bridge has priority 32768, address 0000.0c0c.f573
   Designated port is 001B, path cost 0, peer 0
   Timers: message age 1, forward delay 0, hold 0
Port 002A (TokenRing0/1) of bridge group 1 is blocking. Path cost 16
   Designated root has priority 32768, address 0000.0c0c.f573
   Designated bridge has priority 32768, address 0000.0c0c.f573
   Designated port is 002B, path cost 0, peer 0
   Timers: message age 0, forward delay 0, hold 0
Port 064A (spanRSRB) of bridge group 1 is disabled. Path cost 250
   Designated root has priority 32768, address 0000.0c0c.f573
   Designated bridge has priority 32768, address 0000.0c0c.f68b
   Designated port is 064A, path cost 16, peer 0
   Timers: message age 0, forward delay 0, hold 0
 

A port (spanRSRB) is created with each virtual ring group. The port will be disabled until one or more peers go into open state in the ring group.

Syntax Description

source-ring-number	Ring number for the interface's Token Ring or FDDI ring. It must be a decimal number in the range 1 to 4095 that uniquely identifies a network segment or ring within the bridged Token Ring or FDDI network
bridge-number	Number that uniquely identifies the bridge connecting the source and target rings. It must be a decimal number in the range 1 to 15.
target-ring-number	Ring number of the destination ring on this router. It must be unique within the bridged Token Ring or FDDI network. The target ring can also be a ring group. Must be a decimal number.
conserve-ring	(Optional) Keyword to enable SRB over Frame Relay. When this option is configured, the SRB software does not add the ring number associated with the Frame Relay PVC (the partner's virtual ring) to outbound explorer frames. This option is permitted for Frame Relay subinterfaces only.

Defaults

SRB is disabled.

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.
11.3	This command was revised to enable SRB over Frame Relay.

Usage Guidelines

The parser automatically displays the word "active" in the source-bridge command in configurations that have SRB enabled. You do not need to enter the source-bridge command with the active keyword.

Examples

In the following example, Token Rings 129 and 130 are connected via a router:

interface tokenring 0
 source-bridge 129 1 130
 !
interface tokenring 1
 source-bridge active 130 1 129
 

In the following example, an FDDI ring on one router is connected to a Token Ring on a second router across a DLSw+ link:

dlsw local-peer peer-id 132.11.11.2
dlsw remote-peer 0 tcp 132.11.11.3
interface fddi 0
 no ip address
 multiring all
 source-bridge active 26 1 10
!
dlsw local-peer peer-id 132.11.11.3
dlsw remote-peer 0 tcp 132.11.11.2
interface tokenring 0
 no ip address
 multiring all
 source-bridge active 25 1 10
 

In the following example, a router forwards frames from a locally attached Token Ring over the Frame Relay using SRB:

source-bridge ring-group 200
!
interface Serial0
 encapsulation frame-relay
!
interface Serial0.30 point-to-point
 frame-relay interface-dlci 30 ietf
 source-bridge 100 1 200 conserve-ring
 source-bridge spanning
!
interface TokenRing0
 source-bridge 600 1 200

Related Commands

Command	Description
encapsulation frame-relay	Enables Frame Relay encapsulation.
frame-relay interface-dlci	Assigns a DLCI to a specified Frame Relay subinterface on the router or access server.
source-bridge ring-group	Defines or removes a ring group from the configuration.
source-bridge transparent	Establishes bridging between transparent bridging and SRB.

Syntax Description

seconds

Interval of time, in seconds, before a connection attempt to a remote peer is aborted.

Defaults

The default connection-timeout interval is 10 seconds.

Command Modes

Global configuration

Command History

Release	Modification
10.3	This command was introduced.

Usage Guidelines

Examples

The following example sets the connection timeout interval to 60 seconds:

source-bridge connection-timeout 60

Related Commands

Command	Description
source-bridge ring-group	Defines or removes a ring group from the configuration.

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Global configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

The Cisco IOS software supports two types of Token Ring LLC2 to Ethernet conversion. They are as follows:

• Token Ring LLC2 to Ethernet 802.3 LLC2

• Token Ring LLC2 to Ethernet 0x80d5

Use this global configuration command to change the translation behavior. By default, the Cisco IOS software translates Token Ring LLC2 to Ethernet 802.3 LLC2. This command allows you to configure the software to translate Token Ring LLC2 frames into Ethernet 0x80d5 format frames.

This command is useful when you have a non-IBM device attached to an IBM network with devices that are using the nonstandard Token Ring LLC2 to Ethernet 80d5 translation. If you do not configure your router to enable 80d5 processing, the non-IBM and IBM devices will not be able to communicate.

Note   The 80d5 frame processing option is available only with SR/TLB. It is not available when source-route transparent bridging (SRT) is used.

Use the show span to check whether 80d5 processing is enabled. If it is, the following line displays in the output:

Translation between LLC2 and Ethernet Type II 80d5 is enabled

Examples

The following example enables 0x80d5 processing, removes the translation for SAP 08, and adds the translation for SAP 1c:

source-bridge enable-80d5
 no source-bridge sap-80d5 08
 source-bridge sap-80d5 1c

Related Commands

Command	Description
show span	Displays the spanning-tree topology known to the router.
source-bridge sap-80d5	Allows non-IBM hosts (attached to a router with 80d5 processing enabled) to use the standard Token Ring to Ethernet LLC2 translation instead of the nonstandard Token Ring to Ethernet 80d5 translation, and allows the translation to be set on a per-DSAP basis.

Syntax Description

This command has no arguments or keywords.

Defaults

Duplicate explorer filtering is disabled.

Command Modes

Global configuration

Command History

Release	Modification
11.2	This command was introduced.

Examples

The following example enables duplicate explorer filtering:

source-bridge explorer-dup-ARE-filter

Syntax Description

This command has no arguments or keywords.

Defaults

Fast switching is enabled.

Command Modes

Global configuration

Command History

Release	Modification
10.3	This command was introduced.

Usage Guidelines

Use the no form of this command in conjunction with the source-bridge explorerq-depth and the source-bridge explorer-maxrate command to optimize explorer processing.

Examples

The following example enables explorer fast switching after it has been previously disabled:

source-bridge explorer-fastswitch

Related Commands

Command	Description
source-bridge explorer-maxrate	Sets the maximum byte rate of explorers per ring.
source-bridge explorerq-depth	Sets the maximum explorer queue depth.

Syntax Description

maxrate

Number in the range 100 to 1000000000 (in bytes per second). The default maximum byte rate is 38400 bytes per second.

Defaults

The default maximum byte rate is 38400 bytes per second.

Command Modes

Global configuration

Command History

Release	Modification
10.3	This command was introduced.

Usage Guidelines

Given the number of different explorer packet types and sizes and the bandwidth limits of the various interfaces, the bus data rate (as opposed to the packet rate) is the common denominator used to decide when to flush incoming explorers. The packets are dropped by the interface before any other processing.

Examples

The following command sets the maximum byte rate of explorers on a ring:

source-bridge explorer-maxrate 100000

Syntax Description

depth

The maximum number of incoming packets. The valid range is 1 to 500.

Defaults

The default maximum depth is 30.

Command Modes

Global configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

In this implementation, the limit is on a per-interface basis such that each interface can have up to the maximum (default 30) outstanding packets on the queue before explorers from that particular interface are dropped.

Examples

The following example sets the maximum explorer queue depth:

source-bridge explorerq-depth 100

Syntax Description

access-list-number

Number of the access list. The value must be in the range 700 to 799.

Defaults

No access list is assigned.

Command Modes

Interface configuration

Command History

Release	Modification
10.3	This command was introduced.

Examples

The following example assigns access list 700 to Token Ring 0:

interface tokenring 0
 source-bridge input-address-list 700
!
access-list 700 deny 1000.5A00.0000  8000.00FF.FFFF
access-list 700 permit 0000.0000.0000  FFFF.FFFF.FFFF

Related Commands

Command	Description
access-list	Configures the access list mechanism for filtering frames by protocol type or vendor code.
source-bridge output-address-list	Applies an access list to an interface configured for SRB, and filters source-routed packets sent to the router interface based on the destination MAC address.

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following example specifies access list 203:

interface tokenring 0
 source-bridge input-lsap-list 203

Related Commands

Command	Description
access-list	Configures the access list mechanism for filtering frames by protocol type or vendor code.
source-bridge output-lsap-list	Filters, on output, FDDI and IEEE 802-encapsulated packets that have DSAP and SSAP fields in their frame formats.

Syntax Description

access-list-number

Number of the access list. This access list is applied to all SNAP frames received on that interface prior to the source-routing process. Specify zero (0) to disable the application of the access list on the bridge group. The value must be in the range 200 to 299.

Defaults

Disabled

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

Use the access list command to specify type code when using the source-bridge input-type-list command.

Examples

The following example specifies access list 202:

interface tokenring 0
 source-bridge input-type-list 202
!
access-list 202 deny 0x6000 0x0007
access-list 202 permit 0x0000 0xFFFF

Related Commands

Command	Description
access-list	Configures the access list mechanism for filtering frames by protocol type or vendor code.
source-bridge output-type-list	Filters SNAP-encapsulated frames by type code on output.

Syntax Description

count

Determines the number of bridges an explorer packet can traverse. Typically, the maximum number of bridges for interoperability with IBM equipment is seven.

Defaults

The maximum number of bridge hops is seven.

Command Modes

Interface configuration

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

Frames are forwarded only if the number of hops in the routing information field of the input frame plus hops appended by the router is less than or equal to the specified count. If the interface is connected to a destination interface, the router appends one hop. If the interface is tied to a virtual ring, the router appends two hops. This applies only to all-routes explorer frames on input to this interface.

Examples

The following example limits the maximum number of source-route bridge hops to five.

source-bridge max-hops 5

Related Commands

Command	Description
source-bridge	Configures an interface for SRB.
source-bridge max-in-hops	Controls the forwarding or blocking of spanning-tree explorer frames received on an interface.
source-bridge max-out-hops	Controls the forwarding or blocking of spanning-tree explorer frames sent from this interface.

Syntax Description

count

Determines the number of bridges an explorer packet can traverse. Typically, the maximum number of bridges for interoperability with IBM equipment is seven.

Defaults

The maximum number of bridge hops is seven.

Command Modes

Interface configuration

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

Frames are forwarded only if the number of hops in the routing information field of the input frame is less than or equal to the specified count. This applies only to spanning-tree explorer frames input to the specified interface.

Examples

The following example limits the maximum number of source-route bridge hops to three:

source-bridge max-in-hops 3

Related Commands

Command	Description
source-bridge	Configures an interface for SRB.
source-bridge max-hops	Controls the forwarding or blocking of all-route explorer frames received on an interface.
source-bridge max-out-hops	Controls the forwarding or blocking of spanning-tree explorer frames sent from this interface.

Syntax Description

count

Determines the number of bridges an explorer packet can traverse. Typically, the maximum number of bridges for interoperability with IBM equipment is seven.