[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

4401.0. "RMON Manager and 900EF: Nothing Working" by KERNEL::FREKES (Like a thief in the night) Mon May 12 1997 13:11

Folks

I am running RMON Manager V3.3.0, and V1.7 on a DECswitch900EF. I am having 
quite a few problems trying to get it to work. I have noticed a few things that
are different from expected. 

1. With the SNMP read/write communities set to public, a TEST comes back 
   immediatly. With it set to public-rmon on the write community, it takes
   a good 30 sec only to say that public-rmon failed. So I assume that 
   public-rmon is no longer required, as the read/write community strings.

   Working on that principle, I have the following problems.

1. With the read/write community string set to public at the RMON end of 
   things, I have tried to go into the Domian Manager, and install a domain.
   RMON was already installed, and when I tried to add DECNET, I just get the 
   error message: Entry or Group not present in Agent. I know this as I am 
   trying to install it!!

2. When I try and go into Data Capture, I get the same error message.

3. If I go to Traffic Monitor or Protocol Monitor I get the error message;
   "Cannot communicate with Agent" Why do I get this when the ping works OK. 

4. From Multichassis Manager V5 & V6 I am unable to modify the RMON icon. It
   just says that RMON is "broken". Well, where else are you supposed to 
   enable it from? 

   So I did a Factory reset on the switch, reset the IP address, and this 
   made no difference. I am at a loss, I have done this before, does anybody 
   have any idea why this is not working now? Is there some change is the 
   way this works from previous versions, that I have perhaps missed.
   I thought that you could at least do some of the basic stuff while using
   the basic 4 group image.

  So I went away and upgraded the switch to the full 9 group image. 
  Or I tried to. After entering all the information, like the load file name, 
  the IP address of the node contaiing the image, and hit return until the 
  DLU process started. I was presented with a single period on the screen, and
  then the message Transfer complete. The switch did not reset either. So I 
  did the same thing again, and this time I took a trace. Not a single packet	
  packet was seen with that EF's address as either the source or the IP address.

  Is my switch faulty, or am I missing something really obvious here?

Regards
	Steven Freke

   

   

 
    
T.RTitleUserPersonal
Name
DateLines
4401.1NETCAD::HOPPEMon May 12 1997 17:2833
    
    Only Full RMON images (1.7.0R, 1.6.1R) support full RMON features such
    as the "-rmon" community string extension and the RMON enable/disable
    per port buttons in MCM.
    
    The 4 Groups of RMON supports the RMON domain with statistics,
    history, alarms, and events.  Also, it supports the MCM RMON
    views.
    
    >  So I went away and upgraded the switch to the full 9 group image. 
    >  Or I tried to. After entering all the information, like the load file
    >name, 
    >  the IP address of the node contaiing the image, and hit return until
    >the 
    >  DLU process started. I was presented with a single period on the
    >screen, and
    >  then the message Transfer complete. The switch did not reset either.
    >So I 
    >  did the same thing again, and this time I took a trace. Not a single
    >packet   
    >  packet was seen with that EF's address as either the source or the IP
    >address.
    >
    >  Is my switch faulty, or am I missing something really obvious here?
    
    Make sure that the port you have the tftp server attached to is
    in forwarding mode before you start the download.  The symptoms
    you described always occur when someone starts a tftp download
    before the port is in forwarding.
    
    Hope this helps.
    
    Chris