Ref: 99980055
Title: Network Management Hints
Date: 12/1/85

Copyright 3Com Corporation, 1991.  All rights reserved.

Network Map

The SHow NetMap Long command displays the Ethernet addresses
and software version of the Bridge Communications Servers
that reside on the same network.  The following sample
displays the SHow NetMap Long command on the NCS/150 in an
XNS environment.

                     NETWORK &00003140 MAP

 0-%08000200027E SW/1-HSM     12000    1-%080002003471 SW/1-NCS
 3-%080002002774 SW/100-A/BSC 15010  ***-%080002006068 SW/100-A/
 5-%080002005877 SW/100-A/BSC 15010  ***-%080002005884 SW/100-A/
 7-%080002005569 SW/100-A/BSC 15010    8-%080002005875 SW/100-A/
 9-%080002003185 SW/100-A/BSC 15010   10-%080002003519 SW/4
11-%080002006559 SW/100-A/BSC 15010   12-%080002000807 SW/1-A/BSC
13-%080002001952 SW/1-HSM     12011   14-%080002005868 SW/100-A/
16-%080002000706                      17-%080002000457 SW/1-A/BSC/
18-%080002002137 SW/100-A/BSC 15010   19-%080002000A6C SW/1-A/BSC/
20-%080002000017                     ***-%080002003589 SW/4
22-%080002001695 SW/1-A/BSC/S 20010   23-%08000300003A SW/1-A/BSC
24-%080002000405 SW/100-A/BSC 15010   25-%08000200029D SW/100-A/B
26-%080002000B38 SW/100-A/BSC 15010   27-%080002005578 SW/100-A/B
28-%080002004009 SW/100-A/BSC 15010   29-%08000200066B SW/100-A/
30-%080002000B26 SW/150-NCS   10006   31-%080002002467 SW/100-A/B
32-%080002006069 SW/100-A/BSC 15010

***# inactive nodes***

Three asterisks appear next to a server address to indicate
that the server is inactive.  In this case, the server should
be checked for hardware or software failure and rebooted.  An
inactive server remains on the network for three days.  If it
is not rebooted within this time, the server is eliminated
from the netmap table.

If no software version is listed, the unit is running old
software and should be upgraded.  Note that the netmap only
displays servers on the local Ethernet; it does not display
servers on the remote Ethernet that are separated by
gateways.


Statistics

The SHow STATisticS Sample command is used to display
statistics information for a particular server.

BUSIEST SAMPLES OF THE DAY-------------------------------
TOTAL    CPU(%)   BUF(%)   MAX#SN   PKT/S   BYTE/S   AcuDskEr
VALUE    13       42       4        18      967      0
TIME     0830     1345     0845     0832    0830
PORT  MAX#SN  PKT/S  BYTE/S ERROR   PORT  MAX#SN  PKT/S BYTE/S  E
0     0       0      0      0       1     2       18    967     0
2     1       11     341    0       3     1       8     507     1
4     1       10     965    0       5     0       0     0       0
6     0       0      0      0       7     0       0     0       0
8     0       0      0      0       9     0       0     0       0
10    0       0      0      0       11    0       0     0       0
12    0       0      0      0       13    0       0     0       0

Ethernet  PORT  PKT/S  BYTE/S  ERROR: CRC  ALN  2SHT 2LON COLL

00003140        25     2171           280  3270 0    0    66

This display is in three parts.  The first part shows overall
statistics for the Communications Server.  The second aprt
shows statistics for the server's port.  The third part shows
statistics for the server's Ethernet interface.

Following is a brief description of each of the fields.

OVERALL COMMUNICATIONS SERVER

For each item, the highest value during the period measured
is displayed along with the time at which the peak value
occurred.

*   CPU (%) indicates the peak percentage of CPU time being
used during the specified time.

*   BUF (%) indicates the peak percentage of memory that the
system consumed during the specified time.

*   MAX#SN indicates the maximum number of sessions used in
the system during the specified time.

*   PKT/S indicates the maximum number of packets
transmitted and received per second during the specified time.
This information is measured through all of the protocol
layers.

*   BYTE/S indicates the maximum number of bytes transmitted
and received per second during the specified time.  This
information is measured through all of the protocol
layers.

*   AcuDskEr indicates the total disk errors that occurred
since the system was booted.

Individual Ports

*   The first and sixth columns list the ports on the
Communications Server.

*   The second and seventh columns list the maximum number of
active sessions per port.

