<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Snmp on vlan51</title><link>https://vlan51.com/tags/snmp/</link><description>Recent content in Snmp on vlan51</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Mon, 01 Jan 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://vlan51.com/tags/snmp/index.xml" rel="self" type="application/rss+xml"/><item><title>SNMPv3 Configuration on HPE Aruba ArubaOS-Switch with HPE IMC</title><link>https://vlan51.com/aruba-provision/snmpv3-imc/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://vlan51.com/aruba-provision/snmpv3-imc/</guid><description>&lt;p&gt;How to configure SNMPv3 on HPE Aruba ArubaOS-Switch for HPE IMC. The built-in wizard initialises SNMPv3, then you replace the wizard user with a stronger SHA/AES-128 account.&lt;/p&gt;&#10;&lt;h2 id="step-1--run-the-snmpv3-wizard"&gt;Step 1 — Run the SNMPv3 wizard &lt;a class="anchor" href="#step-1--run-the-snmpv3-wizard" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Use throwaway passwords — you will delete this user:&lt;/p&gt;&#10;&lt;div class="code"&gt;&#10; &lt;div class="code-bar"&gt;&lt;span&gt;cli&lt;/span&gt;&lt;button class="copy" type="button" aria-label="Copy to clipboard"&gt;Copy&lt;/button&gt;&lt;/div&gt;&lt;pre&gt;&lt;code&gt;Switch(config)# snmpv3 enable&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;p&gt;At the prompts: accept defaults, answer &lt;code&gt;n&lt;/code&gt; to creating a SHA user, answer &lt;code&gt;y&lt;/code&gt; to restricting SNMPv1/v2c to read-only.&lt;/p&gt;</description></item><item><title>Adding Devices to HPE IMC with Access Parameter Templates</title><link>https://vlan51.com/imc/adding-devices/</link><pubDate>Wed, 01 Jun 2016 00:00:00 +0000</pubDate><guid>https://vlan51.com/imc/adding-devices/</guid><description>&lt;p&gt;Adding a device to IMC is straightforward once you get the hang of it, but a little preparation makes sure devices go in properly and stay manageable.&lt;/p&gt;&#10;&lt;h2 id="1-set-up-access-parameter-templates-first"&gt;1. Set up access parameter templates first &lt;a class="anchor" href="#1-set-up-access-parameter-templates-first" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;IMC&amp;rsquo;s first screen prompts you to add a device. Before you do, create templates for SNMP and SSH access. You can then apply the same credentials to groups of devices instead of typing them in every time.&lt;/p&gt;</description></item><item><title>Fixing "Device Denied SNMP Access" Traps in HPE IMC</title><link>https://vlan51.com/imc/snmp-denied-access/</link><pubDate>Wed, 01 Jun 2016 00:00:00 +0000</pubDate><guid>https://vlan51.com/imc/snmp-denied-access/</guid><description>&lt;p&gt;IMC needs correct SNMP credentials to read the MIBs on each device. When they&amp;rsquo;re wrong, you&amp;rsquo;ll see traps like these:&lt;/p&gt;&#10;&lt;div class="code"&gt;&#10; &lt;div class="code-bar"&gt;&lt;span&gt;cli&lt;/span&gt;&lt;button class="copy" type="button" aria-label="Copy to clipboard"&gt;Copy&lt;/button&gt;&lt;/div&gt;&lt;pre&gt;&lt;code&gt;Trap Name: Device Denied SNMP Access&#10;Severity: Major&#10;Trap Time: 2016-05-30 19:41:43&#10;Description: Device &amp;#34;My Network Switch&amp;#34; denied access.&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;div class="code"&gt;&#10; &lt;div class="code-bar"&gt;&lt;span&gt;cli&lt;/span&gt;&lt;button class="copy" type="button" aria-label="Copy to clipboard"&gt;Copy&lt;/button&gt;&lt;/div&gt;&lt;pre&gt;&lt;code&gt;iMC: 10.0.10.10&#10;Trap of Source: MYSWITCH (10.0.10.254)&#10;Location: Home&#10;Contact: &amp;#34;Network Admins&amp;#34;&#10;Trap Name: Authentication Failure&#10;Severity: Warn&#10;Trap Time: 2016-05-31 07:15:23&#10;Description: Device receives an SNMP message with an erroneous community string&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;p&gt;These are almost always the device (switch, firewall and so on) refusing IMC&amp;rsquo;s requests. Check the device&amp;rsquo;s own logs and you&amp;rsquo;ll usually find the failures line up with IMC&amp;rsquo;s polling times.&lt;/p&gt;</description></item><item><title>Tuning Link Up/Down Flap Alarms in HPE IMC</title><link>https://vlan51.com/imc/link-flap-alarms/</link><pubDate>Thu, 01 Jan 2015 00:00:00 +0000</pubDate><guid>https://vlan51.com/imc/link-flap-alarms/</guid><description>&lt;p&gt;IMC raises this alarm when a port flaps:&lt;/p&gt;&#10;&lt;div class="code"&gt;&#10; &lt;div class="code-bar"&gt;&lt;span&gt;cli&lt;/span&gt;&lt;button class="copy" type="button" aria-label="Copy to clipboard"&gt;Copy&lt;/button&gt;&lt;/div&gt;&lt;pre&gt;&lt;code&gt;iMC alarm system found event (Link UP) and event (Link DOWN) had 3 intermittent failures from &amp;lt;date/time&amp;gt; to &amp;lt;date/time&amp;gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;h2 id="investigate-before-tuning"&gt;Investigate before tuning &lt;a class="anchor" href="#investigate-before-tuning" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Don&amp;rsquo;t dismiss link flaps. Find the device and port in the alarm, log into the switch, and check the log (newest first on ArubaOS-Switch):&lt;/p&gt;&#10;&lt;div class="code"&gt;&#10; &lt;div class="code-bar"&gt;&lt;span&gt;cli&lt;/span&gt;&lt;button class="copy" type="button" aria-label="Copy to clipboard"&gt;Copy&lt;/button&gt;&lt;/div&gt;&lt;pre&gt;&lt;code&gt;show logging -r&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;p&gt;Look for errors like this one, which point to a real physical problem you need to fix:&lt;/p&gt;</description></item></channel></rss>