[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

2774.0. "HW V4.1 and DECswitch 900EF/MP community pb" by MOSCOW::FELIZHANKO () Mon Sep 18 1995 12:38

I can't launch a telnet session to a DECswitch 900EF/MP neither from 
"Physical view" nor from "LAN Interconnect" windows. When I double-click 
on its icon, HW tries to telnet a MAM address!

900EF/MP, its community, real IP and MAC addresses are in the agent list 
("Community/Manage Table").

Single-click on the icon and "Community/Manage Current" shows the community
"public-7" (900EF/MP is in slot 7) and IP address of a MAM instead of "public"
(or whatever I want after configuring snmp on the brouter) and IP address
of its Ethernet interface connected to a thin backplane channel.

When I make the DECswitch agent current, HW shows the module, "Community/
Manage Current" shows proper community and IP address, double-click
launches a telnet session with the brouter -- it works as it should do
but only from that window.

Is it a bug?

Alexander

Cross-posted to COMMON_BROUTERS

T.RTitleUserPersonal
Name
DateLines
2774.1Known.SLINK::HOODMy God, what have I done to my spleen?Mon Sep 18 1995 13:3415
It is a known problem that will be fixed in HUBwatch 5.0.

What happens with the routers is that HUBwatch will attempt to use the
highest numbered IP address of the device.  If that is unreachable from
your workstation, it defaults to the MAM.  For SNMP, this is the correct
thing to do.  For TELNET, well, it's lame.  But, as should be mentioned
in the HUBwatch release notes, TELNET windows are a best-effort thing, not
guaranteed to work.

It gets fixed in V5.0 because that's when HUBwatch starts doing "real"
management for routers.  It wasn't fixed in V4.1 because TELNET is a poor
excuse for real management, and the simple workaround is to go to an
extra DECterm or (ugh) DOS window somewhere and type "TELNET n.n.n.n".

Tom Hood
2774.2Thanks TomMOSCOW::FELIZHANKOTue Sep 19 1995 02:200
2774.3DS900EF/MP to backplane connectivity pbMOSCOW::FELIZHANKOTue Sep 19 1995 06:4612
Can't configure more than 4 backplane connections of a DS900EF/MP using
HW V4.1. This is because "LAN Interconnect/Configure/Expand" doesn't
work. HW tries to telnet some mysterious IP address instead of
displaying expanded picture of the 900EF/MP. Usual brouter's icon doesn't
have enough room to arrange more than 4 connections to backplane channels
when using non-expanded view.

Hope it will be fixed in V5.0

Alexander

2774.4thanks - bug recordedNETCAD::MOWERWed Oct 04 1995 18:424
    
    Thanks for reporting this bug;  it has been logged in the bug-tracking
    system, and will get attention.