Minor Description
Brocade purchased Stingray from Riverbed a few years ago & rebranded it as Brocade Virtual Traffic Manager. The MIB for this ZXTM-MIB-SMIv2 & it is several years out of date (supporting up to version 9.8r2 of Stingray). The current version is Brocade Virtual Traffic Manager 17.1. Attached is the latest MIB. Thank you.
Attachments
Activity
Looks like they modified sysObjectID in the new updates - The following has been tested in my definitions/os.inc.php file to properly identify the Brocade vTM platform (modified from the zeustm os profile):
// Brocade Virtual Traffic Manager
|
$os = "brocadevtm"; |
$config['os'][$os]['text'] = "Brocade Virtual Traffic Manager"; |
$config['os'][$os]['type'] = "network"; |
$config['os'][$os]['icon'] = "brocade"; |
$config['os'][$os]['discovery'][] = array( |
'sysObjectID' => '.1.3.6.1.4.1.7146.1.2', |
'sysDescr' => '/^Linux/', |
'ZXTM-MIB-SMIv2::version.0' => '/.+/', |
);
|
$config['os'][$os]['mibs'][] = "ZXTM-MIB-SMIv2"; |
To add to this - As of Brocade vTM 17.2/17.3, they have upgraded underlying OS to Ubuntu 16.04. Observium Pro (currently running 17.8.8712) is now categorizing these under Linux Servers instead of identifying them as Network devices (Load Balancers).
My mistake. The MIB I uploaded is from version 17.1 while the 17.3 is latest version.
These changes are committed in r8745. Note that the new mib is only applied to newer devices with the type 'brocade-vtm', not the older versions covered by the older os type.