**9. Appendix**

378 Earthquake Research and Analysis – Statistical Studies, Observations and Planning

useful for collecting information from several independent monitoring systems and for providing the correct information in an integrated wide view in case of significant network

After the earthquake, communication among NOCs was difficult because the fiber break disrupted VoIP and legacy telephone service. Moreover, the earthquake happened on December 26th 2006, overlapping with the Christmas holiday. Thus, all the communication was routed over the instant messaging system and e-mails were routed over the detoured network even though it provided poor quality service. It became obvious that the emergency communication should be guaranteed in case of failures so that the recovery

Since the Internet continues to grow globally and becomes ever more important in daily life, business, and research, the need for fault-tolerant service in network management becomes more urgent. However, during the network failures caused by the 2006 earthquake, it was shown that there are still many challenges in fault-tolerant network management research. Even though multiple fiber cores are installed together to provide backup service, they may be useless during severe natural disasters. Therefore, full-mesh or fiber-disjoint physical network topology should be designed for use during failures. On the available topology, it was seen that BGP routing provided backup AS paths, which was useful for the first step in restoration. However, the traffic engineering issues during restoration were difficult to solve because all the information, such as link capacity, available bandwidth, link delay, traffic load, and routing policy, had to be collected, interpreted, and acted on by human operators. In spite of BGP re-routing, we had to deal with a few single-link ASs to establish direct connections to the R&E networks. From this experience of network recovery during a significant natural disaster affecting several different countries and ISP's, we were able to gather valuable information on network management during emergencies. Therefore, in the Internet of the future, designers should focus on fault-tolerant network management study including robust physical topology, cross-layer restoration, traffic engineering combined

We would like to show the one example from this lesson. In August 2009, the earthquake happened again near Taiwan island and the fiber cut happened again. Table 1 tool was improved as "Compath" already and the table was constructed again for this disaster (Kurokawa, 2010). At that time, the medical demonstration was planned in Asian area and the connectivity of the Thailand was required. The compath table recommended that the TW should have become the hub for the southeast Asian area. This was against the policy of TEIN2, but the R&E networks object is to support the researchers and such the flexibility was approved and the tool from the lesson of the 2006 earthquake improved the network

After the earthquake, KDDI OTC (Otemachi Technical Center) worked very hard to fix the routing problems of APAN Tokyo XP both in their capacity as paid staff and as volunteers.

**6.3 Emergency communication between operators** 

with BGP routing, and simulation of failures in the network.

process can be started quickly

**7. Summary** 

operations.

**8. Acknowledgment** 

failures.

Table 3. ISO 3166 Country Code (International Organization for Standardization [ISO], n.d.) in this chapter

Experience with Restoration of Asia Pacific Network Failures from Taiwan Earthquake 381

Data 7. Application Network Process to application

Segment/Datagram 4. Transport End-toend connections and

Packet 3. Network Path determination and logical

Frame 2. Data Link Physical addressing (MAC &

Bit 1. Physical Media signal and binary

Academia Sinica, (n.d.). The December 26, 2006, Pingtung, Taiwan earthquake, In : *Academia* 

Academia Sinica, (n.d.). The December 26, 2006, Pingtung, Taiwan earthquake, In : *Academia* 

Asian Internet Interconnection Initiative Project, (n.d.). Asian Internet Interconnection

Asia-Pacific Advanced Network, (n.d.). Welcome to Asia-Pacific Advanced Network, In : *Asia-Pacific Advanced Network*, 26.07.2011, Available from: http://www.apan.net/ Asia-Pacific Advanced Network Japan, (n.d.). APAN-JP Network Traffic Weathermap, In :

http://www.cisco.com/en/US/products/ps6601/products\_ios\_protocol\_group\_h

Delivery of Advanced Network Technology to Europe, (n.d.). TEIN2, In : DANTE,

Fumagalli, A. & Valcarenghi, L. (2000). IP Restoration vs. WDM Protection: Is There an

Gerstel, O. & Ramaswami, R. (2000), Optical Layer Survivability: a Services Perspective, *IEEE Communications Magazine,* Vol. 38. No. 3, (March 2000), pp. 104-113, ISSN 01636804 GOOGLE, (n.d.). iperf – TCP and UDP bandwidth performance measurement tool, In :

Optimal Choice?, *IEEE Network Magazine,* Vol. 14, No. 6, (December 2000), pp. 34-

Initiative Project, In : *Asian Internet Interconnection Initiative Project*, 26.07.2011,

http://www.earth.sinica.edu.tw/~smdmc/recent/2006/200612261226.htm

http://www.earth.sinica.edu.tw/~smdmc/recent/2006/200612261234.htm

6. Presentation Data representation and encryption 5. Session Interhost communication

reliability

addressing

transmission

LLC)

Data unit Layer Function

Table 5. Open Systems Interconnection (OSI) Basic Reference Model

*Sinica*, 26.07.2011, Available from :

*Sinica*, 26.07.2011, Available from :

Available from : http://www.ai3.net/

http://monitor.jp.apan.net/weathermap/

ome.html

41, ISSN 08908044

http://code.google.com/p/iperf/

*APAN Japan Consortium*, 26.07.2011, Available from :

CISCO, (n.d.). Cisco IOS NetFlow In : *Cisco*, 26.07.2011, Available from :

26.07.2011, Available from: http://www.tein2.net/

*Google Project Hosting*, 26.07.2011., Available from :

OSI Model

Host layers

Media layers

**10. References** 


Table 4. Network Name


Table 5. Open Systems Interconnection (OSI) Basic Reference Model
