GCB Traffic Health Monitoring
GigaVUE-FM monitors the traffic health of GCB by monitoring the following:
| Configuration Health |
| Traffic Health |
| Resource Utilization Health |
| Connectivity Health |
In GigaVUE-FM, you can view alarms, manage one or more alarms, filter alarms, drill down to alarm source, etc. While configuring, GigaVUE-FM allows to set the threshold conditions so that alarms are raised by the GCB node when those threshold conditions are met.
Configure Alarms in GCB
You can configure alarms in GCB, after registering it with GigaVUE-FM. To register refer to GCB Registration.
To configure Alarms in GCB, follow the given steps:
| 1. | Go to Inventory > Container > Gigamon Containerized Broker > Settings drop-down list box. |
| 2. | In the Settings drop-down list box select Settings. |
| 3. | Click the GCB UUID, and then click Thresholds near the GCB UUID to configure the thresholds for monitoring the following health: |
| Configuration Health |
| To configure the thresholds for monitoring the configuration health, expand Configuration Health and configure the parameters as described in the table. |
| Traffic Health |
| To configure the thresholds for monitoring the traffic health, expand Data Transmission and configure the parameters as described in the table. |
| Resource Health |
| To configure the thresholds for monitoring the traffic health, expand Invalid RxDataand configure the parameters as described in the table. |
| Connectivity Health |
| To configure the thresholds for monitoring the traffic health, expand Transaction Logging and configure the parameters as described in the table. |
Configuration Health
To monitor the configuration health, you can configure the thresholds for the following:
| S.No. | Name | Monitors | Description | Trigger Value Type | Trigger Value Range | Minimum - Maximum Timer Interval |
Default Trigger Value | Default time | Conditions | Severity | Status |
|---|---|---|---|---|---|---|---|---|---|---|---|
|
1 |
ServiceIdTableMiss |
Either of source or destination table does not exist, or both the tables does not exist. |
Alarms are raised when the user fails to upload any one of src / dst table or both ServiceIdTableMiss. |
Integer |
1-10 |
300-6000 |
1 |
300 sec |
above |
Critical |
ON |
|
2 |
SvcIdLookupMiss |
Entry lookup miss in svc-id table |
Alarms are raised when service ID lookup fails for incoming traffic SvcIdLookupMiss. |
Integer |
10-5000 |
300-6000 |
1000 |
300 sec |
above |
Major |
ON |
|
3 |
GCBLogfileTruncated |
Indicates the logging file truncation (Notification) |
Alarms are raised when gcb http pod log is rotated and fresh logging starts GCBLogfileTruncated . |
Integer |
1-10 |
300-6000 |
5 |
300 sec |
above |
|
ON |
|
|
|
|
|
|
|
|
|
|
|
|
Traffic Health
To monitor the traffic health, you can configure the thresholds for the following:
| S.No. | Name | Monitors | Description | Trigger Value Type | Trigger Value Range | Minimum - Maximum Timer Interval |
Default Trigger Value | Default time | Conditions | Severity | Status |
|---|---|---|---|---|---|---|---|---|---|---|---|
|
1 |
TransmitErrors |
Errors in transmitting packets out through tunnel. |
Alarms are raised when tx errors are observed in the http pod TransmitErrors. |
Integer |
10-100 |
60-600 |
100 |
60 sec |
above |
Major |
ON |
|
2 |
TransactionLoggingErrors |
Transaction Logging failures |
Alarms are raised when transaction logging to the designated file fails TransactionLoggingErrors. |
Integer |
10-100 |
60-600 |
100 |
60 sec |
above |
Major |
OFF |
|
3 |
PacketReorderTimeouts |
Packet reordering triggered timeout or transaction packet discards |
Alarms are raised when reordering of the incoming packet is not successful/completed in the defined time interval PacketReorderTimeouts |
Integer |
1-100 |
60-600 |
1 |
60 sec |
above |
Major |
OFF |
|
|
|
|
|
|
|
|
|
|
|
|
Resource Health
To monitor the resource health, you can configure the thresholds for the following:
| S.No. | Name | Monitors | Trigger Value Type | Description | Trigger Value Range | Minimum - Maximum Timer Interval |
Default Trigger Value | Default time | Conditions | Severity | Status |
|---|---|---|---|---|---|---|---|---|---|---|---|
|
1 |
InvalidPostDataReceived |
Missing the POST data or Invalid Binary data or wrong pcap files |
Integer |
Alarms are raised when invalid post data is received by the pod InvalidPostDataReceived. |
1-10 |
60-600 |
10 |
300 sec |
above |
Major |
ON |
Connectivity Health
To monitor the connectivity health, you can configure the thresholds for the following:
| S.No. | Name | Monitors | Description | Trigger Value Type | Trigger Value Range | Minimum - Maximum Timer Interval |
Default Trigger Value | Default time | Conditions | Severity | Status |
|---|---|---|---|---|---|---|---|---|---|---|---|
|
1 |
PcapperConnectionFailure |
Datapath connection failure |
Alarms are raised when connectivity fails between pcapper and http service pcapper connection |
Integer |
1-10 |
60-300 |
3 |
60 sec |
equal |
Critical |
ON |
|
2 |
Controller2FMConnectivity |
GigaVUE-FM reachability issues from GCB-Controller |
Integer |
1-10 |
3 |
300 sec |
equal |
Critical |
OFF |
||
|
3 |
GCB2ControllerConnectivity |
Controller unreachable from GCB |
Integer |
1-10 |
|
3 |
300 sec |
equal |
Critical |
OFF |
|
|
|
|
|
|
|
|
|
|
|
|
|
The YAML updates are as follows:
- name: GCB_ALARM_GROUP_NAME
value: "alarm group name"
# 0 - disabled, 1 - enabled
- name: GCB_ALARM_HMON_SUPPORTED
value: '0'
For more information about Alarms, refer to Alarms section in the GigaVUE Administration Guide.