*   The third and eighth columns list the maximum number of
packets transmitted and received per second for the
particular port during the specified time.  This
information is measured through all of the protocol
layers.

*   The fourth and ninth columns list the maximum number of
bytes transmitted and received per second for the
particular port during the specified time.  This
information is measured through all of the protocol
layers.

*   The fifth and tenth columns list the number of errors
(i.e., frame or parity errors for an asynchronous port,
and CRC, SDLD, or HDLC errors for a synchronous port)
that occurred for the particular port during the
specified time.

Ethernet Interface

*   The Ethernet Port field indicates the Ethernet address of
the server.

*   PKT/S indicates the maximum number of packets per second
transmitted and received by the Ethernet driver.

*   BKT/S indicates the maximum number of bytes per second
transmitted and received by the Ethernet driver.

*   CRC lists the number of packets received during the time
specified that had check sum eerrors.  If a check sum
error occurs, the packet is discarded.

*   ALN lists the number of packets with alignment error
received during the time specified.

*   2SHT lists the number of packets received during the time
specified that were smaller than 60 bytes.

*   2LON lists the number of packets received during the time
specified that were larger than 1500 bytes.

*   COLL lists number of collisions that were detected on the
network during the specified time.

The CRC, ALN, 2 SHT, and 2LON fields should not indicate
numbers higher than 100.  If they do, the Ethernet
controller and transceiver should be checked.


Audit Trail

One of the most important features of the NCS/1 and NCS/150
is the Audit Trail.  The Audit Trail records all session
capacity and activity occurring on the network.  This
information assists the network manager in analyzing network
problems.  Following is a sample of the NCS/1's Audit Trail
and an interpretation of each line of the Audit Trail.

                 Sample of NCS/1 Audit Trail

Date & Time

11/02 05:50:20 &3140%080002000071     BR%080002000077        cs1x
11/02 05:55:00 &3140%080002000071     BC%080002000077     OK
11/02 05:57:21 &3140%080002004009!013 DC%08000200003a!018 NR 44 4
11/02 06:45:57 &3140%080002000A6C!012 CD%08000200015e!006
11/02 06:45:56 &3140%08000200015E!128 RP 8 1
11/02 07:16:42 &3140%0800020001FB!003 CF%08000200027e!128 BU
11/01 07:16:43 &3140%080002000457!004 DQ%08000200027e!078 QY
11/02 07:16:44 &3140%08000200003A!000 LS
11/02 07:16:45 &3140%080002003471     EU 5 1 0 2 3 2 3 0 3 3
11/02 07:16:47 &3140%080002000A6C     ER210
11/02 07:16:48 &3140%080002000B38     EE105

* BR (Boot Request): The client server (destination device)
requested bootstrap service from the Network Control Server
(initiating device).  The file name (cs1x) following the
destination device's address indicates the name of the
particular file that has been loaded from the Network Control
Server into the client server.

* BC (Boot Completed): The Network Control Server indicates
that the bootstrap has been successfully completed.  This
completion is indicated by the OK message following the
destination device's address.  If booting is not completed
successfully, this record type may include explanatory codes
such as AB (the boot process was aborted by the specified
client server), FS (the requested boot was unsuccessful
because of a missing or inaccessible boot file), or SE
(asynchronous parity error, HDLC or SDLC errors, SIO
interrupt errors).

If another Boot Request appears immediately following the
Boot Completed, this indicates that although the NCS
completed the boot successfully, the file was not loaded
properly to the client server.

* DC (Disconnection): When the initiating device was
disconnected from the destination, it received a no response
message as indicated by the NR explanatory code.  This
indicates that the destination server was no longer
responding to the network.  The first number (44) following
the NR indicates the duration of the session in seconds.  The
second number (422) indicates the number of bytes received.
The third number (13) indicates the number of packets
received.  The fourth number (12) indicates number of bytes
transmitted.  The fifth number (9) indicates the number of
packets transmitted.

In addition to NR, a disconnect record type may include other
explanatory codes such as AD (the session was inactive longer
than the interval specified by the AUToDisconnect parameter
of the destination port), OK (the session disconnected
normally), or UE (the disconnection was caused by an
unrecognized condition).

* CD (Connection): The initiating device established a
connection to the destination device.

* RO (Rotary):  This record type is logged whenever a rotary
port is accessed.  The record also shows the utilizations of
the rotary at the time of connection.  Out of eight ports in
the rotary 128, 1 port is currently in use.

