# Phase 3: Vendor Expansion Analysis - Complete

**Completion Date**: 2026-02-11
**Status**: ✅ Complete (Analysis Only)
**Vendors Analyzed**: HP/Aruba, Dell

## Executive Summary

Expanded LibreNMS parity analysis to HP/Aruba and Dell platforms. Results show **excellent coverage for modern platforms** (Aruba CX, Dell OS10, Dell storage/infrastructure) but **significant gaps for legacy network switches**.

### Overall Results

| Vendor | Best Platform | Worst Platform | Average Parity | Critical Gaps |
|--------|---------------|----------------|----------------|---------------|
| **HP/Aruba** | ArubaOS-CX (100%) | hpblmos (0%) | ~75% | Comware temp, hpblmos, ProCurve transceivers |
| **Dell** | OS10/rPDU/OME-M/Compellent (100%) | PowerConnect/FTOS/SONiC/Servers (0%) | ~55% | Network switches, servers, PowerVault |

**Key Finding**: **Network switch platforms are significantly underserved** compared to modern infrastructure/storage platforms.

---

## HP/Aruba Detailed Findings

**Documentation**: `docs/librenms-audit/sensors/hp-aruba-comparison.md`

### Platform Parity Scores

| Platform | Parity | Status | Critical Issues |
|----------|--------|--------|-----------------|
| **HP ProCurve** | 60% | ⚠️ Partial | Missing transceiver metrics (temp, current, voltage, dbm) |
| **HP Comware** | 40% | ❌ Critical | Missing chassis temp + all transceiver metrics |
| **HP BladeSystem/Moonshot** | 0% | ❌ Critical | No sensor profile exists |
| **Aruba ArubaOS** | 100% | ✅ Good | None (controller platform) |
| **Aruba ArubaOS-CX** | 100% | ✅ Excellent | None (exceeds LibreNMS) |
| **Aruba Instant On** | 100% | ✅ Good | None (AP platform) |

### HP/Aruba Sensor Coverage Summary

**Working Well:**
- ✅ Aruba ArubaOS-CX: **Best-in-class coverage** with per-lane transceiver diagnostics, VSX/VSF stack monitoring, detailed PSU states
- ✅ ProCurve chassis monitoring: Fans, PSU (temperature/power/state), PoE power, stack status
- ✅ ArubaOS controllers: Temperature, VPN session counts

**Critical Gaps:**

1. **HP Comware Temperature** (CRITICAL)
   - Missing: `HH3C-ENTITY-EXT-MIB::hh3cEntityExtTemperature`
   - OID: `1.3.6.1.4.1.25506.2.6.1.1.1.1.12.*`
   - Impact: **No temperature monitoring** = no overheating alerts
   - Fix Effort: 2-3 hours

2. **HP Comware Transceivers** (HIGH)
   - Missing: `HH3C-TRANSCEIVER-INFO-MIB::hh3cTransceiverInfoTable`
   - OID: `1.3.6.1.4.1.25506.2.70.1.1.1.*`
   - Sensors: Temperature, bias current, voltage, RX/TX power
   - Impact: No optical SFP/SFP+ monitoring
   - Fix Effort: 2-3 hours

3. **HP BladeSystem/Moonshot** (CRITICAL)
   - Missing: All sensor discovery
   - OIDs: Temperature (`1.3.6.1.4.1.232.22.2.3.1.2.1.5`), Fan/PSU state, PSU power
   - Impact: No hardware monitoring for blade chassis
   - Fix Effort: 4-6 hours

4. **HP ProCurve Transceivers** (HIGH)
   - Missing: `HP-ICF-TRANSCEIVER-MIB::hpicfXcvrInfoTable`
   - OID: `1.3.6.1.4.1.11.2.14.11.5.1.82.1.1.1.1.*`
   - Sensors: Temperature, bias current, voltage, RX/TX power
   - Impact: No optical SFP monitoring
   - Fix Effort: 2-3 hours

### HP/Aruba MIBs Used

**Standard MIBs:**
- ENTITY-MIB (RFC 4133)
- ENTITY-SENSOR-MIB (RFC 3433)

**Vendor MIBs:**
- `HP-ICF-TRANSCEIVER-MIB` - ProCurve transceiver diagnostics
- `HP-ICF-CHASSIS-MIB` - ProCurve chassis (fans/PSU)
- `HP-ICF-POE-MIB` - ProCurve PoE monitoring
- `HH3C-ENTITY-EXT-MIB` - Comware chassis (temp/power)
- `HH3C-TRANSCEIVER-INFO-MIB` - Comware transceiver diagnostics
- `WLSX-SYSTEMEXT-MIB` - ArubaOS controller temperature
- `ARUBAWIRED-CHASSIS-MIB` - ArubaOS-CX temp/PSU
- `ARUBAWIRED-NETWORKING-OID` - ArubaOS-CX VSX/VSF stack
- `ARUBAWIRED-POWERSUPPLY-MIB` - ArubaOS-CX power supplies

