[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DECmcc user notes file. Does not replace IPMT. |
Notice: | Use IPMT for problems. Newsletter location in note 6187 |
Moderator: | TAEC::BEROUD |
|
Created: | Mon Aug 21 1989 |
Last Modified: | Wed Jun 04 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 6497 |
Total number of notes: | 27359 |
421.0. "DECmcc V1.0 and V1.1 functions" by DELNI::HEBENSTREIT () Fri Oct 19 1990 09:06
DECmcc functions
----------------
The question has been asked, what functions can be performed
using DECmcc V1.0? V1.1? and, the modules orderable separately?
The answers to those questions are summarized below:
Here's what can be done using DECmcc BMS V1.0:
---------------------------------------------
From the Command line and forms user interface you can:
Invoke NCL commands (SHOW, SET, TEST, etc) for:
DECnet Phase IV
LANBridge 100, 150, and 200
Using Registration you can make entities known to DECmcc,
store and retrieve reference information about those
entities, and display a list of entities know to DECmcc.
You can create and enable Alarm rules to:
Identify DECnet circuit substate problems
Determine node reachability
Determine area reachability
Identify DECnet line problems
Determine DECnet/VAX traffic loads
Identify DECnet/VAX throughput problems
Ensure end nodes are not configured as routers
Identify an unreachable bridge
Identify a bridge operating as an LTM listener
Identify spanning tree changes
Identify bridge resets
Identify bridge line problems
Identify a heavily used bridge line
Identify a bridge memory problem
and other rules you define.
(The rules specified above are included in
an Appendix to the Alarms Use Manual.)
Here's what can be done using DECmcc BMS and the optional SNMP AM:
-----------------------------------------------------------------
Invoke NCL commands to SHOW and SET all MIB 1
variables maintained by any conformant SNMP
agent, as defined in RFC 1066.
You can create and enable Alarm rules on any of
the MIB 1 variables.
Here's what can be done using DECmcc BMS and the optional DECnet Phase IV
-------------------------------------------------------------------------
Diagnosis FM:
------------
Diagnose the following problems (mostly with VMS nodes):
circuit on-starting
circuit on-synchronizing
insufficient resources at remote node
line open error
line synchronization lost
login information invalid at remote node
network partner exited
object unknown at remote node
remote node unreachable
Invoke the Path trace utility
Here's what additional functions you can do using DECmcc BMS V1.1:
-----------------------------------------------------------------
Invoke commands with the Iconic Map user interface
Using Domains you can divide a network into logical chunks
Using Historian you can store attribute data in the MIR
You can obtain Performance statistics (SHOW ENTITY STAT) for:
DECnet Phase IV statistics
NODE4
REMOTE NODE
LINE
CIRCUIT
DECnet Phase V statistics
NODE
ROUTING
ROUTING PORT
ROUTING CIRCUIT
DDCMP LINE
DDCMP LINE LOGICAL STATION
HDLC LINE
HDLC LINE LOGICAL STATION
CSMACD STATION
BRIDGE LINE (LAN100,LAN150,LAN200)
You can set Alarm rules on statistics (ie thresholding)
Using Export you can store attribute/stats data in RDB
You can run canned reports for DECnet IV and V (via
DATATRIEVE on RDB) for:
DECnet Phase IV reports
NODE Traffic
NODE Error
LINE Traffic
LINE Error
CIRCUIT Traffic
Summary Traffic
Summary Error
CIRCUIT Utilization graph
DECnet Phase V reports
NODE Traffic
NODE Error
LINE Traffic
LINE Error
Summary Traffic
Summary Error
LINE Utilization graph
You can also write your own reports for the data
that Export stores in Rdb.
T.R | Title | User | Personal Name | Date | Lines |
---|
421.1 | Minor nits... | CHRISB::BRIENEN | DECmcc Bridge|Station Management. | Mon Nov 19 1990 12:03 | 6 |
| 1. Performance Statistics are available for Bridge Lines, but Bridge Lines
are not part of DECnet Phase V statistics.
2. Ethernet (Station) AM provides additional V1.0 functionality not listed,
such as path testing using Ethernet V2.0 and IEEE802 standards, and MOP
datalink counters from DECnet (and non-DECnet) entities.
|