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 |
Hello, I'm not sure if this is a problem with DECmcc or DECagent, so I'm posting this note in both applicable conferences. I have just upgraded a customer's DECagents to V1.1, and DECmcc to V1.3. The problem is that under DECmcc I can no longer see anything in the "drpt90PortTable" under the DH90 MIB. HUBwatch V1.1, however, appears to be showing repeater ports OK. (With DECagent 1.0 and mcc 1.2 I *could* see "drpt90PortTable" entries under mcc.) Since I've upgraded *both* DECagent and DECmcc software I'm not sure where the problem's coming from ... ANY IDEAS PLEASE ??? Richard.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
5321.1 | Private MIB on CHNAPS:: | ZTOIS1::VISTA | Renato VISTA, MCS/SPS France/Strasbourg | Fri Jul 09 1993 11:11 | 13 |
Richard, Hereunder an EASYnet pointer where you can find the good private MIB to load into DECmcc dictionary before any operation on DECagent 90 : on CHNAPS:: (47.154) File is CHNAPS::DH90_MIB.TXT I hope this will help you. Renato | |||||
5321.2 | still not working ... | FAILTE::JONESR | Tue Jul 20 1993 05:53 | 23 | |
Renato, Thanks for the MIB - there was a minor bug, line 579 had a comma at the end which should not have been there ... However, I'm still having problems. From the iconic map when I double-click on drpt90PortTable, I get "No response from entity". I find that it is possible to explicitly register repeater ports into the iconic map, then I can select the port and get counters, status, etc - but next time I go into the drpt90PortTable, the ports have gone, and I get no response again. I also tried accessing the repeater prots from the FCL ... eg MCC> show snmp <hubname> dec ema drpt90PortTable * all attrib and this worked OK ... BUT ONLY for the hub where the agent "lives" . ie I don't get any response for proxy hubs. Is this looking like a problem with mcc ?? Has anybody got this to work ? Richard. | |||||
5321.3 | MOLAR::YAHEY::BOSE | Wed Jul 21 1993 10:41 | 11 | ||
>>and this worked OK ... BUT ONLY for the hub where the agent "lives" . ie I >>don't get any response for proxy hubs. Have you managed to get any reponse at all from the foreign devices? Normally, the foreign devices can be accessed using its hardware address as community name. Are you using the correct community name? I don't have any other obvious explanation. Maybe someone else who has managed to query the DECagent can help you out. Rahul. |