---

## Dell Detailed Findings

**Documentation**: `docs/librenms-audit/sensors/dell-comparison.md`

### Platform Parity Scores

| Platform | Parity | Status | Critical Issues |
|----------|--------|--------|-----------------|
| **Dell OS10** | 100% | ✅ Excellent | None |
| **Dell rPDU** | 100% | ✅ Excellent | None |
| **Dell OME-M** | 100% | ✅ Excellent | None |
| **Dell Compellent** | 100% | ✅ Excellent | None |
| **Dell UPS** | 80% | ⚠️ Good | Missing power consumption sensor |
| **Dell PowerVault** | 20% | ❌ Critical | Missing all sensors (temp, voltage, current, charge, state) |
| **Dell PowerConnect/DNOS** | 0% | ❌ Critical | No sensor profile exists |
| **Dell Force10 FTOS** | 0% | ❌ Critical | No sensor profile exists |
| **Dell SONiC** | 0% | ❌ Critical | OS detected, no sensors |
| **Dell Servers (10892)** | 0% | ❌ Critical | No profile exists |
| **Quanta Switches** | 40% | ⚠️ Partial | Incomplete sensor coverage |

### Dell Sensor Coverage Summary

**Working Well:**
- ✅ Dell OS10 switches: Comprehensive chassis and card temperature, fan/PSU state
- ✅ Dell rPDU: Current, power, voltage, temperature, humidity, load/phase state
- ✅ Dell OME-M: Extensive state monitoring, temperature, PSU power/voltage
- ✅ Dell Compellent: Storage-specific sensors (count, fan RPM, state, temp, voltage)

**Critical Gaps:**

1. **Dell PowerConnect/DNOS Switches** (CRITICAL - Network)
   - Missing: All sensor discovery
   - OID: `1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.8.1.5` (CPU temp)
   - MIB: `FASTPATH-BOXSERVICES-PRIVATE-MIB`
   - Impact: **No temperature monitoring on enterprise access switches**
   - Fix Effort: 2-3 hours

2. **Dell SONiC Switches** (CRITICAL - Network)
   - Missing: All sensor discovery (OS detection exists)
   - OIDs: Temperature, Fan speed, PSU state
   - MIB: `NETGEAR-BOXSERVICES-PRIVATE-MIB` (Quanta-based)
   - Impact: **No hardware monitoring on modern data center switches**
   - Fix Effort: 2-3 hours

3. **Dell Force10 FTOS Switches** (CRITICAL - Network)
   - Missing: All sensor discovery
   - OIDs: S-Series, C-Series, E-Series temperature
   - MIBs: `F10-S-SERIES-CHASSIS-MIB`, `F10-C-SERIES-CHASSIS-MIB`, `F10-CHASSIS-MIB`
   - Impact: **No temperature monitoring on data center switches**
   - Fix Effort: 3-4 hours (3 variants)

4. **Dell PowerVault Storage** (CRITICAL - Storage)
   - Missing: All sensor discovery
   - OID: `1.3.6.1.3.94.1.8.1.6.*` (text parsing required)
   - MIB: `FCMGMT-MIB`
   - Sensors: Temperature, voltage, current, battery charge, state
   - Impact: **No storage array monitoring**
   - Fix Effort: 3-4 hours (requires vendor module with text parsing)

5. **Dell Enterprise Servers (10892)** (CRITICAL - Compute)
   - Missing: No profile exists
   - MIB: `MIB-Dell-10892` (iDRAC/OpenManage)
   - Sensors: Temperature, power, voltage, fan speed, PSU/CPU/memory/storage state
   - Impact: **Cannot monitor Dell rack servers, blades, workstations**
   - Fix Effort: 4-6 hours (comprehensive profile)

6. **Dell UPS** (MEDIUM)
   - Missing: Power consumption sensor
   - OID: `1.3.6.1.4.1.674.10902.2.120.2.6.0`
   - Impact: No wattage tracking for capacity planning
   - Fix Effort: 1 hour

### Dell MIBs Used

**Standard MIBs:**
- FCMGMT-MIB - Fibre Channel management (PowerVault)

