Nfc27-40-config

From NetFPGAWiki

NetFPGA Group,

Adam and I connected the rest of the Gigabit Ethernet ports { eth2, nf2c0, .. nfc3 } on twelve of the NetFPGA Cluster machines nfc{27..40}. We now have eight of the NetFPGA cluster machines (nfc29..36) fully connected to a full 48-port GigE switch (nfcSW4) and four machines (nfc35..40) fully connected to ports of the HP ProCurve (gates-sw-0-3, bank D) switch.

  Details of of the physical topology are below:

nfc29 .. 36 : connected to nfcsw4

 nfc29 - sw4port : cable color
     nf2c0 - 1  : blue
     nf2c1 - 2  : green
     nf2c2 - 3  : yellow
     nf2c3 - 4  : red
     eth2 - 5  : gray
 nfc30
     nf2c0 - 6 : blue
       ...
    (skip port 21..24)
  nfc33 -
      nf2c0 - 25 : blue
      ...
  nfc36
      ..
      eth2 - 44

on HP gates-sw-0-3 : Block D nfc37

   nf2c0 - D1 : blue
      ...
   nf2c3 - D4  : red
   eth2 - D5
 (skip 1 port)

nfc38

   nf2c0 - D7
     ...

nfc40

   eth2 - D23

All of the management ports (eth1) remain connected to internal Stanford network and are on-line as (nfcM1..40)

eth1 control ports of nfc29 .. 36

 connected directly to HP Procurve
  gates-sw-0-3 ports e1..e12

nfc37

The next step is to configure VLANs on nfcSW4 to re-test the loopback tests for nfc29..36

After that, we can migrate users of the nf-test machines to the nfc machines and use the VLANs to create a virtual topology on nfcSW4 suitable for each user.

We also talked to Charlie about access to the gates-sw switch. He will provide us mangement access to configure VLANs on the HP ProCurve test for nfc37..40

-- John W. Lockwood