| The DECserver90TL doesn't support "proxy". You can't manage it using
the address of the hub's Management Agent Module. It is only manageable
using the DECserver's IP address and community names.
> Is this a bug? How can I add the server to Hubwatch in a way that
> can be managed by users that use Hubwatch with both community names?
o Give the 90TL an IP address.
o Enable SNMP on the 90TL.
o Change the 90TL's read-write community of the 90TL to "whatever".
o Restart HUBwatch.
> I have checked the hub MIB variables using DECmcc, and under the
> chassis MIB, in the chassisentity table I can see an entry for the
> slots where the DECservers are located. I can only see those
> entries in the table when using "secret". This makes sense with
> the previous problem.
You're looking at the MAM's chassis MIB. When using the read-only
community, you can only view the read-only entries in the chasEntityTable.
When using the read-write community you can view both the read-only and
read-write entries in the table.
Assuming the hub's read-write community is "secret" and the 90TL's
read-write community is "whatever".... After performing the steps above
you should be able to use community "secret" to see entries in the
chasEntityTable for:
o the server's IP address and read-only community ("public"), and
o the server's IP address and read-write community ("whatever").
If you see anything different, please send me a dump of the chasEntityTable.
-Shawn
|
| >>> o Give the 90TL an IP address.
>>> o Enable SNMP on the 90TL.
>>> o Change the 90TL's read-write community of the 90TL to "whatever".
>>> o Restart HUBwatch.
I had already done it using the remote MOP console. Actually, I have
set entries for all servers in HUBWATCH_AGENTS.DAT, and it works OK
when managing servers in "standalone" mode.
When I add the modules to Hubwatch I am specifying the servers' ip
addresses
>>>you should be able to use community "secret" to see entries in the
>>>chasEntityTable for:
>>> o the server's IP address and read-only community ("public"), and
>>> o the server's IP address and read-write community ("whatever").
I will post here a dump of the chasEntityTable tomorrow (I must get to
the customer site), but as far I can remember, there is a single entity
for each slot with the following parameters:
chasEntityfunction = 8 (I believe it means terminal server)
chasEntitydescr = "DECserver 90TL 1 Mb memory ..."
chaentityipaddress = 0.0.0.0
chasentitycomaccessrights = other
chasentityaccessmethod = string including server MAC address
...
Luis
|
| >>> Set the DECserver's community to upper case PUBLIC.
It is already done. I append a harcopy of the MOP console for both
servers (slots 2 and 3) as well the chasentitytable entries
SERVER 1 (slot 3)
=> DECserver 90TL V1.1 BL44G-10A LAT V5.1 ROM 2.0.0 Uptime: 0
=> 20:13:46
=>
=>
=> Address: 08-00-2B-A2-A0-37 Name: LAT_08002BA2A037 Number: 0
=>
=> Identification:
=>
=> Circuit Timer: 80 Password Limit: 3
=> Console Port: 1 Prompt: Local>
=> Inactivity Timer: 30 Queue Limit: 100
=> Keepalive Timer: 20 Retransmit Limit: 8
=> Multicast Timer: 30 Session Limit: 64
=> Node Limit: 200 Software: MNENG1
=>
=> Service Groups: 0
=>
=> Enabled Characteristics:
=> Announcements, Broadcast, Dump, Lock
=>
SERVER 1 SNMP char:
=>
=> SNMP State: ENABLED Authentication Failure:
=> ENABLED
=>
=>
=> Community Name Address GET GETNEXT SET TRAP
=>
=> PUBLIC 7.0.0.1 ENA ENA ENA DIS
=> GOPHER 7.0.0.1 ENA ENA ENA ENA
=>
=>
=> Local>
=> Local>
SERVER 2 (slot 2):
=> DECserver 90TL V1.1 BL44G-10A LAT V5.1 ROM 2.0.0 Uptime: 0
=> 20:15:51
=>
=> Address: 08-00-2B-A2-AC-41 Name: LAT_08002BA2AC41 Number: 0
=>
=> Identification:
=>
=> Circuit Timer: 80 Password Limit: 3
=> Console Port: 1 Prompt: Local>
=> Inactivity Timer: 30 Queue Limit: 100
=> Keepalive Timer: 20 Retransmit Limit: 8
=> Multicast Timer: 30 Session Limit: 64
=> Node Limit: 200 Software: MNENG1
=>
=> Service Groups: 0
=>
=> Enabled Characteristics:
=> Announcements, Broadcast, Dump, Lock
=>
=> Local>
=>
=>
SERVER 2 SNMP CHAR:
=> SNMP State: ENABLED Authentication Failure:
=> ENABLED
=>
=>
=> Community Name Address GET GETNEXT SET TRAP
=>
=> PUBLIC 7.0.0.1 ENA ENA ENA ENA
=> GOPHER 7.0.0.1 ENA ENA ENA ENA
=>
=>
=> Local>
And here are the chasentity variables
show snmp madhub7003 dec ema decmibextension dechub900 mgmtagent
mgmtagentversio
n1 chassis chasEntity chasEntityTable * all char, by password gopher
!
!SNMP madhub7003 dec ema decMIBextension decHub900 mgmtAgent
mgmtAgentVersion1 c
hassis chasEntity chasEntityTable 1
!AT 26-OCT-1994 09:31:06 Characteristics
!
!Examination of attributes shows:
! chasEntityFunction = 1
! chasEntityObjectID = "1.3.6.1.4.1.36.2.15.9.3.1"
! chasEntityDescr = "DECrepeater 90FA,FO/AUI
Ethernet
! Rptr,HW=0"
! chasEntityVersion = "HW=0"
! chasEntityAdminStatus = enable
! chasEntityParty = -- Attribute Not Available
! chasEntityCommunity = %X7075626C69632D31
! chasEntityIpAddress = 7.0.254.13
! chasEntityComAccessRights = readOnly
! chasEntityAccessMethod = -- Attribute Not Available
! chasEntitySlotNumber = 1
!
!SNMP madhub7003 dec ema decMIBextension decHub900 mgmtAgent
mgmtAgentVersion1 c
hassis chasEntity chasEntityTable 2
!AT 26-OCT-1994 09:31:07 Characteristics
!
!Examination of attributes shows:
! chasEntityFunction = 1
! chasEntityObjectID = "1.3.6.1.4.1.36.2.15.9.3.1"
! chasEntityDescr = "DECrepeater 90FA,FO/AUI
Ethernet
! Rptr,HW=0"
! chasEntityVersion = "HW=0"
! chasEntityAdminStatus = enable
! chasEntityParty = -- Attribute Not Available
! chasEntityCommunity = %X676F70686572
! chasEntityIpAddress = 7.0.254.13
! chasEntityComAccessRights = readWrite
! chasEntityAccessMethod = -- Attribute Not Available
! chasEntitySlotNumber = 1
!
!SNMP madhub7003 dec ema decMIBextension decHub900 mgmtAgent
mgmtAgentVersion1 c
hassis chasEntity chasEntityTable 3
!AT 26-OCT-1994 09:31:08 Characteristics
!
!Examination of attributes shows:
! chasEntityFunction = 1
! chasEntityObjectID = "1.3.6.1.4.1.36.2.15.9.3.1"
! chasEntityDescr = "DECrepeater 90FA,FO/AUI
Ethernet
! Rptr,HW=0"
! chasEntityVersion = "HW=0"
! chasEntityAdminStatus = enable
! chasEntityParty = -- Attribute Not Available
! chasEntityCommunity = %X7075626C69632D31
! chasEntityIpAddress = 7.0.254.13
! chasEntityComAccessRights = traps
! chasEntityAccessMethod = -- Attribute Not Available
! chasEntitySlotNumber = 1
!
!SNMP madhub7003 dec ema decMIBextension decHub900 mgmtAgent
mgmtAgentVersion1 c
hassis chasEntity chasEntityTable 4
!AT 26-OCT-1994 09:31:08 Characteristics
!
!Examination of attributes shows:
! chasEntityFunction = 8
! chasEntityFunction = 8
! chasEntityObjectID = "1.3.6.1.4.1.36.2.15.6.3.1"
! chasEntityDescr = "DECserver 90TL,8 port
LAT/Telnet TS
! - 1MB"
! chasEntityVersion = -- Attribute Not Available
! chasEntityAdminStatus = enable
! chasEntityParty = -- Attribute Not Available
! chasEntityCommunity = -- Attribute Not Available
! chasEntityIpAddress = 0.0.0.0
! chasEntityComAccessRights = other
! chasEntityAccessMethod = %X01074D08002BA2A037
! chasEntitySlotNumber = 3
!
!SNMP madhub7003 dec ema decMIBextension decHub900 mgmtAgent
mgmtAgentVersion1 c
hassis chasEntity chasEntityTable 5
!AT 26-OCT-1994 09:31:09 Characteristics
!
!Examination of attributes shows:
! chasEntityFunction = 8
! chasEntityObjectID = "1.3.6.1.4.1.36.2.15.6.3.1"
! chasEntityDescr = "DECserver 90TL,8 port
LAT/Telnet TS
! - 1MB"
! chasEntityVersion = -- Attribute Not Available
! chasEntityAdminStatus = enable
! chasEntityParty = -- Attribute Not Available
! chasEntityCommunity = -- Attribute Not Available
! chasEntityIpAddress = 0.0.0.0
! chasEntityComAccessRights = other
! chasEntityAccessMethod = %X01074D08002BA2AC41
! chasEntitySlotNumber = 2
!
!SNMP madhub7003 dec ema decMIBextension decHub900 mgmtAgent
mgmtAgentVersion1 c
hassis chasEntity chasEntityTable 6
!AT 26-OCT-1994 09:31:09 Characteristics
!
!Examination of attributes shows:
! chasEntityFunction = 32768
! chasEntityObjectID = "1.3.6.1.4.1.36.2.15.9.7.1"
! chasEntityDescr = "DECrepeater 900TM 32 Port
TP
! Ethernet Rptr SNMP,
! HW=v1,RO=v1,SW=v1.0G"
! chasEntityVersion = "HW=v1,RO=v1,SW=v1.0G"
! chasEntityAdminStatus = enable
.... The rest of entries are for the DECrepeater900 in the rest of the
slots , and they look similar to the ones for the DECrepeater 90
in slot one
|
| Hi
I been investigating further this problem, and I have some extra info
that I would like to discuss to the gurus of the HUB SNMP agent.
- As I posted in .-1, there is a single chasEntity in the table for
each slot that contains a DECserver 90TL.
- The chasEntity can only be seen when you use the r/w community name.
- chasEntityDescr is "DECserver ..." for those entries, but you must
extract and insert the module after you update the Hub firmware (what I
did), and then the agent sets this value. Otherwise it is "not gettable"
- chasEntityAccessMethod is %X03076D08002BA2B085 (for slot 2). This
does not make sense according to the MIB description I have (MAy 1994),
since octet one should be:
1 = dh90Module
2 = mgmtSet
- there is a chasEntityAccessLoadTable for this slot with value equal
to the chasEntityAccessMethod
- there is an ERROR when trying to retrieve the value of
chasEntityComAccessRights (this can make sense with the fact that
chasEntityIPAddress is 0.0.0.0)
- if I try to add a module to the hub using the r/o community name, the
module is effectively added to the hub, BUT I can see an error in the
message box = "failed to load slot information into the hub", and the
module "disappears" the next time I enter Hubwatch.
QUESTION:
My guess is that if I enter Hubwatch using the hub's r/w
comm. name, Hubwatch can create or modify the chasEntity entry for the
slot, so it works.
Also, if I enter Hubwatch using the r/o comm. name, Hubwatch CAN NOT
create or modify the entry.
So, is there any way to "modify" the chasEntity entries that exists
now for those slots to make them accessible from the r/o comm. name ? OR
is there any way to create another chasEntity entry for the
slot that is accessible from the r/o comm. name ?
Thanks a lot for any help
Luis
|