[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

1455.0. "COMMUNITY TABLE UPDATE" by SIOG::SMITH () Tue Sep 20 1994 16:28

    When adding an Agent to the community table in HUBWatch V3.1.1 It
    "Cannot write to file C:\HUBWATCH\USERDATA\HW_AGENT.DAT" the paths and
    file atributes are set up correctly the file exists in the correct
    directory.
    Any ideas why and how do I correct this problem ??
    
    Also:
    
    Where will I find detailed documentation on the DECBRIDGE 900MX
    detailing how to set up filtering etc... from HUBWATCH.
    
    Thanks,
    Jim 
T.RTitleUserPersonal
Name
DateLines
1455.1SLINK::HOODI'd rather be at the PenobscotTue Sep 20 1994 20:097
>    Where will I find detailed documentation on the DECBRIDGE 900MX
>    detailing how to set up filtering etc... from HUBWATCH.
    

The HUBwatch on-line help explains how to setup db900 filtering.

Tom Hood
1455.2OK but Explain the ArrowsSIOG::SMITHThu Sep 22 1994 19:447
    Thanks Tom... 
    I've read it and can't make scence of it. Explain why there are 7 arrows
    accross and 14 (I Think) down. 
    
    Can anyone throw some light on the first part of my question.
    
    Jim 
1455.3900 filters and then agents files...SLINK::HOODI'd rather be at the PenobscotThu Sep 22 1994 20:0947
For the 900-series bridges/switches (DECbridge 900MX, DECswitch 900EF, 
DECswitch 900EE, PEswitch 900TX, RoamAbout access point), the filter screen
consists of zero or more filter entries, one per MAC address or per protocol
type.  Each filter entry has three main elements:  (1) the address or protocol 
(2) whether that address or protocol is forwarded or filtered per port,
and (3) whether that address or protocol is rate-limited on broadcast.

Typical filter entry:

	1   2   3   4   5   6   7 
							+-------+
	|   |   |   |   |   |   |   0E-32-04-90-33	| ==O-> |
	|   |   |   V   |   V   |   K-MARTnet		+-------+
	V   V   V   -   V   -   V

For this entry, K-MARTnet is filtered from ports 4 and 6, and can be 
forwarded to the other ports.  For broadcast, rate limiting is enabled
for this protocol (rate limit is shown by the box at the right).

There is also a Manual Mode / Defaults box at the bottom of the Address
Filters and Protocol Filters screen which says, "If I haven't specified
a particular address or protocol in any entry above, this is what to do
with it."  It uses the per-port arrows used in the filter entries.

To add a new filter entry, press the big "+" button on the right side of 
the filters window.  To modify an entry, select it, then press the modify
pushbutton (picture of an arrow being replaced by a different arrow).  You
can only modify entries through the modify function, not directly in the
filters window [this is a slight inconvenience, but was the only way I could
think of to verify the validity of the modified entry].  For the address
filters, you cannot delete or modify the entries for the spanning tree 
addresses nor the MAC addresses of the ports themselves.

As far as 7 arrows across and 14 arrows down, I don't know what you mean.

For the agents file, HUBwatch for Windows will only access an agents file
located in the HUBWATCH_LIBRARY directory.  Check how you've got that
environment variable defined.  Change its definition if you want to use
a different directory for the agents file.  From your question it looks
like HUBWATCH_LIBRARY is defined as C:\HUBWATCH\USERDATA\.  If you don't
want your agents file there, redefine HUBWATCH_LIBRARY.  Otherwise, check
the protections on that directory.
[HUBwatch for OpenVMS VAX uses the logical HUBWATCH$LIBRARY, defined by 
default as "SYS$LOGIN" for this same purpose.  In HUBwatch for DEC OSF/1
and HUBwatch for ULTRIX, it's HUBWATCH_LIBRARY, which users must define.]

Tom Hood
1455.4KAOFS::S_HYNDMANAcronym Decoder Ring ArchitectMon Oct 24 1994 16:5910
    
    
    I also am experiencing the same problem trying to add an agent to the
    c:\hubwatch\userdata\hw_agent.dat file. I get the following error
    
    "can not write to file"
    
    This is Version 3.1 Hubwatch for Windows.  Any Ideas?
    
    Scott
1455.5Probably blanksCONSLT::BUZZELLWed Nov 02 1994 00:328
    
    Make sure that you are not puuting any blanks in the agent name.
    This is after all a robust Simple network protocol that is being
    used and is easily confused. Seriously the times I have seen this 
    doing training it has been because of blanks. If you want to seperate
    parts of names use _.