Source-Route Bridging Commands

Syntax Description

Default

No access expression is defined.

Command Mode

Interface configuration

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.

Related Command

Syntax Description

Default

No access list is configured.

Command Mode

Global configuration

Usage Guidelines

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

Example

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

Default

No bridge group is defined.

Command Mode

Global configuration

Example

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

bridge 1 protocol ibm

Related Commands

Syntax Description

This command has no arguments or keywords.

Command Mode

Privileged EXEC

Usage Guidelines

Routers automatically learn NetBIOS names. This command clears those entries.

Example

The following example shows the use of the clear netbios-cache command:

clear netbios-cache

Related Commands

Syntax Description

This command has no arguments or keywords.

Command Mode

Privileged EXEC

Usage Guidelines

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

Example

The following example shows the use of the clear rif-cache command:

clear rif-cache

Related Commands

Syntax Description

This command has no arguments or keywords.

Command Mode

Privileged EXEC

Example

The following example shows the use of the clear source-bridge command:

clear source-bridge

Related Commands

A dagger (†) indicates that the command is documented in another chapter.

Syntax Description

This command has no arguments or keywords.

Default

Disabled

Command Mode

Privileged EXEC

Usage Guidelines

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

Example

clear sse

Syntax Description

Default

Command Mode

Interface configuration

Usage Guidelines

This command replaces and extends the bridge old-oui command in release 9.0.

Before using this command, you must have completely configured your router using multiport source-bridging and transparent bridging.

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.

Example

The following example specifies standard OUI form:

interface tokenring 0
ethernet-transit-oui standard

Related Commands

Syntax Description

Default

0

Command Mode

Interface configuration

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 through 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.

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

! provide appropriate global configuration command if not currently in your config. 
!
! permit 0, 1, 2, and 3 
lnm alternate 3 

Related Command

lnm password

Syntax Description

This command has no arguments or keywords.

Default

Enabled

Command Mode

Interface configuration

Usage Guidelines

For more information about the Active Monitor, refer to the IBM Token Ring Architecture Reference Manual or the IEEE 802.5 specification.

Example

Because lnm crs is enabled by default, the following example shows the use of the no form of this command of the lnm crs command disable monitoring of the current logical configuration of a Token Ring:

interface TokenRing 0
no lnm crs

Related Commands

Syntax Description

This command has no arguments or keywords.

Default

Enabled

Command Mode

Global configuration

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.

Example

The following example disables LNM functionality:

lnm disabled

Related Commands

Syntax Description

Default

10 (.10 percent)

Command Mode

Interface configuration

Usage Guidelines

The router 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.

Example

In the following example, the loss threshold is set to 0.02 percent:

interface TokenRing 0
lnm loss-threshold 2

Syntax Description

Default

00000000

Command Mode

Interface configuration

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 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 through 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 write terminal command.

Example

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 Command

lnm alternate

Syntax Description

Default

Enabled

Command Mode

Global configuration

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.

Example

The following example disables all pathtrace reporting:

lnm pathtrace-disabled

Related Commands

Syntax Description

This command has no arguments or keywords.

Default

Enabled

Command Mode

Interface configuration

Usage Guidelines

Example

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

interface TokenRing 0
lnm rem

Related Commands

Syntax Description

This command has no arguments or keywords.

Default

Enabled

Command Mode

Interface configuration

Usage Guidelines

Example

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

interface TokenRing 0
lnm rps

Related Commands

Syntax Description

This command has no arguments or keywords.

Default

Enabled

Command Mode

Global configuration

Usage Guidelines

Configuring a router/bridge 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 a router, 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 router.

Example

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

lnm snmp-only 

Syntax Description

Default

200 milliseconds (2 seconds)

Command Mode

Interface configuration

Usage Guidelines

All stations on a Token Ring notify the Ring Error Monitor (REM) when they detect errors on the ring. In order to prevent excessive 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.

Example

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

! provide appropriate Global configuration command if not currently in your config. 
!
lnm softerr 500 

Related Command

lnm rem

Syntax Description

Default

No RSRB priority group is assigned.

Command Mode

Interface configuration

Usage Guidelines

Example

In the following example, Token Ring interface 0 is assigned the RSRB priority group 1:

source-bridge ring-group 2624
source-bridge remote-peer 2624 tcp 1.0.0.1
source-bridge remote-peer 2624 tcp 1.0.0.2 local-ack priority
!
interface TokenRing 0
source-bridge 2576 8 2624
locaddr-priority 1

Related Commands

Syntax Description

Default

No mapping

Command Mode

Global configuration

Usage Guidelines

Use this command to map LUs to queuing priorities. Once you have established the priority for each LU, you can assign a priority to a TCP port. Hence you have established a mapping between the LUs and queuing priorities, and queuing priorities and TCP ports.

It is preferable to prioritize NetBIOS traffic below SNA traffic, but by default is assigned the high priority on TCP port 1996.

Example

