Fault fltEpmRogueIpEpEpIPRogue
                

Rule ID:3013


Explanation:
This fault occurs when a IP endpoint turns rogue

Recommended Action:
If this fault is consistently happening, try the following actions


  1. Check endpoint connectivity
  2. Shutdown endpoint
  3. If the network connectivity is fine, generate the show tech-support file and contact Cisco TAC.

Raised on MO: epm:RogueIpEp

Fault Name: fltEpmRogueIpEpEpIPRogue

Unqualified API Name: epIPRogue
Code: F3013
Applied Mo DN Format:
     topology/pod-[id]/node-[id]/sys/ctxsubstitute-[encap]/bd-[fabEncap]/qinq-[encap]/db-[type]/rogueIpEp-[addr]
     sys/ctxsubstitute-[encap]/bd-[fabEncap]/qinq-[encap]/db-[type]/rogueIpEp-[addr]
     topology/pod-[id]/node-[id]/sys/inst-[name]/bd-[fabEncap]/qinq-[encap]/db-[type]/rogueIpEp-[addr]
     sys/inst-[name]/bd-[fabEncap]/qinq-[encap]/db-[type]/rogueIpEp-[addr]
     topology/pod-[id]/node-[id]/sys/ctx-[encap]/bd-[fabEncap]/qinq-[encap]/db-[type]/rogueIpEp-[addr]
     sys/ctx-[encap]/bd-[fabEncap]/qinq-[encap]/db-[type]/rogueIpEp-[addr]
     topology/pod-[id]/node-[id]/sys/inst-[name]/db-[type]/rogueIpEp-[addr]
     sys/inst-[name]/db-[type]/rogueIpEp-[addr]
     topology/pod-[id]/node-[id]/sys/ctx-[encap]/db-[type]/rogueIpEp-[addr]
     sys/ctx-[encap]/db-[type]/rogueIpEp-[addr]
     topology/pod-[id]/node-[id]/sys/ctxsubstitute-[encap]/bd-[fabEncap]/vxlan-[encap]/db-[type]/rogueIpEp-[addr]
     sys/ctxsubstitute-[encap]/bd-[fabEncap]/vxlan-[encap]/db-[type]/rogueIpEp-[addr]
     topology/pod-[id]/node-[id]/sys/inst-[name]/bd-[fabEncap]/vxlan-[encap]/db-[type]/rogueIpEp-[addr]
     sys/inst-[name]/bd-[fabEncap]/vxlan-[encap]/db-[type]/rogueIpEp-[addr]
     topology/pod-[id]/node-[id]/sys/ctx-[encap]/bd-[fabEncap]/vxlan-[encap]/db-[type]/rogueIpEp-[addr]
     sys/ctx-[encap]/bd-[fabEncap]/vxlan-[encap]/db-[type]/rogueIpEp-[addr]
     topology/pod-[id]/node-[id]/sys/ctxsubstitute-[encap]/bd-[fabEncap]/vlan-[encap]/db-[type]/rogueIpEp-[addr]
     sys/ctxsubstitute-[encap]/bd-[fabEncap]/vlan-[encap]/db-[type]/rogueIpEp-[addr]
     topology/pod-[id]/node-[id]/sys/inst-[name]/bd-[fabEncap]/vlan-[encap]/db-[type]/rogueIpEp-[addr]
     sys/inst-[name]/bd-[fabEncap]/vlan-[encap]/db-[type]/rogueIpEp-[addr]
     topology/pod-[id]/node-[id]/sys/ctx-[encap]/bd-[fabEncap]/vlan-[encap]/db-[type]/rogueIpEp-[addr]
     sys/ctx-[encap]/bd-[fabEncap]/vlan-[encap]/db-[type]/rogueIpEp-[addr]
     topology/pod-[id]/node-[id]/sys/ctxsubstitute-[encap]/bd-[fabEncap]/db-[type]/rogueIpEp-[addr]
     sys/ctxsubstitute-[encap]/bd-[fabEncap]/db-[type]/rogueIpEp-[addr]
     topology/pod-[id]/node-[id]/sys/inst-[name]/bd-[fabEncap]/db-[type]/rogueIpEp-[addr]
     sys/inst-[name]/bd-[fabEncap]/db-[type]/rogueIpEp-[addr]
     topology/pod-[id]/node-[id]/sys/ctx-[encap]/bd-[fabEncap]/db-[type]/rogueIpEp-[addr]
     sys/ctx-[encap]/bd-[fabEncap]/db-[type]/rogueIpEp-[addr]

Type: operational
Cause: ep-ip-is-rogue
Severity: warning
Weight: 100
Tags:
Message: EP IP addr under bd name vrf name is rogue on interface ifId of Node id, Pod podId, moving from interface prevIfInfo

Help:

Triggered By:
         flags contains rogue
        and
        not
          flags contains max-ip-flow-control