Search this Blog

Thursday, August 29, 2013

Cisco ASR Series - Command for the System Usage


We are using a ASR 1001 series router as a gateway router. What is the exact command to see the process usage of the system??
 
show processes memory
show memory
show platform software status control-processor brief

show platform software process slot R0 monitor

Below is the link for Cisco ASR Series Aggregation Services Routers




Citation - This blog post does not reflect original content from the author. Rather it summarizes content that are relevant to the topic from different sources in the web. The sources might include any online discussion boards, forums, websites and others.

BGP Protocol Configuration and Missing Prefix


when configuring protocol BGP - one of the boarders, I do not see prefixes that advertises my other Border ... In order ... 

There are two boarders are included in the AS78:
Point1 - announcement 10.32.19.0/24, received full-view;
Point2 - announcement 10.32.110.0/24, received the default.
Each of the boarders has two BGP session c:
ISP1, AS70;
ISP2, AS32.
Between Point1 and Point2 not connected via iBGP, all communication must be through the external connections.
On Point1 received full-view:
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up / Down State / PfxRcd
10.10.10.1 4 32 2632424 44442 43720971 0 0 4w0d 462061
10.10.20.1 4 70 1701047 36822 43720971 0 0 3w2d 464547
But I do not see in this table prefix 10.32.110.0:
Point1 # sh ip bgp 10.32.110.0/24
% Network not in table
Communicated with specialists ISP, they have successfully received the prefix 10.32.110.0/24 of Point2 and advertised to Point1.
It seems that he Point1, somehow excludes him from the table, the command "# sh ip bgp neighbors 10.10.10.1 received-routes" I do not see that the prefix 10.32.110.0/24 is received from a neighbor.
Maybe this is normal behavior and something needs tweaking to prefixes taken from their neighbors have the same AS, but as long as the documentation did not find anything about this situation. 



The reason point1 does not see 10.32.110.0/24 is that this prefix is reject on point1 because of the AS path loop detection. This prefix is originated by AS78 and on reception point1 checks the AS path, sees its own AS in the path and drops it. This is not an issue if point1 have a default route coming from ISP1 and ISP2 in addition to the full view. The other way to fix it is to allow point1 to receive prefixes originated by AS78 using the "allowas-in" command. This command should be used carefully as it disabled the AS path loop detection. It should not be a problem with the right filtering in place.


Citation - This blog post does not reflect original content from the author. Rather it summarizes content that are relevant to the topic from different sources in the web. The sources might include any online discussion boards, forums, websites and others.


 
/* Google Analytics begin ----------------------------------------------- */ /* Google Analytics end ----------------------------------------------- */