Foundry Networks Switch and Router Installation And Configuration Manual page 794

Foundry Switch and Router Installation and Configuration Guide
Displaying Route Details
Here is an example of the information displayed when you use the detail option. In this example, the information
for one route is shown.
BigIron# show ip bgp routes detail
Total number of BGP Routes: 516985
Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
H:HISTORY I:IBGP L:LOCAL M:MULTIPATH S:SUPPRESSED
Network
1 0.0.0.0/0
Atomic AGGREGATION(ID
None 0.0.0.0
Status Learned From
B 192.169.103.1
remaining entries not shown...
These displays show the following information.
This Field...
Total number of BGP Routes
Status codes
Network
Next Hop
Metric
LocPrf
Weight
Origin
19 - 112
Next Hop Metric
192.169.103.1 None
AS) Originator
0 None
Distance RIB_out Communities
20 10
Table 19.10: BGP4 Network Information
Displays...
The number of BGP4 routes.
A list of the characters the display uses to indicate the route's status.
The status code is appears in the left column of the display, to the left
of each route. The status codes are described in the command's
output.
The network address.
The next-hop router for reaching the network from the Layer 3 Switch.
The value of the route's MED attribute. If the route does not have a
metric, this field is blank.
The degree of preference for this route relative to other routes in the
local AS. When the BGP4 algorithm compares routes on the basis of
local preferences, the route with the higher local preference is chosen.
The preference can have a value from 0 – 4294967295.
The value that this router associates with routes from a specific
neighbor. For example, if the router receives routes to the same
destination from two BGP4 neighbors, the router prefers the route
from the neighbor with the larger weight.
The source of the route information. The origin can be one of the
following:
• EGP – The routes with this set of attributes came to BGP through
EGP.
• IGP – The routes with this set of attributes came to BGP through
IGP.
• INCOMPLETE – The routes came from an origin other than one
of the above. For example, they may have been redistributed
from OSPF or RIP.
When BGP4 compares multiple routes to a destination to select the
best route, IGP is preferred over EGP and both are preferred over
INCOMPLETE.
LocPrf Weight
100 0
Cluster List
None
Internet
Origin
IGP
December 2000