Imc on vlan51

SNMPv3 Configuration on HPE Aruba ArubaOS-Switch with HPE IMC

Mon, 01 Jan 2024 00:00:00 +0000

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.

Step 1 — Run the SNMPv3 wizard #

Use throwaway passwords — you will delete this user:

cli

Switch(config)# snmpv3 enable

At the prompts: accept defaults, answer n to creating a SHA user, answer y to restricting SNMPv1/v2c to read-only.

Adding Devices to HPE IMC with Access Parameter Templates

Wed, 01 Jun 2016 00:00:00 +0000

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.

1. Set up access parameter templates first #

IMC’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.

Fixing "Device Denied SNMP Access" Traps in HPE IMC

Wed, 01 Jun 2016 00:00:00 +0000

IMC needs correct SNMP credentials to read the MIBs on each device. When they’re wrong, you’ll see traps like these:

cli

Trap Name: Device Denied SNMP Access
Severity: Major
Trap Time: 2016-05-30 19:41:43
Description: Device "My Network Switch" denied access.

cli

iMC: 10.0.10.10
Trap of Source: MYSWITCH (10.0.10.254)
Location: Home
Contact: "Network Admins"
Trap Name: Authentication Failure
Severity: Warn
Trap Time: 2016-05-31 07:15:23
Description: Device receives an SNMP message with an erroneous community string

These are almost always the device (switch, firewall and so on) refusing IMC’s requests. Check the device’s own logs and you’ll usually find the failures line up with IMC’s polling times.

HPE IMC Installation and Upgrade Errors (and Fixes)

Wed, 01 Jun 2016 00:00:00 +0000

This isn’t a step-by-step install guide. It’s a collection of problems I’ve hit while installing and upgrading IMC, and how I got past them.

Installing: .NET 3.5 “source files could not be found” #

On Windows Server 2012, IMC’s installer needs the .NET Framework 3.5 feature, which can fail to install because the source files can’t be found.

Mount the Windows Server ISO (here as D:) and run this from an elevated command prompt, changing the drive letter if needed:

Monitoring Hyper-V Hosts in HPE IMC with VRM (without SCVMM)

Wed, 01 Jun 2016 00:00:00 +0000

How to add a Hyper-V host to IMC and monitor it with VRM (Virtual Resource Manager), without System Center Virtual Machine Manager (VMM). Written against IMC 7.1.

Make sure the VRM component is deployed, using the Intelligent Deployment Monitoring Agent (IDM).
Install the LLDP agent on the Hyper-V server.
Install the VRM agent on the Hyper-V server.
Point the VRM agent at the IMC server address on port 8800. The agent’s settings label this field “IMG”.
Configure WMI credentials for the host in IMC.

You don’t need to add PowerShell parameters unless you’re using VMM.

Tuning Link Up/Down Flap Alarms in HPE IMC

Thu, 01 Jan 2015 00:00:00 +0000

IMC raises this alarm when a port flaps:

cli

iMC alarm system found event (Link UP) and event (Link DOWN) had 3 intermittent failures from <date/time> to <date/time>

Investigate before tuning #

Don’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):

cli

show logging -r

Look for errors like this one, which point to a real physical problem you need to fix: