Asterix Tech

Cisco binary image unpacker is a software that allows you to unpack the IOS and ASA images. Follow this steps to use this software for GNS3. With this way the Router loading process can be faster. This is useful for those of you that do start and stop Router frequently.

1. Donwload Cisco image unpacker 0.1 for Windows.
2. Extract thi zip file to your specific folder..
3. Copy the IOS file to this folder, for example "c3640-jk9s-mz.124-16a.bin".
4. On windows command prompt, type the following command:
   "unpack c3640-jk9s-mz.124-16a.bin" (without "").
   
   
   
   
5. The output file stored in temporary folder, in my case "C:\Documents and Settings\dion\Local Settings\Temp".
6. Open the folder and you will find the unpacked file "C3640-JK.bin", file size is about twofold.
7. Copy "C3640-JK.bin" to your IOS folder. Your can also rename the file to "c3640-jk9s-mz.124-16a(unpacked).bin"
   
8. Open GNS3, On the Edit menu, choose IOS image and hypervisors.
9. Reset the location of your new unpacked IOS file.
   
   
   
   
   
   

Routers Used: 3640 w/ NM-4T

IOS: c3640-jk9s-mz.124-16a

Objective

• In this lab, an OSPF stub area and a totally stubby area will be configured.

Scenario

• The Semarang router needs to be upgraded as it is suspected that the router is not keeping up with the growth of the OSPF internetwork. Diagnostics are performed and it is discovered that the router could benefit from more memory due to the large routing table. The router could also use a faster processor because of frequent Shortest Path First calculations. It is decided instead to create a smaller and more stable routing table using a stub or totally stubby area configuration.

Step 1

• Build and configure the network according to the diagram. Configure multiarea OSPF according to
  the diagram. However, do not configure a stub area yet. Use the configuration files from the previous
  lab if available and make adjustments as necessary.
  Note: The loopback, Lo5, on Jakarta1 can be ignored for now.
• Configure each router with the loopback address as indicated in the diagram. Be sure to configure
  Jakarta1 with additional loopbacks using Lo0, Lo1, Lo2, and Lo3. These loopback interfaces will
  simulate the serial links to other local Jakarta sites.
  
  
  
  
  
  
• Use ping and show ip route to test connectivity between all interfaces. Each router should be
  able to ping all network interfaces.

Step 2

• Create a loopback interface as follows to simulate the serial interface connecting to ISP1:
Jakarta1(config)#interface lo5
Jakarta1(config-if)#ip address 10.0.0.6 255.255.255.252
• Configure Jakarta1 as follows to redistribute an external route into the OSPF domain:
Jakarta1(config)#ip route 10.0.0.0 255.0.0.0 null0
Jakarta1(config)#router ospf 1
Jakarta1(config-router)#redistribute static
• Check the routing tables of all three routers. They should be complete.
  
  
  
  
  
  
• Jakarta2 and Semarang should also have a Type 2 external route to 10.0.0.0/8. They will not have a specific route to the loopback network, 10.0.0.4/30. That network has not clearly been advertised by any means.

Step 3

• Semarang has several interarea (IA) routes and one external (E2) route. In complex OSPF networks,
  a large number of external and interarea routes can needlessly weigh down some routers. Semarang
  is in a stub area, an area with one egress point. Semarang does not need external routing information, or even interarea summaries. Semarang just needs a default route to the ABR,
  Jakarta2.
• By configuring Area 2 as a stub area, Jakarta2 automatically produces a default route into Area 2.
  Use the following commands to configure the stub area:
Jakarta2(config)#router ospf 1
Jakarta2(config-router)#area 2 stub
• Also configure Semarang as follows:
Semarang(config)#router ospf 1
Semarang(config-router)#area 2 stub
• Verify that Area 2 is a stub by issuing the show ip ospf command:
  
  
  
  
  
  
• Now check Semarang’s routing table. Notice that a default route, 0.0.0.0/0, has been generated by the ABR, Jakarta2, on the stub area and now appears in Semarang’s table.
  
  
  
  
  /li>
  
  
• Recall that interarea (IA) routes point to networks in different areas within the same OSPF autonomous system.
• Because Area 2 is a stub area, all external routes, Type 5 LSAs, have been prevented from reaching
  internal routers.
• All external routes are filtered from stub areas and are replaced with a default route.

Step 4

• It is decided that the stub area configuration is not making a substantial impact on Area 2. Because Semarang can use the default route to its ABR for all nonlocal area traffic, it is decided to filter Type 3 and Type 4 interarea routes from Area 2. To do this, Area 2 must be configured as a totally stubby area, which is a Cisco proprietary feature.
•  Use the following commands on Jakarta2, the ABR, to configure Area 2 as a totally stubby area:
Jakarta2(config)#router ospf 1
Jakarta2(config-router)#no area 2 stub
Jakarta2(config-router)#area 2 stub no-summary
• The no-summary keyword at the ABR keeps interarea routes from entering stub Area 2, creating a
  totally stubby area. Only the ABR needs the additional configuration. The role of Area 2 internal
  routers has not changed.
