| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 842.1 | Known problem | BERN01::GMUER | | Mon Mar 21 1994 04:00 | 11 |
| Hello Jean-Yves
This is a known problem. I have analyzed the SNMP traffic between DECmcc
and Packetprobe. The problem is that the Packetprobe does not respond to a
GETNEXT request from DECmcc. I also detected problems with SET directives.
You can set MIB II and RMON variables, but you always get a timeout.
Concerning these problems I have sent two mails to Jack Forrest some days
ago. I hope to get some feedback from the engineering.
Edgar
|
| 842.2 | Voila un b.....g alors !!!! | PRSSOS::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Mon Mar 21 1994 06:46 | 8 |
| Edgar,
thanks for your answer, have you officialy escaladed this problem (IPMT)
because , i think it's really a serious bug in firmware code of Probe90..
awaiting a reply from engeenering
Jean-Yves
|
| 842.3 | will try to get fix into V1.1 | NAC::FORREST | | Wed Mar 23 1994 17:27 | 5 |
|
This is being looked into, but of course it will require a firmware
change, so don't expect a fix till we release V1.1.
jack
|
| 842.4 | time frame please | PRSSOS::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Thu Mar 24 1994 12:51 | 5 |
| jack,
have you a timeframe for the firmware upgrade ???
|
| 842.5 | sometime in Q4 | NAC::FORREST | | Tue Mar 29 1994 11:11 | 5 |
|
DECpacketprobe 90 V1.1 - sometime in Q4. I'd like to make it
coincident with the release of the DECpacketprobe 900RR, so that
both products are the same except 1 being Ethernet, the other
Token Ring.
|
| 842.6 | Firmware status | PADNOM::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Wed Mar 30 1994 03:45 | 5 |
| ok,
and for the new firmware always in Q4 too ??
Jean-Yves
|
| 842.7 | DECpacketprobe 90 V1.1 due out in Q4 | NAC::FORREST | | Fri Apr 01 1994 17:55 | 2 |
|
Yes, DECpacketprobe 90 V1.1 - the V1.1 indicates a firmware upgrade.
|
| 842.8 | Eprom 1.1 Flash 1.0 | UTRTSC::VDCRUIJSEN | | Tue May 10 1994 09:35 | 31 |
| Hello
I am also trying to use a DECpacketprobe90 with DECmcc.
The problem is I am not able to register the probe with the
SNMP access module. I always get a partial registration with
no response from entity.
Ping to the box works fine.
At time of registration we receive the following message on
DECpacketprobe console port:
snmp_age: create_identical SNMP error
I can register other IP node correctly, only the Packetprobe fails.
Probe is running from Flash Version 1.0
Eprom version is 1.1
I removed the flash card but running from Eprom 1.1 shows the same problem.
Probe HW revision A01
Questions:
What does the message mean??
Is Eprom 1.1 the new image and should it have the problem fixed??
Regards Gerrit
|
| 842.9 | A firmware fix is coming for SNMP problem | NAC::FORREST | | Wed Jul 06 1994 17:58 | 8 |
|
I know that if your console screen says V1.2, Executing from Flash,
then you can walk the MIB. I still don't know if you can register
it. I'll try to find out and post a reply here.
V1.2 is available on the network, but is not the version that we
will be releasing. See LENAC_USER:[NETWORKS.MANAGE.RMON]PROBCODE.TXT
for a pointer.
|
| 842.10 | DECpacketprobe will not work with DECmcc V1.2 | NAC::FORREST | | Wed Jul 06 1994 19:50 | 4 |
|
By the way, I understand that DECmcc V1.2 has the RMON MIB under
the wrong branch of the MIB tree. I think this is OK with DECmcc
V1.3
|
| 842.11 | to make DECpacketprobe work with generic SNMP manager | NAC::FORREST | | Thu Aug 11 1994 22:46 | 41 |
|
The DECpacketprobe factory defaults are set for optimal performance
with PROBEwatch. For it to work with some other SNMP manager that
understands the RMON MIB, you need to do the following from the
console.
For a probe on which you have loaded new firmware:
--------------------------------------------------
1. From the console, enter 11 for Command line mode.
2. % Get Agent_Options - the first 3 should be on; the rest off
mib_check, mib_defaults, default_groups
3. % Help Set Agent_Options
4. % Set Agent_options mib_check on
% Set Agent_options mib_defaults on
% Set Agent_options default_groups on
5. % Quit
6. enter 12 to Reset the probe
For a probe running V1.0 firmware:
-----------------------------------
(I hope I have the right coding here)
1. From the console, enter 11 for Command line mode.
2. % Get Agent_Options should return "0x2" instead of the parameter names.
3. % Help Set Agent_Options just returns the list of all commands
4. % Set Agent_options 0x0
% Set Agent_options 0x3
5. % Quit
6. enter 12 to Reset the probe
|
| 842.12 | It is still a problem for V1.0 firmware | BERN01::GMUER | Edgar Gmuer @EBO | Wed Aug 17 1994 12:06 | 25 |
| I have tried the method descriobed in .11 for a probe running V1.0 and DECmcc:
> 1. From the console, enter 11 for Command line mode.
>
> 2. % Get Agent_Options should return "0x2" instead of the parameter names.
>
> 3. % Help Set Agent_Options just returns the list of all commands
>
> 4. % Set Agent_options 0x0
> % Set Agent_options 0x3
>
> 5. % Quit
>
> 6. enter 12 to Reset the probe
But the DECmcc register still does not work. Also the SNMP sets came to a
timeout. Still the same message
snmp_age: create_identical SNMP error
Is it the right coding for the Agent_options ?
Thanks for any help or coment !
Edgar
|
| 842.13 | Not fully SNMP compliant is it? | WOTVAX::64021::Tim_Banks | Network Mercenary | Tue Oct 11 1994 05:45 | 13 |
| I have a customer with just the same problems. He has Probe V2.1, and MCC
V1.3, and he too only gets the partial registration. If he adds the RMON MIB
entries to the Probe from MCC (they don't appear as child entities under the
probe by default, due I suspose to the partial registration) he can actually
get a response back when he queries the RMON MIB values.
However basic MIB II variables are not accessible, so he can get basic
interface variables back, but little else.
This needs fixing, how can we claim to be RMON/SNMP compatible when
MCC and other platforms can't register the probe?
Tim
|