[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

1248.0. "SETting values on a DR900TM port." by OSLACT::BJORN (Bj�rn Olav Haugom) Mon Jul 25 1994 10:10

A customer is trying to lock a port on a DECrepeater900TM to a certain MAC-
address, using his own SNMP-program. He has successfully been able to assign
address 08-00-02-04-38-5E to port # 2 with the following MIB-characteristics;

SNMP SET-request
Object Id  	= 1.3.6.1.4.1.36.2.18.11.5.1.1.4.3.2.1.4
MIB Instance 	= 1.2.8.0.2.4.56.94	(= HEX 08-00-02-04-38-5E )
SNMP SET value	= 2

With SNMP SET value = 1, he has verified the address.

He has also been able to set the valid "security function" to "disablePort" by 
using  these values;

SNMP SET-request
Object Id  	= 1.3.6.1.4.1.36.2.18.11.5.1.1.4.3.1.1.4      (diff. object id)
MIB Instance 	= 1.2
SNMP SET value	= 4

The result of this is that he has been able to lock a certain port to a certain
MAC-address. BUT, if he tries to lock a MAC-address that starts with 00- instead
of 08-, the result is a completely different MAC-address. He wants to set the
MAC-address 00-40-8C-10-20-AA (= decimal 0.64.140.16.32.170).

SNMP SET-request
Object Id  	= 1.3.6.1.4.1.36.2.18.11.5.1.1.4.3.2.1.4
MIB Instance 	= 1.2.0.64.140.16.32.170
SNMP SET value	= 2

The result is a MAC address = 239.254.204.221.169.184

Has anyone seen this? Is there a problem with the SNMP agent in the 
DECrepeater900TM? Why is he able to do what he wants to do with a certain MAC-
address and not with the other one?


Bj�rn Olav Haugom
T.RTitleUserPersonal
Name		DateLines
1248.1working on itNACAD::PAGLIARORich Pagliaro, Hub Products GroupMon Jul 25 1994 17:126
    We've reproduced this problem in our lab are currently investigating
    the cause and solutions.  Watch this space for resolution to this bug.
    
    -Regards,
    
    Rich
1248.2OSLACT::BJORNBj�rn Olav HaugomTue Jul 26 1994 09:3812
It also happens with HUBwatch, but not always. Even with the same address
specified, it doesn't always happen. Sometimes it just blanks out the address-
information where you do add the address in Hubwatch. I've tried to use
Probewatch to see what happens, but the after the SET request, I receive a 
GET response from the DECrepeater900TM, containing the same information as in
the SET request. I tries twice, and then it starts GETNEXT for a whole lot of
information. 

Anyway, I'll tell my customer about the bug. Any idea when there will be a fix?
Is the bug related to firmware or to the agent itself?

Bj�rn Olav Haugom
1248.3900TM, 900GM, 900FP, 90FS & 90TS all have this bugNACAD2::PAGLIARORich Pagliaro, Hub Products GroupTue Jul 26 1994 09:549
>>  Is the bug related to firmware or to the agent itself?
    
    I'm not sure I understand what you mean by "the agent itself". There is
    definitely a bug in the repeater firmware. I am working on fixing this
    bug "as we speak".  Right now it is unclear whether or not the fix to
    this bug will make it into the "60 day upgrade" which is supposed to be
    available sometime in the beginning of August. 
    
    -Rich
1248.4updateNACAD::PAGLIARORich Pagliaro, Hub Products GroupTue Aug 02 1994 15:057
    The bug in the repeater firmware which caused this behavior has been
    found and fixed. This fix for the DECrepeater 900TM, 900GM, 900FP,
    90FS, and 90TS will be made available as part of the 60-day upgrade
    consolidated firmware release.
    
    -Rich