SNMP config file/MIB modification on VNX

You can copy your config file from host to host using Linux commands such as scp.  Something to the effect of "scp my.mib nasadmin@remotecelerra:/home/nasadmin/my.mib"

As far as configuring the MIB, you should take a look at the VNX documentation, Configuring Events and Notifications on VNX.  In the section on MIBs, it refers to the trap number that's associated within the MIB file itself.

I have been reading the documentation and that is why i posted here.

The confusion is whether the identifier should be the same for all events.  Since I have so many events that should send traps, if they all come in with the same identifier from the MIB, that would cause confusion.  It is not clear if each event should have its own identifier, especially when, for some of the facilities, i only have a severity range and not specific ranges.

I'm really looking for some guidance as I have been reading the documentation and still have some questions.

That is a little more helpful yes.  So, it's possible i may need to add additional lines to the MIB file, correct?  i know the MIB has 10-12 IDs already. 

You've been very helpful, so thank you.  I can still use the identifiers in the MIB right?  I'll have to take a deeper look into what i have configured and what identifiers i want to use.  This could be a long process, but i appreciate your help.

Take a look at page 45 and page 88.  On page 88, the control station will send the trap you specified with trap number specified in the .cfg file.  So, in your example above, each of your configured events above will send the same trap, because they have the same trap number. So, as it says on page 45, you need to create a unique trap number for the traps you create.  And yes, you may have lots of trap numbers, but it's a 32-bit counter, so you have quite a ways to go.  Does this help?

Yes, that's correct again.  You'll need to create a entry for each additional item you want to trap on.  From Page 45:

Modify the MIB file for SNMP traps

If the default SNMP traps do not properly describe the condition that you want to trap, you

can define additional SNMP traps by modifying the system MIB file:

1. Modify the MIB, /nas/sys/emccelerra.mib, to include the following lines:

celCFS TRAP-TYPE

ENTERPRISE emcCelerra

VARIABLES {celEvent}

DESCRIPTION

" "

::=

where:

= description of the trap.

= arbitrary, yet unique, trap number for the event that you specified in the notification configuration file. Some trap numbers are reserved. Ensure to check the trap definition section of the MIB, /nas/sys/emccelerra.mib, before assigning a trap number.

So, you just need to keep adding trap entries with unique numbers.  I had 30 or so traps back in the day, so it's not unheard of to have as many as you require.  Let me know if you have more questions.

You should be able to use the existing identifiers - the only requirement is that trap IDs must be unique.  After, pretty much anything goes. 

When you're happy with the state of the MIB and any changes made to the notification config file, just use SCP to copy them from one control station to the next.  All the file locations will be the same between each box.  Let us know how it goes!

Do i assign the trap IDs or how can i be sure that the trap IDs are unique?

Yes - when you modify the MIB, you assign the unique ID number as in step 1 above.  For consistency, I started my numbers at 100 and incremented from there.

I modified the MIB and the eventlog.cfg so they would have matching trap IDs.  However, when i tried to send a test trap, it didn't work.  i used trap IDs 50-61.  i'm not sure why the traps didn't go through.  Any suggestions are welcome.