| 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 |
Hi,
I'm not sure if you already knew about this when the DECnet_IV AM was
developed and it was decided not to handle this or what. But I figured I'd
throw it out just in case you weren't aware of the LINE SPEED attribute.
MCC puts LINE SPEED in DNS today. Therefore the node must be registered
and the LINE SPEED set. But if the clock is set to internal on the device
then line speed is set and seen using NCP/NICE but MCC is still unaware
of the attribute unless manually set in DNS. Example below. Was DNS the
desired approach even if LINE SPEED is set on the router?
best regards,
brad...
...........................................................
Line Volatile Characteristics as of 30-MAY-1991 13:22:23
Line = SYN-0
Counter timer = 65000
Device = SYN-0
Receive buffers = 256
Controller = normal
Duplex = full
Protocol = DDCMP point
Clock = internal
Service timer = 20000
Retransmit timer = 5000
Line speed = 2000000
...........................................................
Node4 2.1018 Line syn-0
AT 30-MAY-1991 13:24:00 Characteristics
Examination of Attributes shows:
Counter Timer = 65000 Seconds
Device = SYN-0
Receive Buffers = 256
Controller = Normal
Duplex = Full
Protocol = DDCMP Point
Clock = Internal
Service Timer = 20000 Milliseconds
Retransmit Timer = 5000 Milliseconds
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1074.1 | Oops, we meant to return it if the device did | TOOK::CAREY | Fri Jun 14 1991 11:50 | 37 | |
Brad,
Sorry to overlook this note. I was on the road when you put it in,
and trying to catch up I admit to having scanned a lot of these rather
quickly.
We're aware that MCC only sets the line speed in the MIR, and doesn't
physically try to set it. We felt that this covered *most* cases and
would give us good coverage of the technology. Seemed like a
reasonable tradeoff.
However, if a line returns its speed (and some do, as you point out) we
intended to return that to the user. That there is a bona fide bug.
Oops. I'll get a QAR into MCC_INTERNAL, and we'll make sure that we
can return the line speed on a show if the entity returns it to us.
For returning line speed, our intended algorithm is this:
1) Get the line's characteristics.
2) Check to see if the Line Speed is already there. If it is,
return that.
3) If the Line Speed isn't there, then check to see if the line
speed is being maintained in the MIR (DNS). If it is, then
add that line speed in as a characteristic.
4) If the line speed isn't in the MIR, and the line is a CSMA/CD
(Ethernet) line, then insert the default line speed of 10 Mbits.
So, not showing the line speed for these devices that return it
explicitly is a bug. Thanks for getting this to us.
-Jim Carey
| |||||
| 1074.2 | >>> line speed <<< | KITFOX::BALL | Wed Jul 15 1992 12:30 | 21 | |
Hi -
( 1 ) This has been fixed. The DNA4-AM presently does the following:
( 1 ) checks to see if the line speed was returned from the
entity.
if it was returned the DNA4-AM returns that value to
the user.
( 2 ) if the value was not returned the DNA4-AM returns the
value of 10 meg if this is an ethernet line.
( 3 ) all other lines including the ethernet lines can also
be set by the user via:
MCC> set node4 foo line line-n line speed line_speed_value
( 4 ) to see this value the following commands will work:
MCC> show node4 foo line line-n line speed
MCC> show node4 foo line line-n all char
- darryl
| |||||