Changes between Version 118 and Version 119 of ConnectivityHome


Ignore:
Timestamp:
05/20/11 15:28:50 (13 years ago)
Author:
jwilliams@bbn.com
Comment:

moved IP table to be with the IP network section

Legend:

Unmodified
Added
Removed
Modified

  • ConnectivityHome

    v118 v119  
    1111 4. ConnectivityTesting     - additional reference on common testing software.
    1212 5. OpenFlow/CampusTopology - guidelines for sites' OpenFlow deployment to reach various GENI VLANS.
    13  6. NetworkCore             - Topology and configuration of the Internet2 and National LambdaRail interconnected Backbone OpenFlow Core VLANs.           
    14 
    15 == Site's IP Ranges ==
    16 For initial Connectivity testing, a typical nomenclature is to use a 10.X.X.0/24 net with a VLAN ID encoded into the IP address.  To save time allocating IP addresses the following range-by-subnet scheme can be used for initial connectivity and "path-finding" experiments and configurations. This is particularly useful for multi-site connections, such as the OpenFlow Core VLANs.
    17 
    18 '''To connect your site with GENI:''' Email [mailto:help@gpo.net]
    19 
    20 
    21 ||'''Campus'''                      ||'''(example as VLAN 3705)[[BR]]assigned IP range''' || '''First Host IP''' ||  '''Last Host''' ||
    22 ||[SiteStanford Stanford]           || 10.37.5.0/28                                       || 10.37.5.1/24        || 10.37.5.14/24    ||
    23 ||[SiteClemson Clemson]             || 10.37.5.16/28                                      || 10.37.5.17/24       || 10.37.5.30/24    ||
    24 ||[SiteGeorgiaTech Georgia Tech]    || 10.37.5.32/28                                      || 10.37.5.33/24       || 10.37.5.46/24    ||
    25 ||[SiteIndiana Indiana U.]          || 10.37.5.48/28                                      || 10.37.5.49/24       || 10.37.5.62/24    ||
    26 ||[SitePrinceton Princeton]         || 10.37.5.64/28                                      || 10.37.5.65/24       || 10.37.5.78/24    ||
    27 ||[SiteWashington Washington U.]    || 10.37.5.80/28                                      || 10.37.5.81/24       || 10.37.5.94/24    ||
    28 ||[SiteBbn BBN]                     || 10.37.5.96/28                                      || 10.37.5.97/24       || 10.37.5.110/24   ||
    29 ||[SiteKansasState K-State]         || 10.37.5.112/28                                     || 10.37.5.113/24      || 10.37.5.126/24   ||
    30 ||[SiteWisconsin Wisconsin U.]      || 10.37.5.128/28                                     || 10.37.5.129/24      || 10.37.5.142/24   ||
    31 ||[SiteRutgers Rutgers]             || 10.37.5.144/28                                     || 10.37.5.145/24      || 10.37.5.158/24   ||
    32 ||SiteNlr                           || 192.37.5.192/28                                    || 10.37.5.193/24      || 10.37.5.206/24   ||
    33 ||[wiki:"SiteInternet2" Internet 2] || 192.37.5.208/28                                    || 10.37.5.209/24      || 10.37.5.222/24   ||
    34 
    35 '''Note that these IP addresses are allocated in blocks of /28 for consistency, this ''is not a subnet''. All hosts in the /24 net should be able to ping one another by default.''' For example, a host at Clemson (10.37.5.17) should be able to ping a host at Washington (10.37.5.81).
    36 
    37 This specific IP network (which corresponds to the VLAN) is meant for monitoring and testing of the connection, though host addresses within this IP network may be used in "small" experiments. Other IP networks following the same nomenclature maybe also be used on a given VLAN. Specific experiments may also designate other  addition IP networks on the VLAN for specific use. This scheme lays the groundwork for initial connectivity only, it is expected other IP networks (as well as non-IP networks) will be devised in the future.
    38 
    39 Campuses may assign other sites IPs from their range. This range-by-subnet scheme also allows for campuses to subnet the IP addresses ''not used for connectivity monitoring'' for additional traffic isolation.
    40 
     13 6. NetworkCore             - Topology and configuration of the Internet2 and National !LambdaRail interconnected Backbone OpenFlow Core VLANs.           
    4114
    4215= GENI Layer-2 Connectivity =
    … …  
    154127
    155128= Connectivity IP networks =
     129
     130== Site's IP Ranges ==
     131For initial Connectivity testing, a typical nomenclature is to use a 10.X.X.0/24 net with a VLAN ID encoded into the IP address.  To save time allocating IP addresses the following range-by-subnet scheme can be used for initial connectivity and "path-finding" experiments and configurations. This is particularly useful for multi-site connections, such as the OpenFlow Core VLANs.
     132
     133'''To connect your site with GENI:''' Email [mailto:help@gpo.net]
     134
     135
     136||'''Campus'''                      ||'''(example as VLAN 3705)[[BR]]assigned IP range''' || '''First Host IP''' ||  '''Last Host''' ||
     137||[SiteStanford Stanford]           || 10.37.5.0/28                                       || 10.37.5.1/24        || 10.37.5.14/24    ||
     138||[SiteClemson Clemson]             || 10.37.5.16/28                                      || 10.37.5.17/24       || 10.37.5.30/24    ||
     139||[SiteGeorgiaTech Georgia Tech]    || 10.37.5.32/28                                      || 10.37.5.33/24       || 10.37.5.46/24    ||
     140||[SiteIndiana Indiana U.]          || 10.37.5.48/28                                      || 10.37.5.49/24       || 10.37.5.62/24    ||
     141||[SitePrinceton Princeton]         || 10.37.5.64/28                                      || 10.37.5.65/24       || 10.37.5.78/24    ||
     142||[SiteWashington Washington U.]    || 10.37.5.80/28                                      || 10.37.5.81/24       || 10.37.5.94/24    ||
     143||[SiteBbn BBN]                     || 10.37.5.96/28                                      || 10.37.5.97/24       || 10.37.5.110/24   ||
     144||[SiteKansasState K-State]         || 10.37.5.112/28                                     || 10.37.5.113/24      || 10.37.5.126/24   ||
     145||[SiteWisconsin Wisconsin U.]      || 10.37.5.128/28                                     || 10.37.5.129/24      || 10.37.5.142/24   ||
     146||[SiteRutgers Rutgers]             || 10.37.5.144/28                                     || 10.37.5.145/24      || 10.37.5.158/24   ||
     147||SiteNlr                           || 192.37.5.192/28                                    || 10.37.5.193/24      || 10.37.5.206/24   ||
     148||[wiki:"SiteInternet2" Internet 2] || 192.37.5.208/28                                    || 10.37.5.209/24      || 10.37.5.222/24   ||
     149
     150'''Note that these IP addresses are allocated in blocks of /28 for consistency, this ''is not a subnet''. All hosts in the /24 net should be able to ping one another by default.''' For example, a host at Clemson (10.37.5.17) should be able to ping a host at Washington (10.37.5.81).
     151
     152This specific IP network (which corresponds to the VLAN) is meant for monitoring and testing of the connection, though host addresses within this IP network may be used in "small" experiments. Other IP networks following the same nomenclature maybe also be used on a given VLAN. Specific experiments may also designate other  addition IP networks on the VLAN for specific use. This scheme lays the groundwork for initial connectivity only, it is expected other IP networks (as well as non-IP networks) will be devised in the future.
     153
     154Campuses may assign other sites IPs from their range. This range-by-subnet scheme also allows for campuses to subnet the IP addresses ''not used for connectivity monitoring'' for additional traffic isolation.
     155
    156156
    157157=== net 10.5.46.0 ===