Cisco Service Control Subscriber Manager LEGs User Guide, Release 4.0.x
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
- Updated:
- February 11, 2014
Chapter: Using the MPLS/VPN BGP LEG CLU
Using the MPLS/VPN BGL LEG Command-Line Utility
Introduction
This chapter describes the Multiprotocol Label Switching (MPLS)/Virtual Private Network (VPN) Border Gateway Protocol (BGP) Login Event Generator (LEG) command-line utility (CLU).
Information About the MPLS/VPN BGP LEG CLU
The p3bgp utility controls the operation of the BGP LEG and displays its status. The command format is p3bgp <operation>[parameter].
Table 30-1 lists the p3bgp operations.
BGP LEG Status
The following is an example of the p3bgp command-line utility using the status operation:
ID |
Peer IP |
PE Name |
Updates recv |
Notify recv |
K.Alive sent |
K.Alive recv |
Hold Time |
1 |
1.2.3.4 |
PE101 |
150 |
0 |
58 |
57 |
157 |
2 |
1.2.3.5 |
PE102 |
183 |
0 |
34 |
33 |
77 |
The following list is a description of the status operation output:
•
Peer IP—The IP of the PE/RR that is connected to the LEG.
•PE name—The name of the PE/RR as configured in the configuration file.
•Updates recv—A counter for all the BGP updates received from this PE/RR.
•Notify recv—A counter for all the BGP notifications received from this PE/RR.
•K.Alive sent—A counter for all the BGP keep alives sent to this PE/RR.
•K.Alive recv—A counter for all the BGP keep alives received from this PE/RR.
•Hold Time—The remaining time-out for the next keep alive.
BGP LEG Detailed Status
The following is an example of the p3bgp command line utility using the show operation on a specific PE router named PE101:
1 : PE101 connects : 1 recv UPDATE : 150 recv KEEPALIVE : 57 sent KEEPALIVE : 58 recv NOTIFY : 0 current holdtime : 157 TCP sndwnd : 16384 TCP rcvwnd : 87380 Connection up time : 0 Days, 1 Hrs, 7 Min, 59 Sec refresh requests : 2 recv PE AddRoute messages : 2 send SM AddRoute messages : 10 send SM not connected : 0 BGP state : Established
The following list is a description of the show operation output:
•connects—The number of successful connections established with this PE/RR since the LEG is up.
•recv UPDATE—A counter for all the BGP updates received from this PE/RR.
•recv KEEPALIVE—A counter for all the BGP keep alives received from this PE/RR.
•sent KEEPALIVE—A counter for all the BGP keep alives sent to this PE/RR.
•recv NOTIFY—A counter for all the BGP notifications received from this PE/RR.
•current holdtime—The remaining time-out for the next keep alive.
•TCP sndwnd—The TCP send window buffer size.
•TCP rcvwnd—The TCP receive window size.
•Connection up time—The time since the connection to this PE/RR was established.
•refresh requests—A counter for the number of refresh requests requested for this PE/RR.
•recv PE AddRoute messages—A counter for BGP add-route messages received from the PE/RR.
•send SM AddRoute message—A counter for successful add routes invocations performed on the SM for this PE/RR.
•send SM not connected—A counter for SM invocations that were kept in an internal buffer due to disconnected SM.
•BGP state—The state of the BGP connection to this PE/RR.
Feedback