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 |
Customer states that he cannot see his DECswitch900. ( a new router/ bridge that I've never seen or heard of before), thru 1.3 MCC. Anyone else having a problem with this? thanks.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
6200.1 | Use TCP/IP. no RBMS Management... | MSDOA::REED | John Reed @CBO, (803) 781-9571 NIS Networker | Wed Dec 28 1994 18:37 | 10 |
He won't have any luck, if he is trying the ELM AM/FM. If he can manage the DECswitch900 (Its a DECbridge900mx, with a new name) using HUBwatch, then he can manage it using DECmcc. You must give it an IP address, and SNMP community. Then define it in the MCC database, and you can do MIB-II gets and sets. If you need to do more detailed stuff, you will have to compile the extended MIBS, but I prefer HUBwatch. JR |