The number of BGP dynamic peer sessions exceeded the maximum number. (MaximumNumber=[MaximumNumber])
The number of BGP dynamic peer sessions exceeded the maximum number.
Trap Attribute | Description |
---|---|
Alarm or Event |
Alarm |
Trap Severity |
Critical |
Mnemonic Code |
hwBgpDynamicPeerSessionExceed |
Trap OID |
1.3.6.1.4.1.2011.5.25.177.1.3.17 |
MIB |
HUAWEI-BGP-VPN-MIB |
Alarm ID |
0X08792059 |
Alarm Name |
hwBgpDynamicPeerSessionExceed |
Alarm Type |
communicationsAlarm |
Raise or Clear |
Raise |
Match trap |
BGP_1.3.6.1.4.1.2011.5.25.177.1.3.18 hwBgpDynamicPeerSessionExceedClear |
Parameter | Description |
---|---|
MaximumNumber |
Maximum number of BGP dynamic peer sessions. |
VB OID | VB Name | VB Index |
---|---|---|
1.3.6.1.4.1.2011.5.25.177.1.4.6 |
hwBgpDynamicPeerSessionMaxNum |
- |
1. Run the display bgp component BGP_NM 1 command in the diagnostic view to check whether the number of BGP dynamic peer sessions (uiDynNbrNum) reaches the upper limit (uiDynNbrLimit).
2. Check whether all the BGP dynamic peer sessions are needed.
3. Check user logs to determine whether too many unnecessary BGP dynamic peers were created because the local configuration was modified (the peer listen-net command was run for example).
4. Update the local configuration, run the peer listen-net command to disconnect unnecessary peers, and check whether the fault is rectified.
5. Contact the maintenance personnel of the peer device to check whether all the BGP dynamic peer sessions are necessary.
6. Ask the maintenance personnel of the peer device to delete unnecessary BGP dynamic peer sessions and disconnect unnecessary peers.
7. Increase the upper limit on the maximum number of BGP dynamic peer sessions using the bgp dynamic-session-limit command and check whether the fault is rectified. If the fault persists, go to Step 8.
8. Collect alarm and configuration information, and contact Huawei technical support personnel.
9. End.