[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

3745.0. "RMON Manager V3.3.0 IP Address mismatch!" by ZUR01::ACKERMANN () Thu Jul 25 1996 11:33

    
    
    
            Hello together,
    
            I have a problem with RMON Manager V3.3.0
            If you modify the IP Address in the Agent Entry, because
            you added the wrong address you have to reboot RMON Manager,
            that Traffic Monitor will run.
            Otherwise you will get "Cannot communicate with Agent"
            When you do "Test" to that Agent you see in the
            General Information Part: The correct IP Address, but in
            the Interface and System Information: The Information of the
    	    "old" IP Address! (the whole Stuff is mixed up!)
    
    Its easy to reproduce:
    
    1) start clearVISN 3.3.0 #0 with a empty Agent database
     2) New agent added  (IP 16.135.209.1)
     3) start traffic Monitor
        -> Cannot communicate with Agent ok, (->because this was the wrong
    					     address)
     4) agent edit   (modified the IP address to 16.135.209.11) (effektive
                                                    Address of the Agent)
     5) start traffic Monitor
        -> Cannot communicate with Agent  (-> this is wrong !!)
     6) test
        -> shows as IP address 16.135.209.11 but the
           system info of 16.135.209.1   (-> this is really bad!!)
    
            Now you m u s t reboot RMON Manager, otherwise Traffic Monitor
            will not run and test Info will never be correct.
    
            Any help is very appriciated,
    
            Thanks, Daniel MCS Switzerland
    
    
T.RTitleUserPersonal
Name
DateLines
3745.1yes, it's a bugNAC::FORRESTFri Jul 26 1996 11:484
    The workaround for now is to delete the agent entry and re-add it when
    you make a mistake. We'll try to get this fixed in the next release.
    
    
3745.2ThanksZUR01::ACKERMANNFri Jul 26 1996 13:088
    
    Hello Jack,
    
    Thanks for the confirmation of the Bug
    
    Regards,
    
    Daniel MCS Switzerland