This document describes the Nx Networks implementation of NetBIOS over bridged networks and over DLSw networks. It includes the following topics:
About NetBIOS
Reducing NetBIOS Traffic
About NetBIOS Configuration and Monitoring Commands
Displaying the NetBIOS Configuration Prompt
Displaying the NetBIOS Monitoring Prompt
Configuring NetBIOS Filtering and Caching
NetBIOS Commands
About NetBIOS
NetBIOS was designed only for use on a LAN. It is not a routable protocol and is typically bridged or switched using DLSw.
NetBIOS relies on broadcast frames for most of its functions. While this may not present a problem in LAN environments, these broadcasts can be costly in internetwork environments by causing congestion, as well as increased costs for WAN links.
NetBIOS uses LLC type 1 (LLC1) and LLC type 2 (LLC2) services:
LLC1 provides connectionless data transfer. It requires name conflict resolution, station status gathering flows, and circuit and connection setup flows.
LLC2 provides a connection-oriented data transfer that uses I-frame traffic sent on established LLC2 connections.
NetBIOS names have 16 ASCII characters. IBM and Microsoft reserve the 16th character of the NetBIOS name.
There are two types of NetBIOS names:
Individual names represent a single NetBIOS client or server and should be unique within the NetBIOS network.
Group names represent a group of NetBIOS stations (an OS/2 LAN Server domain, for example). These names should not be the same as any individual NetBIOS names in the network.
NetBIOS Name Conflict Resolution
Before a NetBIOS station uses an individual NetBIOS name, it makes sure that the name is unique. To do so, the station repeatedly broadcasts a Name Conflict Resolution frame to all NetBIOS stations. If the station does not receive a response, it presumes the name is unique and it uses the name.
NetBIOS Session Setup Procedure
To establish a NetBIOS session for data transfer types of operations, the NetBIOS client first determines the MAC address of the NetBIOS server. In Token Ring networks, the client also uses source routing techniques to determine the LLC route to the server.
The following is the process of establishing a session:
The client can then do either of the following:
Filter as many broadcast NetBIOS frames as possible.
Forward unfiltered NetBIOS UI frames on as few bridge ports or DLSw TCP sessions as possible.
| Filter Type | Filters . . . |
| MAC Address | Frames by either the source or destination MAC address. |
| Frame Type | Specific types of NetBIOS frames. |
| Duplicate Frame | Duplicate frames. |
| Response | Responses for which the router did not forward a NetBIOS broadcast frame. |
| Byte | Frames by byte offset and field length within a frame. |
| Name | Frames by NetBIOS source and destination names. |
Once the router filters frames, name caching and route caching control how the router forwards the remaining frames.
Using MAC Filtering describes MAC address filtering.
The following sections describe frame type, duplicate frame, and response filtering, name and route caching, and name and byte filtering.
Frame Type Filtering
Frame type filtering lets you filter the following types of frames:
Use the following guidelines to determine when to filter Name Conflict Resolution frames:
It is critical that the NetBIOS names of stations to which a NetBIOS session is established (typically a server) be unique.
It is also usually critical that the individual NetBIOS names of stations within the same group (or domain) be unique.
It is often not critical that the NetBIOS names of stations from which a NetBIOS session is set up (typically a client) be unique, especially across domains.
For this reason, networks in which there is good control over server names may gain advantage by filtering name conflict resolution frames. This is especially true for DLSw networks.
Trace Control Frames
Trace Control frames terminate NetBIOS traces in all NetBIOS stations in a network. This frame is rarely used and you can typically filter it. The NetBIOS Trace Control frame is Terminate-Trace.
Configuring Frame Type Filtering
For bridged traffic, the router does not filter any of the above frame types as the default. However, if you are bridging NetBIOS traffic on WAN links, it may be beneficial to filter these frames. To turn frame type filtering on or off for bridging, enter set filters bridge.
For DLSw traffic, the router filters all of the above frame types as the default. To turn frame type filtering on or off for DLSw, enter set filters dlsw.
NetBIOS config>set filters bridge
Filter Name Conflict frames? [No]: yes
Name conflict filtering is ON
Filter General Broadcast frames? [No]: yes
General broadcast filtering is ON
Filter Trace Control frames? [No]: yes
Trace control filtering is ON
Duplicate frame filtering causes the router to forward only one instance of each frame within a configurable amount of time. Figure 1 shows how duplicate frame filtering reduces the number of broadcast frames forwarded over the DLSw WAN.
Figure 1 Setting Up a NetBIOS Session Over DLSw
Here is the process that the originating NetBIOS client in Figure 1 uses to set up a session with the target NetBIOS server.
Figure 2 shows the duplicate frame filtering process for bridged traffic. In this example, the router receives six Name-Query frames in half-second intervals. The Duplicate Frame Filter Timeout is set to 1.5 seconds, and the Duplicate Frame Detect Timeout is set to 5 seconds.
Figure 2 Duplicate Frame Filtering Process for Bridged Traffic
Here are the steps for duplicate frame filtering:
For DLSw traffic, the duplicate frame filtering process is the same, except that DLSw does not use the duplicate frame filter timer. DLSw uses only the duplicate frame detect timer. Once the originating router creates an entry, it filters all duplicate frames until the duplicate frame detect timer expires. For DLSw, you can also control how many query frames the target DLSw router sends during a configurable time period.
Configuring Duplicate Frame Filtering
Duplicate frame filtering is always enabled for DLSw traffic. You cannot enable or disable it.
Duplicate frame filtering is disabled for bridged traffic as the default. You can enable or disable it for bridging using the enable duplicate-filtering and disable duplicate-filtering commands.
To change the timers, enter the following:
If you enabled DLSw, the router also prompts you for the following:NetBIOS config>set general
WARNING! Setting Duplicate Frame Filter Timeout to zero...
disables duplicate frame checking!
Duplicate frame filter timeout value in seconds [1.5]?
Duplicate frame detect timeout value in seconds [5.0]?
General parameters set
These parameters control how many query frames the target DLSw router sends during a configurable time period.Command frame retry count [5]?
Command frame retry timeout value in seconds [0.5]?
Response Frame Filtering
NetBIOS stations expect a response frame to Name-Query and Status-Query frames. If a station does not receive a response, it continues to send queries.
If the router receives a response to a command frame that it did not forward, it drops the response and does not forward it.
You cannot disable response frame filtering on the router.
Response Frame Filtering for DLSw
For DLSw traffic, make sure the duplicate frame detect timeout is set high enough for the router to have time to set up a session.
As described in Duplicate Frame Filtering, a target DLSw router takes responsibility for setting up a session.
A router takes responsibility for setting up a session if it matches Name-Query and Name-Recognized frames within the duplicate frame detect timeout period. If the router does not match those frames within that time period, it does not forward Name-Recognized response frames, and it does not set up the session.
The default duplicate frame detect timeout is five seconds. Do not set the duplicate frame detect timeout to zero, or the router will have no time to set up the session. You can increase the duplicate frame detect timeout using the set general command.
NetBIOS config>set general
WARNING! Setting Duplicate Frame Filter Timeout to zero...
disables duplicate frame checking!
Duplicate frame filter timeout value in seconds [1.5]?
Duplicate frame detect timeout value in seconds [5.0]?
General parameters set
With name caching, the router maintains a database of NetBIOS names and routes. Each time the router receives a Name-Recognized frame, it extracts the MAC address and route and enters that information into the database.
When the router receives a Name-Query or Status-Query, it checks to see if the name being queried is already in its database. If it is, route caching converts the frame from an STE frame to a Specifically-Routed Frame (SRF). A timer on the entry invalidates the database information, if the server does not respond before the timer expires.
Enabling Caching
Name caching is always enabled. You cannot disable it. The default for route caching is disabled. Enter enable route-caching to enable it.
Types of Name Cache Entries
There are three types of name cache entries:
Permanent entries are those that you add at the NetBIOS configuration prompt (NetBIOS config>). The router saves permanent entries, and they are still available when you restart the router.
Static entries are those that you enter at the NetBIOS monitoring prompt (NetBIOS>). The router does not save static entries, and they are not available after you restart the router.
Dynamic entries are those that the router learns through Name-Query and Name-Recognized processing. A timer removes dynamic entries that are not referenced within a configurable amount of time. The router does not save dynamic entries, and they are not available after you restart the router.
Individual is a NetBIOS individual name.
Group is a NetBIOS group name.
Unknown means the router does not yet have information about the name, indicating that a search for the name is not complete.
Local is an entry the router can reach locally via the bridge network. The router saves the MAC address associated with the name. If route caching is enabled, the router also saves the best LLC route between the router and the NetBIOS station.
Remote is an entry the router can reach remotely via a DLSw TCP session. The router saves the best TCP sessions.
You can enter NetBIOS names in ASCII and hexadecimal, either separately or intermixed. For example, you would need to enter an adapter address in hexadecimal mode. The default data entry mode is ASCII. To enter hexadecimal mode, type a left angle bracket (<). To return to ASCII mode, type a right angle bracket (>).
Enter add cache-entry at the NetBIOS config> prompt to add permanent entries.
Enter add cache-entry at the NetBIOS> prompt to add static entries.
NetBIOS config>add cache-entry
Enter up to 15 characters of NetBIOS name(no wild cards)[]? nbs<F8>Enter IP Address [0.0.0.0]? 20.15.8.2
Name cache entry has been created
NetBIOS config>set cache-parms
Significant characters in name [15]?
Best path aging timeout value in seconds [60.0]?
Reduced search timeout value in seconds [1.5]?
Unreferenced entry timeout value in minutes [5000]?
Max nbr local name cache entries [500]?
Max nbr remote name cache entries [100]?
Cache parameters set
From the NetBIOS configuration prompt, you can use the list cache commands in Table 2.
| Command | Displays . . . |
| list cache all | All active entries in the router's name cache, including permanent, static, and dynamic entries. |
| list cache entry-number | A cache entry according to its entry number. |
| list cache name | A cache entry for a specific NetBIOS name. |
| list cache ip-address | A cache entry for a specific IP address. |
From the NetBIOS monitoring prompt, you can use the list cache commands in Table 3.
| Command | Displays . . . |
| list cache active | All active entries in the router's name cache, including permanent, static, and dynamic entries. |
| list cache config | Static and permanent entries. Does not show dynamic entries. |
| list cache group | Entries that exist for NetBIOS group names. |
| list cache local | Local cache entries. Local cache entries are those that the router learns over the bridge. |
| list cache name | A cache entry for a specific NetBIOS name. |
| list cache remote | Remote cache entries. Remote cache entries are those that the router learns over the DLSw WAN. |
| list cache unknown | Entries where the type of NetBIOS entry is unknown. The router considers all entries unknown until it learns the type of entry. |
NetBIOS Name Filtering
NetBIOS name filters apply to both bridging and DLSw. You can use them to filter NetBIOS packets that have specific NetBIOS host names. The router examines the source name or destination name field of the following NetBIOS UI packet types:
Add-Group-Name-Query (source)
Add-Name-Query (source)
Datagram (destination)
Name-Query (source and destination)
NetBIOS Byte Filtering
NetBIOS byte filters apply to both bridging and DLSw. Byte filtering lets you filter NetBIOS packets based on fields in the NetBIOS packet.
To build a byte filter, you specify
An offset from the beginning of the NetBIOS header
A byte pattern to match
An optional mask to apply to the selected fields of the NetBIOS header
About NetBIOS Configuration and Monitoring Commands
Enter NetBIOS configuration commands at the NetBIOS config> prompt. This document refers to changes you make at the configuration prompt as permanent. Changes you make at this prompt do not take effect immediately. They become part of the router's configuration memory when you restart the router.
Enter NetBIOS monitoring commands at the NetBIOS> prompt. This document refers to changes you make at the monitoring prompt as static. Monitoring commands take effect immediately, but the router does not save them after you restart the router.
Displaying the NetBIOS Configuration Prompt
You can access the NetBIOS config> prompt from either the Bridge or DLSw configuration environments.
Changes you make at the NetBIOS config> prompt affect both bridging and DLSw.
NetBIOS config> prompt from the Bridge configuration environment, enter protocol bridge at the Config> prompt and netbios at the Bridge Config> prompt.
Config>protocol bridge
Transparent Bridge user configuration
Bridge Config>netbios
NetBIOS Support User Configuration
NetBIOS config>
NetBIOS config> prompt from the DLSw configuration environment, enter protocol dls at the Config> prompt and netbios at the DLSw config> prompt.
Config>protocol dls
DLSw protocol user configuration
DLSw config>netbios
NetBIOS Support User Configuration
NetBIOS config>
NetBIOS> prompt from either the Bridge or DLSw monitoring environments.
Changes you make at the NetBIOS> prompt affect both bridging and DLSw.
NetBIOS> prompt from the Bridge monitoring environment, enter protocol bridge at the Monitor> prompt and netbios at the Bridge> prompt.
Monitor>protocol bridge
Bridge>netbios
NetBIOS Support User Console
NetBIOS>
NetBIOS> prompt from the DLSw monitoring environment, enter protocol dls at the Monitor> prompt and netbios at the DLSw> prompt.
Monitor>protocol dls
DLSw>netbios
NetBIOS Support User Console
NetBIOS>
To configure name caching parameters, enter set cache-parms.
To configure duplicate frame filtering, enter set general.
To configure frame type filtering, enter set filters bridge or set filters dlsw.
Add name cache entries for DLSw neighbors.
Open NetBIOS SAPs.
Set a priority for SNA and NetBIOS sessions.
Set the maximum NetBIOS frame size.
Set the memory allocation for NetBIOS UI frames.
You can enter NetBIOS names in ASCII and hexadecimal, either separately or intermixed. See cache-entry for more information. NetBIOS names are case sensitive and must match the case of the network NetBIOS names.
NetBIOS config>add cache-entry
Enter up to 15 characters of NetBIOS name (no wild cards)[] Accounting<0000>
Enter IP Address [0.0.0.0]? 20.2.1.3
Name cache entry has been created
DLSw config> prompt, open NetBIOS SAPs on both sides of the link to enable DLSw to transmit NetBIOS frames. DLSw config>open-sap
Interface # [0]?
Enter SAP in hex(range 0-F4),'SNA', 'NB' or 'LNM'[4]? nb
SAP F0 opened on interface 0
To do so, at the DLSw config> prompt, enter set priority to set a priority of Critical, High, Medium, or Low for SNA sessions and NetBIOS sessions. Also, set a message allocation that corresponds to a session's priority.
The router uses the priority and message allocation to selectively limit the burst-length of specific types of traffic. For example, if you assignDLSw config>set priority
Priority for SNA DLSw sessions (C/H/M/L) [M]? H
Priority for NetBIOS DLSw sessions (C/H/M/L) [M]? M
Message allocation by C/H/M/L priority (4 digits) [4/3/2/1]?
Maximum NetBIOS frame size (516, 1470, 2052, or 4399) [2052]?
SNA traffic a priority of Critical, and Critical sessions have a message allocation of 4, and
NetBIOS traffic a priority of Medium, and Medium sessions have a message allocation of 2,
You can change the message allocation for sessions from the default of 4/3/2/1. You must always enter four digits, between 1 and 9, in descending order. For example, if the SNA priority is Critical, the NetBIOS traffic is Medium, and you change the message allocation to 8/7/6/5, the router processes 8 SNA frames before it processes 6 NetBIOS frames, and so on.
Setting the Maximum NetBIOS Frame Size
To change the maximum NetBIOS frame size, enter set priority at the DLSw config> prompt. The default is 2052. Set this parameter to the largest frame size you expect to need, and no larger. Setting the frame size larger than needed reduces the number of available buffers.
Setting the Memory Allocation for NetBIOS UI Frames
Enter set memory at the DLSw config> prompt to set the number of bytes the router allocates as a buffer for NetBIOS UI frames. If the TCP transmit buffer becomes full, the router uses this buffer to collect NetBIOS UI frames.
Note that the number of bytes allocated for NetBIOS is global, and not per session.
DLSw config>set memory
Number of bytes to allocate for DLSw (at least 26368) [141056]?
Number of bytes to allocate per LLC session [8192]?
Number of bytes to allocate per SDLC session [4096]?
Number of bytes to allocate for NetBIOS UI-frames [40960]?
[C] means the command is available at the NetBIOS config> prompt.
[M] means the command is available at the NetBIOS> prompt.
| Command | Function |
|---|---|
| Add [C] [M] | Adds cache entries to the router's name cache. |
| Delete [C] [M] | Deletes cache entries that you added using the add cache-entry command. |
| Disable [C] [M] | Disables duplicate frame filtering and route caching. |
| Enable [C] [M] | Enables duplicate frame filtering and route caching. |
| Exit [C] [M] | Returns to the previous prompt. |
| List [C] [M] | Displays various cache entries and configuration information depending on whether you are at the configuration prompt or the monitoring prompt. |
| Set [C] [M] | Configures parameters for name caching, duplicate frame filtering, and frame type filtering. Also, displays the NETBIOS Filter config> prompt. |
Add [C] [M]
Adds a new name cache entry to the router's permanent or static configuration.
From the configuration prompt, adds a permanent entry. From the monitoring prompt, adds a static entry.
You can add multiple entries with different IP addresses for a single NetBIOS name. This allows DLSw to send the frame to multiple DLSw neighbors.
You can enter NetBIOS names in ASCII and hexadecimal, either separately or intermixed. For example, you would need to enter an adapter address in hexadecimal mode. The default data entry mode is ASCII. To enter hexadecimal mode, type a left angle bracket (<). To return to ASCII mode, type a right angle bracket (>).
Note: NetBIOS names are case sensitive and must match the case of the network NetBIOS names.
Example:add cache-entry
Enter up to 15 characters of NetBIOS name (no wild cards)[] nbserve<F1>
Enter IP Address [0.0.0.0]? 20.2.1.3
Name cache entry has been created
Delete [C]
Deletes name cache entries from the router's permanent configuration. The router prompts for a record number, which is the number of the entry you want to delete. To see a list of entry numbers, enter list cache all.
delete cache-entry
Enter name cache record number [1]? 2
Name cache entry has been deleted
Note: NetBIOS names are case sensitive.
Syntax: deletedelete cache-entry
Enter up to 15 characters of NetBIOS name (no wild cards) []? ADMIN
Name cache entry NOT found in Active list for name entered
Name cache entry has NOT been deleted from Active list
Static name cache entry deleted from Config list
Example: disable duplicate-filtering
Duplicate frame filtering is OFF
Example: disable route-caching
Route caching is OFF
Example: enable duplicate-filtering
Duplicate frame filtering is ON
Route caching is ON
exit
List [C] [M]
Displays various cache entry and configuration information, depending on whether you are at the configuration prompt or the monitoring prompt.
See NetBIOS Name Caching and Route Caching for a description of the types of cache entries.
List [C]
Displays all cache entries or displays cache entries by type of entry. Displays filter configuration information or general configuration information.
The router displays all hexadecimal data in angle brackets. The number in angle brackets just before the IP address is the 16th character of the NetBIOS name. IBM and Microsoft reserve the 16th character of the NetBIOS name, and it always appears in hexadecimal.
Entry Name IP Address
----- ------------------- ---------------
1 Accounting <00> 20.2.1.3
2 Notes<00000> <00> 20.2.3.4
Example: list cache entry-number
Enter name cache record number [1]? 1
Entry Name IP Address
----- ------------------- ---------------
1 Accounting <00> 20.2.1.3
|
*
|
Stands for any character string. For example, "San*" could produce: San Francisco Santa Fe San Juan |
|
?
| Stands for any one character. |
|
$
| Must coincide with the last character in a name. |
Following are examples of valid uses of wildcards that match San Francisco:
|
*Fran*
| S??*????????? |
|
San?Fran?isco
| S?* |
|
S*
| S?a?n?F?a?c?s? |
|
*o
| ???????????? |
|
isco?
| isco$ |
|
San?F*
| * |
Use as many wildcards as you like, up to the maximum number of characters in a NetBIOS name (15 or 16, depending on how many significant characters you configured using the set cache-parms command).
Note: NetBIOS names are case sensitive.
Example:list cache name
Enter up to 15 characters of NetBIOS name (wild cards ok) []? Acc*
Entry Name IP Address
----- ------------------- ---------------
1 Accounting <00> 20.2.1.3
Example: list cache ip-address
Enter IP Address [0.0.0.0]? 20.2.1.3
Entry Name IP Address
----- ------------------- ---------------
1 Accounting <00> 20.2.1.3
Bridge name conflict filtering is OFF
Bridge general bcast filtering is OFF
Bridge trace control filtering is OFF
DLS name conflict filtering is ON
DLS general bcast filtering is ON
DLS trace control filtering is ON
Bridge name conflict filtering is OFF
Bridge general bcast filtering is OFF
Bridge trace control filtering is OFF
DLS name conflict filtering is ON
DLS general bcast filtering is ON
DLS trace control filtering is ON
Bridge-only Information:
Bridge duplicate filtering is OFF
Bridge duplicate frame filter t/o 1.5 seconds
DLS-only Information:
DLS command frame retry count 5
DLS max remote name cache entries 100
DLS command frame retry timeout 0.5 seconds
DLS-Bridge Common Information:
Route caching is OFF
Significant characters in name 15
Max local name cache entries 500
Duplicate frame detect timeout 5.0 seconds
Best path aging timeout 60.0 seconds
Reduced search timeout 1.5 seconds
Unreferenced entry timeout 5000 minutes
The router displays all hexadecimal data in angle brackets. The number in angle brackets just before the IP address is the 16th character of the NetBIOS name. IBM and Microsoft reserve the 16th character of the NetBIOS name, and it always appears in hexadecimal.
If the Name Type field does not specify local, it is a remote entry. For a description of the fields in this display, see the list cache name command on page 28.
Cnt NetBIOS Name Name Type Entry Type
--- ------------------- ----------------- ----------
1 HYPERION <01> INDIVIDUAL LOCAL DYNAMIC
2 LANGROUP<F8> <00> UNKNOWN STATIC
3 ACCOUNTING<000><00> GROUP PERMANENT
The router displays all hexadecimal data in angle brackets. The number in angle brackets just before the IP address is the 16th character of the NetBIOS name. IBM and Microsoft reserve the 16th character of the NetBIOS name, and it always appears in hexadecimal.
Name IP Address Source Last Mod
------------------ -------------- --------- ---------
Admin<00000> <00> 20.3.120.8 STATIC ADDED
Finance <01> 20.4.96.8 PERMANENT MODIFIED
Notes <00> 20.8.210.3 PERMANENT UNCHANGED
Cnt NetBIOS Name Entry Type Loc Path St Rem Path St
--- --------------- ----------- ----------- -----------
2 HYPERION <01> DYNAMIC UNKNOWN GROUP
3 EXCEL < > DYNAMIC GROUP GROUP
For NetBIOS clients the Local Path State is always Unknown and the MAC Address and Routing Information fields are always empty.
Cnt NetBIOS Name Loc Path St MAC Address Routing Information
--- --------------- ----------- ----------- --------------------
2 HYPERION <01> UNKNOWN
|
*
|
Stands for any character string. For example, "San*" could produce: San Francisco Santa Fe San Juan |
|
?
| Stands for any one character. |
|
$
| Must coincide with the last character in a name. |
Following are examples of valid uses of wildcards that match San Francisco:
|
*Fran*
| S??*????????? |
|
San?Fran?isco
| S?* |
|
S*
| S?a?n?F?a?c?s? |
|
*o
| ???????????? |
|
isco?
| isco$ |
|
San?F*
| * |
Use as many wildcards as you like, up to the maximum number of characters in a NetBIOS name (15 or 16, depending on how many significant characters you configured using the set cache-parms command).
Note: NetBIOS names are case sensitive.
Example:list cache name
Enter up to 15 characters of NetBIOS name (wild cards ok) []? HYP*
NetBIOS Name Name Type Entry Type
------------------- ----------------- ----------
HYPERION <01> INDIVIDUAL REMOTE DYNAMIC
Count of name cache entry hits 2
Age of name cache entry 689
Age of name cache last reference 85
Local path information:
Loc Path St Timestamp MAC Address LFS Routing Information
----------- --------- ----------- --- -----------------------
UNKNOWN 689
Remote path information:
Rem Path St Timestamp LFS IP Address(es)
----------- --------- --- --------------
BEST FOUND 85 2 52 20.55.27.33
cache remote
Displays cache entries that the router learns over the
DLSw WAN. If the router has found the best path, it displays the IP address associated
with the DLSw neighbor that can reach the NetBIOS station. For a description of
the fields in this display, see the list cache name
command.
Cnt NetBIOS Name Entry Type Rem Path St IP Address(es)
--- --------------- -------------- -------------- --------------
2 HYPERION <01> STATIC BEST FOUND 20.55.27.33
3 EXCEL <00> STATIC SEARCH ALL cache unknown
Cnt NetBIOS Name Entry Type Loc Path St Rem Path St IP Address(es)
--- ------------- ----------- ----------- ----------- --------------
2 HYPERION <01> STATIC UNKNOWN BEST FOUND 23.21.21.2
3 EXCEL <00> STATIC UNKNOWN UNKNOWN
Bridge name conflict filtering is OFF
Bridge general bcast filtering is OFF
Bridge trace control filtering is OFF
DLS name conflict filtering is ON
DLS general bcast filtering is ON
DLS trace control filtering is ON
Bridge name conflict filtering is OFF
Bridge general bcast filtering is OFF
Bridge trace control filtering is OFF
DLS name conflict filtering is ON
DLS general bcast filtering is ON
DLS trace control filtering is ON
Bridge-only Information:
Bridge duplicate filtering is OFF
Bridge duplicate frame filter t/o 1.5 seconds
DLS-only Information:
DLS command frame retry count 5
DLS max remote name cache entries 100
DLS command frame retry timeout 0.5 seconds
DLS-Bridge Common Information:
Route caching is OFF
Significant characters in name 15
Max local name cache entries 500
Duplicate frame detect timeout 5.0 seconds
Best path aging timeout 60.0 seconds
Reduced search timeout 1.5 seconds
Unreferenced entry timeout 5000 minutes
Example: list statistics cache
Local name cache entries 1
Remote name cache entries 1
Local individual names 1
Remote individual names 0
Group names 0
Unknown names 1
Name cache hits 2194
Name cache misses 2
Example: list statistics frames bridge
Frames in cache 0
Name query frames 0
Status query frames 0
Add name frames 0
Add group name frames 0
Name in conflict frames 0
Frames not filtered as duplicates 0
Example: list statistics frames dlsw
Name query frames 0
Status query frames 0
Add name frames 0
Add group name frames 0
Name in conflict frames 0
Frames not filtered as duplicates 0
Example: list statistics general bridge
Frames received 1339
Frames discarded 0
Frames forwarded to bridge 1339
Frames forwarded to DLS 1339
Example: list statistics general dlsw
Frames received 1339
Frames discarded 0
Frames forwarded to bridge 1339
Significant characters in name [15]?
Best path aging timeout value in seconds [60.0]?
Reduced search timeout value in seconds [1.5]?
Unreferenced entry timeout value in minutes [5000]?
Max nbr local name cache entries [500]?
Max nbr remote name cache entries [100]?
Cache parameters set
filters bridge
Turns on or off frame-type filtering for bridging.
Filter Name Conflict frames? [No]: y
Name conflict filtering is ON
Filter General Broadcast frames? [No]:
General broadcast filtering is OFF
Filter Trace Control frames? [No]:
Trace control filtering is OFF
NetBIOS config> prompt, displays the NetBIOS filtering configuration prompt (NETBIOS Filter config>).
From the NetBIOS> prompt, displays the NetBIOS filtering monitoring prompt (NETBIOS Filter>).
These prompts allow you to set up NetBIOS name and byte filters.
See Configuring and Monitoring NetBIOS Name and Byte Filters for information on the commands available at this prompt.
NETBIOS Filtering configuration
NETBIOS Filter config>
Filter Name Conflict frames? [Yes]:
Name conflict filtering is ON
Filter General Broadcast frames? [Yes]:
General broadcast filtering is ON
Filter Trace Control frames? [Yes]:
Trace control filtering is ON
NetBIOS config> prompt, displays the NETBIOS Filter config> prompt.
From the NetBIOS> prompt, displays the NETBIOS Filter> prompt.
These prompts allow you to set up NetBIOS name and byte filters.
See Configuring and Monitoring NetBIOS Name and Byte Filters for a description of the commands available at this prompt.
NETBIOS Filtering configuration
NETBIOS Filter config>
WARNING! Setting Duplicate Frame Filter Timeout to zero...
disables duplicate frame checking!
Duplicate frame filter timeout value in seconds [1.5]?
Duplicate frame detect timeout value in seconds [5.0]?
General parameters set
Command frame retry count [5]?
Command frame retry timeout value in seconds [0.5]?