Fault fltBgpPeerPInvalidConfigBgpPeerP
                

Rule ID:3488

Explanation:
This fault occurs when router id is not used as loopback and explict loopback interface is not configured for a node and bgp peer configured under logical node profile.

Recommended Action:
If you see this fault, take the following actions:

1. Add loopback interface under node.
2. If the above actions did not resolve the issue, collect a tech-support file and contact Cisco TAC.

Fault Name: fltBgpPeerPInvalidConfigBgpPeerP

Unqualified API Name: invalidConfigBgpPeerP
Code: F3488
Applied Mo DN Format:
     topology/pod-[id]/node-[id]/local/svc-[name]-id-[id]/uni/tn-[name]/out-[name]/lnodep-[name]/lifp-[name]/vlifp-[nodeDn]-[encap]/peerP-[addr]
     uni/tn-[name]/out-[name]/lnodep-[name]/lifp-[name]/vlifp-[nodeDn]-[encap]/peerP-[addr]
     topology/pod-[id]/node-[id]/local/svc-[name]-id-[id]/uni/tn-[name]/out-[name]/lnodep-[name]/lifp-[name]/rspathL3OutAtt-[tDn]/peerP-[addr]
     uni/tn-[name]/out-[name]/lnodep-[name]/lifp-[name]/rspathL3OutAtt-[tDn]/peerP-[addr]
     topology/pod-[id]/node-[id]/local/svc-[name]-id-[id]/uni/tn-[name]/out-[name]/lnodep-[name]/peerP-[addr]
     uni/tn-[name]/out-[name]/lnodep-[name]/peerP-[addr]

Type: config
Cause: configuration-failed
Severity: critical
Weight: 100
Tags:
Message: Bgp peer defined under node profile name in tenant name under l3out name does not have a loopback interface configured under node.

Help:

Triggered By:
        ConfigIssues equals no-loopback-configured