Bridging Commands

This document describes the bridging configuration and monitoring commands. It contains the following section:

The Bridge Commands

The Bridge Commands

This section describes the bridging configuration and monitoring commands. They allow you to specify parameters for the bridge and its interfaces.

To display the Bridge Config> prompt: 

Config>protocol bridge
Transparent Bridge user configuration

Bridge Config>
To display the Bridge> monitoring prompt:

+protocol bridge
Bridge>
Table 1 lists the bridging configuration and monitoring commands. Not all parameters apply to all router platforms. Press Space twice after you type a command to display the available parameters for each command for your router. Enter help for information about using the command line interface.

[C] means the command is available at the Bridge Config> prompt.

[M] means the command is available at the Bridge> prompt.

Table 1 Bridging Commands

Command Function
Add [C] [M] Adds station addresses to the permanent database, address mapping, LAN/WAN ports, protocol filters, and a tunnel between end stations across an IP internetwork.

BAN [C] [M] Displays the boundary access node (BAN) configuration or monitoring prompt.

Cache [M] Displays cache entries for a specified port.

Change [C] Changes bridge and segment numbers.

Delete [C] [M] Deletes station address entries, specific address mapping, LAN/WAN ports, protocol filters, and a tunnel between end stations across an IP internetwork.

Disable [C] Disables bridging, duplicate frames, mapping between group and functional addresses, propagation of spanning tree explorer frames, source-routing, FDDI encapsulation, reception of spanning tree explorer frames over a tunnel, conversion of source-routed frame to transparent frame, transparent (spanning tree) bridging, and a tunnel between bridges.

Enable [C] Enables bridging, duplicate frames, mapping between group and functional addresses, propagation of spanning tree explorer frames, source-routing, FDDI encapsulation, reception of spanning tree explorer frames over a tunnel, conversion of source routed frame to transparent frame, transparent (spanning tree) bridging, and a tunnel between bridges.

Exit [C] [M] Returns to the previous prompt.

Flip [M] Flips MAC address from canonical to 802.5 (non-canonical or IBM) bit order.

List [C] [M] Displays information about the complete bridge configuration or about selected configuration parameters.

LNM [C] [M] Displays the LNM (LAN Network Manager) configuration prompt.

NetBIOS [C] [M] Displays the NetBIOS configuration or monitoring prompt.

Set [C] Sets aging time for dynamic address entries, bridge address, maximum frame size for tunneling, Largest Frame (LF) bit encoding, maximum frame size, spanning tree protocol bridge and port parameters, Route Descriptor (RD) values, and filtering database size.

Tunnel [C] [M] Displays the tunnel configuration prompt.

Add [C] [M]

Adds information to your bridging configuration. The router does not save information you add at the monitoring prompt when you restart the router.

Add [C]

At the Bridge configuration prompt, use add to add the following information to your bridging configuration:

Syntax: add

address
mapping
port
prot-filter
tunnel

address addr-value

Adds unique station address entries to the permanent filtering database. Permanent database entries are not destroyed by the power off/on process and are immune to the aging settings. Dynamic entries cannot replace permanent entries.

The addr-value is the MAC address of the desired entry. It can be an individual, multicast, or broadcast address. You can also specify the outgoing forwarding port map for each incoming port.

Example: add address

Address (in 12-digit hex) []? 
Exclude destination address from all ports?(Yes or No): 
Use same output port mapping for all input Ports?(Yes or [No]): 
Output port mapping:
   Input Port Number [1]? 
   Bridge to all ports?(Yes or [No]): 
   continue to another input port? (Yes or [No]): 
   Input Port Number [2]? 
   Bridge to all ports?(Yes or [No]): n
   Bridge to  port 1 - Yes or [No]: y
   Bridge to  port 2 - Yes or [No]: n
   Bridge to  port 3 - Yes or [No]: y
   continue to another input port? (Yes or [No]): y
   Input Port Number [3]? 3
   Bridge to all ports?(Yes or [No]): y
   continue to another input port? (Yes or [No]): y
Source Address Filtering Applies? (Yes or [No]): y
Exclude destination address ...

 Sets destination address filtering for that entry. Yes causes filtering of any frames that contain this address as a destination address, no matter which port it came from.

Use same output port mapping...

Yes creates one outgoing port map for all incoming ports rather than allowing for mapping only to specific ports. No causes further prompting.

Input Port 1, Port 2

Answering No to the previous prompt causes input port-by-input port prompting (Input Port Number [1]?) to select each input port and its associated outgoing bridge ports.

Bridge to all ports?

 Yes creates an outgoing port map that includes all ports. Thus, when a frame with this address as the destination address is received, it is forwarded to all outgoing forwarding ports except for the incoming port. The following are examples of how this is done according to the port map:

 If a frame is received on port 1 and the port map indicates 1 (for port 1), the frame is filtered.

If the same frame is received on port 2 and the port map indicates 1 (for port 1), the frame is forwarded to port 1.

If a frame is received on port 1 and the matching address entry's port map indicates 1, 2, or 3, the frame is forwarded to ports 2 and 3.

 If the port map indicates no port (NONE/DAF) then the frame is filtered. This is known as destination address filtering (DAF).

If no address entry is found to match the received frame, it is forwarded to all the forwarding ports except for the source port).

Bridge to port 1, port 2, etc.

 Associates an address entry with that specific bridge port. Yes maps the address to the specified port so that port is included in that address entry's port map. No skips address mapping for that port.

continue to another input port?

Lets you select the next input port to be configured.

Source address filtering applies

 Allows port-specific address filtering. Yes discards frames received with source addresses matching address entries in the filtering database with source address filtering enabled. This lets a network manager isolate an end station by not allowing traffic to be bridged.

The following sections present examples of how to use add address to manage address entries.

Enabling destination address filtering for entry

Example: add address 000000334455

Filter exclusively, no matter what input port?(Yes or No): y
Source Address Filtering Applies? (Yes or No): y
After adding the address, verify its status by entering list range. The example below shows that no port map exists for that entry (in bold) and that Destination Address Filtering (DAF) is on.

Bridge Config>list range
Start-Index [1]? 
Stop-index [3]? 
ADDRESS                 ENTRY TYPE      PORT MAP
=======                 ==========      ========
01-80-C2-00-00-00       REGISTERED      Input Port:  ALL PORTS
                                        Output ports:  
                                        

00-00-00-22-33-44       PERMANENT       Input Port:  3
                                        Output ports: 1, 2
                                        Input Port:  4
                                        Output ports:  1, 2
                                        
                                        
00-00-00-33-44-55       PERMANENT       NONE/DAF
Creating separate output port maps for an address entry that has more than one input port

Example: add address 000000123456

Filter exclusively, no matter what input port?(Yes or No): n
Single output port map for all input Ports?(Yes or No): n
Input Port Number [1]? 1
All Ports?(Yes or No): n
Port[1] - Yes or No : y
Port[2] - Yes or No: y
Port[3] - Yes or No: n
Port[4] - Yes or No: n
continue? (Yes or No) y
Input Port Number [2]? 2
All Ports?(Yes or No): n
Port[1] - Yes or No: n
Port[2] - Yes or No: n
Port[3] - Yes or No: y
Port[4] - Yes or No: y
continue? (Yes or No): n
Source Address Filtering Applies? (Yes or No): n
After adding the address entry, verify its status by entering list range. The example below shows an entry (in bold) that has ports 1 and 2 as input ports and has separate port maps for both input ports. Source Address Filtering (SAF) is also enabled.

Bridge Config> list range
Start-Index [1]? 
Stop-index [3]? 
ADDRESS                 ENTRY TYPE      PORT MAP
=======                 ==========      ========
01-80-C2-00-00-00       REGISTERED      Input Port:  ALL PORTS
                                        Output ports:  
                                        
01-80-C2-00-00-01       RESERVED        NONE/DAF 

                                        
00-00-00-12-34-56       PERM/SAF        Input Port:  1
                                        Output ports: 1, 2
                                        Input Port:  2
                                        Output ports: 3, 4
Creating a single output port map for all incoming ports associated with an address entry

Example: add address 000000556677

Filter exclusively, no matter what input port?(Yes or No): n
Single output port map for all input Ports?(Yes or No): y
All Ports?(Yes or No): n
Port[1] - Yes or No: y
Port[2] - Yes or No: y
Port[3] - Yes or No: n
Port[4] - Yes or No: y
Source Address Filtering Applies? (Yes or No): y
After adding the address entry, verify its status by entering list range. The example below shows an entry (in bold) that has a single port map for all incoming ports. Source Address Filtering (SAF) is also enabled.

