ASAP Migration Guide for NSX and OMF Users

DOTs, EMS Events, and Other Features

ASAP Migration Guide for NSX and OMF Users—520627-001

3-4

Network Statistics Collection

The ASAP network statistics collection mechanism is similar to NSX. Each SGP sends

its statistics to the ASAP Collector, which writes those statistics in the appropriate

Enscribe DBentity file. There is one partitionable DB file per entity. Partitioning is a

new feature in ASAP 2.0 that can help reduce the workload of specific DB files or store

more ASAP statistics. For an explanation of its options, see the ASAP SET

PARTITION command in the ASAP Server Manual.

The collection infrastructure is self maintaining. It keeps historical statistics for all

entities. To specify how much history is kept, if any, use the ASAP SET RETAIN

command.

Persistence

OMF is persistent because it runs either in a Pathway environment in Single-Node or

under the NSXMON responsibility in Network OMF. In both cases, the OMF Monitor

gets restarted in case of failure.

Like NSX, ASAP 2.0 offers persistence with its process pairs. The ASAP Collector and

ASAP Monitor run as process pairs. The ASAP Monitor is responsible for starting the

SGPs, one per entity, on its node. If an SGP fails, the ASAP Monitor restarts it.