T.R | Title | User | Personal Name | Date | Lines |
---|
4356.1 | | MOLAR::YAHEY::BOSE | | Fri Jan 08 1993 15:21 | 12 |
|
>> - is somewhere a workaround available for "putting" some data via
>> DECMCC into this "empty" datafield or what can I do solve
>> this problem ??
Unfortunately, this is not possible. However, this has been fixed
in T1.3.0 and the data field length is now 64 bytes in the
ICMP echo request packet. I guess all you can do for now is wait
for V1.3.
Rahul.
|
4356.2 | "empty" datafield in T1.3 ! | ZUR01::FRICKER | | Mon Jan 11 1993 04:09 | 14 |
|
>> Unfortunately, this is not possible. However, this has been fixed
>> in T1.3.0 and the data field length is now 64 bytes ....
testsystem ( Ultrix 4.2A, MCCBMS T1.3):
if I do a "test snmp-node" via iconic map, I still see (HP
analyzer) a ICMP datagram with a "empty" datafield. So I don't see any
differences between MCCBMS 1.2 and MCCBMS 1.3
Kurt
|
4356.3 | | MOLAR::YAHEY::BOSE | | Mon Jan 11 1993 15:07 | 14 |
|
I guess there's some confusion about what we mean by an empty
data field. In V1.2 the SNMP AM sent out an ICMP echo message
with just the ICMP header. In T1.3 it sends an ICMP echo message
with the ICMP echo header and a data field which is zero-filled.
The actual length of the data is 24 bytes (and not 64 bytes as I
had mentioned before). So if you mean "zero-filled" when you say
"empty", then you are right about T1.3.
We found that the new ICMP echo message worked with all the IP
nodes we tested against. Are you saying that it doesn't work with
the ODS-Bridges?
Rahul.
|
4356.4 | "empty" = "zero-filled" ! | ZUR01::FRICKER | | Tue Jan 12 1993 05:36 | 12 |
|
when I say "empty" I mean "zero-filled" .
The ODS-Bridge ( HW-Type: ODS294-SB-AU , Firmware: 3.06) at my customer
site doesn't work with a data filed which is zero-filled.
Kurt
|
4356.5 | | MOLAR::YAHEY::BOSE | | Tue Jan 12 1993 09:53 | 5 |
|
File it as a QAR and we will take care of it in the next version.
(It is already too late to fix it for V1.3).
Rahul.
|