**Dell Vendor MIBs:**
- `DELLEMC-OS10-CHASSIS-MIB` - OS10 switches
- `DellrPDU-MIB` - Rack PDUs
- `DELL-SNMP-UPS-MIB` - UPS units
- `DELL-MM-MIB-SMIv2` - OpenManage Enterprise Modular
- `DELL-STORAGE-SC-MIB` - Compellent storage
- `MIB-Dell-10892` - Enterprise servers (iDRAC/OpenManage)
- `FASTPATH-BOXSERVICES-PRIVATE-MIB` - PowerConnect/DNOS switches
- `F10-S-SERIES-CHASSIS-MIB` - Force10 S-Series
- `F10-C-SERIES-CHASSIS-MIB` - Force10 C-Series
- `F10-CHASSIS-MIB` - Force10 E-Series
- `NETGEAR-BOXSERVICES-PRIVATE-MIB` - SONiC/Quanta switches

---

## Summary Statistics

### Sensor Types Analyzed

**Total**: 80+ unique sensor types across 2 vendors

**By Vendor:**
- **HP/Aruba**: 25+ sensor types (temperature, voltage, current, power, dbm, frequency, humidity, fanspeed, state across 6 platforms)
- **Dell**: 55+ sensor types (temperature, power, voltage, fanspeed, current, charge, state across 11 platforms)

### Platform Distribution

**HP/Aruba Platforms**: 6 analyzed
- Modern (excellent): 3 (ArubaOS-CX, ArubaOS, Instant On)
- Legacy (gaps): 3 (ProCurve, Comware, hpblmos)

**Dell Platforms**: 11 analyzed
- Excellent: 5 (OS10, rPDU, OME-M, Compellent, UPS)
- Critical gaps: 6 (PowerConnect, FTOS, SONiC, PowerVault, Servers, Quanta)

### Business Impact Analysis

**Network Switches** (Highest Priority):
- Dell PowerConnect: Common enterprise access layer
- Dell SONiC: Modern data center (Microsoft SONiC-based)
- Dell Force10 FTOS: Data center core/aggregation
- HP Comware: Enterprise distribution/core
- HP ProCurve: Enterprise access layer

**Storage/Compute** (High Priority):
- Dell PowerVault: SAN/NAS storage arrays
- Dell Enterprise Servers: Rack/blade servers (iDRAC)
- HP BladeSystem: Blade chassis

---

## Architecture Comparison

### LibreNMS Strengths

1. **Mature Network Switch Coverage**
   - Comprehensive PowerConnect, Force10, SONiC support
   - HP Comware full temperature + transceiver coverage
   - Established patterns for network hardware

2. **Text Parsing Capabilities**
   - PowerVault FCMGMT-MIB text message parsing
   - Handles non-standard sensor reporting

### Towerops Strengths

1. **Modern Platform Excellence**
   - Aruba ArubaOS-CX: Best-in-class, exceeds LibreNMS
   - Dell OS10: Comprehensive coverage
   - Better structured YAML vs scattered PHP modules

2. **Infrastructure/Storage Coverage**
   - Dell rPDU, OME-M, Compellent: Excellent
   - ProCurve chassis monitoring: Good

3. **Cleaner Architecture**
   - YAML-first declarative approach
   - Vendor post-processing pattern (Arista example)
   - Index templates prevent duplication

---

## Implementation Priorities

### Tier 1: Critical Network Switches (8-12 hours total)

**Business Justification**: Network switches are **core infrastructure** - temperature monitoring is **fundamental** for preventing outages.

1. **HP Comware Temperature** (2-3 hours) - BLOCKING
   - Add `hh3cEntityExtTemperature` to `comware.yaml`
   - Restores fundamental monitoring capability
   - Affects all HP Comware switches

2. **Dell PowerConnect/DNOS** (2-3 hours)
   - Create sensor discovery YAML
   - Add CPU temperature monitoring
   - Common enterprise access switches

3. **Dell SONiC** (2-3 hours)
   - Add sensors to existing `dell-sonic.yaml`
   - Temperature, fan speed, PSU state
   - Modern data center platform

4. **Dell Force10 FTOS** (3-4 hours)
   - Create YAML profiles for S/C/E-Series
   - Temperature monitoring for all 3 series
   - Data center switches

### Tier 2: High Priority Optical Monitoring (4-6 hours total)

1. **HP ProCurve Transceivers** (2-3 hours)
   - Add `hpicfXcvrInfoTable` to `procurve.yaml`
   - Enables optical SFP/SFP+ monitoring
   - Common fiber uplink deployments

2. **HP Comware Transceivers** (2-3 hours)
   - Add `hh3cTransceiverInfoTable` to `comware.yaml`
   - Completes Comware sensor coverage
   - Optical monitoring for enterprise core

### Tier 3: Storage/Compute Platforms (7-10 hours total)

1. **Dell PowerVault** (3-4 hours)
   - Create vendor module with text parsing
   - Similar to Arista post-processing pattern
   - Enables SAN/NAS monitoring