• Return to Semarang and check its routing table:
  
  
  
  
  
  
• Interarea routes have also been replaced by a default route.
• Semarang should get a positive response by forwarding ICMP requests to Jakarta2 using the
  default route 0.0.0.0/0. Jakarta2 has a default route to network 10.0.0.0/8, and Jakarta1 has a
  directly connected route to 10.0.0.4/30 with the loopback interface 10.0.0.6/30. 

Download

• Configuring a Stub Area and a Totally Stubby Area

Routers Used: 3640 w/ NM-4T

IOS: c3640-jk9s-mz.124-16a

Objective

• In this lab, configure OSPF as a point-to-multipoint network type so that it operates efficiently over a hub-and-spoke Frame Relay topology.

Scenario

• International Travel Agency has just connected two regional headquarters to Asterix using Frame Relay in a hub-and-spoke topology. OSPF routing is to be configured over this type of network, which is known for introducing complications into OSPF adjacency relationships. To avoid these complications, manually override the Non-Broadcast Multi-Access (NBMA) OSPF network type and configure OSPF to run as a point-to-multipoint network. In this environment, no DR or BDR is elected.

Step 1

• Cable the network according to the diagram. Configure the FastEthernet or Loopback interface for each router as shown, but leave the serial interfaces and OSPF routing unconfigured for now.
• Until Frame Relay is configured, ping is not useful for testing connectivity.
• Configure port number and DLCI for the Frame Relay Switch Real seen in the picture.
  
  
  
  
  
  

Step 2

• Asterix acts as the hub in this hub-and-spoke network. It reaches Surabaya and Tegal through two separate PVCs. Configure Frame Relay on Asterix’s serial interface shown as follows:
  Asterix(config)#interface serial 0/0
Asterix(config-if)#encapsulation frame-relay
Asterix(config-if)#ip address 192.168.192.1 255.255.255.0
Asterix(config-if)#no shutdown
Asterix(config-if)#frame-relay map ip 192.168.192.2 102 broadcast
Asterix(config-if)#frame-relay map ip 192.168.192.4 103 broadcast
Asterix(config-if)#ip ospf network point-to-multipoint
• Notice that this configuration includes frame-relay map commands, which are also used on multipoint Frame Relay subinterfaces. These commands are used here with the broadcast keyword so that Frame Relay can process broadcast traffic. Without this configuration, OSPF multicast traffic would not be forwarded correctly by the Asterix router.
• Configure the serial interface for Surabaya as follows:
Surabaya(config)#interface serial 0/0
Surabaya(config-if)#encapsulation frame-relay
Surabaya(config-if)#ip address 192.168.192.2 255.255.255.0
Surabaya(config-if)#no shutdown
Surabaya(config-if)#frame-relay map ip 192.168.192.1 201 broadcast
Surabaya(config-if)#frame-relay map ip 192.168.192.4 201 broadcast
Surabaya(config-if)#ip ospf network point-to-multipoint
• Finally, configure the serial interface for Tegal as follows:
Tegal(config)#interface serial 0/0
Tegal(config-if)#encapsulation frame-relay
Tegal(config-if)#ip address 192.168.192.4 255.255.255.0
Tegal(config-if)#no shutdown
Tegal(config-if)#frame-relay map ip 192.168.192.1 301 broadcast
Tegal(config-if)#frame-relay map ip 192.168.192.2 301 broadcast
Tegal(config-if)#ip ospf network point-to-multipoint
• Verify Frame Relay operation with a ping command from each router to the other two. Use show frame-relay pvc and show frame-relay map to troubleshoot connectivity problems. Rebooting the Frame Relay switch might also solve connectivity issues.
  

Step 3

• Configure OSPF to run over this point-to-multipoint network. Issue the following commands at the appropriate router:
Surabaya(config)#router ospf 1
Surabaya(config-router)#network 192.168.200.0 0.0.0.255 area 0
Surabaya(config-router)#network 192.168.192.0 0.0.0.255 area 0

Asterix(config)#router ospf 1
Asterix(config-router)#network 192.168.1.0 0.0.0.255 area 0
Asterix(config-router)#network 192.168.192 0.0.0.255 area 0

Tegal(config)#router ospf 1
Tegalrouter)#network 192.168.232.0 0.0.0.255 area 0
Tegal(config-router)#network 192.168.192.0 0.0.0.255 area 0
• Verify the OSPF configuration by issuing the show ip route command at each of the routers:

• If each router has a complete table, including routes to 192.168.1.0 /24, 192.168.200.0 /24, and 192.168.232.0 /24, OSPF has been successfully configured to operate over Frame Relay.
• Test these routes by pinging the FastEthernet interfaces of each router from Surabaya’s console.
• Finally, issue the show ip ospf neighbor detail command at any router console:
  
  
  
  
• There is no DR. The configuration of OSPF point-to-multipoint network type on serial interfaces creates a logical multi-access network over physical point-to-point links. No efficiency would be realized by electing a DR.

Download

• Configuring Point-to-Multipoint OSPF Over Frame Relay