Bridge Config> list range
Start-Index [1]? 
Stop-index [3]? 
ADDRESS                 ENTRY TYPE      PORT MAP
=======                 ==========      ========
01-80-C2-00-00-00       REGISTERED      Input Port:  ALL PORTS
                                        Output ports:  
                                        
01-80-C2-00-00-01       RESERVED        NONE/DAF  

00-00-00-55-66-77       PERM/SAF        Input Port:  ALL PORTS
                                        Output ports:  1, 2, 4

mapping dlh-type type-field ga-address fa-address

 Adds a specific functional address to group address mapping for a protocol identifier. Converts address mapping only on destination addresses crossing Token Ring to Ethernet/FDDI or vice versa.

Note: For every Ethertype mapped value, add the corresponding SNAP-type value. This is necessary for bidirectional mapping.
dlh-type

 (Data-link-header type); Options are Destination Service Access Point (DSAP), Ethertype, or Subnetwork Access Protocol (SNAP).

type-field

 Protocol type field.

Enter the DSAP protocol type in a range of 1 to FE (hexadecimal).

 Enter Ethernet (Ether) protocol type in a range of 5DD to FFFF (hexadecimal).

Enter SNAP protocol type in 10-digit hexadecimal format.

ga-address

 6-byte (12-digit hexadecimal) group/multicast address.

fa-address

 Enter functional address in non-canonical format. Functional addresses are locally administered group addresses, most commonly used in Token Ring networks.

 The most commonly used values for DECnet group address-to-functional address mapping are the following:
Ethertype Group Address Functional Address
6002

 ab-00-00-02-00-00

C0:00:20:00:00:00

6003

 ab-00-00-03-00-00

 C0:00:10:00:00:00

6003

 ab-00-00-00-04-00

 C0:00:08:00:00:00

SNAP Group Address Functional Address
00-00-00-6002

 ab-00-00-02-00-00

C0:00:20:00:00:00

00-00-00-6003

 ab-00-00-03-00-00

 C0:00:10:00:00:00

00-00-00-6003

 ab-00-00-00-04-00

 C0:00:08:00:00:00

Example: add mapping dsap

Protocol Type in hex (1 - FE) [1]? 
Group-Address (in 12-digit hex) [ ]?
Functional address (in non-canonical format) [ ]?
Example: add mapping ether

Protocol Type in hex (5DD - FFFF) [0800]? 
Group-Address (in 12-digit hex) []?
Functional address (in non-canonical format) [ ]?
Example: add mapping snap

Address (in 10-digit hex) [0000000800]? 
Group-Address (in 12-digit hex) []?
Functional address (in non-canonical format) [ ]?

port interface# port#

Adds a LAN/WAN port to the bridging configuration. Associates a port number with the interface number and enables that port's participation in transparent bridging.

Example: add port

Interface Number [0]? 0
Port Number [5]? 4
If the interface is a Frame Relay interface, you are prompted to assign a circuit name.

If you are adding a port on a PPP or Frame Relay interface, then Proteon recommends that you enable BRS on that interface.

Example: add port

Interface Number [0]? 0
Port Number [5]? 4
assign circuit name []? Baltimore

prot-filter snap or ether or dsap

Configures the bridge to filter packets based on their protocol type. It also discards matching ARP packets. You can apply filters to all ports or only selected ports.

The following protocol filters are available:
SNAP packets

 Subnetwork Access Protocol with protocol type entered in 10-digit hexadecimal format.

Ether packets

 Ethernet type with the protocol type entered in a range of 5DD to FFFF (hexadecimal).

DSAP packets

 DSAP protocol with the protocol type entered in a range of 1 to FE (hexadecimal).

You cannot add the routing protocols enabled in the router (the ones displayed by the configuration command at the + prompt) for filtering. Common protocol filters and their values follow.

DSAP Types
Protocol SAP (hexadecimal value)
Banyan SAP

 BC (used only for 802.5)

Novell IPX SAP

 E0 (used only for 802.5)

NetBIOS SAP

 F0

ISO Connectionless Internet

 FE

SNAP Protocol Identifiers
Protocol SNAP OUI/IP (10-digit)
AppleTalk Phase 2

 08-00-07-80-9B

Apple ARP Phase 2

 00-00-00-80-F3

Proprietary
AppleTalk Phase 1 for FDDI

 00-00-93-00-02

Proprietary
AppleTalk ARP Phase 1 for FDDI

 00-00-93-00-03

Ethernet Types
Protocol Ethernet type (hex value)
IP

 0800

ARP

 0806

CHAOS

 0804

DECnet MOP Dump/Load

 6000

DECnet MOP Remote Console

 6002

DECnet

 6003

DEC LAT

 6004

DEC LAVC

 6007

XNS

 0600

Maintenance Packet Type

 7030

Apollo Domain

 8019 (Ethernet)

Novell NetWare IPX

 8137 (Ethernet)

AppleTalk Phase 1

 809B

Apple ARP Phase 1

 80F3

Loopback assistance

 9000

Example: add protocol

Protocol Type in hex (1 - FE) [1]? 
   Filter packets arriving on all ports?(Yes or [No]): 
   Filter packets arriving on  port 1 - Yes or [No]: 
   Filter packets arriving on  port 2 - Yes or [No]: 
   Filter packets arriving on  port 3 - Yes or [No]:

tunnel port#

Creates an IP tunnel to a bridge port. This tunnel provides a passage for a bridged frame through an IP internetwork. You must enable IP to use the tunnel. This tunnel is counted as only one hop between the bridges no matter how complex the path through the IP internet.

You can add only one tunnel. You must enter a port# that is not used for any other LAN/WAN interface. Internally, the router assigns the interface number 255 to mark that interface as virtual.

Transparent bridging is enabled on this port by default. You can enable source routing using the enable source-routing command.

Example: add tunnel

Port Number   [1] ? 3

Add [M]

At the Bridge> prompt, adds the following information to your bridging configuration. These additions are not saved when you restart the router.

Syntax: add

destination-address-filter
static-entry

destination-address-filter mac_address

Adds a destination address filter to the router's permanent database.

Example: add destination-address-filter

Destination MAC address [00-00-00-00-00-00]?

static-entry mac_address input_port [output_ports]

Adds static address entries to the router's permanent database. The output ports are optional.

To create a static entry with multiple port maps (one per input port), enter the command several times.

Example: add static-entry

MAC address [00-00-00-00-00-00]?00-11-22-33-44-ee
Input port, 0 for all [0]? 2 
Output port, 0 for none [0]? 
Output port, 0 to end [0]? 3

BAN [C] [M]

Displays the BAN config> or BAN> prompt. You can access these prompts by entering ban at either the Bridge Config> or Bridge> prompt as shown below. For further details about using BAN, see Chapter 4 in the SNA Internetworking Guide.

Syntax: ban

Example: Bridge Config>ban

BAN (Boundary Access Node) configuration
BAN config>
Example: Bridge>ban

BAN (Boundary Access Node) configuration
BAN>

Cache [M]

Displays the contents of a selected bridging port routing cache. If the port does not have a cache, you see the message Port X does not have a cache.

Syntax: cache port#

Example: cache

Port number [1]? 3
MAC Address    MC*   Entry Type       Age  Port(s)

00-00-93-00-C0-D0   PERMANENT          0  3 (FDDI/0)
00-00-00-11-22-33   STATIC             0  3 (FDDI/0)
MAC Address

 6-byte MAC address of the entry

Entry Type

 Displays one of the following address entry types:

Reserved Reserved by the IEEE802.1D Standard. Registered Unicast addresses belonging to proprietary communications hardware attached to the box or multicast addresses enabled by protocol forwarders. Permanent User configured entries. Static Monitoring entries. Dynamic Learned by the bridge dynamically. Do not survive power on/off or system resets and have an age associated with the entry. Free Locations in database that are free to be filled by address entries. Unknown Unknown to the bridge. May be bugs and/or illegal addresses.

Age

 Age in seconds of each dynamic entry. The age decrements at each resolution interval.

Port(s)

 The port number associated with the entry. Displays the interface name (always that of the interface having the cache).

Change [C]

Changes source routing bridge and segment numbers in the bridging configuration.

Syntax: change

bridge
segment

bridge new-bridge#

