Address key | X.25 Virtual Circuit Configuration | In the network directory, the name of each
node listed in the remote node name field. HP recommends that you
use the node portion of the remote node's node name as
the address key. |
Card number | X.25 Configuration | Slot number of the DTC/X.25 Network Access
card. |
DTC node name | X.25 Configuration | Node name of the DTC in the form node.domain.organization.
Must agree with node name configured through during configuration
of the datacommunications and terminal subsystem (DTS). The node
name must be entered for each DTC/X.25 network access card that
allows system-to-system connections. |
Enable ethernet/ Enable IEEE 802.3 | LAN Configuration 100VG-AnyLAN Configuration
100Base-T Configuration | Both ethernet and IEEE 802.3 are enabled
by default. You may disable one or the other but not both (one must
be enabled). To disable either ethernet or IEEE 802.3,
enter an N (no) in the field next
to the enable question. |
Facility set | X.25 Virtual Circuit Configuration | For SVCs only. A name for a collection of X.25
connection parameters in the network directory. Use the default
(STDSFSET) or enter a different name, then go to Facility sets to
define parameters. It must match the parameters specified by your
network subscription. |
IP address | LAN Configuration; Token Ring Configuration;
FDDI Configuration; 100VG-AnyLAN Configuration; 100Base-T
Configuration; Point-to-Point Configuration; X.25 Configuration | There are two methods of entering an internet
protocol (IP) address within NMMGR: |
| | Enter the fully
qualified IP address (for example, Class C, C 192.191.191 009). OR Enter only the network (nnn)
and node (xxx) portions of the IP address as four positive integers
between 0 and 255 separated by periods or blanks (for example, 15.123.44.98). You need not enter the following items as NMMGR will fill
these in: Class A, B, C Leading zeros for the network and node portion of
the IP address.
|
| | All nodes on the same network must use the
same class of IP address. The network portion of the address must
be the same for all nodes on the same network. |
IP subnet mask | LAN Configuration; Token Ring Configuration;
FDDI Configuration; 100VG-AnyLAN Configuration; 100Base-T
Configuration; Point-to-Point Configuration; X.25 Configuration | The IP subnet mask is optional. An IP subnet
mask is specified in the same format as an IP address. The mask
identifies which bits of an IP address will be used to define a
subnetwork. For more information refer, to the configuration chapter
for the type of link you are configuring. |
Link name | | The link name represents a hardware interface
card. This name must be unique to both the node and the network.
The link name can have up to eight alphanumeric characters and the
first character must be alphabetic. |
(LAN Link name) | LAN Configuration | This represents the LAN card for which you
are configuring a link. |
(Token Ring Link name) | Token Ring configuration | This represents the Token Ring card for which
you are configuring a link. |
(FDDI Link name) | FDDI Configuration | This represents the FDDI card for which you
are configuring a link. |
(100VG-AnyLAN Link name) | 100VG-AnyLAN Configuration | This represents the 100VG-AnyLAN card for which
you are configuring a link. |
(100Base-T Link name) | 100Base-T Configuration | This represents the 100Base-T card for which
you are configuring a link. |
(X.25 Link name) | X.25 Configuration | The name of the link used by X.25 iX System
Access. It must match the link name configured during configuration
of the datacommunications and terminal subsystem (DTS). |
(Point-to-Point Link name) | Point-to-Point Configuration | This represents the PSI card for which you
are configuring a link. |
Local node name | Main | The node name is the name by which the HP 3000
Series 900 computer is known in the network. The format of a node
name is nodename.domain.organization
where the total number of characters is 50 or fewer, and each field
contains 16 or fewer characters (alphanumeric, underscore, or hyphens).
The first character of each field must be alphabetic. |
Local domain name | NS Configuration | The name of the system in ARPANET standard
format. It is composed of labels, with each label separated by a
period. Labels must start with a letter or digit and have as interior
characters only letters, digits, hyphens(-), or underbars (_). There
may be any number of labels, but the total length of the name, including
periods, is limited to 255 characters. (If not using domain
names for network access, leave the local node name in this field.) |
Network directory name | X.25 Virtual Circuit Configuration | The network directory name must be configured
for each new node. The network directory contains information that
one node needs in order to communicate with other nodes. The only
network directory name supported by HP is NSDIR.NET.SYS. |
Network Interface (NI) name | LAN Configuration; Token Ring Configuration;
FDDI Configuration; 100VG-AnyLAN Configuration; 100Base-T
Configuration; Point-to-Point Configuration; X.25 Configuration | The network interface (NI) name is used to
easily identify a network interface. The name can be up to eight
alphanumeric characters, starting with a letter. The maximum number
of NIs that can be configured on a node is 12. If a node interfaces
to more than one network, give each NI on that node a unique name.
You will use the NI name with the NETCONTROL
command to start the transport and network link. |
Permanent VC number | X.25 Virtual circuit Configuration | For PVCs only. In the network directory, the
number of the permanent virtual circuit on the remote node. |
Physical path | Point-to-Point Configuration | This is the location of the programmable serial
interface. Refer to the system documentation for your HP 3000 model
to find the physical path of the programmable serial interface (PSI)
card. |
Physical path of LANIC | LAN Configuration | This is the location of the LANIC device adapter
card. Run IOMAP utility to determine the physical path for the LAN
adapter. Refer to the system documentation for your HP 3000 model
for further details regarding physical path. |
Physical path of device adapter | FDDI Configuration | This is the location of the FDDI device adapter
card. Run IOMAP utility to determine the physical path for the FDDI
adapter. Refer to the system documentation for your HP 3000 model
for further details regarding the physical path. |
Physical path of Token Ring device adapter | Token Ring Configuration | This is the location of the Token Ring device
adapter card. Run IOMAP utility to determine the physical path for
the Token Ring adapter. Refer to the system documentation for your
HP 3000 model for further details regarding physical path. |
Physical path of device adapter | 100VG-AnyLAN Configuration | This is the location of the 100VG-AnyLAN device
adapter card. Run IOMAP utility to determine the physical path for
the 100VG-AnyLAN adapter. Refer to the system documentation for
your HP 3000 model for further details regarding the physical path. |
Link Speed | 100VG-AnyLAN Configuration | This is the desired speed at which link should
operate. Valid values are 10 or 100 MBit/sec. |
Full Duplex Mode | 100VG-AnyLAN Configuration | If the link is operating in 10 MBit/sec, should
full duplex mode be used. This is based on the capability of the
hub/switch to which the adapter is connected. |
Physical path of device adapter | 100Base-T Configuration | This is the location of the 100Base-T device
adapter card. Run IOMAP utility to determine the physical path for
the 100Base-T adapter. Refer to the system documentation for your
HP 3000 model for further details regarding the physical path. |
Use Auto-Negotiation | 100Base-T Configuration | Should the adapter attempt to auto-negotiate
with the hub/switch. Use this feature ONLY if the hub/switch supports
this feature also. |
Link Speed | 100Base-T Configuration | This is the desired speed at which link should
operate. Valid values are 10 or 100 MBit/sec. This field is only
needed if auto-negotiation is not used. |
Full Duplex Mode | 100Base-T Configuration | Should full duplex mode be used. This is based
on the capability of the hub/switch to which the adapter is connected.
This field is only needed if auto-negotiation is not used. |
Proxy node | LAN Configuration | The proxy field is optional. Enter Y
(yes) only if your network has internetworks (networks with gateways)
or non-HP nodes. Establishing a proxy node is a way of placing node
name and address mapping information in a single location. For more
information, see the configuration chapter for LAN link. |
Remote IP address | X.25 Virtual Circuit Configuration | In the network directory, the IP address of
each node listed in the remote node name field. |
Remote node name | X.25 Virtual Circuit Configuration | In the network directory, the name of each
remote X.25 node on the network |
Remote X.25 address | X.25 Virtual Circuit Configuration | For SVCs only. In the network directory, the
X.25 address of the remote host for X.25 public data networks or
private networks. |
Security class | X.25 Virtual Circuit Configuration | For SVCs only. In the network directory, the
security to be applied for connection establishment with the remote
node. |
Speed | Point-to-Point Configuration | The line transmission speed is given in bits
per second. For direct connect the value must be supported by the
cable. Values are 1200, 2400, 4800, 9600, 19200, 38400, 56000, and
64000. The default is 56000. |
Type | Point-to-Point Configuration | Enter DD (direct dial) if you always want to
call the same host over a dial link. If you choose DD the remote
host does not have to be adjacent and other nodes can be accessed
through the remote host. Enter SD if you want to call more than
one adjacent remote node over a dial link without reconfiguring.
If you choose SD, no other remote nodes can be accessed through
the remote host; it is an end point in the connection. Enter DC
if the link is a leased line, private line, or other non-switched
link. |