| 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 |
I have a problem with the "ACTUAL SPEED" parameter on 2 DECNIS 600.
I think that this parameter is used by DECMCC to calculate line utilization.
"TNNISA" is linked to "HGNISA" by an HDLC line between 2 W618 boards.
These 2 DECNIS are in 2 different european countries and runs V2.0 of
DECNIS software.
The "ACTUAL SPEED" (detected by the DECNIS) is 0.
So i can't get DECMCC statistics about line utilization as you can see
in the MCC log file below.
Is there any pb with line speed detection on the W618 board?
I tried to set "LINE SPEED" but without any success for line
utilization with DECMCC.
What is wrong (in the setting of the line or ...)?
Any idea ?
Regards,
Bernard THOMAS
P.S. I posted this note in DECNIS conference (note 680).
MCC LOG FILE:
=============
sho node tnnisa mod connect line * all att
!
!Node LOCAL_NS:.tnnisa Modem Connect Line W618-3-0
!AT 31-MAR-1993 10:47:25 All Attributes
!
! Name = W618-3-0
! UID = F5AEF900-1353-11CC-8000-08002B204780
! State = On
! Interface State = Full Enabled
! Actual Speed = 0 BPS <============================
! Loopback Mode = Null
! Interface Type = V35
! Modem Type = ""
! Device Availability = Device Present
! Request to Send = Asserted
! Clear to Send = Asserted
! Data Set Ready = Asserted
! Data Terminal Ready = Asserted
! Carrier Detect = Asserted
! Signalling Rate Selector = Not Applicable
! Signalling Rate Indicator = Not Applicable
! Ring Indicator = Not Applicable
! Remote Loopback = Not Applicable
! Local Loopback = Not Applicable
! Test Mode = Not Applicable
! Creation Time = 25-FEB-1993 23:01:01.20
! Losses of Clock = 0
! Cable Faults = 0
! Times DCE Not Ready = 2559
! Transmit Enable Timeouts = 0
! Losses Of Carrier = 73
! Rate Fallbacks = 0
! Test Indications = 0
! Framing Errors = 0
! Times Cable Detected = 1
! Device Errors = 0
! Times Reset = 1639
! Communications Port = W618-3-0
! Connection Type = NonSwitched
! Communications Mode = Synchronous
! Duplex = Full
! Profile = "NORMAL"
! Modem Control = Full
! Modem Options = { }
! Encoding = Normal
! Clock = External
! Speed = 64000 BPS
! Alternate Speed = 0 BPS
! Rate Select = High
! Maximum Enable Transmit Timer = 2000 Milliseconds
! Suppress Test Indicator = True
! Transmit Holdoff Timer = 0 MILLISECONDS
! Carrier Loss Timer = 15000 MILLISECONDS
! Minimum DTR Deassertion Timer = 2000 MILLISECONDS
! Maximum Disable Transmit Timer = 500 MILLISECONDS
! Call Accept Timer = 500 MILLISECONDS
! Successful Call Indication Timer = 30 SECONDS
! Maximum DSR Deassertion Timer = 5000 MILLISECONDS
!
sho node tnnisa hdlc link W618-3-0 log station w618-3-0 all statis
!
!Node LOCAL_NS:.tnnisa HDLC Link W618-3-0 Logical Station w618-3-0
!AT 31-MAR-1993 10:48:42 Statistics
!
!Examination of attributes shows:
! Duration = 59 Seconds
! Outbound Utilization = -- Invalid Value <================
! Inbound Utilization = -- Invalid Value <================
! Average Outbound PDU Size = 182 Octets
! Average Inbound PDU Size = 150.4 Octets
! Outbound PDU Rate = 0.15 pdus/sec
! Inbound PDU Rate = 0.17 pdus/sec
! Outbound Octet Rate = 27.76 octets/sec
! Inbound Octet Rate = 25.49 octets/sec
! Count of Outbound Octets = 1638
! Count of Inbound Octets = 1504
! Count of Outbound PDUs = 9
! Count of Inbound PDUs = 10
! Count of Acknowledge Timeouts = 0
! Count of Negotiation Failures = 0
! Count of Rejects Received = 0
! Count of Rejects Sent = 0
! Count of FRMRs Received = 0
! Count of FRMRs Generated = 0
! Count of Retransmission Requests Sent = 0
!Count of Retransmission Requests Received = 0
! Count of Polls Received = 0
! Count of XIDs Received = 0
!
sho node hgnisa mod connect line * all att
!
!Node LOCAL_NS:.hgnisa Modem Connect Line W618-3-0
!AT 31-MAR-1993 10:48:59 All Attributes
!
! Name = W618-3-0
! UID = 9CEAD920-29C3-11CC-8000-08002B201030
! State = On
! Interface State = Full Enabled
! Actual Speed = 0 BPS <===========================
! Loopback Mode = Null
! Interface Type = RS423-V24
! Modem Type = ""
! Device Availability = Device Present
! Request to Send = Asserted
! Clear to Send = Asserted
! Data Set Ready = Asserted
! Data Terminal Ready = Asserted
! Carrier Detect = Asserted
! Signalling Rate Selector = Not Asserted
! Signalling Rate Indicator = Asserted
! Ring Indicator = Asserted
! Remote Loopback = Not Asserted
! Local Loopback = Not Asserted
! Test Mode = Not Asserted
! Creation Time = 26-MAR-1993 12:15:41.49
! Losses of Clock = 0
! Cable Faults = 0
! Times DCE Not Ready = 2253
! Transmit Enable Timeouts = 0
! Losses Of Carrier = 21
! Rate Fallbacks = 0
! Test Indications = 0
! Framing Errors = 0
! Times Cable Detected = 1
! Device Errors = 0
! Times Reset = 29
! Communications Port = W618-3-0
! Connection Type = NonSwitched
! Communications Mode = Synchronous
! Duplex = Full
! Profile = "NORMAL"
! Modem Control = Full
! Modem Options = { }
! Encoding = Normal
! Clock = External
! Speed = 0 BPS
! Alternate Speed = 0 BPS
! Rate Select = High
! Maximum Enable Transmit Timer = 2000 Milliseconds
! Suppress Test Indicator = True
! Transmit Holdoff Timer = 0 MILLISECONDS
! Carrier Loss Timer = 15000 MILLISECONDS
! Minimum DTR Deassertion Timer = 2000 MILLISECONDS
! Maximum Disable Transmit Timer = 500 MILLISECONDS
! Call Accept Timer = 500 MILLISECONDS
! Successful Call Indication Timer = 30 SECONDS
! Maximum DSR Deassertion Timer = 5000 MILLISECONDS
!
sho node hgnisa hdlc link W618-3-0 log station w618-3-0 all statis
!
!Node LOCAL_NS:.hgnisa HDLC Link W618-3-0 Logical Station w618-3-0
!AT 31-MAR-1993 10:50:13 Statistics
!
!Examination of attributes shows:
! Duration = 59 Seconds
! Outbound Utilization = -- Invalid Value <=================
! Inbound Utilization = -- Invalid Value <=================
! Average Outbound PDU Size = 202.91 Octets
! Average Inbound PDU Size = 137.09 Octets
! Outbound PDU Rate = 0.19 pdus/sec
! Inbound PDU Rate = 0.19 pdus/sec
! Outbound Octet Rate = 37.83 octets/sec
! Inbound Octet Rate = 25.56 octets/sec
! Count of Outbound Octets = 2232
! Count of Inbound Octets = 1508
! Count of Outbound PDUs = 11
! Count of Inbound PDUs = 11
! Count of Acknowledge Timeouts = 0
! Count of Negotiation Failures = 0
! Count of Rejects Received = 0
! Count of Rejects Sent = 0
! Count of FRMRs Received = 0
! Count of FRMRs Generated = 0
! Count of Retransmission Requests Sent = 0
!Count of Retransmission Requests Received = 0
! Count of Polls Received = 0
! Count of XIDs Received = 0
!
sho node tnnisa all attr
!
!Node LOCAL_NS:.tnnisa
!AT 31-MAR-1993 10:50:24 All Attributes
!
! Name = 08-00-2B-30-90-DB-E3-85-79-65-00-83-96
! -00:.TN.NISA
! Address = {{{Network Management -- CMIP or NICE,
! none}
! {DNA Phase V Session Control,
! Network Management}
! {NSP Transport,
! Session Control}
! {OSI network or DNA Routing,
! 39:840:FF-11-36-00-00-00-10-00-00-12:AA-00-04-00-FF-4B:20}}}
! UID = 86D1FE80-4D2C-11CB-8002-08002B204780
! State = On
! Functions Enabled = {Address Watcher,CMIP Listener}
! ID = 08-00-2B-20-47-80
! Last Reboot Reason = Software Crash
! Creation Time = 18-JUN-1992 18:59:54.60
! Renames = 1 Renames
! Changes of ID = 0 Changes
! IDROM Check Failures = 0 Failures
! Changes of Address = 8 Changes
! Script Exceptions = 0 exceptions
! Times Rebooted = 25 times
! Version = T5.0.3
! Maximum Listeners = 0
! Listener Template = ""
! Location = -- Attribute Not Available
! Implementation Desc = -- Attribute Not Available
! Responsible Person = -- Attribute Not Available
! Phone Number = -- Attribute Not Available
! MAIL Account = -- Attribute Not Available
! Remarks = -- Attribute Not Available
! Text File = -- Attribute Not Available
!
sho node hgnisa all attr
!
!Node LOCAL_NS:.hgnisa
!AT 31-MAR-1993 10:50:38 All Attributes
!
! Name = LOCAL_NS:.
! Address = {{{Network Management -- CMIP or NICE,
! none}
! {DNA Phase V Session Control,
! Network Management}
! {NSP Transport,
! Session Control}
! {OSI network or DNA Routing,
! 39:840:FF-11-36-00-00-00-10-00-00-3A:AA-00-04-00-07-E8:20}}}
! UID = 84AA36C0-08CC-11CC-8002-08002B201030
! State = On
! Functions Enabled = {Address Watcher,CMIP Listener}
! ID = 08-00-2B-20-10-30
! Last Reboot Reason = Software Crash
! Creation Time = 12-FEB-1993 13:26:17.90
! Renames = 0 Renames
! Changes of ID = 0 Changes
! IDROM Check Failures = 0 Failures
! Changes of Address = 18 Changes
! Script Exceptions = 0 exceptions
! Times Rebooted = 30 times
! Version = T5.0.3
! Maximum Listeners = 0
! Listener Template = ""
! Location = -- Attribute Not Available
! Implementation Desc = -- Attribute Not Available
! Responsible Person = -- Attribute Not Available
! Phone Number = -- Attribute Not Available
! MAIL Account = -- Attribute Not Available
! Remarks = -- Attribute Not Available
! Text File = -- Attribute Not Available
!
us logging off
!
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4815.1 | TOOK::PURRETTA | Mon Apr 05 1993 11:04 | 3 | ||
I would find out why the line speed is being reported as zero
before going any further. I just tried this command to a wanrouter 500
and got back some real numbers.
| |||||
| 4815.2 | Two fold problem.... | LICAUS::LICAUSE | Al Licause (264-4780) | Thu Apr 08 1993 09:13 | 37 |
This turns out to be a two fold problem. To begin with, both the DECnis and WANrouter 500 engineering groups have openly admitted that their calculation of actual line speed is not very accurate, which is a vast understatement. If you twiddle with the routers, such that you put the various lines into and outof loopback modes, you can get them to report different values for the same line. The line speed of 0 appears to be quite common, so that's why I say this is a vast understatement of inaccuracy. Since this value is apparently a fixed part of the PA line utilization algorythm, it must be given and given accurately in order for the graph or statistic to be accurate or event work, in the case of a zero value. So the first thing that has to happen is for router engineering to fix the problem. They must report an accurate figure for this value or not report it at all. !!! INACCURATE INFORMATION IS WORTHLESS !!! The second part of the problem is that DECmcc never gives the user a chance to input a line speed. So DECmcc engineers.......what we need is the ability to input the line speed for this calculation given the fact that our routers are not to be trusted! If one is attempting to use a third party router, this opens a whole new series of questions.....namely do they report the same information with the same label and is their information accurate. In such cases, DECmcc must provide a method for allowing the user to input an accurate line speed. Al | |||||
| 4815.3 | MARVIN::COBB | Graham R. Cobb, Internetworking, REO2-G/G9, 830-3917 | Thu Apr 08 1993 17:05 | 14 | |
> !!! INACCURATE INFORMATION IS WORTHLESS !!! I'm sorry, Al, that is just not true. The attribute is extremely useful for problem solving (when the hardware reports it) even if the calculation is very inaccurate. It is useful for what it was designed for: to allow you to check the line is supplying clock and to help check it is connected to the modem that you think it is. Nothing on the WANrouter 500 will ever change. For the DECNIS, the attribute will be improved in V2.2 (see the DECNIS conference). However, I agree that DECmcc should provide a way to override it. Graham | |||||
| 4815.4 | final status ? | MARS03::THOMAS | Tue Apr 13 1993 13:04 | 22 | |
repl X.mem
I noted that the pb comes from the fact that DECMCC software only gets
the line speed from the "ACTUAL SPEED" and that W618 has no support to give it.
For my customer, i am looking for a solution either from DECNIS
engineering or/and DECMCC engineering.
This customer (DOW CHEMICAL) already uses 3 DECNIS to link major sites.
He wants to manage these links and to have statistics on line utilization for
reports and alarm detections.
What is our answer (from DECNIS + DECMCC teams) that i can give
it to him:
* what final solution may we expect and when?
* what workaround may we use quickly?
Regards,
Bernard
P.S. There are other DECNIS and DECMCC opportunities in this account.
| |||||
| 4815.5 | Can the DNA5-AM optionally store the 'Actual Speed' in DNS ? | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Tue Apr 13 1993 14:46 | 9 |
The DNA-4 AM stores the Line Speed attribute in DNS ... Could the DNA-5 AM do the same thing, optionally checking DNS for this value and returning it if present .. otherwise return the Actual Speed from the decnis box. . . ? This would be transparent to PA /keith | |||||
| 4815.6 | solution = DECNIS 2.2 | MARS03::THOMAS | Wed Apr 21 1993 10:11 | 7 | |
The release 2.2 of DECNIS will fix this pb (cf notes 680.* in the
DECNIS conference). We may expect this releease for this summer, if
there is about the same amount of time between the releases 2.1 and 2.2
as the time between previous releases.
Bernard
| |||||
| 4815.7 | what about other WAN router products (250 etc...) | HERON::PATEL_A | LoLo-AQIC-I82Q-B4IP, - LMF | Wed May 05 1993 08:25 | 7 |
this is not only a problem with DECnis, it also appears on older WAN
routers. It seems that the AM supporting a lookup in DNS for a
synthesized speed would be a good idea, get the speed from the device, if
valid calculate... if no speed is sent back then use the synthesized
one....
Amrit
| |||||