Snippet possible bug w/ mac address encoding
Has anyone run into an issue where a few MAC addresses are being read by the snmp handler `snmp_walk` method as gibberish? Non-MAC address string data is returned on some interfaces that seems to be some form of unicode. This is an example when running the SNMP walk from bash: IP-MIB::ipNetToMediaPhysAddress.2.10.250.123.5 = STRING: 24:2a:4:f0:7a:c7 This is the same OID when read by the python SNMP handler: ('.1.3.6.1.2.1.4.22.1.2.2.10.250.123.5', '$*\x04ðzÇ') I've tested the python2.7 execution environment, and the 3.6 env from the Cisco base pack 214. Thanks! Joe
Who will be our next SL1 Innovators?
Hello Nexus Members, Looking to showcase your creativity, innovation, and inspiration? Look no further. In case you're opted out of email, we just launched our SL Innovators Awards!! Our ScienceLogic Innovators Awards were established to recognize and learn from those nerdy by nature, tech buffs, and visionaries using SL1 in pioneering ways to power a better way to work. Show the Nexus Community something cool and innovative you've been working on to achieve real business outcomes. We want to hear your ideas! Submit your applicationby September 12.Cisco Unified Communications Manager 14 EOL and 15 Upgrade tips slides from Cisco Live
Hello all! I'm sure some of you are at Cisco Live NAM right now, but if you aren't, there was a great presentation on CUCM. CentOS is being swapped out, CUCM 15 appears to be switching to Python 3, along with other security changes. They've announced an EOL date for CUCM 14 as well. Take a look at the slide deck as it's very interesting. Their product team also informed me that the API is unchanged from v12.5 through CUCM 15, so our integration should continue to work. Please let us know if you have any issues with the latest version of our PowerPack and CUCM 15.
Azure monitoring and integration with CMDB
When gathering information from cloud stuff, or actually doing whatever with cloud staff you most often need the object's ID, that long hexastring. That same ID is also most used identifier and required information when trying to sync those cloud "devices" into ServiceNow CMDB. The issue is that SL1 Azure PP does not gather that information too much, one device class that we have so far found it is those actual VMs in cloud. But one could say that those are the only "devices" where it is easily found. So my question is, how you have planned, or done, the CMDB integration of Azure cloud stuff. Or have you done any automation from SL1 to Azure, because also there one always(?) need that object ID. I could have written also an Idea for this, but at least for me, Nexus does not support my ideas.
