In 20 years, you will be more dissapointed by what you didn't do than by what you did.

Whole Internet BGP Table: Route Server Check for Network Engineers

Whole Internet BGP table checks are useful when you want to compare a lab or provider edge view with a public routing-table perspective. This older note keeps the original route-server example and adds context for engineers using it as a quick BGP reference.

Checking a public BGP route server

If you want to check how currnet BGP table looks like you can do this, just telnet to :

route-server.ip.att.net - 12.0.1.28  login: rviews
route-server.cerf.net - 12.129.193.235



The routing table summary :



route-server>sho ip route summary
IP routing table name is Default-IP-Routing-Table(0)
IP routing table maximum-paths is 32
Route Source    Networks    Subnets     Overhead    Memory (bytes)
connected       0           1           64          152
static          3           11          896         2128
bgp 65000       144357      224127      23582976    56282928
  External: 368484 Internal: 0 Local: 0
internal        4254                                4985688
Total           148614      224139      23583936    61270896
route-server>

Related reading

Discussion

If you have tested this in a lab or seen a different behavior in production, share the platform, software version and troubleshooting notes in the comments. Real results are more useful than generic theory.

Comments

0 Responses to "Whole Internet BGP Table: Route Server Check for Network Engineers"

Post a Comment

Popular Posts