[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

5927.0. "DECnis circuit to DECBrouter" by SPANKY::THOMPSON () Thu Mar 31 1994 09:38

    Hello
    from MCC 1.3, VMS 5.5-2, DECNET IV on a vaxstation 4000-60, I am trying
    to get circuit utilization and exporting  from a DECnis running v.2.2.4
    to a DECBrouter running v.9.14. The DECnis has two circuits configured,
    Port 2, W622-4-0 is a 64k HDLC circuit connected to another DECnis and
    I can get stats and exporting from that. From the iconic map the
    circuit can be found under child entity HDLC- LINK- W622-4-0 -LOGICAL
    STATION- LOGICAL STATION 622-4-0
    The circuit in question is in Port 3 W622-4-1 and is  56k CHDLC circuit
    connected to the DECBrouter.
    From the iconic map I can not find any child entity to get circuit
    stats.
    Is it because its configured as CHDLC going to the DECBrouter running
    CISCO software? If so will this be fixed in future DECnis or DECbrouter
    software?
    
    any help would be appreciated
    brian

T.R Title User Personal
Name Date Lines

5927.1 MARVIN::COBB Graham R. Cobb (Routing), REO2-G/C2, 830-3917 Thu Apr 21 1994 13:52 11

T.R	Title	User	Personal Name	Date	Lines
5927.1		MARVIN::COBB	Graham R. Cobb (Routing), REO2-G/C2, 830-3917	`Thu Apr 21 1994 13:52`	11
	This problem is an MCC problem, not a DECNIS or DECbrouter problem. 1) MCC has not issued a new dictionary recently. The old dictionary doesn't include CHDLC so those entities are not usable from MCC. 2) MCC Performance analysis is not dictionary driven: it requires code to be written for every attribute of every entity which is involved in performance analysis. There are no plans that I know of for MCC PA to be updated to cope with CHDLC links. Graham

This problem is an MCC problem, not a DECNIS or DECbrouter problem.

1) MCC has not issued a new dictionary recently.  The old dictionary doesn't
include CHDLC so those entities are not usable from MCC.

2) MCC Performance analysis is not dictionary driven: it requires code to be
written for every attribute of every entity which is involved in performance
analysis.   There  are  no  plans that I know of for MCC PA to be updated to
cope with CHDLC links.

Graham