[Wg-test-framework] huxelrebe AMT web access

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

So, I have been playing with huxelrebe[01].  I still have a problem,
I'm afraid.  The situation is as follows:

 * I have configured the DHCP server to issue fixed IP addresses to
   each of the four relevant MAC addresses.  (I have not set up any
   DNS or hosts file entries.)  The addresses are 172.16.144.238-0241.
   (I have reconfigured the DHCP server pool to start in 172.16.145
   to avoid clashes.)

 * I can successfully connect to the VNC server on what I have
   described (in the dhcpd.conf) as huxelrebe[01]-amt, using these
   runes
      xvnc4viewer -AutoSelect=0 -PreferredEncoding=hextile localhost:5900
      xvnc4viewer -AutoSelect=0 -PreferredEncoding=hextile localhost:5901
   where those are port forwards made with
      ssh -L 5900:172.16.144.240:5900 -L 5901:172.16.144.241:5900 
root@xxxxxxxxxxxxxxxxxx

   (There seems to be an inactivity timeout, but otherwise these
   connections are reliable.)

 * However, I cannot access the AMT web screens.  The amt.txt provided
   by Don says:

       AMT access is done via web access to:
         http://<machine-IP>:16882/
         login ID default is: admin
         Note: connection from the machine in question may not work.

   Just to check, I used telnet from newcastle:

     root@newcastle:~# telnet 172.16.144.240 16882
     Trying 172.16.144.240...
     telnet: Unable to connect to remote host: Connection refused
     root@newcastle:~# telnet 172.16.144.241 16882
     Trying 172.16.144.241...
     [ long pause ]
     telnet: Unable to connect to remote host: Connection timed out

   I have tried this both (i) with the machine in the BIOS screen (as
   seen in VNC) and (ii) with the machine booted into the OS install
   which Don left on it.

   And, just in case, on the IP addresses allocated by DHCP to the
   host operating system:

     root@newcastle:~# telnet 172.16.144.238 16882
     Trying 172.16.144.238...
     telnet: Unable to connect to remote host: Connection refused
     root@newcastle:~# telnet 172.16.144.239 16882
     Trying 172.16.144.239...
     [ a pause ]
     [telnet: Unable to connect to remote host: No route to host
     [ ^ normally means the host is not responding to ARP ]

These different behaviours suggest that the AMT is not set up
identically on the two boxes.  This is one reason why I wanted to go
through the AMT web configuration screens to check what they said.


I would like to resolve these problems before trying to put the
machines into service.  I particular, I would like to be able to
review the AMT configuration via the web admin.

Thanks,
Ian.

_______________________________________________
Wg-test-framework mailing list
Wg-test-framework@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/wg-test-framework