Changes segment numbers in the bridging configuration.

Example: change bridge 3

segment old-segment# new-segment#

Changes bridge numbers in the bridging configuration.

Example: change segment 2 3

Delete [C] [M]

Removes the information specified below.

Delete [C]

Use the delete command to delete information.

Syntax: delete

address
mapping
port
prot-filter

address addr-value

Deletes MAC address entry from the permanent database.

Enter the addr-value in 12-digit hexadecimal format. You cannot delete reserved multicast addresses. If you attempt to delete an address entry that does not exist, you receive a Record matching that address not found message.

Example: delete address

mapping dlh-type type-field ga-address

Deletes specific address mapping for a given protocol.
dlh-type

 (Data-link-header type); Options are Destination Service Access Point (DSAP), Ethertype, or SNAP.

type-field

 Protocol type field.

Enter DSAP protocol type in a range of 1 to FE (hexadecimal).

 Enter Ethernet (Ether) protocol type in a range of 5DD to FFFF (hexadecimal).

Enter Subnetwork Access Protocol (SNAP) protocol type in 10-digit hexadecimal format.

ga-address

 6-byte (12-digit hexadecimal) group/multicast address.

Example: delete mapping DSAP FE group address

port port#

Removes a port from a bridging configuration. Since enable bridge by default configures all LAN devices to participate in bridging, this command allows you to specify which devices should or should not participate in bridging. The port number normally is one greater than the interface number. If port # is an IP tunnel port#, removes an IP tunnel from a bridging configuration.

Example: delete port 2

prot-filter snap or ether or dsap

Deletes previously specified protocol identifiers used in filtering. You can delete filters for all ports or selected ports. These filters include the following:
SNAP Packets

 Subnetwork Access Protocol with protocol type entered in 10-digit hexadecimal format.

Ethernet Packets

 Ethernet type with the protocol type entered in a range of 5DD to FFFF (hexadecimal).

DSAP Packets

 Destination Service Access Point protocol with the protocol type entered in a range of 1 to FE (hexadecimal).

Example: delete prot-filter snap

Address (in 10-digit hex) [0000000800]?
   Delete filter on all ports?(Yes or No): 
   Delete filter on  port 1 - Yes or No: 
   Delete filter on  port 2 - Yes or No: 
   Delete filter on  port 3 - Yes or No:

Delete [M]

Deletes station (including MAC) address entries from the permanent database.

Syntax: delete

mac-address

mac-address address

 Deletes MAC address entries.

Example: delete 

MAC address [00-00-00-00-00-00]?00-00-93-10-04-15

Disable [C]

Disables the following bridge functions:

For the tunnel feature, disable disables a tunnel between end stations across an IP internetwork.

Syntax: disable

bridge
dls
duplicate
ethertype-ibmrt-pc
fa-ga-mapping
ibm8209_spanning_tree
port
proteon-fddi-encapsulation
spanning-tree-explorer
source-routing
sr-tb-conversion
stp
transparent
tree port
ub-encapsulation

bridge

Disables bridging functionality entirely. Does not remove previously configured bridging values.

Example: disable bridge

dls (Data Link Switching)

Disables DLSw over the bridge. (The router running DLSw appears as a bridge to the end stations.)

Example: disable dls

duplicate frame-type port#

Disables the creation of duplicate frames in mixed bridging environments. SR-TB on an 802.5 interface (with source-routing and transparent bridging enabled), may create inconsistencies when bridging frames to an unknown or multicast destination. The bridge does not know whether the destination is behind a source-routing (only) or transparent bridge.

To remedy this, the bridge sends out duplicates of these frames (by default). One frame has source-routing fields (a spanning tree explorer RIF) and the other is formatted for transparent bridging (no RIF). The disable duplicate command lets you eliminate this duplication by allowing you to disable the creation of one of these types of frames. The disable duplicate command does not allow you to disable both types of frames simultaneously.

Entering STE tells the bridge to refrain from sending spanning tree explorer frames created for the source-routing environment. Entering TSF tells the bridge to refrain from sending out transparent spanning frames for the transparent bridging environment. In both cases, the bridge normally sends both types of frames. Disabling transparent bridging also disables the creation of transparent frames.

Example: disable duplicate TSF

ethertype-ibmrt-pc

Disables translation of SNA frames to Ethernet 2 format used by IBM RTs running OS/2/EE. See IBM RT Feature for SNA Traffic for more details.

Example: disable ethertype-ibmrt-pc

fa-ga-mapping

Disables group address to functional address (and vice versa) mapping. Under certain circumstances, you can disable the mapping between group address and functional address globally.

Example: disable fa-ga-mapping

ibm8209_spanning_tree

Prevents bridges from participating in spanning tree protocols with IBM 8209 bridges.

Example: disable ibm8209_spanning_tree

port

Disables bridging on this port.

Example: disable port

Port Number [1]?

proteon-fddi-encapsulation port#

 Disables the Proteon proprietary method of encapsulating FDDI and uses the standard specified in RFC 1490 for FDDI over frame relay and in RFC 1638 for FDDI over PPP.

If you are interoperating with Proteon routers running a software release prior to OpenROUTE 2.0 (Release 16) proteon-fddi-encapsulation needs to be enabled.

Example: disable proteon-fddi-encapsulation

Port Number [1]?

spanning-tree-explorer port#

Prevents a port from allowing propagation of spanning tree explorer frames if source routing is enabled. Use this command only if transparent bridging is not enabled on the port. In that case, it is automatically in conformance with the transparent spanning tree.

Example: disable spanning-tree-explorer 2

source-routing port#

Disables source routing on a given port for an already participating bridge interface.

Example: disable source-routing 2

sr-tb-conversion

Disables conversion of source-routed frame to transparent frame and vice-versa.

Example: disable sr-tb-conversion

stp (Spanning Tree Protocol)

Disables STP participation for the entire bridge.

Example: disable stp

transparent port#

Disables transparent bridging functionality on the given port. This command is useful for cases where an alternative communication method such as source routing is desirable.

This command is useful when you want to enable, for example, SRB and SR-TB. But the command has pitfalls, so use it with care. For instance, using it on an Ethernet interface disables bridging for that interface. This command is used to enable SRB and SR-TB bridge functionality.

Example: disable transparent 2

tree port#

Disables STP participation for the bridge on a per-port basis.

Example: disable tree 1

Note: Disabling STP on a per-port basis can produce network loops because of the existence of parallel bridges.

ub-encapsulation

Disables Ungermann-Bass OUI encapsulation for XNS frames. The bridge continues to forward XNS frames to both Ethernet and Token Ring using SNAP encapsulation with an OUI of all 0s (zeros) as usual.

Example: disable ub-encapsulation

Enable [C]

Enables the following bridging functions:

For the IP tunnel, enables a tunnel between end stations across an IP internetwork.

Syntax: enable

bridge
dls
duplicate
ethertype-ibmrt-pc
fa-ga-mapping
ibm8209_spanning_tree
port
proteon-fddi-encapsultation
spanning-tree-explorer
source-routing
sr-tb-conversion
stp
transparent
tree port
ub-encapsulation

bridge

Enables transparent bridging on all the LAN devices (interfaces) configured in the router. Assigns port numbers to each interface as the previous interface number plus 1. For example, if interface 0 is a LAN device its port number is 1.

Example: enable bridge

dls (Data Link Switching)

Enables DLSw over the bridge. The router running DLSw looks like a bridge to the end stations.

Example: enable DLS

duplicate frame-type port#

Enables the generation of duplicate STE (Spanning Tree Explorer) or TSF (Transparent Spanning Frames) frames. This command is available to offset the disable duplicate command. Duplicate frame generation is enabled by default. The enable duplicate command may be followed by a frame type of TSF or STE to specifically enable one of the frame types, or by the frame type BOTH which yields the same behavior as not specifying a frame type.

Example: enable duplicate

Port Number [1]?

ethertype-ibmrt-pc port#

Enables translation of SNA frames to Ethernet 2 as used by IBM PC RTs running OS/2/EE. (See IBM RT Feature for SNA Traffic for a detailed discussion.) This results in SNA frames being duplicated into both 802.3/802.2 and IBM-RT formats to unknown hosts on an Ethernet.

Example: enable ethertype-ibmrt-pc

Port Number  [4]?

fa-ga-mapping

