[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

2281.0. "IP Service problems with Switches" by WELSWS::GREENR (Curiosity Killed The Cat) Tue May 16 1995 11:14

    A Distributor that I look after in the UK has recently complained to me
    about inconsistances that they are finding when installing DEChub 900's
    and using either DECswitch 900 EFs or PEswitches as the IP services
    modules.
    They cited a recent case where a customer had purchased a DEChub 900, a
    DECswitch 900EF and a PEswitch 900 (there were no other modules
    installed within the hub). They connected HUBwatch initially via the
    PEswitch and assigned the PEswitch as the IP services module. They were
    not able to ping or get hubwatch to talk to the hub. They tried both
    straight through and twisted utp cables to no avail. They also tried
    factory resets on both the hub and the module to no avail. They checked
    firmware and that was also ok.
    They next tried the same thing with the DECswitch 900EF as the
    IPservices and connected hubwatch via one of its f/p rj45s. Again they
    experienced the same problem. They also connected two systems across
    the DECswitch 900EF and were succesful in pinging each of them however
    they could not ping the hub itself. 
    To fix the problem they returned with a Repeater 900TM set this as ip
    services and used the same hubwatch system - it worked fine.
    They informed me that they were seeing alot of problem like this and
    often found that a DECswitch would work in one hub and not another - is
    anyone else seeing similar probs. I myself have had some strange
    behaviours when using a switch as the IP services module but have
    always put it down to finger problems. 
    regs
    ross

T.R	Title	User	Personal Name	Date	Lines
2281.1	Coonect *switch to the thinwire	DPDMAI::DAVIES	Mark, SCA Area Network Consultant	`Tue May 16 1995 13:57`	14
	This comes from my own learning curve of the past, but with both the DECswitch 900EF and the PEswitch 900 you MUST connect one of the front bezel ethernet ports to the thinwire backplane in the DEChub 900. This is because the DEChub 900 only has an Ethernet backplane defined at initial power up and it has no way to connect to FDDI. WIthe the DECswitch 900EF, the only port which allows this is port #3, the top-most UTP port on the front bezel. I do not know about the PEswitch 900. Regards, Mark
2281.2	ThinWire is 2nd Ethernet port for DECswitches and PEswitch	SLINK::HOOD	Maine state bird: The black fly	`Tue May 16 1995 14:51`	11
	For the DECswitch 900EE, 900EF, and PEswitch 900TX, the ThinWire Ethernet is the 2nd Ethernet port. This is port 3 on the 900EF, port 2 on the 900EE, and either 3 or 2 (depending on whether you count the FDDI as port 1) for the 900TX In any case, as Mark said, by default it is connected to the front panel (as are all ports), and not to the back plane. Tom Hood HUBwatch
2281.3		NPSS::WADE	Network Systems Support	`Tue May 16 1995 14:59`	14
	re .1 Maybe I'm missing something here - If I connect HUBwatch directly into a front panel Ethernet port on the module providing IP services the module does not have to be connected to a backplane Etherent channel. The management channel is seperate from the backplane Ethernet/FDDI channels. Something else is wrong here. Does the fwd light come on on the port that HUBwatch is connected? Did you look at the ARP entry? Bill
2281.4	some do, some don't	DPDMAI::DAVIES	Mark, SCA Area Network Consultant	`Tue May 16 1995 15:13`	13
	I learned the hard way sometime back. The DECrepeater 900TM automatically connects to the thinwire backplane. This makes it a plug-and-play IP Servives module. Just plug it in, start redirection and you are on your way. Do not assume (as I did) that the DECswitches do the same thing. You must assign the specified Ethernet port to the thinwire or it is "No Way Jose". Regards, Mark
2281.5		NPSS::WADE	Network Systems Support	`Tue May 16 1995 15:24`	14
	Agreed - the ports on the DESBF and the DEFBA are all out the front on powerup. What I'm saying is that if I use either a DESBF or a DEFBA as my IP sevices module I can leave all the ports directed out the front. I have a DEFBA and a DESBF in a HUB in my lab. Neither of them have any backplane connections; all ports are out the front. I can set an IP address on the hub and use either of these modules as the IP services module as long as I connect my HUBwatch station to a front panel port of the module providing the IP services. Bill
2281.6	Port in Pre-Forwarding state ?	NETCAD::KRISHNA		`Thu May 18 1995 19:48`	13
	If any our switches is used as the IP services module, they will not respond to ARP requests for the Hub's IP address till the port on which the HUBwatch station is connected enters the FORWARDING state. This is seen by the Port State LED for the port transitioning from a Blinking Green to a Solid Green. Once the port goes into forwarding, the ARP should be resolved and SNMP/IP should work. Normally it takes about 30 seconds for the port to transition into forwarding. Could the percieved problems with IP services and the switches be a consequence of the above fact, i.e the user did not wait long enough before reattempting a connection from HUBwatch through the switch ? Krishna
2281.7	There is something ify here	WELSWS::GREENR	Curiosity Killed The Cat	`Thu May 25 1995 16:54`	12
	Sorry on being so long on responding but my home system decided to have a disk crash and I couldn't get bak in. Firstly - There was no reason to connect one of the DECswitch ports to the hub backplane as HUBwatch was connected to one of the F/P ports of the DECswitch. I have spoken to my Distributor and they assure me that they have tried in vain to connect to the switches minutes after powering up and still sometimes they don't work. I have asked them to inform me next time they have a problem with a DECswitch or PEswitch. regs ross
2281.8	Getting vital info...like pulling hairs from hairless chihuahua...	NETCAD::BATTERSBY		`Thu May 25 1995 17:17`	9
	Ross, please in the future, when you talk to your distributor, try and get them to provide you important information like... � serial number and rev of DECswitch (from rear label of box) � HW=X/Y and FW=X.X.X from the console (if possible) This info would prove useful in helping to diagnose problems. Bob