regggional ip addressing · 2013. 1. 10. · ipv4 addressing private network address rangeprivate...

Regional IP Addressingg g

AMHS Workshop 1Federal AviationAdministrationApril 2012

Discussion Topics

• IPv4 Structure– Private Network address range

– Class A (RFC 1918)( )

• IP Addressing

I t ti dd i• Inter-connection addressing

• Network monitoring


IPv4 AddressingPrivate Network Address RangePrivate Network Address Range

IP Address Classful

Address RangeNumber of

host addresses

Bits for Network ID /

Host ID

Number of Network

addresses

Class A 10.0.0.0 – 10.255.255.255 16,777,214126 8/24

• Private Network address range

• Non-routable outside the network• Non-routable outside the network

• RFC 1918


Example Regional IP Addressing

1000001010 0000 0000 000 00000 00000001

Region Host’sState / Territory00001010 . 0000 0000 . 000 00000 . 00000001

First Byte . Second Byte . Third Byte . Fourth Byte

• APAC: Asia and Pacific (0010)• MID: Middle East Office (0011)• WACAF: Western and Central African Office (0100)• ESAF: Eastern and Southern Africa Office (0101)• EUR/NAT: European and North Atlantic Office (0110)



1000001010 0000 0000 000 00000 00000001

Region Host’sState / Territory00001010 . 0000 0000 . 000 00000 . 00000001


• State / TerritoryState / Territory• 7 bits from the second octet and third octet• A maximum 128



1000001010 00000000 000 00000 00000001

Region Host’sState / Territory00001010 . 00000000 . 000 00000 . 00000001


• 19 bits of sub-netting19 bits of sub netting • 11 bits are borrowed from the host• Networks are divided in 2048 sub networks



1000001010 00000000 000 00000 00000001

Region Host’sState / Territory00001010 . 00000000 . 000 00000 . 00000001


• Host’sHost s• 13 bits from the third and fourth octet• Maximum of 8190 addressable terminal/servers


Intra-Regional IP Addresses

1000001010 00000000 00000000 000000 01

Region Host’sState / Territory00001010 . 00000000 . 00000000 . 000000 01


Network BroadcastAddressesState

10.15.224.60

10.15.224.61Brazil

A ti 10.15.224.62Argentina

10.15.224.63


Intra-Regional IP Addresses

61 62.61 .62

10 15 224 6010 15 224 61

Brazil – Argentina

NWInterface10 15 224 61

10 15 224 6210 15 224 63

InterfaceBC

Interface


Network Monitoringg


NADIN AFTN Topology

ZSE

ZANARTCC Consolidated Facility ATCSCC NNCC WJHTCARTCCARTCC Consolidated FacilityConsolidated Facility ATCSCCATCSCC NNCCNNCC WJHTCWJHTC

Canada

(future) CAATSCAATS

ZLC

ZMP

ZKC

ZAU

ZOB ZNYZID

B7

B7

M15

B7M15

M15

x2

B7

B7

B7

M15

M15 B7

B13M15

B7

M15

B7

M15

M15

SLC

ZDVM15

ZOA 56kbps

56kbps

DCC

ZBW

M15 ZCY

ZDC BermudaPortugalJapan

( )

AMHS

AIDC

ZLA

ZFW

ZABZME

ZJX

M15

M15

M15

B7

B7x2

M15

B13

M15M15

M15

M15

B7

19.2kbps

19.2kbps

56kbps

ZTLZTL

M15

ATLB7

Australia

FijiNew Zealand

U.K(future)

SPANHNL

ZHU

ZJXM15 B7

B7

Brazil

Cuba

Mexico

Turks

MEVA-IIZMAZMA

Bahamas

SAMOA (via A.Samoa)

BVI

ArubaCaymanCaracas (via Puerto Rico)

Cuba

Curacao

Honduras

JamaicaPeru

Panama

St.MaartenTrinidad (via Puerto Rico)Haiti

DominicanRepublic

Puerto Rico

E/CAR Network: (AFTN Piarco, Trinidad):Anguilla, Antigua, St.Kitts&Nevis, Monserrat, Guadeloupe, Dominica, Martinique, St.Lucia, St.Vincent, Barbados, Grenada, Trinidad

CAMSAT Network (COCESNA):Honduras, Belize, Guatemala, El Salvador, Nicaragua, Costa Rica

Antigua (via Puerto Rico)


Future IP Implementations Possibilitiesp


Top 25 Errors

• Top 25 Errors and Discardsand Discards

• Top 25 Interfaces by y

Percent Utilization


Interface Details

• PercentPercent Utilization

Radial Gauges

• Up/Down Status

