Thanks. Your
Cliff Notes were helpful in getting the cams integrated into the environment. At this point, the network is well sorted. The cams and BI are isolated in their own VLAN, and access is controlled via both firewall rules and OpenVPN running on the pfSense router on the network edge. Only the BI server has any access external to the VLAN.
SNMP is a standard protocol for tracking the health and status of network connected devices. The cams report a ton of useful information via SNMP (model, hostname, network configuration & utilization, uptime, firmware version) on (mostly) standard SNMPv2 OIDs. However, when I snmpwalk the devices, they are also reporting quite a bit via enterprise OIDs. For example:
Code:
.1.3.6.1.4.1.1004849.2.3.1.1.1.1.1.1 = INTEGER: 1
.1.3.6.1.4.1.1004849.2.3.1.1.1.1.2.1 = STRING: "H.264H"
.1.3.6.1.4.1.1004849.2.3.1.1.1.1.3.1 = INTEGER: 15
.1.3.6.1.4.1.1004849.2.3.1.1.1.1.4.1 = STRING: "1080P"
.1.3.6.1.4.1.1004849.2.3.1.1.1.1.5.1 = INTEGER: 2048
This appears to be the codec, fps, resolution and bitrate of the main video stream. Similar information is available for the substreams.
Generally, when a vendor reports information unique to the device, they provide a MIB that provides a mapping of the numerical OID (the string of numbers - e.g. .1.3.6.1.4.1.1004849.2.3.1.1.1.1.2.1) to a description of what is being reported. Having this information would allow us to monitor additional health, status and configuration information for every camera in our centralized network management system (in our case, LibreNMS).