Determining the Current RSVP Neighbor State
Display a list of RSVP neighbors that were learned dynamically when exchanging RSVP packets. Once a neighbor is learned, it is never removed from the list of RSVP neighbors.
To determine the current RSVP neighbor state, enter the following Junos OS CLI operational mode command:
user@R6> show rsvp neighbor RSVP neighbor: 2 learned Address Idle Up/Dn LastChange HelloInt HelloTx/Rx MsgRcvd 10.1.36.1 5 1/0 1w5d 6:30:50 9 116734/116734 23558 10.1.56.1 10 1/0 2w2d 23:44:15 9 161600/161600 23570
The sample output shows that R6 has learned about two different RSVP neighbors. Each neighbor has one line of output that includes the neighbor RSVP address, the length of time the interface was idle, the current interface up/down counter, the time of the last interface state change, the current RSVP hello interval, the total number of RSVP hello messages transmitted and received, and the total number of RSVP messages received on the interface.
The show rsvp neighbor command only indicates a neighbor after a session is established. Once an interface is displayed in this command output, it always appears, even if the RSVP neighbor state is down.
The RSVP neighbor 10.1.36.1 was idle for 5 seconds, came up once and has not gone down, indicating that the interface is currently in an Up state. As long as the up counter is one greater than the down counter, the RSVP interface is up. If the up/down counters are equal, the interface is down.
The last state change occurred 6 hours and 30 minutes ago. The current hello interval is 9 seconds. A total of 116,734 hello messages were transmitted and received on this interface, and a total of 23,558 RSVP Path/Resv messages were processed.
The RSVP neighbor 10.1.56.1 was idle for 10 seconds, came up once and has not gone down, indicating that the interface is currently in an Up state. The last state change occurred 23 hours and 44 minutes ago. The current Hello interval is 9 seconds. A total of 161,600 hello messages were transmitted and received on this interface, and a total of 23,570 RSVP Path/Resv messages were processed.