[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

2439.0. "Is DECBridge upgrade required to match Probes" by RDGENG::GREID (Hail,Hail,Hail and Kill!) Wed Jun 28 1995 13:18

    In the last two days I have upgraded to DECProbe 90s to V2.4. However
    although they are correctly configured, Probewatch refuses to talk to
    them when I try and launch the Data Capture.
    
    Is this because my the DECBridge 90s on the Hubs are still running V3.1
    and not 3.9 yet as I can talk to the DECAgent that I upgraded to
    V3.0.0 in one of the Hubs ?
    
    Using HUBwatch for OSF V4 I can now not see the device id for the Probe 
    in the Hub, it is unknown on the view.
    
    This "Error accessing probe Probename, while creating channel" is
    getting a tad bit boring. I can PING the Probes ok but SNMP refuses
    to talk to them.
    
    Giles.
T.RTitleUserPersonal
Name		DateLines
2439.1the unknown module type is expectedNAC::FORRESTThu Jun 29 1995 17:0818
    If your DECagent 90 is not in the hub with the probe, and the 
    DECbridge 90 is the backplane manager, then it will show up as an
    unknown module type. I don't think V3.9 bridge firmware will change
    this.
    
    With the V2.4 probe code, the sysOID changed, so you may need both
    DECagent 90 V3.0 and HUBwatch V4.0, and the DECagent must be in the
    same hub and be the bus master.
    
    Of course, this doesn't explain why you can't do a Data Capture using
    PROBEwatch. Do any of the PROBEwatch functions work since you upgraded,
    or does everything work except Data Capture? If nothing works, then I
    would expect the error to be No Response from Agent.
    
    There may be a Data Capture bug in the OSF version of PROBEwatch; we're
    looking into an earlier report.
    
    jack
2439.2Two Probe or not Two ProbeRDGENG::GREIDHail,Hail,Hail and Kill!Fri Jun 30 1995 06:4630
    Jack,
    
    	In the first instance of the problem the first Probe running V2.4
    is in the HUB 90 with an Agent running V3 and a Bridge running V3.1.
    The second instance is a Probe also running V2.4 but connected via
    thinwire to a DECrepeater 90c in a Hub with an agent running V3.0 and
    a bridge running V3.1.
    
    	I canot talk to either probe using Probewatch on OSF or on a PC, I
    have given up trying to use the Ultrix version because of not being
    able to display back to a VMS node running V6.1 which was noted
    previously, with no response.
    
    	I can talk to my other five probes that are running V1.0 and I 
    dare not upgrade them incase I cannot talk to them either.
    
    	The upgrade to V2.4 on the probes went ok, but I cannot launch most
    of the features eg Data Capture, Domain Manager and some of the
    features in the Traffic monitor, although initially it will launch.
    
    	The other five probes are also in different subnets and I can talk
    to them, no problem and launch whatever I like.
    
    	I may log one of the two probes with Customer Support, as I cannot
    think of anything else to try, having done things like reset to factory
    defaults and resetting up addresses etc..
    
    	Giles.
2439.3Backplanes at fault here ?RDGENG::GREIDHail,Hail,Hail and Kill!Mon Jul 03 1995 12:4410
    Further to my last note I have now upgraded all seven of my Probe 90s
    to V2.4 and even tried a couple in place of the two I'm having trouble
    with. Now all five of the probes that I have just upgraded are working
    fine, however none of the Probes placed in the two Hubs in question
    will work there. 
    
    Is it possible that the Backplanes could be faulty and not passing
    SNMP ?
    
    Giles.
2439.4RDGENG::GREIDHail,Hail,Hail and Kill!Mon Jul 03 1995 12:456
    
    I forgot to mention that the Bridges in both hubs are ok and infact
    have been replaced recently due to hardware failure, this is why I
    suspect the Backplanes.
    
    Giles.
2439.5does the problem move with the probe?NAC::FORRESTThu Jul 06 1995 12:119
    
    If you move those 2 probes somewhere else, do they then communicate
    with PROBEwatch OK?
    
    You said that one of the probes was off a ThinWire port - hard to 
    blame the backplane if other devices off that repeater are
    communicating.
    
    jack
2439.6RDGENG::GREIDHail,Hail,Hail and Kill!Thu Jul 06 1995 12:3410
    Jack,
    
    		The probes both work fine elsewhere, as I have tested them 
    	in other locations, eg HUB90s and a HUB900. 
    	
    		I see your point about the Probe thats thinwired but due to
    	and Agent 90 being in slot 7 I had no other choice. Anyway it works
    	ok elsewhere.
    
    	Giles.
2439.7try to look at SNMP to the problem probeNAC::FORRESTFri Jul 07 1995 12:1210
    The DECpacketprobe 90 does not have any slot restrictions - it does not
    have to be in slot 7 or 8.
    
    But this problem is bizarre - it acts like the bridge is filtering IP,
    and yet you said that you can Ping the probes.
    
    How about if you put another probe in one of the problem hubs or off 
    a repeater port? Maybe you can somehow do a datacapture of the traffic
    between the PROBEwatch station and the problem probe.