1- Check the integrity of the data
Check that the “CI_METRIC_ID” column values in the S_QOS_DATA table are present in the “CM_CONFIGURATION_ITEM_METRIC” table.
If the metric IDs (“CI_METRIC_ID CI_METRIC_ID” column in the “S_QOS_DATA” table) do NOT have a corresponding row in the “CM_CONFIGURATION_ITEM_METRIC” table, they will not display in USM.
In this example, we identified the following hosts as not having metrics available in USM: walsh04-HOST1, walsh04-HOST2, and walsh04-HOST3. Note: In the queries below, pay attention to the Target values. Query 1 -SELECT SOURCE, TARGET, CI_METRIC_ID FROM S_QOS_DATA WHERE SOURCE IN /** enter your source names here **/ ('walsh04-E15600','walsh04-E15601','walsh04-e15603') AND CI_METRIC_ID NOT IN (SELECT CI_METRIC_ID FROM CM_CONFIGURATION_ITEM_METRIC);The CI_METRIC_ID from S_QOS_DATA and the one from CM_CONFIGURATION_ITEM must be the same. If there are any rows returned from the query above, the data will need to be corrected.First, validate whether data is being saved to a new location.Query 2 -SELECT SOURCE, TARGET, CI_METRIC_ID FROM S_QOS_DATA WHERE SOURCE IN ('walsh04-E15600','walsh04-E15601','walsh04-e15603') AND CI_METRIC_ID IN (SELECT CI_METRIC_ID FROM CM_CONFIGURATION_ITEM_METRIC);Pay attention to the “TARGET” values from “Query 1” and “Query 2”. Note if any are the same or similar, for example an interface name changed from ‘Fa0’ to ‘Fa0(FastEthernet0)’.If the target name had changed, look to merge the QOS data by following this technical document: kb000072808 .
2- Update the S_QOS_DATA table
If the “Target” name change is not related, then to correct the data for a single device, run an UPDATE statement (replace 'walsh04-E15601' below).
UPDATE S_QOS_DATA SET CI_METRIC_ID = NULL WHERE SOURCE LIKE = 'walsh04-E15601';
3- Delete the niscache on the robot where the QoS is coming from and then restart that robot. Steps to delete the niscache
Clearing the niscache, using the Infrastructure Manager console
- Select “_nis_cache_clean”
- Command Status should be “OK”
Clearing the niscache using the Web Admin Console (alternative to using the IM console steps above).
Clearing the niscache through the filesystem (alternative to using IM console steps above).
4- Deactivate “discovery_server” and the “nis_server” using the IM or Web Admin Console.
5- Restart these probes on the primary hub:
Note: the discovery_server and nis_server are responsible for cm_configuration_item_metric. That will force the CI (configuration item) to be put in cm_configuration_item_metric table.
6- Check the “CM_CONFIGURATION_ITEM_METRIC”
table to see if it is now present, then check the “Metrics” or “Interface Metrics” in the USM/USM Interface Tab view once again to see if it still shows "No Metrics Available".
You can use one source/device/robot as a test, then restart the data_engine. This will take some time but the mappings should be corrected after this - but please try it on a single robot first to be sure.