Enables mapping of group addresses to functional addresses and vice versa. You need this to forward frames between Token Ring and other media (except serial line). In Token Rings, functional addresses are more popular even though they are locally assigned group addresses due to hardware restrictions. Other media commonly use group addresses. Under normal circumstances mapping group addresses to functional address is inevitable.

Mapping is enabled by default if you have added mapping addresses. Enable/disable mapping lets you have a choice when it comes to deleting added map records.

Example: enable fa-ga-mapping

ibm8209_spanning_tree

Allows bridges to participate in spanning tree protocols with IBM 8209 bridges.

Example: enable IBM8209_spanning_tree

port

Enables bridging on this port.

Example: enable port

Port Number [1]?

proteon-fddi-encapsulation port#

 In software releases prior to OpenROUTE 2.0 (Release 16), Proteon used a proprietary method to encapsulate FDDI frames over PPP and frame relay. Starting with OpenROUTE 2.0, as the default, Proteon complies with RFC 1490 for FDDI over frame relay and RFC 1638 for FDDI over PPP.

If you are interoperating with Proteon routers running a previous software release, there are interoperability issues with using two different methods of encapsulation. Enabling proteon-fddi-encapsulation causes the router to use Proteon's proprietary encapsulation, allowing your router to interoperate with Proteon routers running previous releases of software.

Example: enable proteon-fddi-encapsulation

Port Number [1]?

spanning-tree-explorer port#

Lets the port allow propagation of spanning tree explorer frames if source routing is enabled. This command is valid on Token Ring and WAN ports only. This feature is enabled by default when source routing is configured on the port.

Example: enable spanning-tree-explorer 2

source-routing port# segment# bridge#

Enables source routing for a given port. Use this command when you want source routing on part of the bridge. If source routing is the only feature you want, disable transparent bridging on the interface. For the first instance of the command, you must type the bridge number. Subsequently, you need not.
port#

 Valid port participating in the bridge configuration.

segment#

 12-bit number representing the LAN/WAN to which media are attached. All the media on other bridges attached to this LAN/WAN must be configured with the same value. For correct operations of source routing, it is very important that all the bridges attached to this LAN/WAN have the same perspective of the LAN/WAN identification value.

bridge#

 4-bit value unique among all the bridges attached to the same LAN/WAN. This value is required when you enable source routing on the first interface. For later interfaces, this input is optional. It is recommended that bridge# be unique on the segment.

Note: If the configuration is a situation where two segments have already been configured (that is, a 1:N SRB configuration), you are prompted for an additional virtual-segment# parameter. Example: enable source-routing

Port Number [1]? 
Segment Number for the port in hex(1 - FFF) [1]? 
Bridge number in hex (1 - 9, A - F) [1]?

sr-tb-conversion

Allows for compatibility between source routing and transparent bridging domains. When this feature is enabled, the bridge lets source-routed frames be accepted in a transparent domain by stripping off the RIF and converting them into transparent frames.

The bridge also gathers routing information concerning source routing stations from the RIFs of passing source-routing frames. It uses this RIF information to convert transparent frames to source-routed frames. If a RIF is not available for a station, then the bridge sends the frame out as a spanning tree explorer frame in the source-routing domain.

In order for the conversion to operate properly, you must give the transparent bridging domain a segment number. Configure SR-TB bridges connected to this domain with the same segment number.

Example: enable sr-tb-conversion

TB-Domain Segment Number in hex(1 - FFF) [1]? 2
Bridge Virtual Segment Number in hex(1 - FFF) [1]? aa
TB-Domain's MTU [1470]? 1455
TB-Domain's MTU is adjusted to 1350

stp (Spanning Tree Protocol)

Enables STP participation for the entire bridge.

Example: enable STP

transparent port#

Enables transparent bridging functionality on the given port. Under normal circumstances, this command is not necessary.

Example: enable transparent

Port Number [1]?

tree port#

Enables STP participation for the bridge on a per-port basis.

Example: enable tree

Port Number [1]?

ub-encapsulation

Causes XNS Ethernet 2 frames to be translated into Token Rings using the Ungermann-Bass OUI in the SNAP header. Forwards Token Ring frames containing the UB OUI header to Ethernet as type 0x0600 Ethernet 2 frames rather than as 802.3/802.2 frames.

Example: enable ub-encapsulation

Exit [C] [M]

Use the exit command to return to the + or Config> prompt.

Syntax: exit

Example: exit

Flip [M]

Lets you view specific MAC addresses in the canonical and non-canonical format by flipping the address bit order. Flip translates IEEE 802.5 addresses in their typical non-canonical format to the canonical format universally used by the bridge monitoring process and ELS and vice versa.

Syntax: flip MAC address

Example: flip

MAC address [00-00-00-00-00-00]? 00-00-00-33-44-55
IEEE 802 canonical bit order:  00-00-00-33-44-55
IBM Token-Ring native bit order: 00:00:00:CC:22:AA

List [C] [M]

Displays information about the complete bridge configuration or about selected configuration parameters.

Note: When using list in the monitor process, frame relay circuit names display only the first nine characters. To get the complete circuit name, use list port.

List [C]

Displays information about the complete bridge configuration or about selected configuration parameters.

Syntax: list

address
bridge
filtering
lnm status
mapping
permanent
port
prot-filter
protocol
range

address MAC-address

Reads an address entry from the permanent database.

Example: list address 00-00-00-12-34-56

00-00-00-12-34-56    PERMANENT  Input Port:  ALL PORTS
                                  Output ports: 1, 2, 3, 4
Example: list address 000000112233

00-00-00-11-22-33     PERM/SAF    Input Port:  1
                                  Output ports:  1, 2
Address

 Address entry in 12-digit hexadecimal format.

Entry Type

 Permanent The entry is permanent and survives power on/off or system resets. Reserved The entry is reserved by the IEEE802.1d committee for future use. Frames to reserved addresses are discarded. Registered The entry is meant for the bridge itself. SAF Appears after the entry type if you configure source address filtering.
Input Port

 The numbers of input port(s) associated with that address entry.

Output Port

 The numbers of output port(s) associated with that address entry. NONE/DAF indicates that destination address filtering applies because no ports have been selected to be associated with that address entry.

bridge

Lists all general information regarding the bridge.

Example: list bridge

       Source Routing Transparent Bridge Configuration
       ===============================================
Bridge:          Enabled        Bridge Behaviour: ADAPTIVE SRT
                   +--------------------------+
-------------------|SOURCE ROUTING INFORMATION|----------------- 
                   +--------------------------+
Bridge Number:       01                  Segments:    1
Max ARE Hop Cnt:     14                  Max STE Hop cnt: 14
1:N SRB:           Active                Internal Segment:  0x222
LF-bit interpret:  Extended
                   +-------------------+-
-------------------| SR-TB INFORMATION |------------------------
                   +-------------------+
SR-TB Conversion:        Enabled 
TB-Virtual Segment:      0xEEE            MTU of TB-Domain:  1112
                   +-----------------------------------+      
-------------------| SPANNING TREE PROTOCOL INFORMATION |--------
                   +------------------------------------+
Bridge Address:    Default      Bridge Priority:  32768/0x8000
STP Participation: IEEE802.1d and IBM-8209
                   +-------------------------+
-------------------| TRANSLATION INFORMATION |------------------
                   +-------------------------+
FA<=>GA Conversion:     Enabled    DLS for the bridge:     Enabled
                   +------------------+
-------------------| PORT INFORMATION |---------------------------
                   +------------------+
Number of ports added: 3
Port:   1      Interface:     0 Behaviour:STB & SRB     STP: Enabled
Port:   2      Interface:     1 Behaviour:    STB Only  STP: Enabled
Port:   3      Interface:     2 Behaviour:    STB Only  STP: Enabled
Bridge

Indicates whether the bridge is enabled or disabled.

Bridge Behavior

 Method of bridging being used. Values are STB for transparent, SRB for source routing, and SR-TB for source routing-transparent conversion bridging.

Bridge Address

 Bridge address specified by the user (if set).

Bridge Priority

 A high-order 2-octet bridge address found in the bridge identifier-either the MAC address obtained from the lowest number port or the address set by the set bridge command.

Source Routing Bridge Number

 The unique number identifying a bridge. Distinguishes between multiple bridges connecting the same two rings.

Number of Source Routing Segments

 The number of Source Routing bridge segments configured for the Source Routing domain.

SRB: Max ARE/STE Hop cnt

 The maximum hop count for frames transmitting from the bridge for a given interface associated with source routing bridging.

