[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

1883.0. "DECrepeater 90T does not see station address" by DECPRG::PRNET::Pilar () Fri Jan 13 1995 06:24

Hi,

one of our customer has several DEChub 90 with bunch of DECrepeater 90T, 
DECserver 90L+, DECbridge 90FL and DECagent 90. When looking into 
DECrepeater 90T (V 1.0) I have running port (green) with connected station, 
but I don't see any connected station (field is filled by "No connected 
station message"). When I press <refresh> or when I enable polling nothing 
has changed. 

Can anybody explain why connected station is sometimes detected and 
sometimes not? I saw similar behaviour on DECrepeater 900TM.

Thank you in advance

Jarry

T.R Title User Personal
Name Date Lines

1883.1 For the older 90-series repeaters, the process is inherently unreliable ROGER::GAUDET Because the Earth is 2/3 water Fri Jan 13 1995 12:52 20

T.R	Title	User	Personal Name	Date	Lines
1883.1	For the older 90-series repeaters, the process is inherently unreliable	ROGER::GAUDET	Because the Earth is 2/3 water	`Fri Jan 13 1995 12:52`	20
	Jarry, The DECagent 90 obtains connected station information from each port of a DECrepeater 90T each time the hub is polled. By default, the DECagent builds a forwarding database much like the DECbridge 90 does. However, since this building process is done by polling devices (no more frequently than every 10 seconds and sometimes longer depending on the hub population), it is a slow process. The problem is that the repeater retains only the last address seen on each port, so if several addresses are seen between DECagent polls, only the last one seen on the port will be added to the DECagent's database. The DECagent will retain a particular address in the database for 10 minutes by default, after which time the address is "aged out" of the database if it is not seen again. Note that the DECagent's address aging time is settable via the SNMP MIB object da90BackplaneAddrDbAgingTime. Unfortunately, it is not settable from HUBwatch. I am not qualified to respond about how the DECrepeater 900TM retains addresses. ...Roger...

Jarry,

The DECagent 90 obtains connected station information from each port of a
DECrepeater 90T each time the hub is polled.  By default, the DECagent builds a
forwarding database much like the DECbridge 90 does.  However, since this
building process is done by polling devices (no more frequently than every 10
seconds and sometimes longer depending on the hub population), it is a slow
process.  The problem is that the repeater retains only the last address seen on
each port, so if several addresses are seen between DECagent polls, only the
last one seen on the port will be added to the DECagent's database.  The
DECagent will retain a particular address in the database for 10 minutes by
default, after which time the address is "aged out" of the database if it is not
seen again.

Note that the DECagent's address aging time is settable via the SNMP MIB object
da90BackplaneAddrDbAgingTime.  Unfortunately, it is not settable from HUBwatch.

I am not qualified to respond about how the DECrepeater 900TM retains addresses.

...Roger...