ATM Address Assignments (PVCs) in the
ARC Testbed & GTE SCAN Project

The old table (prior to 3/97) has been archived, but is no longer active.

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.

Go back to the ATOMIC-2 home page. / Go back to the ISI home page.

This page written and maintained by the ATOMIC-2 group.
Please mail us any problems with or comments about this page.

Last modified May 28, 1997.