To display contents of Resource Reservation Protocol (RSVP) high availability (HA) read and write databases used in traffic
engineering (TE), use the
show ip rsvp high-availability database command in user EXEC or privileged EXEC mode.
show ip rsvp high-availability database {hello | if-autotun | link-management {interfaces [fixed | variable] | system} | lsp [filter [destination ip-address] | [lsp-id lsp-id] | [source ip-address] | [tunnel-id tunnel-id]] | lsp-head [filter number] | summary}
Syntax Description
hello
|
Displays information about hello entries in read and write databases.
|
if-autotun
|
Displays information about TE HA autotunnel interface entries in read and write databases.
|
link-management
|
Displays information about link-management entries in the read and write databases.
|
interfaces
|
Displays information about link-management interfaces in the read and write databases.
|
fixed
|
(Optional) Displays information about link-management fixed interfaces in the read and write databases.
|
variable
|
(Optional) Displays information about link-management variable interfaces in the read and write databases.
|
system
|
Displays information about the link-management system in the read and write databases.
|
lsp
|
Displays information about label switched path (LSP) entries in the read and write databases.
|
filter destination
ip-address
|
(Optional) Displays filtered information on the IP address of the destination (tunnel tail).
|
filter lsp-id
lsp-id
|
(Optional) Displays filtered information on a specific LSP ID designated by a number from 0 to 65535.
|
filter source
ip-address
|
(Optional) Displays filtered information on the IP address of the source (tunnel head).
|
filter tunnel-id
tunnel-id
|
(Optional) Displays filtered information on a specific tunnel ID designated by a number from 0 to 65535.
|
lsp-head
|
Displays information about LSP-head entries in the read and write databases.
|
filter
number
|
(Optional) Displays filtered information on a specific LSP-head router designated by a number from 0 to 65535.
|
summary
|
Displays cumulative information about entries in read and write databases.
|
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.2(33)SRA
|
This command was introduced.
|
12.2(33)SRB
|
The command output was modified to display the result of a loose hop expansion performed on the router.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
12.2(33)SRC
|
This command was integrated into Cisco IOS Release 12.2(33)SRC. The command output was modified to include path protection
information specified by the
lsp-head keyword.
|
12.4(20)T
|
This command was integrated into Cisco IOS Release 12.4(20)T.
|
15.0(1)S
|
This command was integrated into Cisco IOS Release 15.0(1)S. The command output was modified to distinguish database-entry
information for point-to-point (P2P) tunnels from that for point-to-multipoint (P2MP) tunnels and to display error database
information.
|
12.2(50)SY
|
This command was integrated into Cisco IOS Release 12.2(50)SY.
|
Cisco IOS XE Release 3.5S
|
This command was integrated into Cisco IOS XE Release 3.5S.
|
15.2(2)S
|
This command was modified. The
if-autotun keyword was added. The output for the
show ip rsvp high-availability database lsp , the
show ip rsvp high-availability database lsp-head , and the
show ip rsvp high-availability database summary commands was enhanced to display checkpoint information for MPLS TE autotunnel and automesh stateful switchover (SSO) tunnels.
|
Cisco IOS XE Release 3.6S
|
This command was modified. The
if-autotun keyword was added. The output for the
show ip rsvp high-availability database lsp , the
show ip rsvp high-availability database lsp-head , and the
show ip rsvp high-availability database summary commands was enhanced to display checkpoint information for MPLS TE autotunnel and automesh stateful switchover (SSO) tunnels.
|
Usage Guidelines
Use the
show ip rsvp high-availability database command to display information about entries in the read and write databases.
Use the
show ip rsvp high-availability database lsp command to display loose hop information. A loose hop expansion can be performed on a router when the router processes the
explicit router object (ERO) for an incoming path message. After the router removes all local IP addresses from the incoming
ERO, it finds the next hop. If the ERO specifies that the next hop is loose instead of strict, the router consults the TE
topology database and routing to determine the next hop and output interface to forward the path message. The result of the
calculation is a list of hops; the list is placed in the outgoing ERO and checkpointed with the LSP data as the loose hop
information.
In Cisco IOS Release 15.0(1)S and later releases, the
show ip rsvp high-availability database lsp command displays sub-LSP information. If any sub-LSP, whether P2MP or P2P, fails to recover after a stateful switchover (SSO),
the failure is noted in an error database for troubleshooting. You can use the
show ip rsvp high-availability database lsp command to display error database entries.
You can use the
show ip rsvp high-availability database lsp-head command only on a headend router; this command gives no information on other routers
Examples
The following is sample output from the
show ip rsvp high-availability database hello command on an active Route Processor (RP):
Router# show ip rsvp high-availability database hello
HELLO WRITE DB
Header:
State: Checkpointed Action: Add
Seq #: 1 Flags: 0x0
Data:
Last sent Src_instance: 0xDE435865
HELLO READ DB
The table below describes the significant fields shown in the display.
Table 11. show ip rsvp high-availability database hello—Active RP Field Descriptions
Field
|
Description
|
HELLO WRITE DB
|
Storage area for active RP hello data consisting of checkpointed RSVP-TE information that is sent to the standby RP when
it becomes the active RP and needs to recover LSPs. This field is blank on a standby RP.
|
Header
|
Header information.
|
State
|
Status of an entry. Values are as follows:
-
Ack-Pending—Entries have been sent but not acknowledged.
-
Checkpointed—Entries have been sent and acknowledged by the standby RP.
-
Send-Pending—Entries are waiting to be sent.
|
Action
|
Action taken. Values are as follows:
-
Add—Adding an item to the standby RP.
-
Delete—Deleting an item from the standby RP. This is a temporary action that takes place while the active RP awaits an acknowledgment
(ack) of the delete operation.
-
Modify—Modifying an item on the standby RP.
-
Remove—Removing an item from the standby RP.
|
Seq #
|
Number used by the active and standby RPs to synchronize message acknowledgments (acks) and negative acknowledgments (nacks)
to sent messages.
|
Flags
|
Attribute used to identify or track data.
|
Data
|
Information about the last transmission.
|
Last sent Src_instance
|
Last sent source instance identifier.
|
HELLO READ DB
|
Storage area for standby RP hello data. This field is blank on an active RP, except when it is in recovery mode.
|
Examples
The following is sample output from the
show ip rsvp high-availability database hello
on a standby RP:
Router# show ip rsvp high-availability database hello
HELLO WRITE DB
HELLO READ DB
Header:
State: Checkpointed Action: Add
Seq #: 1 Flags: 0x0
Data:
Last sent Src_instance: 0xDE435865
These fields are the same as those for the active RP described in the table except they are now in the read database for
the standby RP.
Examples
The following is sample output from the
show ip rsvp high-availability database if-autotun command on an active RP.
Router# show ip rsvp high-availability database if-autotun
IF_AUTOTUN WRITE DB
Header:
State: Checkpointed Action: Add
Seq #: 1 Flags: 0x0
Data:
Tunnel ID: 1000 (if_handle: 85), prot_if_handle: 14
template_unit: n/a, dest: 22.22.22.22, flags=0x0
Header:
State: Checkpointed Action: Add
Seq #: 61 Flags: 0x0
Data:
Tunnel ID: 2000 (if_handle: 86), prot_if_handle: 14
template_unit: n/a, dest: 22.22.22.22, flags=0x1
Header:
State: Checkpointed Action: Add
Seq #: 1 Flags: 0x0
Data:
Tunnel ID: 3000 (if_handle: 87), prot_if_handle: 0
template_unit: 1, dest: 22.22.22.22, flags=0x2
Header:
State: Checkpointed Action: Add
Seq #: 1 Flags: 0x0
Data:
Tunnel ID: 3001 (if_handle: 88), prot_if_handle: 0
template_unit: 1, dest: 172.16.255.128, flags=0x2
Header:
State: Checkpointed Action: Add
Seq #: 1 Flags: 0x0
Data:
Tunnel ID: 3002 (if_handle: 89), prot_if_handle: 0
template_unit: 1, dest: 200.0.0.0, flags=0x2
IF_AUTOTUN READ DB
The table below describes the significant fields shown in the display.
Table 12. show ip rsvp high-availability database if-autotun—Active RP Field Descriptions
Field
|
Description
|
IF_AUTOTUN WRITE DB
|
Storage area for active RP autotunnel interface information. This field is blank on a standby RP.
|
Header
|
Header information.
|
State
|
Status of an entry. Values are as follows:
-
Ack-Pending—Entries have been sent but not acknowledged.
-
Checkpointed—Entries have been sent and acknowledged by the standby RP.
-
Send-Pending—Entries are still waiting to be sent.
|
Action
|
Action taken. Values are as follows:
-
Add—Adding an item to the standby RP.
-
Delete—Deleting an item from the standby RP. This action appears temporarily while the active RP awaits an ack of the delete
operation.
-
Modify—Modifying an item on the standby RP.
-
Remove—Removing an item from the standby RP.
|
Seq #
|
Number used by the active and standby RPs to synchronize message acks and nacks to sent messages.
|
Flags
|
Attributes used to identify or track data.
|
Data
|
Information about the last transmission.
|
Tunnel ID
|
Tunnel identifier.
|
if_handle
|
Internal number representing the autotunnel interface. For the same tunnel ID, this if_handle value should always be the same
for the record in the Standby READ DB as in the Active WRITE DB.
|
prot_if_handle
|
For autotunnel mesh tunnels, this value should always be zero. For autotunnel primary tunnels, this is an internal number
representing the egress interface of the autotunnel primary. For autotunnel backup tunnels, this is an internal number representing
the interface that the backup is protecting. In all three cases, for the same tunnel ID, this value should always be the same
for the record in the Standby READ DB as in the Active WRITE DB.
|
template_unit
|
For autotunnel mesh, this represents the auto-template interface number that the mesh tunnel was created from. For autotunnel
primary and backup, this should be "n/a."
|
dest
|
Destination IP address of the autotunnel.
|
flags
|
Encodings have these values:
-
0 = autotunnel primary
-
1 = autotunnel backup
-
2 = autotunnel mesh
|
IF_AUTOTUN READ DB
|
Storage area for standby RP autotunnel interface information. This field is blank on an active RP.
|
The fields for a standby RP are the same as those described in the table except that they are now in the interface autotunnel
read database instead of the interface autotunnel write database that is used by an active RP.
Examples
The following is sample output from the
show ip rsvp high-availability database link-management interfaces
command on an active RP:
Router# show ip rsvp high-availability database link-management interfaces
TE LINK WRITE DB
Flooding Protocol: ospf IGP Area ID: 0 Link ID: 0 (GigabitEthernet3/2)
Header:
State: Checkpointed Action: Add
Seq #: 4 Flags: 0x0
Data:
Ifnumber: 5 Link Valid Flags: 0x193B
Link Subnet Type: Broadcast
Local Intfc ID: 0 Neighbor Intf ID: 0
Link IP Address: 172.16.3.1
Neighbor IGP System ID: 172.16.3.2 Neighbor IP Address: 10.0.0.0
IGP Metric: 1 TE Metric: 1
Physical Bandwidth: 1000000 kbits/sec
Res. Global BW: 3000 kbits/sec
Res. Sub BW: 0 kbits/sec
Upstream::
Global Pool Sub Pool
----------- ----------
Reservable Bandwidth[0]: 0 0 kbits/sec
Reservable Bandwidth[1]: 0 0 kbits/sec
Reservable Bandwidth[2]: 0 0 kbits/sec
Reservable Bandwidth[3]: 0 0 kbits/sec
Reservable Bandwidth[4]: 0 0 kbits/sec
Reservable Bandwidth[5]: 0 0 kbits/sec
Reservable Bandwidth[6]: 0 0 kbits/sec
Reservable Bandwidth[7]: 0 0 kbits/sec
Downstream::
Global Pool Sub Pool
----------- ----------
Reservable Bandwidth[0]: 3000 0 kbits/sec
Reservable Bandwidth[1]: 3000 0 kbits/sec
Reservable Bandwidth[2]: 3000 0 kbits/sec
Reservable Bandwidth[3]: 3000 0 kbits/sec
Reservable Bandwidth[4]: 3000 0 kbits/sec
Reservable Bandwidth[5]: 3000 0 kbits/sec
Reservable Bandwidth[6]: 3000 0 kbits/sec
Reservable Bandwidth[7]: 2900 0 kbits/sec
Affinity Bits: 0x0
Protection Type: Capability 0, Working Priority 0
Number of TLVs: 0
The table below describes the significant fields shown in the display.
Table 13. show ip rsvp high-availability database link-management interfaces—Active RP Field Descriptions
Field
|
Description
|
TE LINK WRITE DB
|
Storage area for active TE RP link data. This field is blank on a standby RP.
|
Flooding Protocol
|
Protocol that is flooding information for this area. OSPF = Open Shortest Path First.
|
IGP Area ID
|
Interior Gateway Protocol (IGP) identifier for the area being flooded.
|
Link ID
|
Link identifier and interface for the area being flooded.
|
Header
|
Header information.
|
State
|
Status of an entry. Values are as follows:
-
Ack-Pending—Entries have been sent but not acknowledged.
-
Checkpointed—Entries have been sent and acknowledged by the standby RP.
-
Send-Pending—Entries are waiting to be sent.
|
Action
|
Action taken. Values are as follows:
-
Add—Adding an item to the standby RP.
-
Delete—Deleting an item from the standby RP. This action appears temporarily while the active RP awaits an ack of the delete
operation.
-
Modify—Modifying an item on the standby RP.
-
Remove—Removing an item from the standby RP.
|
Seq #
|
Number used by the active and standby RPs to synchronize message acks and nacks to sent messages.
|
Flags
|
Attribute used to identify or track data.
|
Data
|
Information about the last transmission.
|
Ifnumber
|
Interface number.
|
Link Valid Flags
|
Attributes used to identify or track links.
|
Link Subnet Type
|
Subnet type of the link. Values are as follows:
-
Broadcast—Data for multiple recipients.
-
Nonbroadcast Multiaccess--A network in which data is transmitted directly from one computer to another over a virtual circuit
or across a switching fabric.
-
Point-to-Multipoint—Unidirectional connection in which a single source end system (known as a root node) connects to multiple
destination end systems (known as leaves).
-
Point-to-Point—Unidirectional or bidirectional connection between two end systems.
-
Unknown subnet type—Subnet type not identified.
|
Local Intfc ID
|
Local interface identifier.
|
Neighbor Intf ID
|
Neighbor’s interface identifier.
|
Link IP Address
|
IP address of the link.
|
Neighbor IGP System ID
|
Neighbor system identifier configured using IGP.
|
Neighbor IP Address
|
Neighbor’s IP address.
|
IGP Metric
|
Metric value for the TE link configured using IGP.
|
TE Metric
|
Metric value for the TE link configured using Multiprotocol Label Switching (MPLS) TE.
|
Physical Bandwidth
|
Link bandwidth capacity in kilobits per second (kb/s).
|
Res. Global BW
|
Amount of reservable global pool bandwidth (in kb/s) on this link.
|
Res. Sub BW
|
Amount of reservable subpool bandwidth (in kb/s) on this link.
|
Upstream
|
Header for the following section of bandwidth values.
|
Global Pool
|
Global pool bandwidth (in kb/s) on this link.
|
Sub Pool
|
Subpool bandwidth (in kb/s) on this link.
|
Reservable Bandwidth [1]
|
Amount of bandwidth (in kb/s) available for reservations in the global TE topology and subpools.
|
Downstream
|
Header for the following section of bandwidth values.
|
Affinity Bits
|
Link attributes required in tunnels.
|
Protection Type
|
LSPs protected by fast reroute (FRR).
|
Number of TLVs
|
Number of type, length, values (TLVs).
|
The fields for a standby RP are the same as those described in the table except that they are now in the TE link read database
instead of the TE link write database that is used by an active RP.
Examples
The following is sample output from the
show ip rsvp high-availability database link-management system command on an active RP:
Router# show ip rsvp high-availability database link-management system
TE SYSTEM WRITE DB
Flooding Protocol: OSPF IGP Area ID: 0
Header:
State: Checkpointed Action: Modify
Seq #: 4 Flags: 0x0
Data:
LM Flood Data::
LSA Valid flags: 0x0 Node LSA flag: 0x0
IGP System ID: 172.16.3.1 MPLS TE Router ID: 10.0.0.3
Flooded links: 1 TLV length: 0 (bytes)
Fragment id: 0
TE SYSTEM READ DB
The table below describes the significant fields shown in the display.
Table 14. show ip rsvp high-availability database link-management system—Active RP Field Descriptions
Field
|
Description
|
TE SYSTEM WRITE DB
|
Storage area for active TE RP system data. This field is blank on a standby RP.
|
Flooding Protocol
|
Protocol that is flooding information for this area. OSPF = Open Shortest Path First.
|
IGP Area ID
|
IGP identifier for the area being flooded.
|
Header
|
Header information.
|
State
|
Status of an entry. Values are as follows:
-
Ack-Pending—Entries have been sent but not acknowledged.
-
Checkpointed—Entries have been sent and acknowledged by the standby RP.
-
Send-Pending—Entries are waiting to be sent.
|
Action
|
Action taken. Values are as follows:
-
Add—Adding an item to the standby RP.
-
Delete—Deleting an item from the standby RP. This action appears temporarily while the active RP awaits an ack of the delete
operation.
-
Modify—Modifying an item on the standby RP.
-
Remove—Removing an item from the standby RP.
|
Seq #
|
Number used by the active and standby RPs to synchronize message acks and nacks to messages sent.
|
Flags
|
Attribute used to identify or track data.
|
Data
|
Information about the last transmission.
|
LM Flood Data
|
Link management (LM) flood data.
|
LSA Valid flags
|
Link-state advertisement (LSA) attributes.
|
Node LSA flag
|
LSA attributes used by a router.
|
IGP System ID
|
Identification (IP address) that IGP flooding uses in this area to identify this node.
|
MPLS TE Router ID
|
MPLS TE router identifier (IP address).
|
Flooded links
|
Number of flooded links.
|
TLV length
|
TLV length in bytes.
|
Fragment id
|
Fragment identifier for this link.
|
TE SYSTEM READ DB
|
Storage area for standby TE RP system data. This field is blank on a standby RP.
|
The fields for a standby RP are the same as those described in the table except that they are now in the TE system read database
instead of the TE system write database that is used by an active RP.
Examples
The following is sample output from the
show ip rsvp high-availability database lsp command on an active RP for a P2P tunnel:
Router# show ip rsvp high-availability database lsp
Tun ID: 0 LSP ID: 10 (P2P)
SubGrp ID: -
SubGrp Orig: -
Dest: 10.3.0.1
Sender: 10.1.0.1 Ext. Tun ID: 10.1.0.1
Header:
State: Checkpointed Action: Add
Seq #: 2 Flags: 0x0
Data:
PathSet ID: -
Lspvif if_num: -
InLabel: -
Out I/F: Se2/0
Next-Hop: 10.1.3.2
OutLabel: 16
Loose hop info: None (0)
Examples
The following is sample output from the
show ip rsvp high-availability database lsp
command on an active RP for a P2MP tunnel:
Router# show ip rsvp high-availability database lsp
Tun ID: 1 LSP ID: 127 (P2MP)
SubGrp ID: 1
SubGrp Orig: 10.1.0.1
Dest: 10.2.0.1
Sender: 10.1.0.1 Ext. Tun ID: 10.1.0.1
Header:
State: Checkpointed Action: Add
Seq #: 30 Flags: 0x0
Data:
PathSet ID: 0x1A000003
Lspvif if_num: 35 (Lspvif0)
InLabel: 19
Out I/F: None
Next-Hop: -
OutLabel: -
Loose hop info: None (0)
The table below describes the significant fields shown in the display.
Table 15. show ip rsvp high-availability database lsp—Active RP Field Descriptions
Field
|
Description
|
P2P/P2MP
|
Tunnel type.
|
Subgrp ID
|
Subgroup identifier (valid only for P2MP TE LSPs).
|
Subgrp Orig
|
Subgroup origin IP address (valid only for P2MP TE LSPs).
|
Lspvif if_num
|
Interface number of the LSPVIF (valid only for P2MP TE tailends).
|
PathSet ID
|
Path set identifier (valid only for P2MP TE LSPs)
|
LSP WRITE DB
|
Storage area for active RP LSP data. This field is blank on a standby RP.
|
Tun ID
|
Tunnel identifier.
|
LSP ID
|
LSP identifier.
|
Dest
|
Tunnel destination IP address.
|
Sender
|
Tunnel sender IP address.
|
Ext. Tun ID
|
Extended tunnel identifier; usually set to 0 or the sender’s IP address.
|
Header
|
Header information.
|
State
|
Status of an entry. Values are as follows:
-
Ack-Pending—Entries have been sent, but not acknowledged.
-
Checkpointed—Entries have been sent and acknowledged by the standby RP.
-
Send-Pending—Entries are waiting to be sent.
|
Action
|
Action taken. Values are as follows:
-
Add—Adding an item to the standby RP.
-
Delete—Deleting an item from the standby RP. This action appears temporarily while the active RP awaits an ack of the delete
operation.
-
Modify—Modifying an item on the standby RP.
-
Remove—Removing an item from the standby RP.
|
Seq #
|
Number used by the active and standby RPs to synchronize message acks and nacks to messages sent.
|
Flags
|
Attribute used to identify or track data.
|
Data
|
Information about the last transmission.
|
InLabel
|
Incoming label identifier.
|
Out I/F
|
Outgoing interface.
|
Next-Hop
|
Next hop IP address.
|
OutLabel
|
Outgoing label identifier.
|
Loose hop info
|
Lists the loose hop expansions performed on the router, or specifies None.
|
LSP READ DB
|
Storage area for standby RP LSP data. This field is blank on an active RP.
|
The fields for a standby RP are the same as those described in the table except that they are now in the LSP read database
instead of the LSP write database that is used by an active RP.
Examples
The following is sample output from the
show ip rsvp high-availability database lsp-head command on an active RP for a P2P tunnel:
Router# show ip rsvp high-availability database lsp-head
LSP_HEAD WRITE DB
Tun ID: 0 (P2P)
Header:
State: Checkpointed Action: Add
Seq #: 2 Flags: 0x0
Data:
lsp_id: 10, bandwidth: 5, thead_flags: 0x1, popt: 1
feature flags: none
output_if_num: 11, output_nhop: 10.1.3.2
RRR path setup info
Destination: 10.3.0.1, Id: 10.3.0.1 Router Node (ospf) flag:0x0
IGP: ospf, IGP area: 0, Number of hops: 3, metric: 128
Hop 0: 10.1.3.2, Id: 10.2.0.1 Router Node (ospf), flag:0x0
Hop 1: 10.2.3.3, Id: 10.3.0.1 Router Node (ospf), flag:0x0
Hop 2: 10.3.0.1, Id: 10.3.0.1 Router Node (ospf), flag:0x0
Examples
The following is sample output from the
show ip rsvp high-availability database lsp-head
command on an active RP for a P2MP tunnel:
Router# show ip rsvp high-availability database lsp-head
LSP_HEAD WRITE DB
Tun ID: 1 (P2MP)
Destination: 10.2.0.1
Header:
State: Checkpointed Action: Add
Seq #: 3 Flags: 0x0
Data:
lsp_id: 11, bandwidth: 100, thead_flags: 0x1, popt: 1
Subgrp_id: 1
feature flags: none
output_if_num: 3, output_nhop: 10.1.2.2
RRR path setup info
Destination: 10.2.0.1, Id: 10.2.0.1 Router Node (ospf) flag:0x0
IGP: ospf, IGP area: 0, Number of hops: 3, metric: 10
Hop 0: 10.1.2.1, Id: 10.1.0.1 Router Node (ospf), flag:0x0
Hop 1: 10.1.2.2, Id: 10.2.0.1 Router Node (ospf), flag:0x0
Hop 2: 10.2.0.1, Id: 10.2.0.1 Router Node (ospf), flag:0x0
The table below describes the significant fields shown in the display.
Table 16. show ip rsvp high-availability database lsp-head—Active RP Field Descriptions
Field
|
Description
|
LSP_HEAD WRITE DB
|
Storage area for active RP LSP-head data. This field is blank on a standby RP.
|
P2P/P2MP
|
Tunnel type.
|
Tun ID
|
Tunnel identifier.
|
Header
|
Header information.
|
State
|
Status of an entry. Values are as follows:
-
Ack-Pending—Entries have been sent, but not acknowledged.
-
Checkpointed—Entries have been sent and acknowledged by the standby RP.
-
Send-Pending—Entries are waiting to be sent.
|
Action
|
Action taken. Values are as follows:
-
Add—Adding an item to the standby RP.
-
Delete—Deleting an item from the standby RP. This is a temporary action that takes place while the active RP awaits an ack
of the delete operation.
-
Modify—Modifying an item on the standby RP.
-
Remove—Removing an item from the standby RP.
|
Seq #
|
Number used by the active and standby RPs to synchronize message acks and nacks to messages sent.
|
Flags
|
Attribute used to identify or track data.
|
Data
|
Information about the last transmission.
|
lsp_id
|
LSP identifier.
|
bandwidth
|
Bandwidth on the LSP (in kb/s).
|
thead_flags
|
Tunnel head attribute used to identify or track data.
|
popt
|
Parsing option number.
|
feature_flags
|
Indicates whether the LSP being used to forward traffic is the secondary LSP using the path protection path option. Valid
values are as follows:
-
none
-
path protection active
|
output_if_num
|
Output interface number.
|
output_nhop
|
Output next hop IP address.
|
RRR path setup info
|
Routing with Resource Reservation (RRR) path information.
|
Destination
|
Destination IP address.
|
Id
|
IP address and protocol of the routing node. Values are as follows:
|
flag
|
Attribute used to track data.
|
IGP
|
Interior Gateway Protocol. OSPF = Open Shortest Path First.
|
IGP area
|
IGP area identifier.
|
Number of hops
|
Number of connections or routers.
|
metric
|
Routing cost.
|
Hop
|
Hop’s number and IP address.
|
LSP_HEAD READ DB
|
Storage area for standby RP LSP-head data. This field is blank on an active RP.
|
The fields for a standby RP are the same as those described in the table except that they are now in the LSP_head read database
instead of the LSP_head write database that is used by an active RP.
Examples
The following is sample output from the
show ip rsvp high-availability database summary command on an active RP:
Router# show ip rsvp high-availability database summary
Write DB:
Send-Pending: 0
Ack-Pending : 0
Checkpointed: 10
Total : 10
Read DB:
Total : 0
The table below describes the significant fields shown in the display.
Table 17. show ip rsvp high-availability database summary—Active RP Field Descriptions
Field
|
Description
|
Write DB
|
Storage area for active RP summary data. This field is blank on a standby RP.
|
Send-Pending
|
Entries are waiting to be sent.
|
Ack-Pending
|
Entries have been sent, but are waiting to be acknowledged.
|
Checkpointed
|
Entries have been sent and acknowledged.
|
Total
|
Total number of entries in the write database.
|
Total
|
Total number of entries in the read database.
|
Examples
The following is sample output from the
show ip rsvp high-availability database summary command on a standby RP:
Router# show ip rsvp high-availability database summary
Write DB:
Send-Pending: 0
Ack-Pending : 0
Checkpointed: 0
Total : 0
Read DB:
Total : 10
The table below describes the significant fields shown in the display.
Table 18. show ip rsvp high-availability database summary—Standby RP Field Descriptions
Field
|
Description
|
Write DB
|
Storage area for active RP summary data.
|
Send-Pending
|
Entries are waiting to be sent.
|
Ack-Pending
|
Entries have been sent but are waiting to be acknowledged.
|
Checkpointed
|
Entries have been sent and acknowledged.
|
Total
|
Total number of entries in the write database.
|
Total
|
Total number of entries in the read database.
|