ROUTER CONFIGURATION PARTITIONING

-
If you have to troubleshoot routers with long configurations, you're probably as fed up with the slow response of the show running-config command as I am. Unfortunately, there's not much you can do; the running configuration is reverse-engineered from various memory variables every time you ask for it and that process simply takes time if you've configured many parameters.


IOS release 12.2(33)SRB has introduced a fantastic feature: router configuration partitioning. The early seeds of this idea are already present in mainstream IOS releases. For example, you can display the configuration of a single interface, all class-maps or all policy-maps. The configuration partitioning gives you the ability to display access-lists, route-maps, static routes, router configurations ...
PE-A#show running-config partition ?
  access-list       All access-list configurations
  class-map         All class-map configurations
  common            All remaining unregistered configurations
  global-cdp        All global cdp configurations
  interface         Each Interface specific Configurations
  ip-as-path        All IP as-path configurations
  ip-community      All IP community list configurations
  ip-domain-list    All ip domain list configurations
  ip-prefix-list    All ip prefix-list configurations
  ip-static-routes  All IP static configurations
  line              All line mode configurations
  policy-map        All policy-map configurations
  route-map         All route-map configurations
  router            All routing configurations
  snmp              All SNMP configurations
  tacacs            All TACACS configurations
For example, if you want to display just the configuration of the OSPF process, you'd ask for show running partition router ospf 1:
PE-A#show running partition router ospf 1
Building configuration...

Current configuration : 164 bytes
!
Configuration of Partition - router ospf 1
!
!
router ospf 1
 log-adjacency-changes
 passive-interface Serial1/1
 network 0.0.0.0 255.255.255.255 area 0
!
!
end

Comments

Post a Comment

Popular posts from this blog

Disabling Unneeded Services

-
Step 1: Configure the Physical Interface Because this lab uses only one router, you will simulate an active FastEthernet connection by activating the interface and applying the no keepalive command to initiate an “always up” state, regardless of the existence of a device at the remote end. Normally, you would not use the no keepalive command on a routed interface, except in special circumstances. In this lab, you will use it only for simulation purposes. Configure the R1 physical interface using the IP address shown in the topology diagram. Use the no keepalive command in interface configuration mode, and then use the no shutdown command to activate the interface. Because you have disabled keepalives, the interface status displays as link state (Layer 1) and line protocols state (Layer 2) “up,” even if it is not connected to an external device. R1(config)# interface fastethernet0/0 R1(config-if)# ip address 192.168.10.1 255.255.255.0 R1(config-if)# no keepalive R1(config-if)# no s...
Read more

EBGP Multihop

-
Image
Configuring iBGP doesn't require the neighbor address to be directly connected. The best practice for iBGP is to use the loopback address as the ip address configured on the BGP neighbor statement. Loopback interfaces never go down so provided that there is an alternate route to the loopback ip address through an IGP, BGP session will not be torn down. Using loopback addresses for eBGP is also a good practice if there are multiple links between two routers on different autonomous system as shown on the example diagram below. This will also achieve load balancing. The initial configuration for this lab is shown below. R1# ! interface Serial1/0 ip address 10.10.10.1 255.255.255.0 serial restart-delay 0 end ! interface Serial1/1 ip address 10.10.20.1 255.255.255.0 serial restart-delay 0 end ! interface Loopback0 ip address 1.1.1.1 255.255.255.255 ! router bgp 1 no synchronization bgp log-neighbor-changes neighbor 2.2.2.2 remote-as 2 no auto-summary ! ip route 2.2.2.2 255.255.2...
Read more