[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

4219.0. "Can't look at per-port statistics; Rptr900PortMain screen(??)" by KAOT01::WATTERS () Wed Feb 19 1997 15:51

HEEEEEEELLLLLLP!!!!

Customer can't look at the 'per port' statistics on a certain DEChub900.
2 Portswitch900tp and 1 Portswitch900fp. Using Hubwatch v4.1.1 from a 
Unix box.

When he 'clicks' on one of the 32 ports he gets a screen w/ a title of
'Rptr900PortMain' instead of (for example): 
'Repeater Port Summary: hub900: slot 2: port A1
 
On top of that screen is one that says: No response from agent.
He clicks OK on that one and then he's back to the 'Repeater Summary'
screen. We've tried 2 other modules as the agent; same problem.
 
To add to this dilemna (to complicate things) :*)
Using the same Unix system, if he connects to another hub; no problem.
If he uses ClearVISN instead of Hubwatch; no problem on EITHER hub.
The versions of firmware are the same everywhere (he's current).

Weird eh? 

Hub manager on both Hubs is v4.2.0

He had a major network problem that we fixed by replacing his DECswitch 900EF.
This 'minor' problem seems to have stuck around and his boss is 'demanding'
an explanation.

Any help would be greatly appreciated.

Andy
T.RTitleUserPersonal
Name		DateLines
4219.1NETCAD::DOODYMichael DoodyThu Feb 20 1997 09:354
    Sometimes you see wierdness like this if two devices
    have the same IP address. Just a hunch.
    
    -Mike
4219.2I'll double-check anyways. Thanks.KAOT01::WATTERSThu Feb 20 1997 10:036
    Thanks....but I don't *think* so since:
    
    - it happens to 3 modules in the same hub; each w/ their own address
    - ClearVISN doesn't seem to have the same problem.
    
    Andy
4219.3probably connectivity pbmNETCAD::DOODYMichael DoodyThu Feb 20 1997 14:1718
Okay, make sure the unix system can ping each of
the affected module's IP addresses. 

Since you said that ClearVISN MCM can see them, you 
must be running that on a PC. I'll bet the PC
can ping them but not the unix system.

Check the Arp table on the unix system with a 
"arp -a" and do the same thing on the PC.
The hardware addresses might be different, for the
same IP address. Clear the bad ones on the
Unix system using "arp -d hostname". Or reboot.

The hardware address would change if the repeaters
are reached "through" the DEFBA that you swapped out,
the new DEFBA has a new hardware address.

-mike