| 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 |
Hi,
Yesterday I installed the new FT 1.2.7 and tried to add the MIBs for
CISCO, coming with the kit, on VMS and ultrix. Unfortunately they
do not translate good.
Before I did the same exwercise with v 1.2.4 and there were no
problems. With the new version most of the important classes are
disappeared.
I have to demonstrate to a very large customer next week that we can
manage very well cisco boxes, but at this moment it is not possible.
Do you have any idea why this is happening. IT IS VERY URGENT !
Thanks in advance,
Tankut
below is the log from ultrix: (vms log is the same as well)
# mcc_tcpip_mtu.csh
Welcome to the DECmcc TCP/IP MIB Translator Utility driver procedure
<T1.2.7>
Fri Apr 24 17:11:06 WET DST 1992
This procedure operates in a 2 phased manner --
Phase 1 translates a MIB definition into a management specification.
Phase 2 (as an option) translates the management specification into a
dictionary loadable file and updates the DECmcc data dictionary.
Phase 1 -- Enter name(s) of file(s) to translate
(separate multiple files by spaces): cisco_mibdef.txt
* * *
(Now processing file # 1 out of a list of 1 file(s) ...)
Beginning Phase 1 for file cisco_mibdef.txt
Fri Apr 24 17:11:15 WET DST 1992
Now starting to run the MIB Translator ...
This may take approximately 1-5 minutes.
Issuing following command:
mcc_tcpip_mtu cisco_mibdef.txt
Entity Model tree is being pruned.
The following non-leaf objects are being removed:
Child entity gateway_server
Child entity terminal_server
Child entity trouter
Child entity protocol_translator
Child entity protocol_translator
Child entity igs
Child entity linterfaces
Child entity lat
Child entity licmp
Child entity ltcp
Child entity ludp
Child entity legp
MIB translation completed successfully.
Fri Apr 24 17:11:18 WET DST 1992
Phase 1 for file cisco_mibdef.txt completed.
Phase 2 for file cisco_mibdef.txt not performed.
(MIB definition translated into management specification but
management specification not translated into dictionary loadable
file and
DECmcc data dictionary not updated)
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2856.1 | YAHEY::BOSE | Mon Apr 27 1992 11:08 | 10 | ||
>> problems. With the new version most of the important classes are >> disappeared. Can you say specifically which classes have disappeared? Can you do a diff on the old chipcom_mibdef.ms and the new file. (The .ms files are created in the directory where you sitting when you run the mtu script). Rahul. | |||||
| 2856.2 | HOO78C::TURHAN | Tue Apr 28 1992 03:40 | 35 | ||
Hi,
First to clear some misunderstanding, in your reply .1 you mention
about chipcom, but I was talking about cisco.
The clases marked as pruned in the log are disappeared. Previously,
when I clicked on the cisco line I used to get a full list of all
protocols plus some others. And nothing was pruned during translation.
A lot of things are pruned with the new version.(i.e. lat, terminal
server, ltcp,licmp,ludp,legp,igs,linterfaces ...)
Now when you click on the cisco line in the snmp am, you get three
lines,
- products
- local
- temporary
where products has no children, local has: lsystem, liftable,lip,lts
and temporary has decnet,xns,appletalk,novel,vines.
I am not sure but it also seems that there are less "set"able things
now.
About the diff on the ms file, I do not have it stored so I cannot give
you a clear answer on this. When I scan my directories, the mib file I
used (I think I used) is 269 blocks and the new one coming with the kit
is 266 blocks. If you like I can send them to you.
Looking forward to hear more on this.
Regards,
Tankut
| |||||
| 2856.3 | Limited MIB Function = True | SEDOAS::BEST | Tue Apr 28 1992 07:16 | 19 | |
It is my understanding that the CISCO MIB has very few "settable"
variables available. Cisco themselves have said that this was a
planned design constraint after feedback from it's customers about
the lack of security around SNMP.
What I'm really saying is that you still have to TELNET to the
Cisco box to perform key management tasks and this leads to
customers thinking what do I want SNMP for?
I'm afraid until Cisco are convinced of the need to change the
variable which are "Settable" then customers will have to make
do with Telnetting to the box.
One thing to make quite clear to customers is that this is not
a problem with DECmcc but one of the "risks" associated with
the SNMP market today.
Regards... Peter B
| |||||
| 2856.4 | YAHEY::BOSE | Tue Apr 28 1992 11:34 | 23 | ||
RE .2 >> First to clear some misunderstanding, in your reply .1 you mention >> about chipcom, but I was talking about cisco. Sorry about that. I meant "cisco" but typed in "chipcom" instead. Must have been a temporary disconnect between my brain and my motor organs. :-) >> A lot of things are pruned with the new version.(i.e. lat, terminal >> server, ltcp,licmp,ludp,legp,igs,linterfaces ...) I looked in the mib and found the above groups to be empty. As you know, the mib translator prunes all child entities which do not have any attributes (except the top level in the tree). So you are not losing any information as a result of this pruning. Maybe the mib that you had originally differs from what we have on the kit. Mail me the mib and I'll try to find out if it is different. You may also want to run MTU with your own copy of the mib and see if the result differs. Rahul. | |||||