Conference netcad::hub_mgnt

3179.0. "long sysuptime a problem?" by CSC32::D_PERRIN () Thu Jan 18 1996 10:58

    There may be a problem communicating with modules that have very
    long SysUpTime. A customer who has all his modules on UPS has
    begun having difficulty communicating w/ his dr900tm and ds900ef
    from hubwatch/vms 3.1.3. Modules are still at 3.1 firmware because he
    has hubwatch/vms.
    
    When he clicks on a module, the error he sees is:
    
     parsed_signedinteger, length error: 5
     parse_varbind, vb_ptr->value.sl_value
     parse_pdu, vb_ptr
     
    He gets this error trying to talk to 3 ds900ef that have uptimes
    of @340 days. He does not get the error on one with uptime of
    220 days. 
    
    He was getting the same error w/ a dr900tm. After a "reset w/
    current settings" the problem went away. We can't do this on 
    the ds900ef yet because they can't interrupt their users.
    
    Are we overflowing an integer somewhere? Anybody else seen this?
    

Yes, this might be a problem.  I've asked that this problem be entered into
our QAR system and will let you know what we find.

						-Shawn

    And the answer from a IPMT I sent up is:
    
    This will be fixed in the next release, clearVISN Multichassis Manager
    5.0, of HUBwatch. clearVISN will not support the VMS platform.
    
    HUbwatch for VMS 4.1.1 will be the last release of the VMS version and
    it will not include the fix for sysuptime.