| 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 am unable to get the TEC AM to run properly...
I have installed the AM and the netprof software I recieved on a tape
from TEC, the AM is T1.0.0 (the netprof software seems to be a demo
kit)
Register of a NetPOD works regardless of a valid address being
supplied.
The IMPM crashes with ACvio, and the FCL also crashes when you do any
function using the netpod AM, any help appreciated...
Amrit
the am image ident...
Image Identification Information
image name: "MCC_NETPOD"
image file identification: "NETPODAM T1.0.0"
link date/time: 9-JUL-1992 10:41:36.12
linker identification: "05-05"
MCC> register netpod netpod-1 address =00-80-52-01-00-c8
NetPod DESIR_NS:.netpod-1
AT 22-DEC-1992 18:43:02
Registration successful.
MCC> sho netpod netpod-1 all char
%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=262C0950,
PC
=005A27C7, PSL=03C00000
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
005A27C7 005A27C7
00594C5C 00594C5C
00594818 00594818
000A2D65 000A2D65
0007A8AB 0007A8AB
0007506C 0007506C
000857B1 000857B1
000A2E6D 000A2E6D
000EFB3F 000EFB3F
000AFCAB 000AFCAB
000AF9B3 000AF9B3
000AF935 000AF935
000AF375 000AF375
000AEE58 000AEE58
000AEC77 000AEC77
001C9524 001C9524
001CA236 001CA236
001C8D3D 001C8D3D
001CBF05 001CBF05
001CB2DB 001CB2DB
001C8208 001C8208
001C6A0C 001C6A0C
000C4C76 000C4C76
MCC_MAIN main 7687 00000208 000020B4
0000596F 0000596F
MCC_KERNEL_INIT MCC_KERNEL_INITIALIZE 163 00000027 000059A3
0000594A 0000594A
$
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4315.1 | I have same problems | HLRG02::NOTES | Opel Manta GSI | Mon Dec 28 1992 05:11 | 32 |
Hi, > The IMPM crashes with ACvio, and the FCL also crashes when you do any > function using the netpod AM, any help appreciated... > > Amrit I have the same problem. I think the problem is that this version of the POD AM is not suitable for your DECmcc version. The version I have from the POD AM is: - Image Identification Information - - image name: "MCC_NETPOD" - image file identification: "DECMCC T1.2.4" - link date/time: 1-MAY-1992 18:11:23.13 - linker identification: "05-05" I think you (and me too) need a new version of the POD AM. Kindest regards, /-/ Henk. | |||||
| 4315.2 | version skew | GOSTE::CALLANDER | Thu Dec 31 1992 18:19 | 2 | |
highly possible it is a version problem, what version of mcc are
you running?
| |||||
| 4315.3 | fails on V1.2 and V1.2.3 | HERON::PATEL_A | LoLo-AQIC-I82Q-B4IP, - LMF | Mon Jan 04 1993 07:57 | 3 |
I have tried the POD am on V1.2.3 and V1.2 with the same results
Amrit
| |||||
| 4315.4 | POD registration and ACCVIO | LARVAE::POETT | Mon Jan 04 1993 12:23 | 12 | |
Amrit,
I've had the same problem on our system. I've spoken to Mentec and it
appears that the ACCVIO occurs if the POD does not register itself
correctly. To check registration do a Directory under the Operations
menu of MCC and you should see the POD's Ethernet address. If not, your
registration of the POD has failed, and whatever you do causes an ACCVIO.
Regards,
Dave
| |||||
| 4315.5 | this looks like a different prob.. | HERON::PATEL_A | LoLo-AQIC-I82Q-B4IP, - LMF | Mon Jan 04 1993 15:23 | 84 |
Dave,
It looks like this is not the same problem... ps who is your contact
at Mentec ?
No matter what address I provide the registration is allways
sucessful...
see the attached listing
MCC>
MCC>
MCC> register netpod npod1 address = 00-80-52-01-00-c8 <this is a valid address
NetPod DESIR_NS:.npod1
AT 4-JAN-1993 18:15:12
Registration successful.
MCC> dir netpod npod1
NetPod DESIR_NS:.npod1
AT 4-JAN-1993 18:15:24
Directory successful.
Name = DESIR_NS:.npod1
MCC> sho netpod npod1 all att
%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=263CE550, PC
=006B03C7, PSL=03C00000
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
006B03C7 006B03C7
006A285C 006A285C
006A2418 006A2418
000A2D65 000A2D65
0007A8AB 0007A8AB
0007506C 0007506C
000857B1 000857B1
000A2E6D 000A2E6D
000EFB3F 000EFB3F
000AFCAB 000AFCAB
000AF9B3 000AF9B3
000AF935 000AF935
000AF375 000AF375
000AEE58 000AEE58
000AEC77 000AEC77
001C9524 001C9524
001CA236 001CA236
001C8D3D 001C8D3D
001CBF05 001CBF05
001CB2DB 001CB2DB
001C8208 001C8208
001C6A0C 001C6A0C
000C4C76 000C4C76
MCC_MAIN main 7687 00000208 000020B4
0000596F 0000596F
MCC_KERNEL_INIT MCC_KERNEL_INITIALIZE 163 00000027 000059A3
0000594A 0000594A
$ mana/e
DECmcc (V1.2.3)
MCC> dereg netpod npod1
NetPod DESIR_NS:.npod1
AT 4-JAN-1993 18:23:12
Deregistration successful.
MCC> register netpod npod1 address = 11-11-11-11-11-11
NetPod DESIR_NS:.npod1
AT 4-JAN-1993 18:23:29
Registration successful.
MCC> dir netpod npod1
NetPod DESIR_NS:.npod1
AT 4-JAN-1993 18:24:00
Directory successful.
Name = DESIR_NS:.npod1
MCC>
| |||||
| 4315.6 | re .-* | PHDVAX::COMFORT | Mon Jan 04 1993 16:05 | 12 | |
I don't know if this will help, but the folks that produce Network
Professor had sent my customer the Netpod AM and it also crashes under
V1.2 and V1.2.3. The reason supplied to my customer was that the
Netpod AM was linked against T1.2.7 and never re-linked against V1.2.
That version that then shipped and of course we had gotten the SSB
release and upgraded. The situation was identified about three months
ago and has not yet been resolved. Be mindful that this info comes
from my customer and not directly from Technically Elite (which makes
it heresay from my point of view).
Dave
| |||||
| 4315.7 | Contact at MENTEC | LARVAE::POETT | Mon Jan 04 1993 16:13 | 13 | |
Amrit,
From the IMPM if you do a directory on a POD that has not registered
(although when adding from the toolbox all seems to have worked) you
only see the 'Name =' and no Ethernet address rather like what you are
seeing from the FCL interface. You should see both for a POD that has
registered OK.
The contact at Mentec is Mick Hogan, Tel. 353 12 858444
Regards,
Dave
| |||||
| 4315.8 | NetPOD works with MCC V1.2.(.3) but not with MCC T1.3.0 | COL01::WELZEL | Uwe Welzel, NIS, Cologne | Tue Jan 05 1993 09:58 | 27 |
Hello Amrit, the problem can be solved via a correct registration in DECmcc (re.7). This means, you have to register (and register...) again the Pod until you see the hardware address using the Directory command in DECmcc. This bug is known to Mentec (Mick Hogan) and they will fix this problem in the release which becomes available this month (perhaps in the next days). But in addition there is a problem with the NETPODAM T1.0.0 and DECmcc T1.3.0. When you try to get a statistic from the Netpod via MCC> show netpod netpod1 all statistic DECmcc returns the error message %MCC-E-INV_IN_ENTITY, software error: invalid in_entity (input entity) parameter Other functions as MCC> show netpod netpod1 all chara works without problems. I've reported this problem to Mentec (Mick Hogan) and they will work on it. Best regards Uwe | |||||
| 4315.9 | working but not stable | HERON::PATEL_A | LoLo-AQIC-I82Q-B4IP, - LMF | Tue Jan 05 1993 15:32 | 5 |
Thanks to all... I got it to work - sort offff
When I try to set a alarm threshold it acvios again :-(
Amrit
| |||||