| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4669.1 | another DEMFA user... | GIDDAY::DRANSFIELD | Mike Dransfield, Sydney RSSG | Tue Apr 06 1993 06:09 | 11 |
| I also have problems with a DEMFA at a customer site.
This is with MCC 1.2.3
I get a couple of errors.
on SHOW CHAR get no corresponding entity instance exists
and som messages extra info returned code 63, 62 and similar
message with SHOW COUNT but different codes.
IMPM and FCL behave differently.
What is the story?
thanks,
Mike
|
| 4669.2 | | TOOK::PURRETTA | | Tue Apr 06 1993 09:35 | 5 |
| Put a short log (example) of the request showing the problem,
preferably against a node on the enet so that I can get to it
as a reply here.
John
|
| 4669.3 | Still a problem in 1.3 SSB | STKMCC::LUND | Niklas Lund | Wed Apr 07 1993 13:10 | 138 |
| Hi,
This is a customers system, but it seems like the problem exists in 1.3 as weel.
ASTSSP> man/ent
DECmcc (V1.3.0)
MCC> show node4 ast04 line mfa-0 all stati
Node4 ast04 Line mfa-0
AT 7-APR-1993 17:50:44 Statistics
Cannot locate services required information for computing statistics.
MCC> show node4 ast04 line mfa-0 all attr
Node4 LOCAL_NS:.ast04 Line mfa-0
AT 7-APR-1993 17:51:03 All Attributes
Name = MFA-0
State = On
Substate = None
nmfoperationalState = Enabled
Seconds Since Last Zeroed = >65535 Seconds
Bytes Received = >4294967295 Bytes
Bytes Sent = >4294967295 Bytes
Data Blocks Received = 86680687 Blocks
Data Blocks Sent = 72209184 Blocks
Multicast Bytes Received = 562404354 Bytes
Multicast Blocks Received = 4481170 Blocks
Send Failure = 0 Errors
Receive Failure = 0 Errors
Unrecognized Frame Destination = 0 Errors
Data Overrun = 0 Errors
System Buffer Unavailable = 0 Errors
User Buffer Unavailable = 0 Errors
Multicast Bytes Sent = 77007943 Bytes
Multicast Blocks Sent = 672207 Blocks
Counter Creation Time = 6-APR-1993 23:38:49.32
Receive Buffers = 32
Controller = Normal
Protocol =
%MCC-E-NOENTITY, no corresponding entity instance exists
Line Speed = 100000000
Service Timer = 4000 Milliseconds
Buffer Size = 1498 Bytes
Hardware Address = 08-00-2B-24-FD-02
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
These are the attributes my customer would like to see.
MCC> spawn ncp tell ast04 show known line count
Known Line Counters as of 7-APR-1993 17:51:33
Line = MFA-0
>65534 Seconds since last zeroed
86682858 Data blocks received
4481272 Multicast blocks received
0 Receive failure
>4294967294 Bytes received
562417156 Multicast bytes received
0 Data overrun
72212201 Data blocks sent
672223 Multicast blocks sent
>4294967294 Bytes sent
77009812 Multicast bytes sent
0 Send failure
0 Unrecognized frame destination
0 System buffer unavailable
0 User buffer unavailable
>4294967294 MAC frame count
0 MAC error count
0 MAC lost count
0 Ring initializations initiated
12 Ring initializations received
0 Ring beacons initiated
0 Duplicate address test failures
0 Duplicate tokens detected
0 Ring purge errors
0 FCI strip errors
0 Traces initiated
0 Traces received
0 Directed beacons received
0 Elasticity buffer errors
0 LCT rejects
0 LEM rejects
0 Link errors
0 Connections completed
MCC> spawn ncp tell ast04 show line mfa-0 char
Line Volatile Characteristics as of 7-APR-1993 17:53:04
Line = MFA-0
Receive buffers = 32
Controller = normal
Protocol = FDDI
Service timer = 4000
Hardware address = 08-00-2B-24-FD-02
Device buffer size = 1498
Requested TRT = 8000
Valid transmission time = 2600
Restricted token timeout = 1000
Ring purger enable = on
Echo data = 55
Echo length = 1
MCC> spawn ncp tell ast04 show line mfa-0 status
Line Volatile Status as of 7-APR-1993 17:53:14
Line = MFA-0
State = on
Negotiated TRT = 99840
Duplicate address flag = unknown
Upstream neighbor DA flag= unknown
Ring purger state = off
Ring error reason = no error
Neighbor PHY type = A
Link error estimate = 15
Reject reason = none
/Niklas
|
| 4669.4 | When is the demfa going to be supported? | GIDDAY::DRANSFIELD | Mike Dransfield, Sydney RSSG | Tue May 18 1993 02:25 | 11 |
|
What is the story with the DEMFA?
Is it supposed to be supported or what?
I was just out at the customer site again today and they are now using
V1.3 MCC and when you try to show characteristics on the mfa-0 circuit
it returns a few error messages about extra information returned and
a couple of other errors I didn't keep.
I need support for the demfa please!
thanks,
Mike
|
| 4669.5 | looking into it | TOOK::PURRETTA | | Tue May 18 1993 18:42 | 9 |
| You're right. It looks like FDDI protocol is not fully supported
by the AM. I'll spend some time figuring out what it would take
to get it supported and bring it to management. There may be something
we can do cheaply in the meantime to get things working better than
they do now which could be field installed rather than waiting for
a new release. Please also be aware that we don't have many resources
back here (I work mainly on phaseV and common agent but jump in to
help with phaseIV issues when they arise). We're trying to do the best
we can.
|
| 4669.6 | What next? | GIDDAY::DRANSFIELD | Mike Dransfield, Sydney RSSG | Wed May 19 1993 06:27 | 13 |
| re: .5
thanks for the reply.
So what do I have to do to get it supported?
We are talking about one of our major customers here!
They are spending about US$4M in the next twelve months if we look
good....
Do you want me to raise a CLD for this problem... I already have two
open, so another one isn't a problem for me :-)
I know its tough, but it's also tough trying to explain to customers
why things don't work the way they want them to.....
cheers,
Mike
|
| 4669.7 | | TOOK::MINTZ | Erik Pavlik Mintz | Wed May 19 1993 11:14 | 6 |
| Engineering is examining what workarrounds may be possible in the short term.
However, to get "full support" I suggest that you contact product management.
They are the people who prioritize the requirements for implementation
changes. In this case, try Laura (MOLAR::) Sargent.
-- Erik
|
| 4669.8 | is workaround available yet ? | GIDDAY::CHONG | Andrew Chong - Sydney CSC | Tue Jul 13 1993 23:12 | 17 |
|
re .-1
>Engineering is examining what workarrounds may be possible in the
>short term
Is a work around available yet ?
Another customer has reported the same problem with decnet phase4
AM over FDDI. Show line and circ counters from the iconic map
produced many many pop up boxes with warning messages about extra
information being returned.
I will send mail to Laura (MOLAR::) Sargent as suggested in .-1
but would be nice to have a temporary workaround.
Regards,
Andrew
|
| 4669.9 | Workaround | TOOK::PURRETTA | | Wed Jul 14 1993 13:14 | 10 |
| I've provided Mike Dransfield two new .COM procedures to
replace the dictionary definitions of DNA4 Circuit and Line
with something which won't give you all those pop-up windows.
MCC will display those attributes returned which overlap with
ethernet attributes. Attributes which are specific to FDDI (new)
will require development support in the AM and Dictionary.
It looks like Mike is in the same area as you are so you might
try getting the new procedures and instructions from him.
Otherwise send me mail - TOOK::PURRETTA
|