SCOPE.TXT
12/94

A. IPX Scoping (NetExplorer Server)
In NMS 2.0, it was possible to specify IP network addresses to be used to
control the scope of IP discovery.  NMS002 adds a similar feature to IPX
discovery.  This section describes that feature, and explains how you can
use scoping.

Typically, NetExplorer attempts to discover all nodes within the IPX
internetwork.  If your internetwork is large, you might not be interested
in discovering all parts of it.  IPX scoping allows you to restrict the
scope of IPX discovery to certain IPX network numbers. You specify a list
of IPX network numbers to be discovered.  Only these networks, and IPX
nodes connected to these networks, are discovered.

The effect of this is to reduce memory, disk usage, bandwidth, and CPU
usage on both your NetExplorer server and your NMS Console. It also reduces
traffic on your internetwork.  By restricting discovery to only those
networks in which you are interested, NMS is also likely to detect any
changes that occur in your network more quickly.

These are the steps you should take to use IPX scoping:

1. Decide which IPX networks you want to include in your normal scoping.

One way to decide this is to first run NMS without scoping, then decide
which networks you want from the NMS internet map.

Alternatively, you can use the DISPLAY NETWORKS command at the console of
the server running NetExplorer.  This displays a list of all IPX networks
in your internetwork, and shows the hop count and an estimate of the delay
to reach that network.  The delay is in units of 1/18th of a second.

For example:
00001232 5/6 means that Network 00001232 is 5 hops away - delay is 6/18
second.

A good approach is to start by including only networks that are close, just
a few hops away.

Note that a network is only discovered if there is a path to that network
through networks that are also in the specified list.

All nodes that are attached to a particular IPX network are discovered,
even if they have other IPX addresses that are not within your specified
scope.

2.  The network numbers that you want to include in the scope of your IPX
discovery must be included in SYS:\NMDISK\NXPIPX.INI using the format
specified below.  Note that you can use the '?'character to match any
single hexadecimal digit.  This is most useful if IPX network numbers have
been assigned with some geographical or other administrative significance.

3. If you have previously discovered IPX networks that are no longer in
your specified scope, you should reset your NMS database before reloading
NetExplorer on your server.

PROCEDURE

Add to SYS:\NMDISK\NXPIPX.INI a line of the following format for each IPX
network to be included within the scope of IPX discovery:

IPXQNET=xxxxxxxx

where

* xxxxxxxx is an 8-digit hexadecimal string that specifies an IPX network,
which can be an IPX internal network number or an IPX network number to
which a network node interface is bound. If there are fewer than 8 digits,
it is padded with leading zeros. IPXQNET can be in uppercase or lowercase.

* The discovery scope MUST include the IPX network number where the
NetExplorer software resides. If this network number is omitted, nothing is
discovered by NXPIPX.

* Scoping can consist of a single network or a list of networks. If no
valid IPXQNET line is specified, NXPIPX interprets that as indicating that
IPX discovery is not to be restricted.

* All IPXQNET network number values are hexadecimal. If an invalid value is
entered on an IPXQNET line, NXPIPX displays the invalid value and the file
location on the system console and unloads NXPIPX with error code 10061.

* A network is only discovered if there is a path to it through networks
that are also in the specified list. That is, NXPIPX cannot go through an
unlisted network to get to a listed network.

* A question mark (?) can be used as a wildcard to indicate that any value
can be accepted in that specific digit position.

For example:

IPXQNET=C824????
IPXQNET=C834????
IPXQNET=C7??????
IPXQNET=7777ABCD

This restricts IPX discovery to IPX network numbers that begin with the
values C824, C834, or C7, and to the network 7777ABCD.

If a node is connected to more than one IPX network, that node is
discovered if any of its addresses are specified. This means that a system
with an IPX internal network number is discovered, even if the internal
network has not been specified as long as the IPX network number of at
least one of its interfaces has been specified.

For example, in the following topology, where there are two NetWare servers
(S1 and S2) and one IPX workstation (W1), it is only necessary to specify
the IPX network numbers of the two LANs (120000C6 and 120000C7) to discover
all three nodes, and any other nodes connected to these LANs.
   -----
   | W1 |   Workstation
   -----
      |
      |
      ----------- Network 120000C6
      |
      |
    ------
    | S1 | - Internal Network 120000FF
    ------
      |
      |
      -------------- Network 120000C7
      |
      |
    ------
    | S2 | - Internal Network 12000076
    ------

RESTRICTIONS TO IPX SCOPING
1. If you move a node that was previously within the scope of IPX discovery
to a network that is outside that scope, NetExplorer does not detect the
change and the node remains in the database at its old location.

To remove this node, take the following steps:
a. Unload the NetExplorer software on your server.
b. Delete the node from the NMS map (using Edit > Delete) or reset your NMS
database.
c. Reload the NetExplorer software on your server.

