EcoStruxure IT forum
Schneider Electric support forum about installation and configuration for DCIM including EcoStruxure IT Expert, IT Advisor, Data Center Expert, and NetBotz
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-02 10:19 PM . Last Modified: 2024-04-09 01:30 AM
Dear guys,
We are running a PoC in a customer who is using BEM. From DCE we are sending traps to the BEM and the customer is asking for a mib file to import in the BEM system. Where can we find it?
Best regards,
Enric
(CID:105460358)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-02 10:19 PM . Last Modified: 2024-04-09 01:29 AM
Hi Enric,
The MIB that is used to define the traps sent using the NMS integration feature is the powernet MIB which is available on the APC downloads page. The MIB used for traps sent using the alarm action trap is the NetBotz MIB which should also be available on the software downloads page. It is also downloadable from a NetBotz version 3 appliance.
Please note one you can not poll DCE for device specific data via SNMP.
Steve
(CID:105460382)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-02 10:19 PM . Last Modified: 2024-04-09 01:29 AM
Hi Enric,
The MIB that is used to define the traps sent using the NMS integration feature is the powernet MIB which is available on the APC downloads page. The MIB used for traps sent using the alarm action trap is the NetBotz MIB which should also be available on the software downloads page. It is also downloadable from a NetBotz version 3 appliance.
Please note one you can not poll DCE for device specific data via SNMP.
Steve
(CID:105460382)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-02 10:19 PM . Last Modified: 2024-04-09 01:29 AM
Please check out kbase FA231439 for more info
(CID:105460677)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-02 10:20 PM . Last Modified: 2024-04-09 01:29 AM
Hi Steve,
I'm using both, netbotz and powernet mibs and the customer cannot read the sent traps.
Any suggestion? He is receiving a non readable traps.
Regards,
Enric
(CID:105468048)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-02 10:20 PM . Last Modified: 2024-04-09 01:29 AM
Hi Enric,
Traps actually come across with both OIDs and text. An isxcErrorAlarm or an isxcCriticalAlarmCleared for instance. No MIB is required to see this information. The traps noted above as well as the ones sent using the NetBotz MIB are nested traps. You can actually see the nested data (arguments) as in the k-base I previously posted. I have seen a few trap receivers have issues with nested traps. I am not familiar with the tool you are using but perhaps it too is seeing issues with these nested traps.
As an example, you can use a freeware trap receiver and actually see the info to which I'm referring. You can also use a packet capture utility and even in that raw data, you can see the alarm text as well as the text for each of the arguments. Here's an example of the raw text that comes across with a NetBotz trap on a freeware trap receiver with no NetBotz MIB installed:
VarBinding 1: 1.3.6.1.4.1.5528.100.11.1 = nbErrorCond_6372BB85
VarBinding 2: 1.3.6.1.4.1.5528.100.11.2 = nbErrorType_errorstate
VarBinding 3: 1.3.6.1.4.1.5528.100.11.3 = Value Error
VarBinding 4: 1.3.6.1.4.1.5528.100.11.4 = nbAlinkEnc_0_2_SPLK
VarBinding 5: 1.3.6.1.4.1.5528.100.11.5 = Spot leak (2)
VarBinding 6: 1.3.6.1.4.1.5528.100.11.6 = nbAlinkEnc_0
VarBinding 7: 1.3.6.1.4.1.5528.100.11.7 = Sensor Pod
VarBinding 8: 1.3.6.1.4.1.5528.100.11.8 =
VarBinding 9: 1.3.6.1.4.1.5528.100.11.9 =
VarBinding 10: 1.3.6.1.4.1.5528.100.11.10 = 1431620034
VarBinding 11: 1.3.6.1.4.1.5528.100.11.11 = 1431620034
VarBinding 12: 1.3.6.1.4.1.5528.100.11.12 = 0
VarBinding 13: 1.3.6.1.4.1.5528.100.11.13 = 2
VarBinding 14: 1.3.6.1.4.1.5528.100.11.14 = No Leak
VarBinding 15: 1.3.6.1.4.1.5528.100.11.15 = 0
VarBinding 16: 1.3.6.1.4.1.5528.100.11.16 = 0
Steve
(CID:105468062)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-02 10:20 PM . Last Modified: 2024-04-09 01:29 AM
Hi again Steve,
Now I find the problem. The customer is monitoring an AP8453 device with OID 1.3.6.1.4.1.5528.100.10.2.33.
The latest netbotz mib file is netbotz410.mib and it hasn't this OID.
Do you know where can I found a newer mib file?
Regards,
Enric Climent
(CID:105468081)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-02 10:20 PM . Last Modified: 2024-04-09 01:29 AM
Hi Enric, If you would like an early evaluation of the new NetBotz410 MIB, I'm attaching it here. It is running through our final testing process right now, and will be available to download from the APC website in a few weeks. But I thought I'd offer you the opportunity to try it out now and make sure it solves your customer's issue. -Scott
(CID:105474373)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-02 10:20 PM . Last Modified: 2024-04-09 01:29 AM
Hi Steve, I'd like to try this new NetBotz410 MIB. Could you attach it? Best regards, Enric
(CID:105474429)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-02 10:20 PM . Last Modified: 2024-04-09 01:29 AM
Hi Steve, Now I can see the Scott attached file. Best regards, Enric
(CID:105474462)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-02 10:20 PM . Last Modified: 2024-04-09 01:29 AM
Hi Enric, Were you able to try out the new MIB and verify whether it worked for your customer? Please keep us let us know once you've had the opportunity. Thanks, Scott
(CID:106203187)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-02 10:20 PM . Last Modified: 2024-04-09 01:29 AM
Hi Enric,
AP8453 is an APC device. If the device itself is sending a trap, it would be under 1.3.6.1.4.1.318. This would be an APC trap found in the Powernet.mib file from www.apcc.com/tools/download. If you are using DCE to monitor the devices and the traps are coming from DCE and not directly from the device, that's when you want to look at the k-base I noted earlier. If you have it set up so that you're using the NMS integration feature in DCE, you will get a 1.3.6.1.4.1.318 based trap such as isxcCriticalAlarm.
If on the other hand you are using the SNMP trap alert action, you would then get a NetBotz 1.3.6.1.4.1.5528. trap. Either way a packet capture will tell you what is being sent from DCE (if anything). If you are not looking to receive a trap but are instead trying to do a get or a set, that must go directly to the device and you must use the powernet mib 1.3.6.1.4.1.318. If you are looking to poll the unit for a specific OID, please give me an example and I can show you an OID to use. Most OIDs you would be using for a get or set would be found under:
.1.3.6.1.4.1.318.1.1.26
.iso.org.dod.internet.private.enterprises.apc.products.hardware.rPDU2
Steve
(CID:105468090)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-02 10:20 PM . Last Modified: 2024-04-09 01:29 AM
Hi Steve,
Attached you can find the trap received in BEM. There you can see the OID 1.3.6.1.4.1.5528.100.10.2.33 which is not found in the netbotz410 mib file.
Regards,
Enric
(CID:105468174)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-02 10:21 PM . Last Modified: 2024-04-09 01:29 AM
Hi Enric,
Thank you for that information, it clarifies the issue. I must have missed the specific OID in an earlier post. So it is not that you can not find traps in the mib in general, it is that there is a specific trap missing. For this OID, enterprise.5528.100.10.2.33, I already have an enhancement request in the system to get the NetBotz MIB updated. The only thing I can do at this point is to add this post to the request and I have done so.
I have also asked engineering that if they have a specific definition for any missing OIDs, if they can at least define it, for instance if I could just answer this post and say 5525.100.10.2.31 is netBotzLoopVoltageSensorTraps, that would at least be somewhat helpful for now.
Steve
(CID:105468212)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-02 10:21 PM . Last Modified: 2024-04-09 01:29 AM
Hi Enric,
Scott has attached it above in his comment yesterday at 10:36 AM. Are you not able to see / download it?
(CID:105474444)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-02 10:21 PM . Last Modified: 2023-10-31 10:27 PM
This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.
Link copied. Please paste this link to share this article on your social media post.
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.