SR-TB Conversion

 Indicates whether source routing/transparent bridge frame conversion is enabled or disabled.

TB-Virtual Segment

 The segment number of the transparent bridging domain.

MTU for TB-Domain

 The maximum frame size (maximum transmission units) the transparent bridge can transmit and receive.

1:N Source Routing

 The current state of 1:N Source Routing ACTIVE or NOT ACTIVE.

Internal Virtual Segment

 Displays the virtual segment number configured for 1:N SRB bridging.

SRB LF-bit interpretation

 Indicates the largest frame (LF) bit encoding interpretation mode if source routing is enabled in this bridge (BASIC or EXTENDED).

FA-GA conversion

 Indicates whether FA-GA conversion is enabled or disabled.

Spanning Tree
Protocol Participation

 The types of spanning tree protocols that the bridge participates in.

Number of ports added

 The number of bridge ports added to the bridging configuration.

Port Number

 A user-defined number assigned to an interface using the add port command.

Interface Number

 Identifies devices connected to a network segment through the bridge. You must add at least two interfaces to participate in bridging. Use 255 for bridging.

Port Behavior

 Indicates method of bridging being used by that port. The values are STB for Transparent, SRB for Source Routing, and SR-TB for Source Routing-Transparent conversion bridging.

filtering datagroup-option

You can display the following general data groups under the list filtering command:

The following examples illustrate each of the list filtering display options.

Example: list filtering all

Ethernet type 0800 is routed on ports 1
IEEE 802.2 destination SAP 42 is routed on ports 1
IEEE 802 SNAP PID 00-00-00-08-00 is routed on ports 2-3
Descriptors used in explaining how packets are communicated include the following:

All of these descriptors also apply to ARP packets with this Ethertype.

Example: list filtering ethertype

Ethernet type (in hexadecimal), 0 for all [0]? 0800
Ethernet type 0800 is routed on ports 1
Example: list filtering sap

SAP (in hexadecimal), 100 for all [100]? 42
IEEE 802.2 destination SAP 42 is routed on ports 1
Example: list filtering snap

SNAP Protocol ID, return for all [00-00-00-00-00]? 
IEEE 802 SNAP PID 00-00-00-08-00 is routed on ports 2-3

mapping add-type type-field

Lists specific address mapping for given protocol.

Example: list mapping DSAP

PROTOCOL TYPE         GROUP ADDRESS          FUNCTIONAL ADDRESS
=============         =============          ==================
01                    11-22-33-44-55-66      22:33:44:55:66:AA
Example: list mapping ether

PROTOCOL TYPE           GROUP ADDRESS         FUNCTIONAL ADDRESS
=============           =============         ==================
FFFF                    00-11-22-33-44-55     AA:BB:CC:DD:EE:FF
add-type

 DSAP, Ether (Ethernet), or SNAP.

type-field

 Protocol type field.

Destination Service Access Point (DSAP) with protocol type in a range of 1 to FE (hexadecimal).

Ethernet (Ether) with protocol type in a range of 5DD to FFFF (hexadecimal).

Subnetwork Access Protocol (SNAP) with protocol type in 10-digit hexadecimal format.

permanent

Displays the number of entries in the bridge's permanent database.

Example: list permanent 

Number of Entries in Permanent Database:  17

port port#

Displays port information related to ports already configured. Port# selects the port you want to list. Specifying no number displays all ports.

Example: list port

Port Id (dec)    : 128: 1, (hex): 80-01
Port State       : Enabled
STP Participation: Enabled
Port Supports    : Transparent Bridging and Source Routing
SRB: Segment Number: 0x111       MTU:  4399     STE: Enabled
Duplicates Frames Allowed:   STE: Yes, TSF: Yes
Assoc Interface  : 0
Path Cost        : 0
IBM RT-PC Ethertype (0x80D5) processing is enabled
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Port Id (dec)    : 128: 2, (hex): 80-02
Port State       : Enabled
STP Participation: Enabled
Port Supports    : Transparent Bridging Only
Assoc Interface  : 1
Path Cost        : 0
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Port Id (dec)    : 128: 3, (hex): 80-03
Port State       : Enabled
STP Participation: Enabled
Port Supports    : Transparent Bridging Only
Assoc Interface  : 2
Path Cost        : 0
Proteon FDDI encapsulation is enabled
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Port ID

 The ID consists of two parts: the port priority and the port number. In the example, 128 is the priority and 1, 2, and 3 is the port number. In hexadecimal format, the low-order byte denotes the port number and the high order byte denotes the priority.

Port State

 Whether or not the port is enabled or disabled.

Port Supports

 Displays bridging method supported by that port (for example, transparent bridging, source routing bridging).

SRB

 Displayed only when SRB is enabled and lists source-routing bridging information. This includes the SRB segment number (in hex), the Maximum Transmission Unit size, and whether the transmission of Spanning Tree Explorer Frames is enabled or disabled.

Duplicate Frames
Allowed

 Displays a breakdown and count of the types of duplicate frames allowed.

Assoc Interface

 Interface number associated with the displayed port, and FR circuit name if applicable.

Path Cost

 Cost associated with the port used for possible root path cost. The range is 1 to 65535.

Note: If IBM RT-PC Ethertype processing or Proteon FDDI encapsulation are enabled, they appear on this display. If they are not enabled, their status does not appear.

prot-filter port#

Reads a current list of the filter protocol types. You can list filters selectively by port or display all ports at once. Port# selects the bridge port that you want to list.

Example: list prot-filter 2 

No DSAP Filter Records Associated
Protocol Class: ETHER
Protocol Type : 0800
Protocol State: FILTERED
==========================
Protocol Class: SNAP
Protocol Type : 000000-0800
Protocol State: FILTERED
==========================
Port Number

 Displayed for each port if you list all ports.

Protocol Class

 Displays protocol class (SNAP, Ether, or DSAP).

Protocol Type

 Protocol ID in hexadecimal format.

Protocol State

 Denotes that protocol is being filtered for selected port.

protocol

Displays bridge information related to the spanning tree protocol.

Example: list protocol

Bridge Identifiers: 32768/000000000036  
Bridge-Max-Age (in seconds): 20
Bridge-Hello-Time (in seconds): 2
Bridge-Forward-Delay (in seconds): 15


Note:  
Each of these bridge-related parameters is also described in detail in previous chapters. 





Bridge Identifiers



8-byte value in ASCII format.  If you do not set the bridge address prior to displaying this information, the low order six bytes displayed as zero indicates the default MAC address of a port.  When a bridge is selected as the root bridge, it transmits the bridge max age and bridge hello time to all the bridges in the network via the Hello BPDUs. 



Bridge-Max-Age



Maximum age (period of time) that should be used to time out spanning-tree-protocol-related information.



Bridge-Hello-Time



Time interval between Hello BPDUs.



Bridge-Forward- Delay



Time interval used before changing to another state (should this bridge become the root).

range start-index stop-index

Reads a range of address entries from the permanent database. To do this, first determine the size of the database by using the list permanent command. From this value you can then determine a start index value for your entry range. The start index is one to the size of the database. You can then choose a stop index to display a limited number of entries. This input is optional. If the stop index is not provided the default is the size of the database.

Address entries contain the following information:

Example: list range 16

ADDRESS             ENTRY TYPE       PORT MAP
=======                                 ========                      =======
01-80-C2-00-00-00    REGISTERED        Input Port: ALL PORTS
                                       Output ports:  
                                        
01-80-C2-00-00-01    RESERVED          NONE/DAF 
01-80-C2-00-00-02    RESERVED          NONE/DAF 
01-80-C2-00-00-03    RESERVED          NONE/DAF 
01-80-C2-00-00-04    RESERVED          NONE/DAF 
01-80-C2-00-00-05    RESERVED          NONE/DAF
Address

6-byte MAC address of the entry.

Entry Type

Specifies one of the following types:

Reserved Reserved by the IEEE802.1d committee

Registered Unicast addresses belonging to proprietary communications hardware attached to the box or multicast addresses enabled by protocol forwarders

Permanent Entries entered in the configuration process that survive power on/off or system resets

Static Entries entered in the monitoring process that do not survive power on/off or system resets and are ageless

Dynamic Entries learned by the bridge dynamically that do not survive power on/off or system resets and have an age associated with them

Free Locations in database free to be filled by address entries
Port Map

 Outgoing port map for all incoming ports.

List [M]

Displays information about the complete bridge configuration or about selected configuration parameters.

