How does eye.lo interact with NBAR custom apps defined on routers ?

LivingObjects default recommendation is to define custom applications directly in eye.lo, rather than touching the router configurations: traffic will get classified in reports for all the exporting devices at once.

However, there may be cases justifying the creation of NBAR custom applications on routers (for example QoS, or PfR application-based policies): NBAR on each device would then generate a new entry in its application dictionary, with an identifier code that eye.lo would not understand in the flows. For eye.lo to support customapps on routers, please follow these guidelines:

1. Specify on router CLI for each application the same id across all routers of the client
   (For example ‘ip nbar custom cisco_site composite server-name *cisco.com id 50’)
2. Manually create this definition in eye.lo, on the application criterion
   (‘application=6:50’, 6 being the ‘User-Defined’ NBAR classification engine)