Fault fltInfraIlClMsgSrcOutsider
                

Rule ID:1370


Explanation:
This fault occurs when keepalive messages arrive periodically from controllers that are considered illegitimate by the controller cluster.< br/>
Recommended Action:
If you see this fault, take the following actions:


  1. The message included with the fault will also include a reason the controller messages are considered illegitimate. Investigate the reason and correct it.
  2. If you encounter this fault while trying to add a new controller to cluster, please ensure following:
    1. If fault is due to a mismatched parameter like fabric domain, TEP pool etc, please setup the new controller again with correct parameters.
    2. If you are expanding the cluster(increasing cluster size), please ensure new controller has ID = current cluster size +1.
    3. If new controller is replacing an old controller, please ensure decommission, wait for few min and commission back was done for old controller slot.
    4. If new controller was part of other cluster, please ensure new controller is cleaned and setup with new cluster parameters.
    5. Please ensure new controller is running same version as the existing cluster
    6. Please ensure new controller is not configured as standby
  3. Please ensure decommissioned controllers don't stay up and connected to the fabric.
  4. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.


Raised on MO: infra:IlClMsgSrc

Fault Name: fltInfraIlClMsgSrcOutsider

Unqualified API Name: outsider
Code: F1370
Applied Mo DN Format:
     topology/pod-[id]/node-[id]/lon/ilClMsgSrc-[chassis]-[icmsReason]

Type: operational
Cause: intrusion
Severity: critical
Weight: 100
Tags:
Message: Messages from a controller (node-id) with the Globally Unique Identifier (GUID) chassis and the IP address addr started arriving at frstMsgTs and are being rejected because: icmsReason

Help:

Triggered By:
        isFault equals true