Brocade Logo

Add Brocade MLX & VDX Support to HP IMC

HP IMC 7.1 E0303P13 does not support configuration backups for Brocade MLX & VDX devices. But they do have an extensible model, so it’s easy to add support. Here’s how to do it, and how to fix the Brocade ICX support.

Here’s the steps to add support for MLX & VDX devices to HP IMC:

  1. Download the current set of adapters from GitHub.
  2. Unpack the zip file, and copy the adapters into place.
  3. Add Device Series & Device Model definitions.
  4. Restart IMC, re-synchronise, and check file transfer modes.

Going into a bit more detail:

NB: Yes, I do work for Brocade. That doesn’t mean that these adapters are fully supported by Brocade. I’ll help out however I can, but can’t promise anything.

NetOps Custom Adapters

This GitHub repository maintains a set of 3rd-party developed adapters for HP IMC. You can download individual files, create a local copy of the repo using Git, or just download a zip file containing all current scripts from here.

On the IMC server, adapters are stored at (IMC)/server/conf/adapters/ICC. You’ll see directories for all supported vendors there:

Under each vendor directory is an adapter-index.xml file containing mappings to specific adapters, and a directory for each specific adapter. So we can see here that Cisco has a number of different adapters for different Cisco devices:

From either your local copy of the repo, or the downloaded zip file, find the adapters/ICC/Brocade directory. Copy adapter-index.xml, Vyatta, BrocadeMLX and BrocadeNOS to (IMC)/server/conf/adapters/ICC/Brocade on your IMC server.

Device Definitions

If you discover a Brocade VDX system with HP IMC, it will be monitored via SNMP. But it shows up as “Brocade Generic.” Similarly, an MLX will show up as “Foundry Generic.” This is mostly just a cosmetic annoyance (but make sure the displayed vendor name matches the adapter directory). Here’s how to fix that:

  1. Open the IMC web interface. Go to System -> Resource Management -> Device Series
  2. Click “Add” – add new series name “Brocade MLX.” Set the vendor to Brocade, and Description to “Brocade NetIron MLX.”
  3. Repeat the above for “Brocade VDX”
  4. Go to Device Model. Add new sysOID -> Device Model mappings. Make sure you pick the right vendor & series.

If you’ve already discovered devices in IMC, you can select one to copy the sysOID from. Here’s some MLX & VDX sysObjectIDs:

  • MLX:
    • MLX16Rt –
    • MLX8Rt –
    • MLX4Rt –
    • MLX-32Rt –
    • MLXe-16Rt –
    • MLXe-8Rt –
    • MLXe-4Rt –
    • MLXe-32Rt –
  • VDX:
    • VDX6740 –
    • VDX6747 –
    • VDX6740T –
    • VDX2740 –
    • VDX6740T1G –
    • VDX7770P36 –
    • VDX7770P72 –
    • VDX8770S4
    • VDX8770S8
    • VDX8770S16

Restart & Resynchronise

You’ll need to restart IMC so it picks up the changes to device adapter definitions. It will also need to resynchronise the devices to pick up the changes. This will happen automatically within a few hours, or you can force it.

The MLX adapter supports SCP. I strongly recommend setting the file transfer mode to SCP. This is better than using the CLI adapters.

Now you should be able to back up those devices.

ICX Adapter Updates

HP IMC ships with adapters for the Brocade/Foundry ICX FastIron systems. This adapter does not support SCP, and there are issues with the CLI fall-back adapter. If you want to apply these changes, copy the adapters/ICC/Foundry/FoundryNetIron directory from the GitHub repo to (IMC)/server/conf/adapters/ICC/Foundry and restart IMC.

Now you can use SCP for those devices too.

These adapters have had limited testing. Device backup works, and Configuration deployment should work. Firmware deployment has not been tested. If you have any problems, either get in touch with me, or submit a Pull Request.

, ,
Comments are closed.