2. Setting up IPX scoping does not completely eliminate NetExplorer IPX
traffic outside the networks specified. This is because IPX discovery
periodically tries to see whether there are any new IPX addresses that
match one of the specified networks.

3. The presence of NetWare LANalyzer Agent software in your internetwork
might result in networks that are outside the IPX scope continuing to be
discovered.  The solution is to make sure that the NetWare LANalyzer Agent
SAP type (570 decimal, 23A hex) is being filtered between all NetWare
LANalyzer Agent software that is outside the IPX scope, and your
NetExplorer discovery server.

The simplest way to do this might be to ensure that all your routers filter
out this SAP type, so that the SAP is never sent beyond the local network
where NetWare LANalyzer Agent generated it. SAP filtering can be performed
in any NetWare 3.11 or later server.  When doing this, be careful only to
filter NetWare LANalyzer Agent from networks that you do not want to
discover.  Indiscriminate filtering of the NetWare LANalyzer Agent SAP
could result in a diminished capacity to discover networks within your
desired scope.

After you have set up these filters, you should take the following steps:
a. Unload the NetExplorer software on your server.
b. Reset your NMS database.
c. Reload the NetExplorer software on your server.

4. Nodes that do not respond to IPX diagnostic requests show up in
discovery in progress. This is true even for nodes that are outside the
scope, because they do not provide enough information to determine that
they are not within the discovery scope.


B. IP Scoping (NetExplorer Server)
IP discovery, by default, discovers routers that are within the network to
which the NetExplorer system is directly attached.  NMS 2.0 has a feature
to allow you to expand discovery to other networks, by specifying these
addresses in NXPIP.INI.

NMS002 adds the ability to specify a network of *.*.*.*, which means
discover all IP networks.

How to set up IP scoping using either specified IP network numbers or the
new *.*.*.* wildcard network number.
-------------------------------------------------------------------------
By default, the NetExplorer discovery software discovers IP routers on only
the local IP network, as defined by the class of the IP network.

An IP network class is determined by the first byte of the IP address:
The range of class A addresses is 1-127.
The range of class B addresses is 128-191.
The range of class C addresses is 192-223.

For class A addresses, the IP network is the first byte.
For class B addresses, the IP network is the first two bytes.
For class C addresses, the IP network is the first three bytes.

Format of a class A address:
   -------------------------------------
   |        |        |        |        |
   |Network |        |        |        |
   |        |        |        |        |
   -------------------------------------

Format of a class B address:
   ------------------------------------
   |        |        |        |        |
   |<--- Network --->|        |        |
   |        |        |        |        |
   -------------------------------------

Format of a class C address:
   -------------------------------------
   |        |        |        |        |
   |<-------- Network ------->|        |
   |        |        |        |        |
   -------------------------------------

Examples:
A server has an IP address of 195.6.25.4. 
This is a class C address.  IP discovery is restricted to network
195.6.25.0.

A server has an IP address of 139.56.15.9.  
This is a class B address.  IP discovery is restricted to network
139.56.0.0.  This includes all IP subnets within this network.

A server has an IP address of 33.22.2.11.  
This is a class A address.  IP discovery is restricted to network 33.0.0.0.
This includes all IP subnets within this network.

Note: NetExplorer finds the local IP network address by examining the first
address that is bound to a driver on the NMS Server.  If the server has
multiple bindings to subnets that are in different networks, all the
networks must be included in SYS:\NMDISK\NXPIP.INI.  Otherwise, only the
first IP network is discovered.

If you want to extend the range of IP networks discovered by NetExplorer,
you should edit the SYS:\NMDISK\NXPIP.INI on the server to list the IP
networks that you want to add.
For example:
89.0.0.0
139.56.0.0
195.6.25.0

This adds three IP networks: a class A network, a class B network, and a
class C network to the scope of IP discovery.

NetExplorer IP discovery does not discover a system in a listed IP network,
unless all the IP networks needed to reach that network are also listed. 
An IP node, with more than one IP address, is discovered if any of its IP
addresses is in a listed network.

NMS002 adds the ability to specify a wildcard network of *.*.*.*, which
means; discover all IP networks.

Note: we recommend that you NOT use this feature if your IP internetwork is
connected to the Internet, because you might unintentionally start
discovering the Internet.

If you have an Internet connection and still want to use the IP wildcard
address (*.*.*.*), you should ensure that the community access string of
the router that is the boundary between your internetwork and the Internet
is unique and DOES NOT appear in the SNMP community strings file on the NMS
Server.  This prevents NetExplorer from discovering this router and any
routers beyond it.

Reminder: The SNMP community strings filename, if used, is described in
NETXPLOR.NCF and is used with the /C parameter on the LOAD NXPIP command
line.  It includes the SNMP community strings used by the routers in your
internetwork, if they use any string other than "public."

Note: Because IP discovery only discovers one IP network by default, IP
scoping is a means to extend discovery to other IP networks.  IPX scoping,
on the other hand, is a means of restricting IPX discovery so that instead
of the entire IPX internetwork, only certain IPX networks are discovered.
IP scoping cannot be used to restrict discovery to anything less than the
local IP network, as defined by the class of the IP address.

Note: For more information about the discovery process, see the
"NetExplorer Rules of Thumb" document supplied with NMS 2.0.

RESTRICTION TO IP SCOPING
If a node that was previously within the scope of IP discovery is moved to
a network that is outside that scope, the change is not detected - the node
remains in the database at its old location.

To remove this node, you should take the following steps:
a. Unload the NetExplorer software on your server.
b. Delete the node from the NMS map (using Edit > Delete) or reset your NMS
database.
c. Reload the NetExplorer software on your server.
IP Scoping (NetExplorer Server)
IP discovery, by default, discovers routers that are within the network to
which the NetExplorer system is directly attached.  NMS 2.0 has a feature
to allow you to expand discovery to other networks, by specifying these
addresses in NXPIP.INI.

NMS002 adds the ability to specify a network of *.*.*.*, which means
discover all IP networks.

How to set up IP scoping using either specified IP network numbers or the
new *.*.*.* wildcard network number.
-------------------------------------------------------------------------
By default, the NetExplorer discovery software discovers IP routers on only
the local IP network, as defined by the class of the IP network.

An IP network class is determined by the first byte of the IP address:
The range of class A addresses is 1-127.
The range of class B addresses is 128-191.
The range of class C addresses is 192-223.

For class A addresses, the IP network is the first byte.
For class B addresses, the IP network is the first two bytes.
For class C addresses, the IP network is the first three bytes.

Format of a class A address:
   -------------------------------------
   |        |        |        |        |
   |Network |        |        |        |
   |        |        |        |        |
   -------------------------------------

Format of a class B address:
   ------------------------------------
   |        |        |        |        |
   |<--- Network --->|        |        |
   |        |        |        |        |
   -------------------------------------

Format of a class C address:
   -------------------------------------
   |        |        |        |        |
   |<-------- Network ------->|        |
   |        |        |        |        |
   -------------------------------------

Examples:
A server has an IP address of 195.6.25.4. 
This is a class C address.  IP discovery is restricted to network
195.6.25.0.

A server has an IP address of 139.56.15.9.  
This is a class B address.  IP discovery is restricted to network
139.56.0.0.  This includes all IP subnets within this network.

A server has an IP address of 33.22.2.11.  
This is a class A address.  IP discovery is restricted to network 33.0.0.0.
This includes all IP subnets within this network.

Note: NetExplorer finds the local IP network address by examining the first
address that is bound to a driver on the NMS Server.  If the server has
multiple bindings to subnets that are in different networks, all the
networks must be included in SYS:\NMDISK\NXPIP.INI.  Otherwise, only the
first IP network is discovered.

If you want to extend the range of IP networks discovered by NetExplorer,
you should edit the SYS:\NMDISK\NXPIP.INI on the server to list the IP
networks that you want to add.
For example:
89.0.0.0
139.56.0.0
195.6.25.0

This adds three IP networks: a class A network, a class B network, and a
class C network to the scope of IP discovery.

NetExplorer IP discovery does not discover a system in a listed IP network,
unless all the IP networks needed to reach that network are also listed. 
An IP node, with more than one IP address, is discovered if any of its IP
addresses is in a listed network.

NMS002 adds the ability to specify a wildcard network of *.*.*.*, which
means; discover all IP networks.

Note: we recommend that you NOT use this feature if your IP internetwork is
connected to the Internet, because you might unintentionally start
discovering the Internet.

If you have an Internet connection and still want to use the IP wildcard
address (*.*.*.*), you should ensure that the community access string of
the router that is the boundary between your internetwork and the Internet
is unique and DOES NOT appear in the SNMP community strings file on the NMS
Server.  This prevents NetExplorer from discovering this router and any
routers beyond it.

Reminder: The SNMP community strings filename, if used, is described in
NETXPLOR.NCF and is used with the /C parameter on the LOAD NXPIP command
line.  It includes the SNMP community strings used by the routers in your
internetwork, if they use any string other than "public."

Note: Because IP discovery only discovers one IP network by default, IP
scoping is a means to extend discovery to other IP networks.  IPX scoping,
on the other hand, is a means of restricting IPX discovery so that instead
of the entire IPX internetwork, only certain IPX networks are discovered.
IP scoping cannot be used to restrict discovery to anything less than the
local IP network, as defined by the class of the IP address.

Note: For more information about the discovery process, see the
"NetExplorer Rules of Thumb" document supplied with NMS 2.0.

RESTRICTION TO IP SCOPING
If a node that was previously within the scope of IP discovery is moved to
a network that is outside that scope, the change is not detected - the node
remains in the database at its old location.

To remove this node, you should take the following steps:
a. Unload the NetExplorer software on your server.
b. Delete the node from the NMS map (using Edit > Delete) or reset your NMS
database.
c. Reload the NetExplorer software on your server.