[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

4207.0. "Recovery Manager can't see hubs..." by RTP4ME::GALLAGHER (Life is good!) Mon Feb 10 1997 16:47

    
    Config:
    PC running Win95
    ClearVisn MultiChasis V5.0
    ClearVisn Recovery Manager V1.1.0
    
    Recovery Manager worked fine before they decided to change the names
    of all their agents.  Now the only way to successfully backup any
    hub is to use it's IP address with no other data present. Attempting
    to use agent name in anyway (i.e. w or w/o IP addresses) causes
    the hub to come up with every module either empty or unrecognizable.
    They have changed the agent names in the HW_AGENT file.  HubWatch
    can see the hubs w/o any problem.
    
    Any ideas,
    Ed Gallagher
T.RTitleUserPersonal
Name
DateLines
4207.1V1.0 Recovery Manager and the agents file?NETCAD::GILLISTue Feb 11 1997 16:0135
Ed,


1)Was any error indication written to the Recovery Manager system-wide
log file (recov.log, found in the same directory as the executable)?

2)Was any error indication written to the log file for the backup
session?

3)Is this only an issue on Windows95 (not WindowsNT?)

4)What were the "before-and-after" agents names for one of
the agents that this problem occurs on?

5)When using the "new" agents file entries ....
  - do they appear in Recovery Manager's "Backup From" listbox
    when you select the "pull-down" button?  -----
		                             | | |
			                     | V |
                                             -----
  - can you select from this list once agents entries
    appear? (Each entry is abbreviated with name&ip_address)

  

I was hoping that the user changed their community strings
as well as their agent names, but this sounds unlikely, as
MCM can still access the devices.


Send me the log files that the Recovery Manager backup operation
generated after you had changed the agents file entries.

John Gillis (netcad::gillis)
clearVISN 
4207.2Recovery Mgr working again.RTP4ME::GALLAGHERLife is good!Tue Feb 18 1997 09:1513
    John,
    
    	Sorry I didn't get back to you before this...I actually had
    all your questions answered in a reply I was entering when in the
    middle of including the last agent file my network connection
    hung and I lost it all.
    	In the meantime, we figured out what the problem was.  The
    customer had changed the community name in all the hubs but didn't
    perform the "Reset to current" function.  We have since performed
    that function on all the hubs and everything's working again.
    
    Thanks for you quick response,
    Ed Gallagher
4207.3NETCAD::MILLBRANDTanswer mamTue Feb 18 1997 10:429
>    The
>    customer had changed the community name in all the hubs but didn't
>    perform the "Reset to current" function.  We have since performed
>    that function on all the hubs and everything's working again.
 
In MAM V5.0 and the 600 Stack Director ("stackMAM") you won't have to
do Reset to current any more after changing the community string.

	Dotsie