Syntax: list

adaptive-bridge
bridge
conversion
database
filtering
lnm status
source-routing
spanning-tree-protocol
transparent
tunnel

adaptive-bridge datagroup-option [sub-option]

Lists all general information regarding the SR-TB bridge which converts between types of bridging. There are a number of general data group options that may be displayed under the list adaptive-bridge. These include the following:

The following examples illustrate each of the list adaptive-bridge display options.

Example: list adaptive-bridge config

Adaptive bridge:               Disabled
Translation database size:     0
Aging time:                    300 seconds
Aging granularity              5 seconds

   Port  Segment  Interface   State     MTU
     1    1        Eth/0      Up        0
     2    3        Eth/1      Up        0
Conversion bridge

 Current state of the SR-TB conversion bridge, either enabled or disabled.

Translation database size

Current size of the SR-TB database, which contains MAC addresses and associated RIFs for the source-routing domain.

Aging time

 Aging timer setting in seconds. All SR-TB RIF database entries that exceed this time limit are discarded.

Aging granularity

 How often entries are scanned to look for expiration according to the aging timer.

Port

 Number of a port associated with conversion bridging.

Segment

 Source-routing segment number assigned to the port associated with conversion bridging.

Interface

 Device connected to a conversion bridge network segment.

State

 Current state of the conversion bridge port.

MTU

 Maximum frame size (from the end of the RIF to the beginning of the FCS) that the conversion-bridge can transmit and receive.

Example: list adaptive-bridge counters

Hash collision count: 28
Adaptive. database overflow  count: 0
Hash Collision Count

 Number of addresses that were stored (hashed) to the same location in the hash table. This number is cumulative and reflects the total number of hash collision incidents that occurred. Increases in this number may indicate a potential table size problem.

Adaptive Database Overflow

 Number of times that an address was overwritten as the conversion database table ran out of table space.

The database option of the list adaptive bridge command lets you select certain portions of the adaptive bridge RIF database to display. This is due to the potential size of the database. The display options include the following:

The following example illustrates each of the list adaptive-bridge database command options.

Note: These are only displayed if adaptive bridging is enabled. Example: list adaptive-bridge database address mac-address
list adaptive-bridge database all
list adaptive-bridge database port segment#
list adaptive-bridge database segment segment#

The following information is displayed for each entry:
Canonical address

 MAC address of the node corresponding to this entry displayed in the IBM non-canonical bit order.

Interface

Name of the network interface that learned this entry.

Port

 Number of the port that learned this address entry.

Seg

 Number of the segment that learned this address.

Age

 Entry age in seconds.

RIF Type

 RIF type (SRF, STE, or ARE).

RIF Direction

 RIF direction (Forward or Reverse).

RIF Length

 RIF length in bytes.

RIF LF

 Largest frame value in the RIF.

RIF

 Routing Information Field learned from this node.

bridge

Lists all general information regarding the bridge.

Example: list bridge

Bridge ID (prio/add):	32768/11-22-33-AA-BB-CC
Bridge state:         	Enabled
UB-Encapsulation:      	Enabled
Bridge type:           	SR-TB
Bridge capability:     	ASRT
Number of ports:       	3
STP Participation:     	IEEE802.1d on TB ports only
**Bridge is enabled for Data Link Switching**                                                      
			  Maximum           
Port Interface  State  MAC Address        Modes MSDU Segment Flags
  1  Eth/0       Up    00-00-93-B8-00-48    T    1514        RE
  2  PPP/0       Down  00-00-00-00-00-00    T       0        RD
  3  SL/0        Down  00-00-00-00-00-00    T       0        RD

Flags:RE= IBMRT PC behaviour Enabled,RD = IBMRT PC behaviour Disabled

SR bridge number:      1
SR virtual segment:    222
Adaptive segment:      EEE
Bridge State

Indicates whether bridging is enabled or disabled.

Bridge Type

 The configured bridge type (NONE, SRB, STB, SRT, ADAPT, A/SRB, A/TB, or ASRT).

Number of Ports

 Number of ports configured for that bridge.

Port

 Number assigned to an interface using the add port command.

Interface

 Devices connected to a network segment through the bridge.

State

The current state of the port (UP or DOWN).

MAC address

 The MAC address associated with that port in canonical bit order.

Modes

 The bridging mode for that port. T indicates transparent bridging. SR indicates source routing. A indicates adaptive bridging.

MSDU

 The maximum frame (data unit) size (including the MAC header but not the FCS field) the source-routing bridge can transmit and receive on this interface.

Segment

 The source routing bridge segment number assigned to that port (if any).

LNM

 Displays whether the LNM feature is enabled on that port.

SR bridge number

 The user-assigned source routing bridge number.

SR virtual segment

 The source-routing bridge virtual segment number, if any.

Adaptive segment

 The number of the segment used in the source-routing domain to route to the transparent domain (via conversion).

conversion datagroup-option

Displays general information about the bridge's rules for converting frame formats based on the frame type. You can display the following general data groups under the list conversion command:

The following examples break down each of the list conversion display options.

Example: list conversion all
list conversion ethertype
list conversion SAP
list conversion SNAP

database datagroup-option

Lists the contents of transparent filtering databases. You can choose the following data groups to display under the list database command

The following examples break down the list database command options. The first example also shows the related output.

Example: list database all

MAC Address    MC*  Entry Type       Age  Port(s)

00-00-00-00-AA-AA   Dynamic          295  4 (Eth/0)
00-00-00-12-34-56   Perm/Source filter    2 (TKR/0)  ->  3-4
                                          1-2
00-00-00-22-33-44   Permanent             1-2
                                          1-2
00-00-00-33-44-55   Perm Dest filter      All
00-00-00-55-66-77   Perm/Source filter    1-2,4

00-00-93-00-C0-D0   Registered            3 (FDDI/0)
00-00-93-10-04-15   Registered            1 (Eth/0)
00-00-93-10-E4-F9   Dynamic          300  1 (Eth/0)
00-00-93-90-04-A6   Dynamic          300  1 (Eth/0)
00-00-A7-10-68-28   Dynamic          270  1 (Eth/0)
01-80-C2-00-00-00*  Registered            1,3
01-80-C2-00-00-01*  Reserved              All
01-80-C2-00-00-02*  Reserved              All
01-80-C2-00-00-03*  Reserved              All
01-80-C2-00-00-0D*  Reserved              All
01-80-C2-00-00-0E*  Reserved              All
01-80-C2-00-00-0F*  Reserved              All
03-00-00-00-80-00*  Reserved              All
08-00-17-00-35-F9   Dynamic          300  1 (Eth/0)
08-00-17-00-4D-DA   Dynamic          300  1 (Eth/0)


Note:  
The fields described below are displayed for all of the list database command options.  





MAC Address



Address in 12-digit hex format (canonical bit order).



MC*



An asterisk following an address entry indicates that the entry has been flagged as a multicast address.



Entry Type



Specifies one of the following types: 

Reserved 	Reserved by the IEEE802.1D standard.

Registered 	Consist of unicast addresses belonging to interfaces participating in the bridge or multicast addresses enabled by protocol forwarders. 

Permanent 	Entered in the configuration process and survives power on/off or system resets.

Static 	Entered in the monitoring process, do not survive power on/off or system resets, and are ageless.

Dynamic	Learned by the bridge dynamically and do not survive power on/off or system resets and have an age associated with the entry.

Free 	This type is not used and should not be seen except in occasional race conditions between the monitor process and the bridge.

Unknown 	Unknown entry type.  May indicate a software bug.  Report the hex entry type to Customer Service.  




Age



The age (in seconds) of each dynamic entry.  Age is decremented at each resolution interval.



Port(s)



The outgoing port number(s) for that entry.  Device type is also listed for single port entries.  If dynamic entry on IP tunnel, the port is 5 for IP tunnel.
Example: list database dynamic
list database local
list database permanent
list database port port#
list database static
list database range 

First MAC address [00-00-00-00-00-00]? 00-00-93-00-C0-D0
Last MAC address [FF-FF-FF-FF-FF-FF]? 01-80-C2-00-00-00

MAC Address    MC*  Entry Type       Age  Port(s)
Example: 

Aging Time (in seconds):   300
Resolution (in seconds):     5
Filtering Database Size

 The maximum number of entries that the filtering database can hold.

Aging Time

 Amount of time (in seconds) for aging out (discarding) dynamic entries in the filtering database.

