| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
I had read the discussion in note 5090 & 4625 about the problem of partial
registration of foreign devices such as DecHub. I managed to partially register
a few more DecHubs (with no resident DecAgent in them) and nomiated another
DecAgent as the proxy agent. The normal DecMcc command works fine on these hubs.
But when I tries to fire up HubWatch from DecMcc on these hubs, I got an error
saying "Attribute Not Gettable". I guess the reason is that HubWatch is looking
for the IP address of the Hub rather than the proxy agent and thus it failed.
Is there any way to workaround this problem ie to fire up HubWatch to look
into the secondary hubs directly?
Cross posted in Hub_mgnt conf.
The DecMcc entity attributes of these hubs are shown as belows.
.ip.decagent90 is the primary hub with a resident Decagent90.
.ip.denny_hub_2 is a secondary hub using the Decagent90 in .ip.decagent90 as
its proxy agent.
Regards,
Denny.
================================================================================
SNMP .ip.decagent90
AT 16-JUL-1993 12:03:45 All Attributes
Address = 16.153.32.205
Name = decagent90
Registered Name = WAVE3_NS:.ip.decagent90
ipReachability = up
sysUpTime = 128369100
CounterCreationTime = 1-JUL-1993 15:28:56.10
sysDescr = "DEChub 90 8 slots, DECagent 90
HW=D01 ROM=BL05.00 SW=V1.1"
sysObjectID = "1.3.6.1.4.1.36.2.15.10.1"
sysContact = "mike dransfield"
sysName = "decagent90"
sysLocation = "csc toy room"
sysServices = 1
ifNumber = 3
Read Community Name = ""
Write Community Name = ""
Location = -- Attribute Not Available
Implementation Desc = -- Attribute Not Available
Responsible Person = -- Attribute Not Available
Phone Number = -- Attribute Not Available
MAIL Account = -- Attribute Not Available
Remarks = -- Attribute Not Available
Text File = -- Attribute Not Available
SNMP .ip.denny_hub_2
AT 16-JUL-1993 11:50:38 All Attributes
Address = -- Attribute Not Gettable
Name = -- Attribute Not Gettable
Registered Name = WAVE3_NS:.ip.denny_hub_2
ipReachability = up
sysUpTime = 128290400
CounterCreationTime = 1-JUL-1993 15:28:56.59
sysDescr = "DEChub 90 16 slots, DECagent 90
HW=D01 ROM=BL05.00 SW=V1.1"
sysObjectID = "1.3.6.1.4.1.36.2.15.10.1"
sysContact = -- Attribute Not Available
sysName = -- Attribute Not Available
sysLocation = -- Attribute Not Available
sysServices = 1
ifNumber = 1
Read Community Name = "hub_2"
Write Community Name = "hub_2rw"
Proxy Agent Address = 16.153.32.205
Location = -- Attribute Not Available
Implementation Desc = -- Attribute Not Available
Responsible Person = -- Attribute Not Available
Phone Number = -- Attribute Not Available
MAIL Account = -- Attribute Not Available
Remarks = -- Attribute Not Available
Text File = -- Attribute Not Available
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5345.1 | MOLAR::YAHEY::BOSE | Fri Jul 16 1993 12:32 | 9 | ||
The foreign devices (in your case the hubs without a DECagent) have neither an IP Address, nor an Internet Name. So, when you launch HUBwatch none of these identifiers can be passed to the application. I can't think of any way to launch HUbwatch directly on the secondary hubs. Maybe someone has some ideas regarding this. Rahul. | |||||
| 5345.2 | Can be done fairly easily | WELLIN::MCCALLUM | Wed Nov 03 1993 03:58 | 13 | |
The launch procedure could be updated to pass the proxy agent address
through to the command procedure as well as a community name and thus
make it work.
What I have done is to use a reference icon for each hub and proxied
hub, and use its reference attributes for agent name and community
name. You can then start hubwatch for any hub by clicking on the
appropriate reference icon. I put the reference icon next to the
appropriate agent icon.
Dave McCallum.
| |||||