• Min/Max/Ave bps In/Out chart

P t• Percent Utilization Line

Chart


Node Details

• Response Time/PacketTime/Packet Loss chart

• Up/Down pStatus

• Active Alerts


NADIN II X.25 Decommissioningg


Current NADIN-II Network•NADIN PSN

•ARTCC •Consolidated Facility •ATCSCC •NEMC

•WJHTC

C d

•ZAN

•ZMP

•B7

M15

•B7

•B7

•M15

•56kbps

•Canada

•ZSE

•ZKC

•ZAU

•ZOB •ZNY•ZID•B7

•M15

•M15•M15

•B7•M15

•M15

•x2

•B7

•B7

•M15

•M15 •B7

•B13•M15

•B7

•M15

•B7

•M15

•56kbps •DCC

•ZBW

•M15

•ZDC

•SLC

•ZOA

•ZLC•ZCY

•ZDV

•ZAB

•ZME

•M15

M15

•B7•M15

•M15

•M15

•M15

•M15

•B7

•19.2kbps

•56kbps

•M15

•B7

•ZTL

•ZLA

•ZFW

•ATL

•ZHU

•ZJX•M15 •B7

•B7

•ZMA

•HNL


NADIN-II Decommissioning StrategySLC NEMC Move (completed)

– SLC node consolidation into the ZLC ARTCC node

Phase 1• Reduce the network from 26 to 9 core nodes that support key

systems (e.g. Oceanic) to give additional time to formulate a transition plans

– NAS users to move to TCP/IP; External users to move to CMHP– International users to consolidate to ATL/SLC or move to AMHS– Move user connections/circuits to core nodes

Phase 2• Concentrate residual X.25 links (e.g. International AFTN)

on Atlanta (ATL) and Salt Lake City (SLC/ZLC)– Move remaining user connections to ATL and SLC/ZLCg

Phase 3• Provide X.25 to CMHP conversion for remaining X.25 traffic


Core Network (Phase 1 Goal)

•NADIN PSN

•ARTCC •Consolidated Facility •ATCSCC •NEMC

•WJHTC

C d

•ZAN

•ZMP

•B7

M15

•B7

•B7

•M15

•56kbps

•Canada

•ZSE

•ZKC

•ZAU


•M15

•M15•M15

•B7•M15

•M15

•x2

•B7

•B7

•M15

•M15 •B7

•B13•M15

•B7

•M15

•B7

•M15

•56kbps •DCC

•ZBW

•M15

•SLC

•ZOA

•ZLC•ZCY

•ZDV

•ZDC

•ZAB

•ZME

•M15

M15

•B7•M15

•M15

•M15

•M15

•M15

•B7

•19.2kbps

•56kbps

•M15

•B7

•ZTL

•ZLA

•ZFW

•ATL

•ZHU

•ZJX•M15 •B7

•B7

•ZMA

•HNL


Residual X.25 (Phase 2 Goal)

C d

•ZAN

•ZMP

•B7

M15

•B7

•B7

•M15

•56kbps

•Canada

•ZSE

•ZKC

•ZAU


•M15

•M15•M15

•B7•M15

•M15

•x2

•B7

•B7

•M15

•M15 •B7

•B13•M15

•B7

•M15

•B7

•M15

•56kbps •DCC

•ZBW

•M15

•ZOA

•ZLC•ZCY

•ZDV

•ZDC•SLC

•ZAB

•ZME

•M15

M15

•B7•M15

•M15

•M15

•M15

•M15

•B7

•19.2kbps

•56kbps

•M15

•B7

•ZTL

•ZLA

•ZFW

•ATL•ATL

•ZHU

•ZJX•M15 •B7

•B7

•ZMA

•HNL


NADIN-II – FY 12 Goals (Dec 2011)

– ARINC IP transition for NADIN and TDLS – schedule Mar-Jul 2012

– Concentrate international AFTN at ATL and SLC – 72% completep

– ADAS rehost deployment - OMO data distribution via WMSCR

• Scheduled April-June 2012

– NAIMES (AISR, USNS, FS21) redeploymentMoving from Herndon VA to OKC (complete)

• Transition OKC from X.25 to IP (Apr-Jun 2012)( p )• Establish disaster backup at Herndon (CY13Q1 Herndon)

– ATOP/ DOTS/ FDP2000 IP solution for ARINC/ SITA1370 114 (1/2012) now gives clear path forward• 1370.114 (1/2012) now gives clear path forward

– Reduce the number of nodes to Phase1 (Core)


Questions


regggional ip addressing · 2013. 1. 10. · ipv4 addressing private network address rangeprivate...

Documents