Filter
Top Products
Subnetwork visit count
is the first of these, and describes the same concept as
defined at the node level. When a port is first configured this parameter is initialized
to the node setting. With this parameter you allow individual ports to deviate from
the node level setting.
Adjacent subnetwork affiliation
is controlled by the other new extended border node
prompt. This allows you to define whether or not the adjacent node is in the same
network as the extended border node. The value specified here will be used as the
default value for all links through the port. Allowed values are:
Native Adjacent node is in the same topology subnetwork as the extended border
node.
Non-native
Adjacent node is not part of the extended border node’s topology
subnetwork.
Negotiable
Adjacent node may or may not be in the same topology subnetwork
depending upon how the adjacent node is defined. The adjacent node is in
the extended border node’s topology subnetwork unless the adjacent
node’s corresponding link definition is one of:
v Non-native
v Negotiable and the adjacent node has a different network name
v Negotiable and the adjacent node has defined the link as non-native
Add link
If extended border node is enabled the same two additional prompts are presented
when you invoke the add link menu item as were previously presented under add
port.
Subnetwork visit count
and
adjacent subnetwork affiliation
are the same concept as
defined at the port level. They are initialized to the corresponding port setting when
a link is first configured. You change the value here if you want different links to
have different values even though they are on the same port.
Add Routing List(s)
Note: Routing lists are not supported for 2210 12x models.
A configured routing list allows you to explicitly define one or more possible next
hop CPs for one or more destination resources (LUs). A wildcard character “*” may
be used when defining the LU names to reduce the amount of configured data. You
can also vary some of the node level defaults for a given routing list.
You can define multiple routing lists. Typically a group of LUs with similar routing
requirements would be configured into a single routing list. Additional groups of
LUs, each group with its own routing requirements, would be configured into
additional routing lists.
There are limits on the number of LU names and number of CP names used in
routing lists. These limits vary according to the model router you have. See Table 37
on page 188 for the configuration command detail. Limits have been set to allow as
much flexibility as possible in various environments. The ability of the router to
handle the specification of many routing lists, each with many LU names and CP
names, is limited by the availability of configuration nonvolatile memory, router
APPN
Chapter 1. APPN 33