2. **Dell Enterprise Servers** (4-6 hours)
   - Create comprehensive `dell-server-10892.yaml`
   - Temperature, power, voltage, fan, state sensors
   - iDRAC/OpenManage support

### Tier 4: Blade Chassis & Minor Gaps (5-7 hours total)

1. **HP BladeSystem/Moonshot** (4-6 hours)
   - Create `hpblmos.yaml` sensor profile
   - Temperature, fan/PSU state, PSU power
   - Blade chassis monitoring

2. **Dell UPS Power Sensor** (1 hour)
   - Add single OID to `dell-ups.yaml`
   - Power consumption tracking

---

## Recommended Implementation Sequence

### Phase 3A: Network Switch Focus (1-2 days)

**Goal**: Restore fundamental temperature monitoring for all major switch platforms

1. HP Comware temperature (2-3 hours)
2. Dell PowerConnect/DNOS (2-3 hours)
3. Dell SONiC (2-3 hours)
4. Dell Force10 FTOS (3-4 hours)

**Result**: 4 switch platforms gain temperature monitoring (8-12 hours total)

### Phase 3B: Optical Monitoring (0.5-1 day)

**Goal**: Enable fiber optic link monitoring

1. HP ProCurve transceivers (2-3 hours)
2. HP Comware transceivers (2-3 hours)

**Result**: 2 platforms gain optical monitoring (4-6 hours total)

### Phase 3C: Storage/Compute (1-2 days)

**Goal**: Expand to storage arrays and servers

1. Dell PowerVault (3-4 hours)
2. Dell Enterprise Servers (4-6 hours)

**Result**: Storage and compute monitoring (7-10 hours total)

### Phase 3D: Blade Chassis & Polish (1 day)

**Goal**: Complete remaining gaps

1. HP BladeSystem/Moonshot (4-6 hours)
2. Dell UPS power (1 hour)
3. Quanta switches completion (2-3 hours)

**Result**: All platforms covered (7-10 hours total)

---

## Total Effort Estimate

| Phase | Effort | Platforms | Impact |
|-------|--------|-----------|--------|
| **Phase 3A** | 8-12 hours | 4 switch platforms | **CRITICAL** |
| **Phase 3B** | 4-6 hours | 2 transceiver platforms | HIGH |
| **Phase 3C** | 7-10 hours | Storage + servers | HIGH |
| **Phase 3D** | 7-10 hours | Blade chassis + polish | MEDIUM |
| **Total** | **26-38 hours** | **10+ platforms** | Full parity |

---

## Production Readiness Assessment

**Current State:**

| Vendor | Production Ready? | Notes |
|--------|-------------------|-------|
| **Cisco** | ✅ Yes | 95% parity (Phase 2) |
| **Juniper** | ✅ Yes | 100% parity (Phase 2) |
| **Arista** | ✅ Yes | 100% parity (Phase 2 + fixes) |
| **HP/Aruba** | ⚠️ Partial | CX/ArubaOS ready, Comware/ProCurve need work |
| **Dell** | ⚠️ Partial | OS10/rPDU/OME-M ready, switches need work |

**After Phase 3A (Network Switches):**

| Vendor | Production Ready? | Notes |
|--------|-------------------|-------|
| **HP/Aruba** | ✅ Yes | All switch platforms covered |
| **Dell** | ✅ Yes | All switch platforms covered |

---

## Conclusion

**Overall Status**: ⚠️ **Network Switches Need Urgent Attention**

**Key Achievements:**
- ✅ Modern platforms excellent (Aruba CX, Dell OS10)
- ✅ Infrastructure/storage well-covered (Dell rPDU, OME-M, Compellent)
- ✅ Wireless controllers adequate (ArubaOS, Instant On)

**Critical Needs:**
- ❌ **Legacy network switches severely underserved**
- ❌ HP Comware missing fundamental temperature monitoring
- ❌ Dell PowerConnect, Force10, SONiC missing all sensors
- ❌ Dell enterprise servers (iDRAC) not supported

**Business Impact:**
- Dell and HP switches are **extremely common** in enterprise deployments
- Lack of temperature monitoring = **no alerting on overheating equipment**
- **Production blocker** for customers with these platforms

**Next Steps:**
1. **Immediate (Phase 3A)**: Implement network switch sensor profiles (8-12 hours)
2. **Short-term (Phase 3B)**: Add optical transceiver monitoring (4-6 hours)
3. **Medium-term (Phase 3C-D)**: Complete storage, servers, blade chassis (14-20 hours)

**Recommendation**: Prioritize Phase 3A (network switches) immediately to restore fundamental monitoring capability for common enterprise platforms. This resolves the most critical business blockers.
