Troubleshooting
Problem
A Sterling B2B Integrator (SBI) adapter is being monitored by a wildcard rule configured in Sterling Control Center (SCC), however when the adapter is brought down, the wildcard rule which should alert to this fact does not fire. The rule should fire based on the first 2 characters of the adapter's name, for example 'AB'
Symptom
No alert is generated.
Cause
The wildcard rule is configured to look for the CGIS011I event ANDed with a wildcarded adapter name like AB*. This will not work, however, because the event in the SCC evennode1.ABSomeAdapterNamet log contains the SBI node name AND the adapter name separated by a full stop, for example 'node1.ABSomeAdapterName'. The wildcard match 'AB*' therefore doesn't match true, and the rule doesn't get triggered.
Diagnosing The Problem
Ensure your SCC rule has the correct match criteria defined.
Resolving The Problem
Make sure that your SCC wildcard rule's match criteria suit the adapter in question. For example, to match against adapter 'node1.ABSomeAdapterName', you may want to use wildcard 'node1.AB*', or perhaps '*.AB*'.
Was this topic helpful?
Document Information
Modified date:
17 December 2019
UID
swg21958853