| 217 | ------ |
| 218 | |
| 219 | = Cisco GENI Racks = |
| 220 | **These racks are currently undergoing GENI Acceptance Testing. Please contact [mailto:help@geni.net help@geni.net]if you are interested in their current status.** |
| 221 | |
| 222 | These dual fabric interconnect expandable GENI Racks combine ExoGENI software with Cisco UCS-B and C series servers, UCS and NetApp FAS 2240 storage, and Nexus 3548 dataplane switches. All equipment is physically located in one cabinet, but the rack operates as two separate but related GENI racks. Cisco racks support OpenFlow, virtual topologies, data centers, and multi-site cloud applications. |
| 223 | |
| 224 | |
| 225 | == Cisco GENI Rack Components == |
| 226 | |
| 227 | A Cisco GENI rack includes the following types of systems: |
| 228 | |
| 229 | * Control Node - Server that runs the GENI API server |
| 230 | * Experiment Nodes - Nodes managed by ExoGENI software, to provide boot services, account creation, experimental management, etc. |
| 231 | * Experimenter Storage - Slicable storage for experimenters from the UCS onboard disks and NetApp FAS 2240 storage |
| 232 | * !OpenFlow Switch - Provides internal routing and data plane connectivity to the GENI backbone (layer 2 and layer 3) |
| 233 | * Management Switch - Provides control plane connectivity to the Internet (layer 3) |
| 234 | |
| 235 | Following are the network connections for an Cisco GENI rack: |
| 236 | |
| 237 | [[Image(GENI-OpenGENI-components.jpg)]] |
| 238 | |
| 239 | == Cisco GENI Rack Specifications == |
| 240 | |
| 241 | The main hardware components undergoing acceptance testing are shown in the attached Cisco presentation. A detailed BOM will be added to this page later. |
| 242 | |
| 243 | == Cisco GENI Rack Implementation == |
| 244 | |
| 245 | Configuration details, run-time requirements, and design documents for the Cisco GENI rack are not yet available. |
| 246 | |
| 247 | == Cisco GENI Monitoring == |
| 248 | |
| 249 | Development is taking place to meet [wiki:GeniRacks#D.MonitoringRequirements monitoring requirements] by implementing [wiki:OperationalMonitoring GENI Operational Monitoring]. GENI monitoring is not yet available for the system undergoing acceptance testing. |
| 250 | |
| 251 | |
| 252 | == Cisco GENI Site Requirements == |
| 253 | |
| 254 | Cisco GENI racks have the following site requirements: |
| 255 | * Network Setup - Define how the rack will connect to the Internet and to the GENI backbones. Ex Regional connections, connection speed, VLANs to be used, etc. |
| 256 | * Address assignment for rack components - Define which address, subnet mask, routing is to be configured for the rack components. |
| 257 | * Power requirements - based on site requirements |
| 258 | * Administrative accounts - Setup of site administrator account that will be created on the all rack devices. |
| 259 | * Delivery logistics - Details for ''where'' the rack is to be delivered, ''who'' will accept the delivers, and ''when'' the delivery will take place. Also covers any physical restrictions for the rack delivery. |