Resolution

 How often dynamic entries are scanned to look for expiration according to the aging timer.

filtering datagroup-option

You can display the following general data groups under the list filtering command:

The following examples break down each of the list filtering display options.

Example: list filtering all

Ethernet type 0800 is routed on ports 1
IEEE 802.2 destination SAP 42 is routed on ports 1
IEEE 802 SNAP PID 00-00-00-08-00 is routed on ports 2-3
Descriptors used to explain how packets are communicated include the following:

All of the descriptors just explained also apply to ARP packets with this Ethertype.

Example: list filtering ethertype

Ethernet type (in hexadecimal), 0 for all [0]? 0800
Ethernet type 0800 is routed on ports 1

lnm status

 Displays general information about the configuration of the LNM feature enabled on the bridge.

Example: list lnm status

Port Number [1]? 1
Port 1
LNM Agents Enabled: RPS CRS REM
Reporting Link          State          LNM Station Address
      0                 AVAILABLE      
      1                 AVAILABLE      
      2                 AVAILABLE      
      3                 AVAILABLE      
MAC Addresses to use when configuring LNM Manager:
      00:00:C9:08:35:47
      40:00:D9:08:35:47
Port Number

 Number of the port running the LNM feature.

LNM Agents Enabled

LNM agents enabled on that port.

Reporting Link

 Number of a specific reporting link.

State

 State of the reporting link (available, active, or connecting).

LNM Station Address

Station address associated with that link.

MAC addresses...

 MAC addresses required by the LNM Management Station for correct configuration to the LNM agents in the router.

source-routing configuration or counters

Displays source-routing bridge configuration information. There are general data group options that you can display under the list source-routing command:

The following examples illustrate each of the list source-routing display options.

Example: list source-routing configuration

Bridge number:               1
Bridge state:                Enabled
Maximum STE hop count        14
Maximum ARE hop count        14
Virtual segment:             003

Port  Segment  Interface   State     MTU    STE Forwarding LNM
 2    001      TKR/0       Enabled   4399   Yes            ENA
 3    002      TKR/1       Enabled   4399   Yes
 -    003      Adaptive    Enabled   1470   Yes
Bridge number

 Bridge number (in hexadecimal) assigned to this bridge.

Bridge state

Indicates whether bridging is enabled or disabled.

Maximum STE hop count

 Maximum hop count for Spanning Tree Explorer frames transmitting from the bridge for a given interface associated with source routing bridging.

Maximum ARE hop count

 Maximum hop count for All Route Explorer frames transmitting from the bridge for a given interface associated with source routing bridging.

Virtual segment

 Virtual segment number assigned for 1:N bridging.

Port

 Numbers of ports associated with source routing bridging

Segment

 Assigned segment numbers for networks associated with source routing bridging.

Interface

 Associated interface names. Lists Adaptive for interfaces participating in the SR-TB.

State

 Current port state (Enabled or Disabled).

MTU

 MTU size set for that port.

STE Forwarding

 Indicates whether Spanning Tree Explorers received on this port are forwarded (Yes) and whether STEs from other ports go out this port.

LNM

 Indicates whether LAN Network Manager (LNM) agents are enabled (ENA) or disabled (DIS) on that specific port.

The counters option has further subgroups of information that you can display using the list source-routing command:

The following examples illustrate each of the list source-routing display options.

Example: list source-routing counters all-ports

Counters for port 2, segment 001, interface TKR/0:
SRF frames received:          0    sent:          0
STE frames received:          0    sent:          0
ARE frames received:        648    sent:          0
SR frames sent as TB:                             0
TB frames sent as SR:                          2057
Dropped, input queue overflow:                    0
Dropped, source address filtering:                0
Dropped, invalid RIF length:                      0
Dropped, duplicate segment:                    2594
Dropped, segment mismatch:                        0
Dropped, Duplicate LAN ID or tree error:          0
Dropped, STE hop count exceeded:                  0

Counters for port 3, segment 002, interface TKR/1:
SRF frames received:          0    sent:          0
STE frames received:          0    sent:          0
ARE frames received:        825    sent:          0
SR frames sent as TB:                             0
TB frames sent as SR:                          2041
Dropped, input queue overflow:                    0
Dropped, source address filtering:                0
Dropped, invalid RI length:                       0
Dropped, duplicate segment:                   3300
Dropped, segment mismatch:                        0
Dropped, Duplicate LAN ID or tree error:          0
Dropped, STE hop count exceeded:                  0
Port

 Numbers of ports associated with source routing bridging

Segment

 Source-routing segment numbers in hex.

Interface

 Name of the network interface.

SRF Frames Received/Sent

 Specifically Routed Frames received or sent on this bridge.

STE Frames Received/Sent

 Spanning Tree Explorer Frames received or sent on this bridge.

ARE Frames Received/Sent

 All Routes Explorer Frames received or sent on this bridge.

SR Frames Sent as TB

 Source routing frames received on this interface that were sent as Transparent Bridge frames.

TB Frames Sent as SR

 Transparent bridge frames received on this interface that were sent as source routing frames.

Dropped, input queue

 Frames dropped because the input queue overflowed.

Dropped, source address filtering

 Frames dropped because this source address matched a source address filter in the filtering database.

Dropped, destination address filtering

 Frames dropped because this destination address matched a destination address filter in the filtering database.

Dropped, protocol filtering

 Frames dropped because their protocol identifier is being administratively filtered.

Dropped, duplicate RIF length

Frames dropped because the RIF length was less than 2 or over 30.

Dropped, duplicate segment

 Frames dropped because of a duplicate segment in the RIF. This is normal for ARE frames.

Dropped, segment mismatch

 Frames dropped because the outgoing segment number does not match any in this bridge.

Example: list source-routing counters port port#

Counters for port 3, segment 002, interface TKR/1:
SRF frames received:          0    sent:          0
STE frames received:          0    sent:          0
ARE frames received:       1140    sent:          0
SR frames sent as TB:                             0
TB frames sent as SR:                          2931
Dropped, input queue overflow:                    0
Dropped, source address filtering:                0
Dropped, invalid RIF length:                       0
Dropped, duplicate segment:                     4560
Dropped, segment mismatch:                         0
Dropped, Duplicate LAN ID or tree error:           0
Dropped, STE hop count exceeded:                   0
Dropped, ARE hop count exceeded:                   0
Dropped, no buffer available to copy:              0
Dropped, MTU exceeded:                             0
Example: list source-routing counters segment 2

Counters for port 3, segment 002, interface TKR/1:
SRF frames received:          0    sent:          0
STE frames received:          0    sent:          0
ARE frames received:       1249    sent:          0
SR frames sent as TB:                             0
TB frames sent as SR:                          3200
Dropped, input queue overflow:                    0
Dropped, source address filtering:                0
Dropped, dest address filtering:                  0
Dropped, protocol filtering:                      0
Dropped, invalid RI length:                       0
Dropped, duplicate segment:                    4996
Dropped, segment mismatch:                        0
Dropped, Duplicate LAN ID or tree error:          0

spanning-tree protocol

Displays spanning tree protocol information. The transparent bridge uses the spanning tree protocol to form a loop-free topology. You can display the following general data group options under the list spanning-tree-protocol command:

The following examples illustrate each of the list spanning-tree-protocol display options.

Example: list spanning-tree-protocol configuration

Bridge ID (prio/add):  32768/00-00-93-00-84-EA
Bridge state:          Enabled
Maximum age:           20 seconds
Hello time:            2 seconds
Forward delay:         15 seconds
Hold time:             1 seconds

Port  Interface  Priority  Cost   State
   1  FDDI/0    128    10      Enabled
   4  Eth/0     128    100     Enabled
 128  Tunnel    128    65535   Enabled
Example: list spanning-tree-protocol counters

Time since topology change (seconds)          0
Topology changes:                             3
BPDUs received:                               0
BPDUs sent:                                3866

Port  Interface BPDUs received BDPU input overflow Forward transitions
   1  FDDI/0             0               0                   1
   4  Eth/0              0               0                   1
 128  Tunnel             0               0                   1
Example: list spanning-tree-protocol state

Designated root (prio/add):    32768/00-00-93-00-84-EA
Root cost:                     0
Root port:                     Self
Current (root) maximum age:    20 seconds
Current (root) hello time:     2 seconds
Current (root) Forward delay:  15 seconds
Topology change detected:      FALSE
Topology change:               FALSE

