Vstatus Configuration

After you install the SolutionPack for Network Configuration Manager, you must configure the variable status task for the SQL Collector. Use the M&R UI to change the value from 14 days to 1 day to avoid stale data in NCM reports. To configure the vstatus filter for the Activity table report, the configuration of variable status is modified to take care of the inactive metrics. To configure variable status, perform the following procedure:

Procedure

1. Click Administration .
2. Click Centralized Management > Scheduled Tasks.
3. In the Scheduled Tasks pane, click the Backend category.
4. In the Task backend/Default/import_variable_status.task pane, expand Configuration Files.
5. Click the pencil icon for data/task_repository/backend/Default/import_variable_status.task.
   The import_variable_status.task file opens.
6. For the inactive parameter, change 14d to 1d.
   Before editing:

   <param>{"inactive":"14d","vgroups":[{"condition": [{"source":"VMWareCollector"}], "group":["vcenter","devtype","parttype"],"max-inactive":"24h"},{"condition": [{"source":"VMWareCollector"}], "group":["vcenter","devtype"],"max-inactive":"24h"},{"condition": [{"devtype":"FabricSwitch"}], "group":["device","parttype","datagrp"],"max-inactive":"24h"},{"condition": [{"devtype":"PassiveHost"}], "group":["device","parttype","datagrp"],"max-inactive":"24h"},{"group":["devtype","device","source","parttype","collcfg"],"max-inactive":"24h"},{"group":["devtype","device","source","parttype","datagrp"],"max-inactive":"24h"},{"group":["devtype","device","source","datagrp"],"max-inactive":"24h"},{"group":["devtype","device"],"max-inactive":"24h"}]}</param>

   For MySQL, for DB activity and job use the following configuration:
   After editing:

   <param>{"inactive":"1d","vgroups":[{"condition": [{"source":"EMC-NCM"},{"parttype":"DBACTIVITY"}], "group":["appsrv"],"max-inactive":"5m"},{"condition": [{"source":"EMC-NCM"},{"parttype":"JOBS"}], "group":["appsrv"],"max-inactive":"5m"},{"condition": [{"source":"VMWareCollector"}], "group":["vcenter","devtype","parttype"],"max-inactive":"24h"},{"condition": [{"source":"VMWareCollector"}], "group":["vcenter","devtype"],"max-inactive":"24h"},{"condition": [{"devtype":"FabricSwitch"}], "group":["device","parttype","datagrp"],"max-inactive":"24h"},{"condition": [{"devtype":"PassiveHost"}], "group":["device","parttype","datagrp"],"max-inactive":"24h"},{"group":["devtype","device","source","parttype","collcfg"],"max-inactive":"24h"},{"group":["devtype","device","source","parttype","datagrp"],"max-inactive":"24h"},{"group":["devtype","device","source","datagrp"],"max-inactive":"24h"},{"group":["devtype","device"],"max-inactive":"24h"}]}</param>

   For Elastic Search, for DB activities only use the following configuration:
   After editing:

   <param>{"inactive":"1d","vgroups":[{"condition": [{"source":"EMC-NCM"},{"parttype":"DBACTIVITY"}], "group":["appsrv"],"max-inactive":"5m"},{"condition": [{"source":"VMWareCollector"}], "group":["vcenter","devtype","parttype"],"max-inactive":"24h"},{"condition": [{"source":"VMWareCollector"}], "group":["vcenter","devtype"],"max-inactive":"24h"},{"condition": [{"devtype":"FabricSwitch"}], "group":["device","parttype","datagrp"],"max-inactive":"24h"},{"condition": [{"devtype":"PassiveHost"}], "group":["device","parttype","datagrp"],"max-inactive":"24h"},{"group":["devtype","device","source","parttype","collcfg"],"max-inactive":"24h"},{"group":["devtype","device","source","parttype","datagrp"],"max-inactive":"24h"},{"group":["devtype","device","source","datagrp"],"max-inactive":"24h"},{"group":["devtype","device"],"max-inactive":"24h"}]}</param>

7. Click Save.
8. Click Restart in the Service Status pane to restart the collector-manager service.