Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
Link copied. Please paste this link to share this article on your social media post.
Hi Good day!
The customer wants snmp trap to be receive from dce. Hence, I configured the the alarm thresholds and actions and also add the trap receiver. I downloaded also the MIB file (powernet421.mib) and provide to customer.
After the test, they were saying "We received test traps at Spectrum, communication test is fine. But some errors on the MIB file" in which they could not see the alarm. Below snap shot for reference.
Please advice.
Thanks,
Lizlex
Link copied. Please paste this link to share this article on your social media post.
Hi Lizlex,
K-base FA231439 may help you understand DCE traps, the 2 different ways they can be sent, and what each argument is referring to.
As for specific errors in the mib, I have not seen any issues to this point but have you tried using different versions of the MIB to see if there is something specific to the version you're using? You can find different versions here:
ftp://ftp.apc.com/apc/public/software/pnetmib/mib/
When opening the MIB in a text editor, I checked line 15809 and the trap that includes that line does indeed have an access component:
If I assume that the first 241 lines of the mib that are commented out are not part of what this 3rd party software is counting, I would then go to line 16050. I see an access identifier there too:
The one thing I DID see in the initial screenshot was in the syntax field there were 2 lines, each end with a comma. In every other object type ni that area that has similar syntax components, the last line of the mib does not have a comma as seen in my second screenshot. It may be something as simple as that. You can edit the MIB, delete that comma, and try again. commas , colons, brackets and the lack thereof can often cause NMS systems to see errors.
Steve
Link copied. Please paste this link to share this article on your social media post.
Hi Steve,
I have provided other version which is the powernet419.mib to the customer and below is the feedback.
"Given MIB is error free, but it doesn’t seems to support the OIDs we are receiving in Traps."
Trap OIDs supported by given MIB: 1.3.6.1.4.1.318.0.*
Trap OIDs being received from System : 1.3.6.1.4.1.5528.100.*
Please share the relevant MIB.
Please advice.
Lizlex
Link copied. Please paste this link to share this article on your social media post.
Hi Steve,
Going back to the topic.
I have provided the NetBotz MIB 410 and also the 320 to the Integration team. However, they were saying that both mib have the same issue. They are recieving traps, but some of the traps recieved have no definition on the mib file. please find below their feedback.
"Provided MIB doesn’t seems to be updated or complete. It doesn’t have definition of few traps.
Like following trap has no definition in MIB. Trap ID : 1.3.6.1.4.1.5528.100.10.2.6.10
They are requesting the updated or modified mib file.
Please advice.
Thanks,
Lizlex
Link copied. Please paste this link to share this article on your social media post.
This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.