Max areas per OSPF process

Ever wondered how many OSPF areas are supported in single OSPF process?

I am not sure about Cisco, although it seems this is neither documented in H3C or in Cisco documents. I had to learn it through the hard way, and it seems the H3C routers supports only 50 areas per OSPF process (confirmed on MSR 30-40). Once you have 50 areas in a process, and you try to create 51st area, you shall encounter the error:

"warning: ospf 1 maximum limit reached"

The OSPF that I encountered this error was having following details:


<ROUTER>display ospf br

          OSPF Process 1 with Router ID 10.1.201.125
                 OSPF Protocol Information

  RouterID: 10.1.201.125     Router Type:  ABR  ASBR  NSSA
 Route Tag: 0
 Multi-VPN-Instance is not enabled
 Applications Supported: MPLS Traffic-Engineering
 SPF-schedule-interval: 5
 LSA generation interval: 5
 LSA arrival interval: 1000
 Transmit pacing: Interval: 20 Count: 3
 Default ASE parameters: Metric: 1 Tag: 1 Type: 2
 Route Preference: 10
 ASE Route Preference: 150
 SPF Computation Count: 899
 RFC 1583 Compatible
 Graceful restart interval: 120
 Area Count: 50  Nssa Area Count: 49
 ExChange/Loading Neighbors: 0



If you have more than 50 areas, you will need to add another process in the OSPF and then add the new areas in that new process, and then redistribute both processes in to each other...


Comments

Post a Comment

Popular posts from this blog

Show tech command in H3C

Normally we use " show tech " (show tech-support) command to gather ALL the information from a switch or a router. This applies to all Cisco networking devices as well as HP Procurve switches (I don't know about other vendors). The show tech command in H3C is display diagnostic-information . It does exactly the same thing as show tech, except that it will ask you if you want to save the output in a file [(inside flash), so that you can copy it using tftp], or display it on screen (as usual).
Read more

Telnet failed: Can't send after socket shutdown

Telnet failed: Can't send after socket shutdown. If you are getting this error on HP Procurve switch, it means that the Procurve switch is not accepting telnet sessions. A common reason for this is that you might have enabled SSH (and disabled telnet), or telnet on the swtich is not enabled at all (by default, telnet is disabled on Procurve switches). Telnet can be enabled on a Procurve switch as follows: Procurve-Switch (config)# telnet-server Thats it. Now you should be able to telnet your Procurve switch. Note: If you are in a different vlan than the management IP address of the switch, you need to set the correct default-gateway on the switch (only for edge switches).
Read more

3Com switches Password Recovery procedure

Use the password recovery method outlined below to define a new password for the admin username:  (This method works for most of the 3-Com switches) 1. Access the Command Line Interface and enter the user name "recover" and password "recover" to place your unit in password recovery mode. The unit will remain in password recovery mode for a maximum of 30 seconds, before it returns to the CLI login prompt.  2. During these 30 seconds, perform a hard reboot on the unit while it is still in password recovery mode by turning it off, waiting for a few seconds, and then switching it on again.  3. When the unit has rebooted following the hard reboot enter a new password for the "admin" user account.  4. Enter enable to leave password recovery enabled (to enable recovery of the password next time if you forget), or enter disable to turn it off (not recommended). You are now logged in as the default "admin" user. 
Read more