ATOMIC-2 is implementing a production-quality IP LAN at 640 Mbps for the 65 workstations in the HPCC division at ISI. ATOMIC-2 is specifically researching the issues in augmenting this LAN to provide an integrated high-speed network, including ATM interconnectivity to the WAN, file services, etc.
We are members of an ATM Research Consortium (ARC) ATM testbed in the Los Angeles area, composed of two groups of participants:
ISI’s ATOMIC-2 project has the role of managing the network administration and configuration as follows:
Project status and milestones
Milestones
- 4-6/95 – ISI ATM fiber installed
- 10/95 – “scan.net” DNS installed
- 12/95 – Web pages with IP, ATM link numbers and DNS forms released
- 12/95 – single LIS chosen for IP configuration
- 1/96 – Web pages with integrated DNS queries released
- 2/96 – default IP router and ATM pvc configuration specified
- 2/96 – ISI ATM line is up
- 3/96 – ISI pings TAC, UCLA
- 4/96 – TAC pings HMC
- 4/96 – ISI installs default IP / ATM configuration
- 4/96 – Web status pages installed
- 5/96 – ISI pings HMC
- 5/96 – DNS available over scan.net itself
- 7/96 – PVC 3 used for ISI-UCLA link
- 3/97 – Network redesigned to use a backbone PVC ring
Status – by site
- ISI
- ATM – done
- 2/95 switch
- 4-6/95 fiber
- 12/95 single-mode line card
- 2/96 line
- 7/96 PVC 3 setup to UCLA for tests
- 3/97 Redesign backbone PVC ring as full mesh
- IP – full default IP table
- 10/95 “scan.net” DNS installed
- 3/96 pings TAC, UCLA, CIT
- 4/96 full default IP router table configured
- 5/96 pings HMC
- 5/96 “scan.net” DNS moved onto scan.net
- 5/96 added CSUN
- ATM – done
Status – by topic
- ATM
- 12/95 TAC vcc table created
- 7/96 PVC setup ISI-UCLA for tests
- 2/97 TAC/UCLA Backbone redesigned based on PVC ring
- 3/97 ISI full mesh based on PVC mask designed
- IP
- 10/95 ISI “scan.net” DNS installed
- 12/95 ISI/TAC single LIS chosen, partitioned
- 1/96 ISI Web pages with integrated DNS
- 4/96 ISI default configuration specified
- 5/96 ISI “scan.net” DNS moved onto scan.net
- 5/96 ISI updated allocations to add CSUN
- Web
- ARC pages
- SCAN pages
- 12/95 ISI Network management
- 1/96 ISI DNS query
- 4/96 ISI project status
IP address tables
Abbrev. Full name Location ----------------------------------------------------------------------- ISI USC/Information Sciences Institute Marina del Rey UCI Univ. Calif. at Irvine Irvine HMC Harvey Mudd College Claremont UCLA Univ. Calif. at Los Angeles West LA VAWLA Veteran's Admin., West LA West LA TAC The Aerospace Corp. El Segundo CIT Calif. Institute of Tech. Pasedena SWRL Calif. State Univ. / Soutwest Regional Lab San Diego USC Univ. of Southern Calif. / ATRIUM Los Angeles JPL Jet Propulsion Lab Pasedena CSUN Calif. State Univ. / Northridge Northridge GTE GTE / Marina del Rey lab Marina del Rey
NB: Some sites have multiple internal connections.
IP Allocations
Loc. IP Subnet/28 DNS Info ISI 198.32.6.0 UCI 198.32.6.16 HMC 198.32.6.32 UCLA 198.32.6.48 VAWLA 198.32.6.64 TAC 198.32.6.80 CIT 198.32.6.96 SWRL 198.32.6.112 USC 198.32.6.128 JPL 198.32.6.144 CSUN 198.32.6.160 (resv) 198.32.6.176 (resv) 198.32.6.192 (resv) 198.32.6.208 (resv) 198.32.6.224 GTE 198.32.6.240
IP Address Conventions
For each subnet, the following addresses are predefined: 198.32.6.subnet | 0.0.0.0 = network named (sitename)-net.scan.net 198.32.6.subnet | 0.0.0.1 = primary router named (sitename).scan.net, i.e., for ISI: isi.scan.net 198.32.6.subnet | 0.0.0.15 = subnet broadcast
IP address information and policy
ISI’s ATOMIC-2 project has the role of managing the network administrationand configuration.
To request an IP address within a preallocated set, use our handy form (DEPRECATED). (Exchange is SCAN)
To request an IP set to be allocated to your project, or for questions, send mail to Joe Touch.
The SCAN IP address is a Class C of 198.32.6.0 / 24, and is a single LIS (logical IP subnet). The mask is 198.32.6.255. The SCAN.NET IP network DNS is maintained at IDN.ISI.EDU (128.9.160.72), also available via SCAN.NET itself at ISI.SCAN.NET (198.32.6.1).
You can use dig at your site, or click on the handy web-accessible versions below:
Get DNS Summary Info list of forward zone transfer: dig @idn.isi.edu scan.net axfr list of nameservers (NS): dig @idn.isi.edu scan.net ns list of reverse (PTR) resolutions: dig @idn.isi.edu -x 198.32.6 axfr | grep " A "
To permit each site to allocate within this range autonomously, the IP address has been grouped into 16 “subnets”.
NOTE: subnetting is used for address assignment only, and does not imply that there are subnet routers or that subnet network addresses or broadcast addresses are valid.
A clickable table with current DNS information is available. (DEPRECATED)
Note – you may allocate only 14 hosts in your virtual subnet (addresses whose last 4 bits represent 0 and 15 are reserved for possible future subnet and broadcast use, IF SUBNETTING via multiple LIS’s is supported).
A dummy host has been setup in the reserved space to test DNS requests ONLY: foo.scan.net 198.32.6.1
ATM ring and VCI address tables
new table:
THIS ALLOCATION HAS BEEN CONFIRMED as of 5/97
The current table is as follows.
ATM PVP:PVC virtual routes
| from:to | Do not use | locally allocated |
ISI | HMC | UCLA | TAC |
|---|---|---|---|---|---|---|
| ISI | 0-127 | 128-255 | — | 3:384-447 (UCLA) 6:384-447 (TAC) |
3:256-381* | 6:256-383 |
| HMC | 0-127 | 128-255 | 4:384-447 (UCLA) 5:384-447 (TAC) |
— | 4:256-383 | 5:256-383 |
| UCLA | 0-127 | 128-255 | 3:256-381* | 4:256-383 | — | 3:448-511 (ISI) 4:448-511 (HMC) |
| TAC | 0-127 | 128-255 | 6:256-383 | 5:256-383 | 6:448-511 (ISI) 5:448-511 (HMC) |
— |
(X) means the path is indirect, and X is the direct next-hop.
* indicates that some PVCs of this set are allocated to CAIRN, specifically the pair
ISI/3:382 <-> UCLA/3:382 and ISI/3:383 <-> UCLA/3:383
This table relies on the following allocations:
ATM PVP:PVC THRU maps
MUST BE IMPLEMENTED AT THE SITE LISTED BELOW
| ISI- | 3:448-511 <-> 6:448-511 |
| HMC- | 4:384-447 <-> 5:384-447 |
| UCLA- | 3:448-511 <-> 4:448-511 |
| TAC- | 5:384-447 <-> 6:384-447 |
NOTE: – = not implemented yet
ATM PVP Allocations
| from:to | ISI | HMC | UCLA | TAC |
|---|---|---|---|---|
| ISI | — | * | 3 | 6 |
| HMC | * | — | 4 | 5 |
| UCLA | 3 | 4 | — | * |
| TAC | 6 | 5 | * | — |
Notes: * = not connected
3 ISI-----UCLA | | 6 ++++ | 4 | + | TAC-+---HMC 5 (TAC is in Pacbell, others are in GTE)
ATM PVC Allocations
Although PVCs are intended to be link-based, not path-based, we use them for paths from source to destination. The reason is to reduce the number of PVCs allocated at the telco interfaces. It results in extending the ‘SCAN PVPs’ in the top part of the PVC space, and masking out the telco PVPs.
The space is allocated out of PVCs 128-511. 0-127 is avoided due to partial use as reserved space. Above 512 is avoided due to host interface limitations, and the desire to use end-to-end PVCs. There are 6 blocks of 64 PVCs remaining, which are used to create the full backbone interconnect:
PVCs: 0-127 reserved (in-use) 128-255 reserved for site-specific use 256-383 use for direct-connected PVPs ISI-UCLA ISI-TAC UCLA-HMC TAC-HMC 3:256-381 (382,383 for CAIRN) ISI<---------->UCLA ^ ^ | | 6:256-383 +++++ | 4:256-383 | + | v + v TAC<-+---------->HMC 5:256-383 384-511 used for 2-hop PVPs THRU SITE CONFIGURATION: ISI 3:448-511 <-> 6:448-511 THRU UCLA 3:384-447 <-> 4:384-447 THRU HMC 4:448-511 <-> 5:448-511 THRU TAC 5:384-447 <-> 6:384-447 THRU 2-hop TO-SITE addresses: ISI-HMC 3:384-447 <-> 4:384-447 via UCLA ISI-HMC 6:384-447 <-> 5:384-447 via TAC UCLA-TAC 3:448-511 <-> 6:448-511 via ISI UCLA-TAC 4:448-511 <-> 5:448-511 via HMC 384-447 use for 2-hop PVPs ISI-(UCLA)-HMC ISI-(TAC)-HMC 3:384-447 ISI<----------(UCLA) ^ | | | 6:384-447 +++++ | 4:384-447 | + | | + v (TAC)-+---------->HMC 5:384-447 448-511 use for 2-hop PVPs UCLA-(HMC)-TAC UCLA-(ISI)-TAC 3:448-511 (ISI)---------->UCLA | ^ | | 6:448-511 +++++ | 4:448-511 | + | v + | TAC<-+----------(HMC) 5:448-511
NOTE: PVC “0” (the lowest number in each group above) is pre-allocated for IP pings. Sites are expected to support 3 IP ping addresses, one for each remote site. The final ping address (for alternate path for the indirect site) is not strictly required.
archived old table:
This table invalid as of 3/97
PVC TABLE ============================================================================================= ISI UCI HMC UCLA VAWLA TAC CIT SWRL USC JPL CSUN ISI --- 1112 1007++ 1022* 497 1067++ 92++ 1037 1142 1097 ? UCI 1112 --- 1247 1367 617 1637 212 1472 1802 1742 ? HMC 1007++ 1247 --- 1157++ 512 1202++ 107+* 1172 1277 1232 ? UCLA 1022* 1367 1157++ --- 527 1337* 122* 1292 1397 1352 ? VAWLA 497 617 512 527 --- 572 47 542 647 602 ? TAC 1067++ 1637 1202++ 1337* 572 --- 167* 1427 1667 1622 ? CIT 92++ 212 107+* 122* 47 167* --- 137 242 197 ? SWRL 1037 1472 1172 1292 542 1427 137 --- 1502 1457 ? USC 1142 1802 1277 1397 647 1667 242 1502 --- 1772 ? JPL 1097 1742 1232 1352 602 1622 197 1457 1772 --- ? CSUN ? ? ? ? ? ? ? ? ? ? --- ============================================================================================= Notes: All VCIs are in VPI 0. Each pair of sites is allocated 15 VCIs. + - 1 PVC established ++ - 8 PVCs established +* - 12 PVCs established * - 15 PVCs established
ATM PVC Conventions
For each PVC pair, there is a block of 15 PVCs allocated. The lowest-numbered PVC will be maintained by the backbone (Steve Schwab at Aero), and is presumed to connect the primary IP router.