* CF (Connection Failed): When the initiating device attempted
to establish a connection to the destination device, the
connection failed because all of the ports in the destination
rotary were busy.  This is indicated by the BU code.  Other
explanatory codes for this record type include BA (the port
number in the specified destination address was invalid), DA
(the requested destination port did not respond to a
connection request), IC (a remote server is running a version
of the communication software that is incompatible with the
version running on the report server), NR (destination server
is not responding to the network), or UE (the disconnection
was caused by an unrecognized condition).

* DQ (Connection Dequeued): When the initiating device removed
itself from the queue, it received a queue timeout message
because the initiating device failed to complete a queued
connection within five minutes.  If the connection is
dequeued successfully, the OK message will appear.

* LS (Listen): The initiating device entered listen mode.

* EU (Ethernet Utilization): The numbers following the EU
message indicate the percentage of the Ethernet being
utilized at 10 minute intervals for the last 90 minutes.  For
example, reading from right to left in the above entry for
07:16:45: at 07:16, .3 percent of the Ethernet is being
utilized; at 07:06, .3 percent is being utilized; at 06:56,
0 percent is being utilized; and so on.  Note that only the
NCS/1 logs Ethernet utilization.

* ER (Excessive Retransmission): Every hour, the server reports
200 or more retransmissions of Sequenced Packet Protocol
(SPP).  In this example, the number (210) following the ER
message indicates that 210 excessive retranmissions hve
occurred at this time.

* EE (Ethernet Error): Every hour, the server reports 100 or
more Ethernet errors such as Cyclic Redundancy Check (CRC),
alignment, packet too short, packet too long, and collision
errors.  In this example, the number (105) following the EE
message indicates that 105 Ethernet errors have occurred at
this time.

The Audit Trail for the NCS/150 has record types and explanatory
codes similar to those for the NCS/1 except that the NCS/150's
Audit Trail does not show the Ethernet Utilization (EU).

The Audit Trail for the NCS/150 with TCP/IP has similary record
types and explanatory codes but the initiating and destination
devices' Ethernet addresses are replaced by Internet addresses.
The NCS/150 with TCP/IP does not show the Ethernet Utilization
record type.  The following table illustrates a sample of the
NCS/150 with TCP/IP Audit Trail.

      Sample of the NCS/150 with TCP/IP Audit Trail

Date & Time  Initiating Device   Record  Destination  Explanatory
                                   Type     Device       Code

01/08 15:53:40 192.009.200.071       BR  192.009.200.077
01/08 15:54:25 192.009.200.071       BC  192.009.200.077   OK
01/08 15:59:25 192.009.200.077!004   CD  192.009.200.004
01/08 15:50:36 192.009.200.077!004   DC  192.009.200.004   OK
01/08 16:01:01 192.009.200.071       BR  192.009.200.076
01/08 16:01:48 192.009.200.071       BC  192.009.200.076   OK
01/08 16:09:10 192.009.200.071       BR  192.009.200.075
01/08 16:09:54 192.009.200.071       BC  192.009.200.075   OK
01/08 16:18:49 192.009.200.075! 128  RO  14 0
01/08 16:18:49 192.009.200.075! 020  CD  ! 000
01/08 16:19:26 192.009.200.075! 020  DC  ! 000             OK
01/08 16:22:19 192.009.200.075! 128  RO  14 4
01/08 16:22:19 192.009.200.075! 020  CF  ! 128             DA
01/08 16:22:57 192.009.200.075! 004  LS
01/08 16:23:01 192.009.200.075! 006  LS
01/08 16:23:07 192.009.200.075! 005  LS
01/08 16:23:12 192.009.200.075! 007  LS
01/08 16:32:43 192.009.200.075! 128  RO  14 2
01/08 16:32:43 192.009.200.075! 020  CD  !005
01/08 16:33:37 192.009.200.075! 128  RO  14 3
01/08 16:33:37 192.009.200.075! 020  CD  !006
01/08 16:35:42 192.009.200.075! 128  RO  14 4
01/08 16:35:42 192.009.200.075! 020  CD  !007
01/08 16:39:12 192.009.200.075! 128  RO  14 5


Connection Oriented Network Management

In SW/1-A/BSC/SDLC Version 20000 or later and SW.100-A/BSC
Version 15000 or later of the CS/1 and CS/100, an additional
form of network management is supported called Connection

Oriented Network Management.  This feature allows XNS and
Bridge VTP compatible products such as a PC running EtherTerm
to access Bridge's network management facilities.  Access to
this feature is through a conection to port 136 in the CS/1
or CS/100.  Furthermore, macros can be defined remotely via
this port.