In the following example LU 01 has been assigned a medium priority and maps to TCP port 1996; LU 02 has been assigned a normal priority and maps to TCP port 1987; LU 03 has been assigned a low priority and maps to TCP port 1988; LU 04 has been assigned high priority and maps to TCP port 1989.

locaddr-priority-list 1 01 medium
locaddr-priority-list 1 02 normal
locaddr-priority-list 1 03 low
locaddr-priority-list 1 04 high
 
priority-list 1 protocol ip low tcp 1996
priority-list 1 protocol ip high tcp 1987
priority-list 1 protocol ip medium tcp 1988
priority-list 1 protocol ip normal tcp 1989

Related Commands

Syntax Description

Default

No MAC layer address is set.

Command Mode

Interface configuration

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 TI MAC firmware problem. It is up to the network administrator to ensure that no other host on the network is using that MAC address.

Example

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

Default

Disabled

Command Mode

Interface configuration

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
  
  

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.

Example

These commands enable 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

A dagger (†) indicates that the command is documented in another chapter.

Syntax Description

Default

No offset or pattern is defined.

Command Mode

Global configuration

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

Syntax Description

Default

No access list is assigned.

Command Mode

Global configuration

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

Syntax Description

This command has no arguments or keywords.

Default

Disabled

Command Mode

Interface configuration

Usage Guidelines

Example

The following example enables NetBIOS name caching for interface tokenring 0:

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

Related Commands

Syntax Description

Default

No access list is defined.

Command Mode

Interface configuration

Example

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

Syntax Description

Default

No access list is defined.

Command Mode

Interface configuration

Example

The following example shows how to filter packets coming into Token Ring unit 1 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

Syntax Description

Default

No entry is defined.

Command Mode

Global configuration

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 router 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.

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 Command

Syntax Description

Default

15 characters

Command Mode

Global configuration

Example

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

Syntax Description

Default

There is no default time interval.

Command Mode

Global configuration

Example

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

netbios name-cache proxy-datagram 20

Related Commands

Syntax Description

Default

6 seconds

Command Mode

Global configuration

Example

The following example sets the timeout to 15 seconds:

netbios name-cache query-timeout 15

Related Command

Syntax Description

Default

6 seconds

Command Mode

Global configuration

Example

The following example sets the timeout to 15 seconds:

netbios name-cache recognized-timeout 15

Related Command

Syntax Description

Default

15 minutes

Command Mode

Global configuration

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.

Example

The following example sets the timeout to 10 minutes:

interface tokenring 0
netbios name-cache timeout 10

Related Command

Syntax Description

Default

No access list is defined.

Command Mode

Interface configuration

Example

The following example filters packets leaving Token Ring unit 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

Syntax Description

Default

No access list filter is defined.

Command Mode

Interface configuration

Example

The following example filters packets leaving Token Ring unit 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

Syntax Description

Default

No queuing priorities are established.

Command Mode

Global configuration

Usage Guidelines

Syntax Description

Default

No static source-route information is entered.

Command Mode

Global configuration

Usage Guidelines

Syntax Description

Default

15 minutes

Command Mode

Global configuration

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 aged out and removed from the cache, no new RIF information is accepted for the same RIF entry.

Example

The following example changes the timeout period to 5 minutes:

rif timeout 5

Related Commands

Syntax Description

Default

2 seconds

Command Mode

Global configuration

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.

Example

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

rif validate-age 3

Related Commands

Syntax Description

This command has no arguments or keywords.

Default

RIF validation is enabled.

Command Mode

Global configuration

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.
  
  

Example

The following example enables RIF validation:

rif validate-enable

Related Commands

Syntax Description

This command has no arguments or keywords.

Default

RIF validation is enabled.

Command Mode

Global configuration

Usage Guidelines

Syntax Description

This command has no arguments or keywords.

Default

This command is disabled by default.

Command Mode

Global configuration

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.

Related Command

Syntax Description

Default

No filters are assigned.

Command Mode

Global configuration

Example

The following example specifies SAP filters by LSAP address:

rsrb remote-peer 1000 tcp 131.108.2.30 lsap-output-list 201

Related Commands

Syntax Description

Default

No filter is assigned.

Command Mode

Global configuration

Example

The following example filters packets by NetBIOS station name:

rsrb remote-peer 1000 tcp 131.108.2.30 netbios-output-list host engineering

Related Commands

Syntax Description

Default

No priority list is defined.

Command Mode

Interface configuration

Example

The following example specifies priority list number 1:

sap-priority 1

Related Command

Syntax Description

Default

No priority list is defined.

Command Mode

Global configuration

Usage Guidelines

To give precedence to traffic on a particular LLC2 session, you must specify all four keywords (dsap, ssap, dmac, and smac) to uniquely identify the LLC2 session.

Example

The following example defines priority list 1 and specifies SSAP and DSAP addresses:

sap-priority-list 1 high dsap 04 ssap 04

Syntax Description

This command has no arguments or keywords.

Command Mode

Privileged EXEC

Sample Display

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

Command Mode

Privileged EXEC

Sample Display

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