Links Between Aggregates

1. Links Between Aggregates Both the compute AM and the network AM advertise this link. Each side must know the exact URN of the interface and interface-vlan of the other side. Compute Aggregate 1 Local DS Interface on the node (may be a VM) Network Aggregate AM Node 1 Switch Local DS Node 2 egress interface from rack to the outside world. Ingress/egress are from the point of view of traffic going from Compute Aggregate 1 to 2. Switch Node 3 ingress interface into the network aggregate Compute Aggregate 2 If there are transit networks on this path that do not run GENI monitoring, they are either omitted or expressed as an L2 (layer 2) path. Transit networks that do run GENI monitoring will appear as link endpoints. Compute Aggregate 1 must advertise this link. We omit the physical port on the switch to which the node is directly connected. egress interface from the network aggregate This switch connects the rack to the outside world. Rack AMs such as this compute AM must advertise this switch as a node so that we have a place to put its interfaces and interface-vlans. The network AM advertises this link. It is strongly encouraged to include an L2path giving the details of the path between the ingress and egress interfaces. = endpoint of a link represented by an interfacevlan, which must then reference a valid interface. The vlan must be the same on both sides of a link. Both interface and interfacevlan are needed because most switches can supply more statistics for interfaces than for interfacevlans, but a link is really the combination of an interface and a vlan. Without the vlan, you would not be able to trace where the link goes. Only dataplane links are reported, i.e., links that are part of an experiment and thus can carry experiment traffic. Endpoints of such links are not usually reachable from the arbitrary places on the Internet, in contrast to the control plane.

2. Multiple Links to the Compute Aggregate All links to destinations outside of the rack should be represented. Compute Aggregate 2 Switch CA1 must advertise these links. We omit the physical ports on the switch to which the nodes are directly connected. Network Aggregate 1 CA1 is still expected to advertise this link, even though there is no reciprocal advertisement from the campus side. CA1 must create a URN representing the interface and interfacevlan for the campus endpoint, since these are required to represent the link. Local DS Link Interface-VLAN Compute Aggregate 1 (CA1) Local DS Network Aggregate 2 Switch AM Node 1 Local DS Switch Node 2 Switch Campus Network not running GENI monitoring Compute Aggregate 3 Network Aggregate 3 Node 3 Local DS

3. Links Internal to a Rack There is no need for a dummy node to represent these switches because they do not terminate one of the link endpoints. Interface on this node Link Interface-VLAN Compute AM optionally advertises this link Compute Aggregate Local DS Interface on this node AM Node 1 Representing these rack-internal links is optional. GENI network operators will probably not delve into the innards of a rack to diagnose a problem. Rack admins, however, may find these links useful. Nodes and their associated slivers must be advertised, though. This also applies to the previous slides. Virtual Switch Switch Node 2 Node 3