Cisco Systems BC-109 Manual De Usuario
Configure LNM Support
BC-126
Bridging and IBM Networking Configuration Guide
The Cisco IOS software also converts pairs of FIND_NAME and NAME_RECOGNIZED packets
received from explorers, which traverse all rings, to specific route frames that are sent only between
the two machines that need to see these packets.
received from explorers, which traverse all rings, to specific route frames that are sent only between
the two machines that need to see these packets.
You can specify a query-timeout, or “dead-time” interval to prevent repeat or duplicate broadcast of
these type of packets for the duration of the interval.
these type of packets for the duration of the interval.
To specify dead time intervals, use one or both of the following commands in global configuration
mode:
mode:
Configure LNM Support
LAN Network Manager (LNM), formerly called LAN Manager, is an IBM product for managing a
collection of source-route bridges. Using either a proprietary protocol or the Simple Network
Management Protocol (SNMP), LNM allows you to monitor the entire collection of Token Rings
that comprise your source-route bridged network. You can use LNM to manage the configuration of
source-route bridges, monitor Token Ring errors, and gather information from Token Ring parameter
servers.
collection of source-route bridges. Using either a proprietary protocol or the Simple Network
Management Protocol (SNMP), LNM allows you to monitor the entire collection of Token Rings
that comprise your source-route bridged network. You can use LNM to manage the configuration of
source-route bridges, monitor Token Ring errors, and gather information from Token Ring parameter
servers.
Note
LNM is supported on the 4/16-Mb Token Ring cards that can be configured for either 4- or
16-Mb transmission speeds. LNM support is not provided on CSC-R16M cards with SBEMON 2.0.
LNM is not limited to managing locally attached Token Ring networks; it also can manage any other
Token Rings in your source-route bridged network that are connected through non-Token Ring
media. To accomplish this task, LNM works in conjunction with the IBM Bridge Program. The IBM
Bridge Program gathers data about the local Token Ring network and relays it back to LNM. In this
manner, the bridge program becomes a proxy for information about its local Token Ring. Without
this ability, you would require direct access to a device on every Token Ring in the network. This
process would make managing an SRB environment awkward and cumbersome.
Token Rings in your source-route bridged network that are connected through non-Token Ring
media. To accomplish this task, LNM works in conjunction with the IBM Bridge Program. The IBM
Bridge Program gathers data about the local Token Ring network and relays it back to LNM. In this
manner, the bridge program becomes a proxy for information about its local Token Ring. Without
this ability, you would require direct access to a device on every Token Ring in the network. This
process would make managing an SRB environment awkward and cumbersome.
Figure 51 shows some Token Rings attached through a cloud and one LNM linking to a source-route
bridge on each local ring.
bridge on each local ring.
Command
Purpose
netbios name-cache query-timeout seconds
Specify a dead time interval during which the
Cisco IOS software drops any broadcast
(NetBIOS ADD_NAME_QUERY,
ADD_GROUP_NAME, or STATUS_QUERY)
frames if they are duplicate frames sent by the
same host.
Cisco IOS software drops any broadcast
(NetBIOS ADD_NAME_QUERY,
ADD_GROUP_NAME, or STATUS_QUERY)
frames if they are duplicate frames sent by the
same host.
netbios name-cache recognized-timeout seconds
Specify a dead time interval during which the
software drops FIND_NAME and
NAME_RECOGNIZED frames if they are
duplicate frames sent by the same host.
software drops FIND_NAME and
NAME_RECOGNIZED frames if they are
duplicate frames sent by the same host.