Port  Interface   State
   1  FDDI/0      Forwarding
   4  Eth/0       Forwarding
 128  Tunnel      Forwarding
Example: list spanning-tree-protocol tree

Port                        Designated   Desig.          
Designated
Des.
No.  Interface       Root          Cost       Bridge            Port
  1  FDDI/0  32768/00-00-93-00-84-EA 0  32768/00-00-93-00-84-EA 80-01
  4  Eth/0   32768/00-00-93-00-84-EA 0  32768/00-00-93-00-84-EA 80-04
128  Tunnel  32768/00-00-93-00-84-EA 0  32768/00-00-93-00-84-EA 80-80

transparent

Displays transparent bridge configuration information. You can display the following general data group options under the list transparent command:

The following examples illustrate each of the list transparent display options.

Example: list transparent configuration

Filtering database size:    5141
Aging time:                 300 seconds
Aging granularity           5 seconds

Port  Interface   State     MTU
   1  FDDI/0						Enabled			0
   4  Eth/0						Enabled			0
 128  Tunnel						Enabled			0
Example: list transparent counters all-ports

Counters for port 4, interface Eth/0:
Total frames received by interface:           25885
Frames submitted to bridging:                 13732
Frames submitted to routing:                   6101
Dropped, source address filtering:                0
Dropped, dest address filtering:              12677
Dropped, protocol filtering:                      0
Counters for port 128, interface Tunnel:
Total frames received by interface:               0
Frames submitted to bridging:                     0
Frames submitted to routing:                      0
Dropped, source address filtering:                0
Dropped, dest address filtering:                  0
Dropped, protocol filtering:                      0
Dropped, no buffer available to copy:             0
Dropped, input queue overflow:                    0
Dropped, source port blocked:                     0
Frames sent by bridging:                       5327
Dropped, dest port blocked:                       0
Dropped, transmit error:                          0
Dropped, too big to send on port:                 0
Example: list transparent counters port 4

Counters for port 4, interface Eth/0:
Total frames received by interface:           25885
Frames submitted to bridging:                 13732
Frames submitted to routing:                   6101
Dropped, source address filtering:                0
Dropped, dest address filtering:              12677
Dropped, protocol filtering:                      0
Dropped, no buffer available to copy:          6073
Dropped, input queue overflow:                  122
Dropped, source port blocked:                    31
Frames sent by bridging:                        388
Dropped, dest port blocked:                       0
Dropped, transmit error:                          0
Dropped, too big to send on port:                 0
Example: list transparent state

Filtering database size:                       5141
Number of static entries:                         0
Number of dynamic entries:                       10
Hash collision count:                             1
Filtering database overflow count:                0

tunnel bridges or config

 Displays tunnel configuration information. You can display the following general data group options under the list tunnel command:

The following examples illustrate each of the list tunnel display options.

Example: list tunnel bridges
list tunnel config

LNM [C] [M]

Displays the LNM prompt. Enter lnm at the Bridge Config> prompt to display the LNM configuration prompt. Enter lnm at the Bridge> prompt to display the LNM monitoring prompt. See Configuring and Monitoring LAN Network Manager (LNM) for an explanation of the LNM commands.

Syntax: lnm

Example: lnm

NetBIOS [C] [M]

Displays the NetBIOS configuration or monitoring prompt. Enter netbios at the Bridge Config> prompt to display the NetBIOS configuration prompt. Enter netbios at the Bridge> prompt to display the NetBIOS monitoring prompt.

See NetBIOS Commands for an explanation the NetBIOS commands.

Syntax: netbios

Example: netbios

NetBIOS Support User Configuration

NetBIOS config>


Note:  
If you have not purchased the NetBIOS feature, you receive the following message if you use this command:
NetBIOS Filtering is not available in this load.

Set [C]

Use the set command to set the following parameters:

Syntax: set

age
bridge
filtering
lf-bit-interpretation
maximum-packet-size
protocol bridge
protocol port
route-descriptor-limit

age seconds resolution

 Sets the time for aging out dynamic entries in the filtering database when the port with the entry is in the forwarding state. This age is also used for aging RIF entries in the RIF table in the case of an SR-TB bridge personality.

The default for the aging timer is 300 seconds with a range of 1 to 1,000,000 seconds. The default for the resolution parameter is 5, with a range of 1 to 60 seconds.

Example: set age 

seconds [300]  ?  300   
resolution [5] ?   5

bridge bridge-address

 Sets the bridge address. In cases where a serial line interface (or tunnel) is the lowest numbered port, you must use this command so that the bridge has a unique address when it is restarted. This is necessary because serial lines do not have their own MAC address.

Note: Each bridge in the network must have a unique address for the spanning tree protocol to operate properly. This is the low order 6-octet bridge address in the bridge identifier. By default, the bridge-address is set to the Media Access Control (MAC) address of the lowest numbered port at initialization. You can use this command to override the default address and enter your own unique address.

Do not use dashes or colons to separate each octet. If you enter the address in the wrong format you receive the message Illegal Address. If you enter no address at the prompt, you receive the message Zero length address supplied and the bridge maintains its previous value. To return the bridge address to the default, enter an address of all zeroes.

Example: set bridge

Bridge Address (in 12-digit hex)[]?

filtering database-size

 Sets the number of entries that can be held in the bridge filtering database. The default is 1024 times the number of bridge ports. For more information, see the list filtering command in this chapter.

Example: set filtering

database-size [2048]?

lf-bit-interpretation encode-mode

Sets the Largest Frame (LF) bit encoding interpretation if source routing is enabled in this bridge.

Example: set lf-bit-interpretation basic
Encode-mode

Entered as either basic or extended. In basic mode only three bits of the routing control field are used. This is the common practice in source routing bridges that exist today. In extended mode, six bits of the routing control field are used to represent the maximum data unit that the bridge supports.

The default is extended. Extended and basic nodes are compatible.

maximum-packet-size port# msdu-size

Sets the largest MAC Service Data Unit (MSDU) size for the port, if source routing is enabled on this port. Obviously, MSDU setting has no implication on traditionally transparent media. An MSDU value greater than the packet size configured in the router is treated as an error.

The default is the size configured as the packet size for that interface.

Example: set maximum-packet-size

Port Number [1]? 2
MSDU size [4399]? 2048
MSDU is adjusted to 1979

protocol bridge or port

Modifies the spanning tree protocol bridge or port parameters for a new configuration or to tune the configuration parameters to suit a specific topology.

Enter protocol bridge to modify bridge parameters. The bridge related parameters that can be modified with this command are described below.

When setting these values, make sure that the following relationships exist between the parameters or the input is rejected:

2 X (Bridge Forward Delay - 1 second) > Bridge Maximum Age

Bridge Maximum Age > 2 X (Bridge Hello Time + 1 second)

Example: set protocol bridge

Bridge Max-Age [20]  20   
Bridge Hello Time [2]   2 
Bridge Forward Delay [15] 15 
Bridge Priority [32768]    1
Bridge Maximum Age

 Maximum age (period of time) used to time out spanning tree protocol related information.

Bridge Hello Timer

 Time interval between Hello BPDUs.

Bridge Forward Delay

 Time interval before changing to another state (should this bridge become the root).

Bridge Priority

 A high-order 2-octet bridge address found in the Bridge Identifier - either the MAC address obtained from the lowest number port or the address set by the set bridge command.

Enter protocol port to modify the spanning tree protocol port parameters.

Example: set protocol port

Port Number [1] ? 1
Port-Path-Cost [1] ?   1
Port Priority [128] ?   1
Port Number

 Bridge port number; selects the port for which the path cost and port priority will be changed.

Path Cost

 Cost associated with the port which is used for possible root path cost. The range is 1 to 65535.

Port Priority

 Identifies port priority for the specified port. The range is 0 to 255.

route-descriptor-limit limit-type RD-limit-value

Allows you to associate a maximum Route Descriptor (RD) length for All Route Explorer (ARE) or Spanning Tree Explorer (STE) frames forwarded by the bridge if source routing is enabled.

Example: set route-descriptor-limit ARE 14
Limit-type

 Entered either as ARE or STE depending on whether the RD-limit-value is applied to All Route Explorer (ARE) or Spanning Tree Explorer (STE) frames.

RD-limit-value

 Specifies the maximum number of RDs that might be contained in the Routing Information Field (RIF) of the frame type specified by the RD limit type. This field takes values from 0 to 14. The default RD limit value for ARE and STE frames is 14.