Ian,
Dell has sent me a diagnostic tool to run in each server and collect data for them. They want me to reseat all the connectors and boards in the servers.
I will make the tool and test the servers for them when I go to the COLO to install the upgraded RIMAVA 0 /1.
I will forward the mail from Dell, along with the contact information and service request #.. Bruce said he prefers email and will respond. BIOS changes can take from 6 to 8 months to complete.
Paul
From: Lars Kurth [mailto:lars.kurth@xxxxxxxxxx]
Sent: Wednesday, April 01, 2015 10:57 AM
To: wg-test-framework@xxxxxxxxxxxxxxxxxxxx
Cc: Paul George; 'Don Koch'
Subject: Minutes: Xen Project - Allnet sync ... April 1st 2014
== huxelrebe[01] remote BIOS access ==
Don: reconfigured the machine with the issues; could not resolve
Ian: has not touched huxelrebe at all
ACTION Ian: verify whether huxelrebe0 actually works with AMT set-up
* If huxelrebe0 can't be used with AMT, we may need a different approach entirely *
Paul: AMD servers should be in back in the rack with the new motherboard by Friday
Ian: Can you check whether Power ON Always and serial connection works
== oseleta[01] lengthy delay during boot (while still in BIOS) ==
Paul: Opened ticket with DELL, no response
Paul: Contains latest BIOS
Lars: Contacted Linux Foundation and waiting for a DELL contact
Ian: Suggests to give them the URL's with the issue description
ACTION Paul: add URLs to ticket
ACTION Paul to send Lars invoice and Paul to handle it
Lars has been looking at options for MS licensing, which is necessary to allow community members access to the COLO.
Most standard solutions, such as an MSDN subscription, non-profit deals, etc. do not look suitable
Lars has asked the LF for help and Steve Westmoreland is investigating with the LF's MS contact (still open, as the MS contact only just returned from vacation)
ACTION Lars to ping Steve Westmoreland from the LF
#1: Drop windows tests entirely - from a capacity perspective this would be beneficial. But we expect that some AB members would not be happy with it
#2: Escalate to test WG/Advisory Board â in essence until this is resolve we cannot grant any access to the test COLO to people who do not have a personal MSDN license or are covered by any other means (e.g. a Citrix employee)
Ian: several of our boxes have TG3 ethernet card (broadcom NICs)
Ian: Looks like a bug in the TG3 - will raise a ticket
* A broadcom "managerial" contact may help resolve this faster *
