Intel Communities: Message List

Re: Need to change the Maximum Transmission Unit (MTU) size for vPro packets

webadmin@intel.com — Wed, 09 Sep 2009 13:03:55 GMT

Ali,

Is there a more formal process I can go through to officially request the PMTU issue be resolved in the 3.0 firmware version? It would be very helpful in our environment if we could get the 3.0 working.

Thanks!

Re: Need to change the Maximum Transmission Unit (MTU) size for vPro packets

webadmin@intel.com — Mon, 24 Aug 2009 18:46:41 GMT

Ali,

Sorry for the delay in response. Here are the tests I ran. The workstations were already provisioned prior to the test.

Firmware	OS Loaded	vPro Functioning
5.0	OS loaded	No
5.0	No OS loaded (powered off or in BIOS config)	No ??
5.1	OS loaded	Yes
3.0	OS loaded	No
3.0	No OS loaded (powered off or in BIOS config)	Yes

So, it would appear that the new firmware (5.1) is working in our environment!! I didn't, however, get the same results between a 5.0 and 3.0 firmware when the OS wasn't loaded. 3.0 worked but 5.0 didn't. Not sure what that was about. Maybe I did something wrong...I didn't spend too much time troubleshooting.

We would definitely be very appreciative if the issue could be addressed in legacy firmware as well (specifically 3.0 for us). We have a couple hundred AMT 3.0 PC's already in use (vPro currently disabled) as well as some already purchased that have not yet been deployed. It would be great to be able to get vPro working on them as well.

Thanks again for your help!

Re: Need to change the Maximum Transmission Unit (MTU) size for vPro packets

webadmin@intel.com — Wed, 19 Aug 2009 15:13:30 GMT

I am testing with the 5.1 firmware upgrade today. I will also run the test without the OS loaded to see how it behaves.

What about 4.0 versions and below? Will there or is there a firmware update available to include the fix for PMTU filtering? I have quite a few AMT 3.0 PC's out there as well.

Re: Need to change the Maximum Transmission Unit (MTU) size for vPro packets

webadmin@intel.com — Mon, 17 Aug 2009 15:54:14 GMT

Ali,

I do not have the option "Do not respond to ping" or Ping Disabled" set. I double checked that the option was not enabled on one of my test systems by browsing to the HTTPS page and verifying that "Respond to Ping" is selected in the "Network Settings" section.

I will go ahead and get the 5.1.x firmware update and let you know if that makes any difference. If you have any other suggestions, let me know.

Thanks,
Jason

Re: Need to change the Maximum Transmission Unit (MTU) size for vPro packets

webadmin@intel.com — Wed, 29 Jul 2009 15:19:10 GMT

Do you have to change the default MTU size of Windows TCP stack from1500 to lower than 1400 in your environment in order to optimize packet sizes for each medium too?

We do not modify the Windows stack. We have, however, modified the MTU size to be below 1400 in order to optimize some file replication we are doing.

Is it possible to attach a copy of the wireshark capture when managing AMT?

I will have to clear it through our security team, but possibly. I will get back to you.

Also what is the version of AMT and manufacture and model of the vPro system?

We are on firmware version 5.0.1.1111 as supplied by Dell for the Optiplex 960.

Was system provisioned with use of Provisioning Certificate, PID/PPS, or simply in non-secure manner?

PID/PPS

Need to change the Maximum Transmission Unit (MTU) size for vPro packets

webadmin@intel.com — Tue, 19 May 2009 19:22:38 GMT

Hi!

I am trying to configure vPro workstations to be managed by a Landesk server. I am able to get a workstation through the "provisioning" process successfully, however, I am not able to perform any of the remote management functions (from the Landesk server) after it has gone through the provisioning process. What I did discover is that I am able to access the workstation's AMT web page from any workstation/server on the same subnet. However, when trying to access it from a workstation/server on a different subnet, the web page fails to load.

In order to troubleshoot the issue further, I ran a Wireshark capture of the traffic while trying to access the workstation's AMT web page from the Landesk server. I found that the "don't fragment" flag is set on the packets before the traffic dies out. After talking with our network team, I found that the MTU size accross our WAN is set to 1400. We did test allowing the traffic from the vPro workstation to the Landesk server to transmit packets above the 1400 limit and the vPro management works great.

So, long story short, I need to be able to set the MTU size to be less than 1400 bytes in order to keep the packets from fragmenting. This appears to be the only way to get the vPro communication to work across our WAN link.

Any ideas?

Re: Intel Active Management Technology Status: Disabled

webadmin@intel.com — Mon, 24 Mar 2008 11:55:18 GMT

The default password is "admin".

Re: Intel Active Management Technology Status: Disabled

webadmin@intel.com — Tue, 18 Mar 2008 15:20:56 GMT

First off, working with Dell's tech support on this issue was a little tough. I think in total, I talked with three different reps, each

of which had never heard of AMT or didn't know much about it.

So, each new tech I talked with had to pull up the Dell CBT's before

they could talk to me and then each tech had me run through the same steps. We were just trying to get SMB mode to work, so that is where I focused. I confirmed the AMT configs with the Dell rep. I confirmed that the required

ports (16992) were open on my network and that I was using the correct URL to try and access the AMT web interface (http://hostname:16992). I also gave them all of the info that I posted on this thread originally. The final troubleshooting step that I ran was to acquire another Dell 755 and try SMB mode with it. When the 2nd workstation's AMT responded without any problems, they replaced the motherboard in my 1st workstation.

Re: Intel Active Management Technology Status: Disabled

webadmin@intel.com — Wed, 05 Mar 2008 20:54:26 GMT

I ran the test on the 2nd workstation and it came up the same.

Processor test: Passed

LAN test: Passed

OS test: Passed

AMT test: Passed

BIOS test: Did not pass

TPM test: Did not pass

VA test: Passed

Re: Intel Active Management Technology Status: Disabled

webadmin@intel.com — Wed, 05 Mar 2008 19:35:54 GMT

Here are the results from the CTUVPRO tool. AMT is enabled in the MEBx, but still gives the status of disabled when the OS loads.

Chipset test: Passed

Processor test: Passed

LAN test: Passed

OS test: Passed

AMT test: Passed

BIOS test: Did not pass

TPM test: Did not pass

VA test: Passed