Most Opmantek commercial products are licensed by the total number of devices under management. However, both opFlow and opFlowSP use interface licensing; that is how many interfaces does our system see which have NetFlow data.

A Branch router with 4 interfaces, 1 WAN, and 3 LAN ports, NetFlow export is enabled only on the WAN port, but there is traffic from each of the 3 LAN ports going out the WAN port (typical branch scenario), this would use 4 interface licenses as we are seeing traffic from 4 interfaces.

Likewise if a large Data Center switch had 100 ports and NetFlow export was enabled on 2 interfaces, it is completely conceivable that we would only see data for 10 or 20 interfaces, only the interfaces which have traffic which enters or exits on the two NetFlow export enabled ports.


Example 2:

It is licensed by interfaces. It is made per interface connection, eg. intf1->intf2, intf1->intf3 is 2 interfaces even though it's really just getting data from intf1

 

This is how it counts them as shown in the code snippet below:

---

{ '$match' => {
            'in_if' => { '$ne' => '*' },
            'out_if' => { '$ne' => '*' },
            'admin_status' => 'active'
        }},
        { '$group' => {
          _id => '$agent',
          'in_if' => { '$addToSet' => '$in_if' },
          'out_if' => { '$addToSet' => '$out_if'}
        }},
        { '$project' => {
          _id => 1,
          interfaces => { '$setUnion' => [ '$in_if','$out_if' ] }
        }},
        { '$project' => {
          _id => 1,
          'nrintfs' => { '$size' => '$interfaces'}
        }},
        { '$group' => {
          _id => undef,
          'totalintfs' => { '$sum' => '$nrintfs'}
        }},

 

---