Maximum Payload

What is the maximum payload we can send to a BPEL process?
Our clients want to send 7000 records to a BPEL process, but it fails randomly for heavy payloads.
It gives following error
An unhandled exception has been thrown in the ESB system. The exception reported is: "org.collaxa.thirdparty.apache.wsif.WSIFException: exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message transmission failure, response code: 500
     at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeOperation(WSIFOperation_JaxRpc.java:1874)
     at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeRequestResponseOperation(WSIFOperation_JaxRpc.java:1570)
     at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.executeInputOnlyOperation(WSIFOperation_JaxRpc.java:1193)
     at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(WSIFInvoker.java:927)
     at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:842)
     at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:865)
     at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(OutboundAdapterService.java:231)
     at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(OutboundAdapterService.java:138)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(InitialEventDispatcher.java:411)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:169)
     at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:2010)
     at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1469)
     at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:215)
     at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:139)
     at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:317)
     at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:141)

This issue looks like the request is timing out making the request, meaning the network is not fast enough for this size message.
If you use a different adapter, e.g. JMS. then you can debatch the message.
cheers
James

Similar Messages

BIOS SETTING, need help! MAXIMUM PAYLOAD SIZE? NEO4 PLAT SLI

Hi everyone, this is my first post here, and hope someone will help me out. I've searched the internet, posted on other websites and no one can help me with this question. What does MAXIMUM PAYLOAD SIZE do? What is the correct setting for this? Curruntly I have it at 4096, but what should it be at? Thanks everyone.

Thats a good one (question)... as far as I know it could be similar to the old AGP Aperture Size, but the amount of data doesn't correspond; megabytes vs. kilobytes.
It could be the logical data unit which is carried thru the PCI-E bus in order to feed the PCI-E devices, this is sounds better yet again would be something similar to the AGP Aperture Size: not amount of data being mapped at physical memory, but the size of the data units being transfered.
Hope this helps... try the values to either side and test with a 3d Benchmark, if you see a diference then come back and tell us.
Good Luck.

Proxy Maximum Payload size

Hi ,
What is the maximum size of payload a proxy ( ABAP server/client) can handle in XI? Also send me docs on Proxy Sizing ?
Regards,
Praveen Kumar

Hi,
I don't think there is any limitation of the size of payload.
You can refer to these guides.
SAP XI sizing guide
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/72e2bb90-0301-0010-e883-c390ad8a975a
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/150ac490-0201-0010-0cb3-dee8d5262778
Check this -https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/150ac490-0201-0010-0cb3-dee8d5262778
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/72e2bb90-0301-0010-e883-c390ad8a975a
Here is a presenation from SAP -https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b4f3755a-0401-0010-b6b3-9b65bb7d4503
Check this thread discuss the same
XI SIZING
XI sizing
Check out these links on Sizing. can you also explain, how you managed to make the configurations for so many senders/ receivers. It would be helpful.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/423f5046-0a01-0010-2698-b2dc7c3185f1
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10b54994-f569-2a10-ad8f-cf5c68a9447c
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4dc9381e-0a01-0010-c692-f6bf424b0b94
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70ada5ef-0201-0010-1f8b-c935e444b0ad
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c02b4fc0-be11-2a10-4984-9713585ca128
Regards
Aashish Sinha
PS : reward points if helpful

Maximum input payload size(for an XML file) supported by OSB

Hey Everyone,
I wanted to know, what is the maximum payload size that OSB can handle.
The requirement is to pass XML files as input to OSB and insert the data of the XML files in the oracle staging tables. The OSB will host all the .jca,wsdl, xml, xml schema and other files required to perform the operation.
The hurdle is to understand, what is the maximum XML file size limit, that OSB can allow to pass through without breaking.
I did some test runs and got the following output,
Size of the XML file: OSB successfully read a file of size, 3176kb but failed for a file of size 3922kb, so the OSB breakpoint occurs somewhere between 3-4 MB, as per the test runs.
Range of number of Lines of XML: 102995 to 126787, since OSB was able to consume a file with lines (102995) and size 3176kb but broke for a file with number of lines (126787) and size 3922kb.
Request to please share your views on the test runs regarding the OSB breakpoint and also kindly share the results, if the same test has been performed at your end.
Thank you very much.

Hey Everyone,
I wanted to know, what is the maximum payload size that OSB can handle.
The requirement is to pass XML files as input to OSB and insert the data of the XML files in the oracle staging tables. The OSB will host all the .jca,wsdl, xml, xml schema and other files required to perform the operation.
The hurdle is to understand, what is the maximum XML file size limit, that OSB can allow to pass through without breaking.
I did some test runs and got the following output,
Size of the XML file: OSB successfully read a file of size, 3176kb but failed for a file of size 3922kb, so the OSB breakpoint occurs somewhere between 3-4 MB, as per the test runs.
Range of number of Lines of XML: 102995 to 126787, since OSB was able to consume a file with lines (102995) and size 3176kb but broke for a file with number of lines (126787) and size 3922kb.
Request to please share your views on the test runs regarding the OSB breakpoint and also kindly share the results, if the same test has been performed at your end.
Thank you very much.

Payload Size

Whats the Maximum Payload Size XI can handle?
We are expecting one of our outbound IDOC to a size of 7.37 MB's and we are not sure Whether XI is capable of handling this size?

Whatever the source system, message processing is taking place in the Integration Engine. So payload size comes into picture there only. If once file is picked up, then messages will be in XI pipleine..So you can consider one of parameters.
Some real sceanrios about Huge file processing-
/people/sravya.talanki2/blog/2005/11/29/night-mare-processing-huge-files-in-sap-xi
/people/alessandro.guarneri/blog/2006/03/05/managing-bulky-flat-messages-with-sap-xi-tunneling-once-again--updated
Regards,
Moorthy

Maxium Payload Size...where to find its meaning?

What does Maxium Payload Size mean in the graphics Bios?
Right now it is set to 4096 and wich are the differences among other settings???
Pad

Pad,
I thought that the Whatis.com information complete enough, but I have had a little experience with Serial Data Transitions Protocols.
However, when you looking for information on computer functions, you will find the data is 9 out 10 times in two forms. One is so general in nature that it only gives you small piece of what need to know or if it goes in detail, then it is so narrow scope that you spend hours boiling down all the detailed information and again it only gives you small piece of what need to know. However, over time, you learn to put all of the little pieces of information together, and then you know the subject.
I do not know if this will help will help, but I will try to explain what I learned to day from the Whatis.com. As far, a PCI-E data transmitions are concerned in regards to Maximum Payload Size.
PCI-Express data transmitions are serial data transmitions, it is just that the controller, which is transmitting the data, has multiple serial routes to send the data to the device that is to receive the data. Therefore, to send the data faster the controller breaks the data down into packages of data and sends the packets of data all at the time using its multiple routes.
This is where “Maximum Payload Size” comes in the controller as it divides the data by the number of routes it has to send the data on. If the block of data the controller has to transmit is large each packet send by each route would be long and if the were no limit on the size of the packet the controller can send. Then larger data blocks could tie up transmition of data to the device for long periods. This is fine if there is only one program that needs to communicate with the device, but if and other program need to send a block of data to the device that is more important then its data would not get sent in a timely manor and say its was time dependant the system breaks down and the system crashes.
Therefore, your Maximum Payload size tell controller if the block of data being transmited must be broken a into groups of packets to be sent and before it sends each group of packets. The controller must check and see if the is another block of data with higher priority that need to be sent. If there is the controller switches to sending the higher priority block of data’s groups of packets and is checking priority of data blocks waiting repeated repeatedly until all blocks of data are sent with the data packet groups with highest priority being send first. Then, it is the poor device controller’s job to receive those packets, place them back into individual blocks of data and for the device to use and act upon.
If still confused, Pad just say, so and I will try again.
Roger
When submitting a problem, include a complete list of your system components; include part numbers, all Power Supply Voltages, and their output ratings. It is almost impossible to estimate what your problem is without knowing something about it.

New system, MSI X800XT PCI-E Issues

Hi there!
I just bought a new motherboard, new ram, new cpu and new videocard and was eagerly wanting to set this stuff up.
My system is now as follows:
Motherboard: MSI 925X Neo-54G
CPU: P4 3.40Ghz (1 Mb L2 Cache) (Socket 775)
RAM: 1 GByte DDR2 533
Video Card: MSI RX800 XT-VTD256 (ATI Radeon X800XT PCI-E)
I put everything up and working and installed Windows XP w/ SP2. Installed every driver needed from the motherboard CD, went to ATI's site and downloaded the latest Catalyst Drivers, etc.
After having everything apparently working as it should, I downloaded 3dMark 2005 to see how it went. I had never used the 2005 version before so I wasn't too shocked to see it only got like 3200 points although I was kinda suspicious after seeing some of the tests going at like 1 fps.
I went back to another PC I have at home (a socket 478, P4 3.0Ghz, Asus P4C800 mobo, 1 GByte DDR400 Ram and a GeForce 6800 Ultra). Ran 3dMark 2005 and to my amazement, it got like 4400 points.
Well, double checked everything on the catalyst control panel (nothing really useful there)... then went back to the BIOS setup to investigate what is not working as it should. MSI boards have that nifty Dynamic Overclocking thing and so I turned it on. My BIOS settings are now as following (only listing settings I have doubts on):
DDR2 533 (Dual Channel Mode Enabled)
DRAM Timing Selectable: By SPD
Memory Hole: Disabled
PCI Express Root Port Func: Auto on all 4 ports
PCI-E Compliance Mode: v1.0a
DRAM Data integrity mode: Non-ECC
PCI IDE Busmaster: Enabled (I have a 250GB 8MB SATA HD,fyi)
Init Display First: PCI-E
Maximum Payload Size (PCI-E): 4096
High performance mode: Optimized (Manual is the other option)
Dynamic Overclocking: 5% (0-15% range)
Adjust DDR Frequency: Auto
Auto Detect PCI Clock: Enabled
Spread Spectrum: Disabled
CPU Clock: 200Mhz
CPU Voltage: By CPU default
Memory Voltage: 1.8v
AGP/PCI-E Voltage: 1.5v
Ok, so, can anyone tell me what is wrong (if anything)? I mean, I think this PC should be faster than my other one...
I'm not really interested in overclocking and I am really convinced this hardware should be able to beat my other one easily with default operating status.
Also, I tested this PC's performance with Rome: Total War and it is just as 3dMark had showed, it performs worse than the other pc I mentioned, with the same exact settings.
Any help please?
Regards!

Quote
Originally posted by thegrommit
I'm not familiar with Intel motherboards, but posting your DirectX results might help someone who is work out whether you have all the right drivers installed:
Ok, here goes:
System Information
Time of this report: 10/3/2004, 15:48:43
Machine name: PC2
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_rtm.040803-2158)
Language: English (Regional Setting: Portuguese)
System Manufacturer: INTELR
System Model: AWRDACPI
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: Intel(R) Pentium(R) 4 CPU 3.40GHz (2 CPUs)
Memory: 1024MB RAM
Page File: 138MB used, 2323MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.2180 32bit Unicode
DxDiag Notes
DirectX Files Tab: No problems found.
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Music Tab: No problems found.
Input Tab: No problems found.
Network Tab: No problems found.
DirectX Debug Levels
Direct3D: 0/4 (n/a)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
Display Devices
Card name: RADEON X800 XT
Manufacturer: ATI Technologies Inc.
Chip type: RADEON X800 XT (0x5D57)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_5D57&SUBSYS_03121002&REV_00
Display Memory: 256.0 MB
Current Mode: 1280 x 1024 (32 bit) (85Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: ati2dvag.dll
Driver Version: 6.14.0010.6476 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 8/25/2004 13:29:04, 209408 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: ati2mtag.sys
Mini VDD Date: 8/25/2004 13:28:46, 787456 bytes
Device Identifier: {D7B71EE2-1E17-11CF-FE6A-1823A1C2CB35}
Vendor ID: 0x1002
Device ID: 0x5D57
SubSys ID: 0x03121002
Revision ID: 0x0000
Revision ID: 0x0000
Video Accel: ModeMPEG2_C ModeMPEG2_D
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
DDraw Test Result: Not run
D3D7 Test Result: Not run
D3D8 Test Result: Not run
D3D9 Test Result: Not run
Sound Devices
Description: SB Audigy Audio [D000]
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1102&DEV_0004&SUBSYS_00531102&REV_03
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: e10kx2k.sys
Driver Version: 5.12.0001.0136 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 11/5/2001 13:02:30, 1758336 bytes
Other Files:
Driver Provider: Creative
HW Accel Level: Full
Cap Flags: 0xF5F
Min/Max Sample Rate: 4000, 191999
Static/Strm HW Mix Bufs: 32, 31
Static/Strm HW 3D Bufs: 32, 31
HW Memory: 0
Voice Management: Yes
EAX(tm) 2.0 Listen/Src: Yes, Yes
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: Not run
Sound Capture Devices
Description: SB Audigy Audio [D000]
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: e10kx2k.sys
Driver Version: 5.12.0001.0136 (English)
Driver Attributes: Final Retail
Date and Size: 11/5/2001 13:02:30, 1758336 bytes
Cap Flags: 0x41
Format Flags: 0xFFF
DirectMusic
DLS Path: C:\WINDOWS\SYSTEM32\drivers\GM.DLS
DLS Version: 1.00.0016.0002
Acceleration: Enabled
Ports: SB Audigy DirectMusic Synthesizer [D000], Hardware (Kernel Mode), Output, DLS, Internal, Default Port
SB Audigy Audio [D000], Software (Kernel Mode), Output, DLS, Internal
Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy Synth A [D000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy Sw Synth [D000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy Synth B [D000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy MIDI Port [D000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, External
Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy MIDI Port [D000] [Emulated], Hardware (Not Kernel Mode), Input, No DLS, External
Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal
Registry: OK
Test Result: Not run
DirectPlay Service Providers
DirectPlay8 Modem Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 Serial Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 IPX Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 TCP/IP Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
Internet TCP/IP Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)
IPX Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)
Modem Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)
Serial Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)
DirectPlay Voice Wizard Tests: Full Duplex: Not run, Half Duplex: Not run, Mic: Not run
DirectPlay Test Result: Not run
Registry: OK
DirectPlay Adapters
DirectPlay8 Serial Service Provider: COM1
DirectPlay8 TCP/IP Service Provider: Local Area Connection - IPv4 -
DirectPlay Voice Codecs
Voxware VR12 1.4kbit/s
Voxware SC06 6.4kbit/s
Voxware SC03 3.2kbit/s
MS-PCM 64 kbit/s
MS-ADPCM 32.8 kbit/s
Microsoft GSM 6.10 13 kbit/s
TrueSpeech(TM) 8.6 kbit/s
DirectPlay Lobbyable Apps
Disk & DVD/CD-ROM Drives
Drive: C:
Free Space: 190.3 GB
Total Space: 239.4 GB
File System: NTFS
Model: Maxtor 7Y250M0
Drive: E:
Free Space: 42.0 GB
Total Space: 117.8 GB
File System: FAT32
Model: IC35L120AVV207-0
Drive: F:
Free Space: 28.9 GB
Total Space: 76.3 GB
File System: NTFS
Model: ST380011A
Drive: D:
Model: CREATIVE DVD-ROM DVD6240E
Driver: c:\windows\system32\drivers\cdrom.sys, 5.01.2600.2180 (Portuguese), 8/4/2004 06:59:54, 49536 bytes
Drive: G:
Model: AXV CD/DVD-ROM SCSI CdRom Device
Driver: c:\windows\system32\drivers\cdrom.sys, 5.01.2600.2180 (Portuguese), 8/4/2004 06:59:54, 49536 bytes
System Devices
Name: Intel(R) 82801FB/FBM Ultra ATA Storage Controllers - 266F
Device ID: PCI\VEN_8086&DEV_266F&SUBSYS_70531462&REV_03\3&2411E6FE&0&F9
Driver: C:\WINDOWS\system32\DRIVERS\pciide.sys, 5.01.2600.0000 (English), 8/17/2001 13:51:52, 3328 bytes
Driver: C:\WINDOWS\system32\DRIVERS\pciidex.sys, 5.01.2600.2180 (Portuguese), 8/3/2004 22:59:42, 25088 bytes
Driver: C:\WINDOWS\system32\DRIVERS\atapi.sys, 5.01.2600.2180 (English), 8/3/2004 22:59:44, 95360 bytes
Name: Intel(R) 82801FB/FBM SMBus Controller - 266A
Device ID: PCI\VEN_8086&DEV_266A&SUBSYS_70531462&REV_03\3&2411E6FE&0&FB
Driver: n/a
Name: PCI Device
Device ID: PCI\VEN_8086&DEV_2668&SUBSYS_26688086&REV_03\3&2411E6FE&0&D8
Driver: n/a
Name: Intel(R) 82801FB/FBM PCI Express Root Port - 2660
Device ID: PCI\VEN_8086&DEV_2660&SUBSYS_00000000&REV_03\3&2411E6FE&0&E0
Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 5.01.2600.2180 (English), 8/3/2004 23:07:48, 68224 bytes
Name: Intel(R) 82801FB/FBM USB2 Enhanced Host Controller - 265C
Device ID: PCI\VEN_8086&DEV_265C&SUBSYS_70531462&REV_03\3&2411E6FE&0&EF
Driver: C:\WINDOWS\system32\drivers\usbehci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 26624 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 00:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Driver: C:\WINDOWS\system32\hccoin.dll, 5.01.2600.2180 (English), 8/4/2004 08:56:44, 7168 bytes
Name: Intel(R) 82801FB/FBM USB Universal Host Controller - 265B
Device ID: PCI\VEN_8086&DEV_265B&SUBSYS_70531462&REV_03\3&2411E6FE&0&EB
Driver: C:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 20480 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 00:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Name: Intel(R) 82801FB/FBM USB Universal Host Controller - 265A
Device ID: PCI\VEN_8086&DEV_265A&SUBSYS_70531462&REV_03\3&2411E6FE&0&EA
Driver: C:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 20480 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 00:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Name: Intel(R) 82801FB/FBM USB Universal Host Controller - 2659
Device ID: PCI\VEN_8086&DEV_2659&SUBSYS_70531462&REV_03\3&2411E6FE&0&E9
Driver: C:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 20480 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 00:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Name: Intel(R) 82801FB/FBM USB Universal Host Controller - 2658
Device ID: PCI\VEN_8086&DEV_2658&SUBSYS_70531462&REV_03\3&2411E6FE&0&E8
Driver: C:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 20480 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 00:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Name: Intel(R) 82801FB Ultra ATA Storage Controllers - 2652
Device ID: PCI\VEN_8086&DEV_2652&SUBSYS_70531462&REV_03\3&2411E6FE&0&FA
Driver: C:\WINDOWS\system32\DRIVERS\pciide.sys, 5.01.2600.0000 (English), 8/17/2001 13:51:52, 3328 bytes
Driver: C:\WINDOWS\system32\DRIVERS\pciidex.sys, 5.01.2600.2180 (Portuguese), 8/3/2004 22:59:42, 25088 bytes
Driver: C:\WINDOWS\system32\DRIVERS\atapi.sys, 5.01.2600.2180 (English), 8/3/2004 22:59:44, 95360 bytes
Name: Intel(R) 82801FB LPC Interface Controller - 2640
Device ID: PCI\VEN_8086&DEV_2640&SUBSYS_00000000&REV_03\3&2411E6FE&0&F8
Driver: C:\WINDOWS\system32\DRIVERS\isapnp.sys, 5.01.2600.0000 (English), 8/17/2001 13:58:02, 35840 bytes
Name: Intel(R) 925X PCI Express Root Port - 2585
Device ID: PCI\VEN_8086&DEV_2585&SUBSYS_00000000&REV_04\3&2411E6FE&0&08
Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 5.01.2600.2180 (English), 8/3/2004 23:07:48, 68224 bytes
Name: Intel(R) 925X Memory Controller Hub - 2584
Device ID: PCI\VEN_8086&DEV_2584&SUBSYS_00000000&REV_04\3&2411E6FE&0&00
Driver: n/a
Name: Intel(R) 82801 PCI Bridge - 244E
Device ID: PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_D3\3&2411E6FE&0&F0
Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 5.01.2600.2180 (English), 8/3/2004 23:07:48, 68224 bytes
Name: Intel(R) PRO/100 VE Network Connection
Device ID: PCI\VEN_8086&DEV_1064&SUBSYS_053C1462&REV_03\4&10355354&0&40F0
Driver: C:\WINDOWS\system32\DRIVERS\e100b325.sys, 7.01.0012.0000 (Portuguese), 2/10/2004 07:49:14, 154112 bytes
Driver: C:\WINDOWS\system32\Prounstl.exe, 7.00.0006.0000 (English), 11/21/2003 07:26:42, 118784 bytes
Driver: C:\WINDOWS\system32\e100b325.din, 6/26/2002 22:53:38, 5110 bytes
Driver: C:\WINDOWS\system32\IntelNic.dll, 2.05.0001.0000 (English), 7/27/2003 22:55:40, 24064 bytes
Driver: C:\WINDOWS\system32\e100bmsg.dll, 2/18/2004 09:40:00, 12288 bytes
Name: Broadcom NetXtreme Gigabit Ethernet
Device ID: PCI\VEN_14E4&DEV_1677&SUBSYS_053C1462&REV_01\4&F39E1D8&0&00E0
Driver: n/a
Name: Standard Dual Channel PCI IDE Controller
Device ID: PCI\VEN_1106&DEV_3164&SUBSYS_31641106&REV_06\4&10355354&0&20F0
Driver: C:\WINDOWS\system32\DRIVERS\pciidex.sys, 5.01.2600.2180 (Portuguese), 8/3/2004 22:59:42, 25088 bytes
Driver: C:\WINDOWS\system32\DRIVERS\atapi.sys, 5.01.2600.2180 (English), 8/3/2004 22:59:44, 95360 bytes
Driver: C:\WINDOWS\system32\DRIVERS\pciide.sys, 5.01.2600.0000 (English), 8/17/2001 13:51:52, 3328 bytes
Name: Creative Game Port
Device ID: PCI\VEN_1102&DEV_7003&SUBSYS_00401102&REV_03\4&10355354&0&01F0
Driver: C:\WINDOWS\system32\drivers\gameenum.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:22, 10624 bytes
Name: OHCI Compliant IEEE 1394 Host Controller
Device ID: PCI\VEN_1102&DEV_4001&SUBSYS_00101102&REV_00\4&10355354&0&02F0
Driver: C:\WINDOWS\system32\DRIVERS\ohci1394.sys, 5.01.2600.2180 (English), 8/4/2004 07:10:10, 61056 bytes
Driver: C:\WINDOWS\system32\DRIVERS\1394bus.sys, 5.01.2600.2180 (English), 8/4/2004 07:10:08, 53248 bytes
Driver: C:\WINDOWS\system32\DRIVERS\nic1394.sys, 5.01.2600.2180 (English), 8/4/2004 09:05:44, 61824 bytes
Driver: C:\WINDOWS\system32\DRIVERS\arp1394.sys, 5.01.2600.2180 (English), 8/4/2004 09:05:44, 60800 bytes
Driver: C:\WINDOWS\system32\DRIVERS\enum1394.sys, 5.01.2600.0000 (English), 8/17/2001 14:46:40, 6400 bytes
Name: Creative SB Audigy
Device ID: PCI\VEN_1102&DEV_0004&SUBSYS_00531102&REV_03\4&10355354&0&00F0
Driver: C:\WINDOWS\system32\ksuser.dll, 5.03.2600.2180 (Portuguese), 8/4/2004 00:56:44, 4096 bytes
Driver: C:\WINDOWS\system32\ksproxy.ax, 5.03.2600.2180 (Portuguese), 8/4/2004 00:56:58, 130048 bytes
Driver: C:\WINDOWS\system32\drivers\ks.sys, 5.03.2600.2180 (Portuguese), 8/3/2004 23:15:22, 140928 bytes
Driver: C:\WINDOWS\system32\drivers\drmk.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:00, 60288 bytes
Driver: C:\WINDOWS\system32\drivers\portcls.sys, 5.01.2600.2180 (English), 8/3/2004 23:15:50, 145792 bytes
Driver: C:\WINDOWS\system32\drivers\stream.sys, 5.03.2600.2180 (Portuguese), 8/3/2004 23:08:04, 48640 bytes
Driver: C:\WINDOWS\system32\wdmaud.drv, 5.01.2600.2180 (English), 8/4/2004 00:56:58, 23552 bytes
Driver: C:\WINDOWS\system32\drivers\e10kx2k.sys, 5.12.0001.0136 (English), 11/5/2001 13:02:30, 1758336 bytes
Driver: C:\WINDOWS\system32\drivers\ctoss2k.sys, 5.12.0001.0131 (English), 9/11/2001 13:10:14, 186944 bytes
Driver: C:\WINDOWS\system32\ctdlang.dat, 9/11/2001 13:36:02, 161900 bytes
Driver: C:\WINDOWS\system32\ctstatic.dat, 9/11/2001 13:27:44, 144493 bytes
Driver: C:\WINDOWS\system32\ctdaught.dat, 9/11/2001 13:24:48, 44055 bytes
Driver: C:\WINDOWS\system32\default.ecw, 9/23/1999 00:18:50, 2259067 bytes
Driver: C:\WINDOWS\system32\sfman32.dll, 5.12.0001.0130 (English), 8/17/2001 15:35:44, 36864 bytes
Driver: C:\WINDOWS\system32\a3d.dll, 80.00.0000.0003 (English), 9/11/2001 13:05:52, 49152 bytes
Driver: C:\WINDOWS\system32\ctbas2w.dat, 9/11/2001 13:35:58, 111123 bytes
Driver: C:\WINDOWS\system32\SBAudigy.ico, 8/17/2001 13:42:28, 7406 bytes
Driver: C:\WINDOWS\system32\AUDIGYICON.bmp, 8/17/2001 13:42:08, 1912 bytes
Name: RADEON X800 XT Secondary
Device ID: PCI\VEN_1002&DEV_5D77&SUBSYS_03131002&REV_00\4&2B4A1FD5&0&0108
Driver: C:\WINDOWS\system32\DRIVERS\ati2mtag.sys, 6.14.0010.6476 (Portuguese), 8/25/2004 13:28:46, 787456 bytes
Driver: C:\WINDOWS\system32\ati2dvag.dll, 6.14.0010.6476 (English), 8/25/2004 13:29:04, 209408 bytes
Driver: C:\WINDOWS\system32\ati2cqag.dll, 6.14.0010.0252 (English), 8/25/2004 13:10:20, 237568 bytes
Driver: C:\WINDOWS\system32\Ati2mdxx.exe, 6.14.0010.2494 (English), 8/25/2004 13:27:08, 65536 bytes
Driver: C:\WINDOWS\system32\ati3duag.dll, 6.14.0010.0257 (English), 8/25/2004 13:25:56, 2239328 bytes
Driver: C:\WINDOWS\system32\ativvaxx.dll, 6.14.0001.0029 (English), 8/25/2004 13:15:16, 476928 bytes
Driver: C:\WINDOWS\system32\ATIDDC.DLL, 6.14.0010.0005 (English), 8/25/2004 13:26:32, 81920 bytes
Driver: C:\WINDOWS\system32\atitvo32.dll, 6.14.0010.4100 (English), 8/25/2004 13:12:10, 17408 bytes
Driver: C:\WINDOWS\system32\ativcoxx.dll, 6.13.0010.0005 (English), 11/9/2001 11:01:04, 24064 bytes
Driver: C:\WINDOWS\system32\ati2evxx.exe, 6.14.0010.4105 (English), 8/25/2004 13:26:56, 389120 bytes
Driver: C:\WINDOWS\system32\ati2evxx.dll, 6.14.0010.4105 (English), 8/25/2004 13:27:00, 86016 bytes
Driver: C:\WINDOWS\system32\atipdlxx.dll, 6.14.0010.2491 (English), 8/25/2004 13:27:18, 126976 bytes
Driver: C:\WINDOWS\system32\Oemdspif.dll, 6.14.0001.0010 (English), 8/25/2004 13:27:12, 102400 bytes
Driver: C:\WINDOWS\system32\ati2edxx.dll, 6.14.0010.2494 (English), 8/25/2004 13:27:04, 30720 bytes
Driver: C:\WINDOWS\system32\ATIDEMGR.dll, 1.00.1698.24059 (Portuguese), 8/25/2004 14:22:08, 151552 bytes
Driver: C:\WINDOWS\system32\atioglxx.dll, 6.14.0010.4582 (English), 8/25/2004 13:48:12, 6508544 bytes
Driver: C:\WINDOWS\system32\atiiiexx.dll, 6.14.0010.4003 (English), 8/25/2004 14:40:02, 294912 bytes
Name: RADEON X800 XT
Device ID: PCI\VEN_1002&DEV_5D57&SUBSYS_03121002&REV_00\4&2B4A1FD5&0&0008
Driver: C:\WINDOWS\system32\DRIVERS\ati2mtag.sys, 6.14.0010.6476 (Portuguese), 8/25/2004 13:28:46, 787456 bytes
Driver: C:\WINDOWS\system32\ati2dvag.dll, 6.14.0010.6476 (English), 8/25/2004 13:29:04, 209408 bytes
Driver: C:\WINDOWS\system32\ati2cqag.dll, 6.14.0010.0252 (English), 8/25/2004 13:10:20, 237568 bytes
Driver: C:\WINDOWS\system32\Ati2mdxx.exe, 6.14.0010.2494 (English), 8/25/2004 13:27:08, 65536 bytes
Driver: C:\WINDOWS\system32\ati3duag.dll, 6.14.0010.0257 (English), 8/25/2004 13:25:56, 2239328 bytes
Driver: C:\WINDOWS\system32\ativvaxx.dll, 6.14.0001.0029 (English), 8/25/2004 13:15:16, 476928 bytes
Driver: C:\WINDOWS\system32\ATIDDC.DLL, 6.14.0010.0005 (English), 8/25/2004 13:26:32, 81920 bytes
Driver: C:\WINDOWS\system32\atitvo32.dll, 6.14.0010.4100 (English), 8/25/2004 13:12:10, 17408 bytes
Driver: C:\WINDOWS\system32\ativcoxx.dll, 6.13.0010.0005 (English), 11/9/2001 11:01:04, 24064 bytes
Driver: C:\WINDOWS\system32\ati2evxx.exe, 6.14.0010.4105 (English), 8/25/2004 13:26:56, 389120 bytes
Driver: C:\WINDOWS\system32\ati2evxx.dll, 6.14.0010.4105 (English), 8/25/2004 13:27:00, 86016 bytes
Driver: C:\WINDOWS\system32\atipdlxx.dll, 6.14.0010.2491 (English), 8/25/2004 13:27:18, 126976 bytes
Driver: C:\WINDOWS\system32\Oemdspif.dll, 6.14.0001.0010 (English), 8/25/2004 13:27:12, 102400 bytes
Driver: C:\WINDOWS\system32\ati2edxx.dll, 6.14.0010.2494 (English), 8/25/2004 13:27:04, 30720 bytes
Driver: C:\WINDOWS\system32\ATIDEMGR.dll, 1.00.1698.24059 (Portuguese), 8/25/2004 14:22:08, 151552 bytes
Driver: C:\WINDOWS\system32\atioglxx.dll, 6.14.0010.4582 (English), 8/25/2004 13:48:12, 6508544 bytes
Driver: C:\WINDOWS\system32\atiiiexx.dll, 6.14.0010.4003 (English), 8/25/2004 14:40:02, 294912 bytes
Name: SOJU SCSI Controller
Device ID: PCI\SOJU341\0000
Driver: n/a
Hope anyone can help me out

QinQ MTU

Hello,
we are using the following configuration to a QinQ link in the subinterface to our users:
interface GigabitEthernet0/0/0/3.900 l2transport
description To CUSTOMER - PSEUDOWIRE A
encapsulation default
l2protocol cpsv tunnel
interface TenGigE0/1/0/3.900 l2transport
description To BACKBONE - PSEUDOWIRE A
encapsulation dot1q 900 second-dot1q any
rewrite ingress tag pop 1 symmetric
Everything is working fine and frames with a payload with 1500 bytes is beeing transported. The issue is that
a ethernet frame with a payload of 1500 has a total size of 1518 bytes. I know that IOS XR MTU
concept discard 4 bytes for the ethernet trailer (FCS or CRC). So for Cisco and MTU the original frame size is 1514.
However the frame received in the GigabitEthernet0/0/0/3.900 has a VLAN TAG because we
have a trunk to our customer with multiples VLANS. So the MTU size should be 1518. But if we get the
out of the show interface command:
sh interface GigabitEthernet0/0/0/3.900
Wed Sep 12 12:56:32.130 CEST
GigabitEthernet0/0/0/3.900 is up, line protocol is up
Interface state transitions: 1
Hardware is VLAN sub-interface(s), address is 6c9c.ed09.295f
Description:To CUSTOMER - PSEUDOWIRE A
Layer 2 Transport Mode
MTU 1514 bytes, BW 1000000 Kbit (Max: 1000000 Kbit)
     reliability Unknown, txload Unknown, rxload Unknown
Encapsulation Default,
    Default match
    Ethertype Any, MAC Match src any, dest any
loopback not set,
ARP type ARPA, ARP timeout 04:00:00
Last input never, output never
Last clearing of "show interface" counters never
     1924812905 packets input, 1293208601922 bytes
     3 input drops, 0 queue drops, 0 input errors
     778056641 packets output, 447390756224 bytes
     0 output drops, 0 queue drops, 0 output errors
sh interface TenGigE0/1/0/3.900
Wed Sep 12 13:02:26.173 CEST
TenGigE0/1/0/3.900 is up, line protocol is up
Interface state transitions: 7
Hardware is VLAN sub-interface(s), address is 4055.3968.7d2b
Description: BACKBONE - PSEUDOWIRE UPCT-FTALMO
Layer 2 Transport Mode
MTU 1518 bytes, BW 10000000 Kbit (Max: 10000000 Kbit)
     reliability Unknown, txload Unknown, rxload Unknown
Encapsulation 802.1Q Virtual LAN,
    Outer Match: Dot1Q VLAN 900
    Inner Match: Dot1Q VLAN any
    Ethertype Any, MAC Match src any, dest any
loopback not set,
ARP type ARPA, ARP timeout 04:00:00
Last input never, output never
Last clearing of "show interface" counters never
     778152164 packets input, 450515418508 bytes
     31813 input drops, 0 queue drops, 0 input errors
     1902517045 packets output, 1287687321444 bytes
     308359 output drops, 0 queue drops, 0 output errors
We have a 1514 bytes MTU instead of 1518 bytes in GigabitEthernet0/0/0/3.900 and 1518 bytes instead
1522 (there is two 4 bytes tags). Why frames are working fine?. In the following document explains that
by default the MTU are:
1514 bytes for normal frames
1518 bytes for 802.1Q tagged frames
1522 bytes for QinQ frames
http://www.cisco.com/en/US/docs/routers/asr9000/software/asr9k_r3.9/lxvpn/configuration/guide/lesc39ethi.html#wp1200718
How can we explain the 4 bytes difference?.
Thanks.

Hello Antonio,
Here are numbers which are used for L2 MTU calculation:
"encapsulation untagged” and "encapsulation default” counts 0 tags. >> 1514
“encapsulation dot1q 900 second-dot1q any”. The any keyword used as the innermost tag match does not increase the number of tags in the calculation. This is to ensure consistency with the old style XR VLAN Id semantics. >> 1518
“encapsulation dot1q 900 second-dot1q 900”. No any keyword >> 1522
but for L2VPN we’d use payload MTU to properly transfer our data. The rationale behind the payload MTU calculation is to get the correct maximum payload size of frames that may be carried over an xconnected PW relative to the L2 MTU of the interface.
Let’s take your example:
interface TenGigE0/1/0/3.900 l2transport
description To BACKBONE - PSEUDOWIRE A
encapsulation dot1q 900 second-dot1q any
rewrite ingress tag pop 1 symmetric
sub-l2-mtu = parent-l2-mtu + (4 * encaps-tag-count)
sub-l2-mtu = 1514 + ( 4 * 1 ) = 1518
sub-l2-payload-mtu = sub-l2-mtu – (14 + (4 * (encaps-pop-tags-count – encaps-push-tags-count)))
sub-l2-payload-mtu = 1518 - (14 + (4 * (1 - 0)))= 1500
So we’d be still forwarding 1500b payload.
You should be able to find your xconnect/BD MTU using “show l2vpn xconnect detail” or “show l2vpn bridge-domain detail”.
Regards,
/A

PnP/pci configrations

I have a MSI K8N NERO4 PLATIMIUM board,and in the bios there is a menu called:PnP/pci configrations,and in there,there is a menu called maximum payload size,where i can seclect some numberes 128,256,512,1024,2018,4096,what does that means and what is the best settings,i have a asus Nividia geforce 600gt 256md display card

Hello !!
This has something to to with the PCI-E Buswidth, higher numbers increase PCI-E Performance but can make the system unstable.
If your system works fast and stable let this item alone.
Greetz

PCIe tx engine stops due to trn_tdst_rdy_n is deasserted

HI,
I have implemented DMA engine using Spartan-6 45T PCIe endpoint Block v1.3. It performs DMA write and sends the data to the host memory. When the application is started, after sending few data the Tx Engine stops due to trn_tdst_rdy_n is high.
The application software running on the host system is also halted as it is waiting for the data from the core, but the core has deasserted the trn_tdst_rdy_n. What can be the reason?

It likely is a malformed TLP packet going into the core. Check that the payload size field in the header matches the actual number of data beats, that the transaction doesn't cross 4KB boundaries and you're respecting the maximum payload size of the link.

Need help with bios settings for Neo4 Platinum

Hi. I've checked several guides on bioses and still have questions about my settings. I'm not an overclocker, so I'm looking for stability over anything else (although I don't want my computer to run like a pig . I'll post what I have and the parts of the bios that I'm unsure of. I also have saved pictures of a Cpu-z scan if that helps. Any suggestions are much appreciated!
Here's my stuff:
Motherboard: MSI K8N NEo4 Platinum (MS-7125)
Processor: AMD Athlon 64 3000+ 512K 90nm (Winchester socket 939)
   clock frequency: 1800mhz
   system bus: 2000
   operating mode: 32/64
   voltage: 1.40v
   max temp: 70 degrees C
   thermal power: 89w
   L1 cache: 128KB
   L2 cache: 512KB
   cmos technology: 90nm SOI
   memory controller: 128-bit
Award bios version: 1.9
Installed ram: Micron Crucial Ballistix 512MBx2 (1024MB total) (Crucial
part number BL6464Z402)
   PC3200 400mhz Dual-Channel DDR Dimm (184 pins)
   configuration: 64Meg x 64
   unbuffered/non-ecc
   voltage: 2.8v
   memory timings:   2-2-2-6
Here's my current bios settings (I've only listed sections that contained settings that I was unsure of):
ADVANCED BIOS FEATURES
quick booting: enabled
boot to os/2: no
ioapic function: enabled
mps table version: 1.4
full screen logo display: disabled
seek floppy: enabled
typematic rate setting: enabled
typematic rate: 30
typematic delay: 1000
security option: setup
ADVANCED CHIPSET FEATURES
--->>DRAM CONFIGURATION
timing mode: manual
memclock index value: 200mhz
cas# latency TCL:2
min ras# active time TRAS: 6t
ras# to cas# delay TRCD: 2t
row precharge time TRP: 2t
row to row delay TRRD: auto
row cycle time TRC: 8t
row refresh cyc time TRFC: 11t
read-to-write time TRWT:auto
write recovery time TWR:auto
write to read delay: TWTR:auto
refresh period TREF:auto
user config mode: auto
x bottom of 32-bit [31:24] io: D8
x 1t/2t memory timing: 2t
x read preamble value: 8ns
x async latency value: 9ns
s/w memory hole remapping: disabled
mtrr mapping mode: continuous
PNP/PCI CONFIGURATIONS
primary graphic's adapter: first pcie
resources controlled by: auto (escd)
x irq resources setup: press enter
maximum payload size: 4096
CELL MENU
current cpu clock: 1810 mhz
current ddr clock: 201 mhz
high performance mode: manual
aggressive timing: disabled
dynamic overclocking: disabled
adjust cpu fsb frequency: 200
ht frequency: 5x
ht width: (down arrow 16/up arrow 16)
cpu spread spectrum: disabled
sata spread spectrum: disabled
pcie spread spectrum: disabled
pcie clock: 100 mhz
sse/sse2 instructions: enabled
cool'n'quiet: disabled
adjust cpu vid: startup
extra cpu voltage: by cpu vid
cpu voltage 1.400v
memory voltage: auto
nf4 voltage: 1.50v
Thanks again. xpfshost

I'll do that, thanks. I guess I'm really mostly clueless about the following items:
memclock index value: 200mhz
row cycle time TRC: 8t
row refresh cyc time TRFC: 11t
current cpu clock: 1810 mhz
current ddr clock: 201 mhz
adjust cpu fsb frequency: 200
ht frequency: 5x
ht width: (down arrow 16/up arrow 16
pcie clock: 100 mhz
Do they look OK?? Thanks!
xpfshost
Quote from: Grayone on 19-April-07, 05:13:03
Change your user config mode in dram configuration to manual and change your memory timing to 1T. The 1T setting will speed up your memory slightly.

PXI-5402 timeout error

I am running into an issue with the PXI-5402 Function Generator card in my system. First, here is the configuration of my system:
PXI Chassis (1045)
PXI-8361 controller card (MXI-Express) controlled by a remote computer running the PCI-E controller card.
PXI-5402 Fgen running niFGEN 2.9 software
PXI-4070 DMM
SCXI 1001 w/ multiple modules, controlled through DMM
PC is running Windows XP w/ SP3
The issue I am having is when I try and command an output wave through the NI soft panel, I get a timeout error (-200221). When I run the Self Calibration, I get the same error. The card is showing up in the MAX software with no issues. I can run the Self-Test and it returns successful. I put this 5402 into another system that is using the MXI-4 interface and everything works fine (verified output of Fgen using a DMM). So, this points me to the MXI-Express interface. I read about the PCI-Express compatability software, but it says to only use it if the computer will not boot or if the NI PXI cards do not get recognized in MAX. Should I try to install that software to see if it resolves my issue? I also have a DMM card (PXI-4070) that seems to blue screen Windows XP when trying to read a resistance using the niDMM_32.DLL (it works about 1 time out of 7) (message posted on here a week ago for that). It will read through the test panel in MAX though. I am also controlling an SCXI chassis through the DMM card, and every once in a while the SCXI modules can't be accessed (using my program or MAX). I thought the DMM card was going out, but with the Fgen card doing weird things, I wonder if the PCI-Express bus is causing all of it.
I did look in my computer BIOS settings, and here is what is listed for the PCI-Express bus:
American Megatrends BIOS:
PCI-Express Settings:
Relaxed Ordering - Disabled
Extended Tags - Disabled
Maximum Payload - Auto
Maximum Read Request - Auto
ASPM Support - Disabled
Extended Synch - Disabled
Link Training Retry - 5
Link Training Timeout - 100 (micro seconds)
Unpopulated Links - Keep Link on
Any thoughts on why the card is not working in this system? The fact that it works fine in a system using MXI-4 points to the interface. Should I try the compatibility software to see if that solves it? Any help is greatly appreciated.

There are only 4 interrupts available to the chassis (neglecting message-signalled interrupts, which aren't being used in this case). The 4 interrupts are rotated between slots, so conceptually every fourth slot will have the same interrupt. But there are several factors that affect the rotation so it's not as simple as every-fourth-slot. The rotation will change for each segment in the chassis (there are dividing lines on the 1045 that show where the segments change). There's also a discontinuity where the PCI-PCI bridge is connected on one segment to bridge to the next. The 4 interrupt lines are mapped to IRQs that Windows shows in device manager.
So interrupts will need to be shared if you have more than 4 cards. Depending on your motherboard, those interrupts may also be shared with other things in the system. To change what interrupt is being used means changing slots. Any card in a given slot will always use the same interrupt unless it's a "complex" card, meaning it is multi-function in the PCI sense, or it has a bridge. The rotation of the interrupts will also change if you change the path to the host, meaning changing slots the PCI card is in or changing the PCI card to a PCIe card.
I'm not sure all of that rambling will help with your issue, but it may help as you're trying to reduce/balance the sharing of the interrupts.
- Robert

How to diagnose what is causing occasionally 'hang' of my WRT400N?

We have lost our internet access three times since installing our new WRT400N router. I'm trying to figure out what to do the next time it happens to determine what the problem is.
I have only witnessed this once myself and what I discovered is that the router configuration was no longer accessible through http://192.168.1.1. I also noticed that the LELA software would just hang. When I rebooted the router everything went back to working just fine. The other two times this happened when I wasn't around and my wife rebooted our DSL Modem (ActionTec M1000 with Qwest 7MB DSL). This also fixed the problem.
Our network is wired up so that the router is just a link from the DSL Modem to a Switch. So, if the router goes down the rest of our internal network continues to run just fine (as long as no device needs to get an IP address).
Can anyone point me to a troubleshooting guide that will help figure out the problem next time this happens? Or does it sound like any known issues?
Thanks,
Randy.

Thanks,
I'll definitely try the direct-to-modem thing next time it happens.
Can you tell me what problem changing the MTU would solve? From what I've read, changing this should not be done lightly. It sounds like individual computers should also be updated to match so things run efficiently. Also, it sounds like XBox Live, which I use, requires a minimum of 1365.
Also, I downloaded and ran mturoute.exe in a number of different ways and it seems to be happy with the default setting of 1492, example:
C:\>mturoute.exe www.slashdot.org
* ICMP Fragmentation is not permitted. *
* Maximum payload is 10000 bytes. *
- ICMP payload of 5046 bytes failed..
- ICMP payload of 2569 bytes failed..
+ ICMP payload of 1330 bytes succeeded.
- ICMP payload of 1949 bytes failed..
- ICMP payload of 1639 bytes failed..
- ICMP payload of 1484 bytes failed..
+ ICMP payload of 1407 bytes succeeded.
+ ICMP payload of 1445 bytes succeeded.
+ ICMP payload of 1464 bytes succeeded.
- ICMP payload of 1474 bytes failed..
- ICMP payload of 1469 bytes failed..
- ICMP payload of 1466 bytes failed..
- ICMP payload of 1465 bytes failed..
+ ICMP payload of 1464 bytes succeeded.
+ ICMP payload of 1464 bytes succeeded.
Path MTU: 1492 bytes.
Thanks,
Randy.

Need very high PCIe throughput in your next design? Get help using Xilinx UltraScale, UltraScale+ devices in new White Paper

The Xilinx UltraScale architecture has many features that make implementing high-performance PCIe designs possible. Each of the integrated PCIe blocks in Xilinx Virtex UltraScale+ and Kintex UltraScale+ devices can transfer more than 14Gbytes/s in each direction sustained throughput when configured to operate as PCIe Gen3 x16 or Gen4 x8 port using a 256-byte system Maximum Payload Size and most UltraScale and UltraScale+ devices incorporate more than one such integrated PCIe block.
The transceivers in Xilinx devices based on the UltraScale architecture contain features that allow for very robust operation at these high PCIe data rates. These features include:
Transmitter emphasis/equalization
Auto-adaptive equalization
In addition, most PCIe applications use some type of high-speed memory for data buffering. Here again, Xilinx UltraScale and UltraScale+ devices provide for robust PCIe designs by supporting high-speed DDR4-2400 and DDR4-2666 SDRAM.
A new Xilinx White Paper, “PCI Express for UltraScale Architecture-Based Devices” (WP464), discusses these topics in much more detail.

The Xilinx UltraScale architecture has many features that make implementing high-performance PCIe designs possible. Each of the integrated PCIe blocks in Xilinx Virtex UltraScale+ and Kintex UltraScale+ devices can transfer more than 14Gbytes/s in each direction sustained throughput when configured to operate as PCIe Gen3 x16 or Gen4 x8 port using a 256-byte system Maximum Payload Size and most UltraScale and UltraScale+ devices incorporate more than one such integrated PCIe block.
The transceivers in Xilinx devices based on the UltraScale architecture contain features that allow for very robust operation at these high PCIe data rates. These features include:
Transmitter emphasis/equalization
Auto-adaptive equalization
In addition, most PCIe applications use some type of high-speed memory for data buffering. Here again, Xilinx UltraScale and UltraScale+ devices provide for robust PCIe designs by supporting high-speed DDR4-2400 and DDR4-2666 SDRAM.
A new Xilinx White Paper, “PCI Express for UltraScale Architecture-Based Devices” (WP464), discusses these topics in much more detail.

Site to Site VPN Setup: Error processing payload: Payload ID: 1

Hello,
I am currently getting the error Error processing payload: Payload ID: 1 when attempting to connect an old RV082 (local) to an ASA5520 (in lab). I'm not really sure what is causing this, going through what I've found via Google hasn't really helped much and I was hoping one of you could point me in the right direction.
I've attached a screen grab of the RV configuration and below is an (abridged) copy of the running config from the ASA. Any and all help would be amazing, I'm sure it's something simple that I'm overlooking but I just don;t have the experience with Cisco gear to nail it down.
Thank you very much!
Result of the command: "show running-config"
: Saved
ASA Version 9.0(3)
hostname epath-asa02
domain-name epathlearning.com
enable password hqamp6WHO7djZ5fP encrypted
xlate per-session deny tcp any4 any4
xlate per-session deny tcp any4 any6
xlate per-session deny tcp any6 any4
xlate per-session deny tcp any6 any6
xlate per-session deny udp any4 any4 eq domain
xlate per-session deny udp any4 any6 eq domain
xlate per-session deny udp any6 any4 eq domain
xlate per-session deny udp any6 any6 eq domain
passwd 2KFQnbNIdI.2KYOU encrypted
names
ip local pool REMOTE_VPN_POOL 192.168.5.201-192.168.5.205 mask 255.255.255.0
interface GigabitEthernet0/0
nameif outside
security-level 0
ip address xx.xx.xx.xx 255.255.255.254
interface GigabitEthernet0/1
nameif inside
security-level 100
ip address 192.168.5.1 255.255.255.0
interface GigabitEthernet0/2
nameif storage
security-level 100
ip address 192.168.6.1 255.255.255.0
interface GigabitEthernet0/3
shutdown
no nameif
no security-level
no ip address
interface Management0/0
shutdown
no nameif
no security-level
no ip address
boot system disk0:/asa903-k8.bin
ftp mode passive
clock timezone EST -5
clock summer-time EDT recurring
dns domain-lookup inside
dns server-group DefaultDNS
name-server 192.168.5.4
name-server 8.8.8.8
same-security-traffic permit inter-interface
same-security-traffic permit intra-interface
pager lines 24
logging enable
logging asdm informational
mtu outside 1500
mtu inside 1500
mtu storage 1500
no failover
icmp unreachable rate-limit 1 burst-size 1
icmp permit any outside
icmp permit any inside
asdm image disk0:/asdm-715-100.bin
asdm history enable
arp timeout 14400
no arp permit-nonconnected
nat (inside,inside) source static any any destination static NETWORK_OBJ_192.168.5.200_29 NETWORK_OBJ_192.168.5.200_29 no-proxy-arp route-lookup
nat (inside,outside) source static any any destination static NETWORK_OBJ_192.168.5.200_29 NETWORK_OBJ_192.168.5.200_29 no-proxy-arp route-lookup
nat (inside,outside) source static DMZ_Network DMZ_Network destination static NETWORK_OBJ_192.168.10.0_24 NETWORK_OBJ_192.168.10.0_24 no-proxy-arp route-lookup
access-group outside_access_in in interface outside
route outside 0.0.0.0 0.0.0.0 192.168.1.1 1
timeout xlate 3:00:00
timeout pat-xlate 0:00:30
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
user-identity default-domain LOCAL
aaa authentication telnet console LOCAL
aaa authentication ssh console LOCAL
http server enable
http 192.168.5.0 255.255.255.0 inside
http 0.0.0.0 0.0.0.0 outside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec ikev1 transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac
crypto ipsec ikev1 transform-set ESP-DES-SHA esp-des esp-sha-hmac
crypto ipsec ikev1 transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
crypto ipsec ikev1 transform-set ESP-DES-MD5 esp-des esp-md5-hmac
crypto ipsec ikev1 transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac
crypto ipsec ikev1 transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto ipsec ikev1 transform-set ESP-AES-256-SHA esp-aes-256 esp-sha-hmac
crypto ipsec ikev1 transform-set ESP-AES-128-SHA esp-aes esp-sha-hmac
crypto ipsec ikev1 transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac
crypto ipsec ikev1 transform-set ESP-AES-128-MD5 esp-aes esp-md5-hmac
crypto ipsec ikev1 transform-set ESP-AES-128-SHA-TRANS esp-aes esp-sha-hmac
crypto ipsec ikev1 transform-set ESP-AES-128-SHA-TRANS mode transport
crypto ipsec ikev1 transform-set ESP-DES-SHA-TRANS esp-des esp-sha-hmac
crypto ipsec ikev1 transform-set ESP-DES-SHA-TRANS mode transport
crypto ipsec ikev1 transform-set ESP-AES-192-SHA-TRANS esp-aes-192 esp-sha-hmac
crypto ipsec ikev1 transform-set ESP-AES-192-SHA-TRANS mode transport
crypto ipsec ikev1 transform-set ESP-AES-256-SHA-TRANS esp-aes-256 esp-sha-hmac
crypto ipsec ikev1 transform-set ESP-AES-256-SHA-TRANS mode transport
crypto ipsec ikev1 transform-set ESP-3DES-SHA-TRANS esp-3des esp-sha-hmac
crypto ipsec ikev1 transform-set ESP-3DES-SHA-TRANS mode transport
crypto ipsec ikev1 transform-set ESP-AES-128-MD5-TRANS esp-aes esp-md5-hmac
crypto ipsec ikev1 transform-set ESP-AES-128-MD5-TRANS mode transport
crypto ipsec ikev1 transform-set ESP-AES-192-MD5-TRANS esp-aes-192 esp-md5-hmac
crypto ipsec ikev1 transform-set ESP-AES-192-MD5-TRANS mode transport
crypto ipsec ikev1 transform-set ESP-AES-256-MD5-TRANS esp-aes-256 esp-md5-hmac
crypto ipsec ikev1 transform-set ESP-AES-256-MD5-TRANS mode transport
crypto ipsec ikev1 transform-set ESP-3DES-MD5-TRANS esp-3des esp-md5-hmac
crypto ipsec ikev1 transform-set ESP-3DES-MD5-TRANS mode transport
crypto ipsec ikev1 transform-set ESP-DES-MD5-TRANS esp-des esp-md5-hmac
crypto ipsec ikev1 transform-set ESP-DES-MD5-TRANS mode transport
crypto ipsec ikev2 ipsec-proposal DES
protocol esp encryption des
protocol esp integrity sha-1 md5
crypto ipsec ikev2 ipsec-proposal 3DES
protocol esp encryption 3des
protocol esp integrity sha-1 md5
crypto ipsec ikev2 ipsec-proposal AES
protocol esp encryption aes
protocol esp integrity sha-1 md5
crypto ipsec ikev2 ipsec-proposal AES192
protocol esp encryption aes-192
protocol esp integrity sha-1 md5
crypto ipsec ikev2 ipsec-proposal AES256
protocol esp encryption aes-256
protocol esp integrity sha-1 md5
crypto ipsec security-association pmtu-aging infinite
crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set pfs group1
crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set ikev1 transform-set ESP-AES-128-SHA ESP-AES-192-SHA ESP-AES-256-SHA ESP-3DES-SHA ESP-DES-SHA ESP-AES-128-SHA-TRANS ESP-AES-192-SHA-TRANS ESP-AES-256-SHA-TRANS ESP-3DES-SHA-TRANS ESP-DES-SHA-TRANS
crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set ikev2 ipsec-proposal AES256 AES192 AES 3DES DES
crypto map outside_map 1 match address outside_cryptomap
crypto map outside_map 1 set peer 208.103.76.212
crypto map outside_map 1 set ikev1 transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA ESP-3DES-MD5 ESP-DES-SHA ESP-DES-MD5
crypto map outside_map 1 set ikev2 ipsec-proposal DES 3DES AES AES192 AES256
crypto map outside_map 65535 ipsec-isakmp dynamic SYSTEM_DEFAULT_CRYPTO_MAP
crypto map outside_map interface outside
crypto map inside_map 65535 ipsec-isakmp dynamic SYSTEM_DEFAULT_CRYPTO_MAP
crypto map inside_map interface inside
crypto ca trustpoint _SmartCallHome_ServerCA
crl configure
crypto ca trustpoint ASDM_TrustPoint0
enrollment self
email [email protected]
subject-name CN=xxxxxx
serial-number
ip-address xx.xx.xx.xx
keypair xxxxxxxxxxxxxx
proxy-ldc-issuer
crl configure
crypto ca trustpoint ASDM_TrustPoint1
crl configure
crypto ca trustpoint localtrust
crl configure
crypto ca trustpool policy
crypto ca certificate chain _SmartCallHome_ServerCA
certificate ca 6ecc7aa5a7032009b8cebcf4e952d491
308205ec 308204d4 a0030201 0202106e cc7aa5a7 032009b8 cebcf4e9 52d49130
0d06092a 864886f7 0d010105 05003081 ca310b30 09060355 04061302 55533117
30150603 55040a13 0e566572 69536967 6e2c2049 6e632e31 1f301d06 0355040b
13165665 72695369 676e2054 72757374 204e6574 776f726b 313a3038 06035504
0b133128 63292032 30303620 56657269 5369676e 2c20496e 632e202d 20466f72
20617574 686f7269 7a656420 75736520 6f6e6c79 31453043 06035504 03133c56
65726953 69676e20 436c6173 73203320 5075626c 69632050 72696d61 72792043
65727469 66696361 74696f6e 20417574 686f7269 7479202d 20473530 1e170d31
30303230 38303030 3030305a 170d3230 30323037 32333539 35395a30 81b5310b
30090603 55040613 02555331 17301506 0355040a 130e5665 72695369 676e2c20
496e632e 311f301d 06035504 0b131656 65726953 69676e20 54727573 74204e65
74776f72 6b313b30 39060355 040b1332 5465726d 73206f66 20757365 20617420
68747470 733a2f2f 7777772e 76657269 7369676e 2e636f6d 2f727061 20286329
3130312f 302d0603 55040313 26566572 69536967 6e20436c 61737320 33205365
63757265 20536572 76657220 4341202d 20473330 82012230 0d06092a 864886f7
0d010101 05000382 010f0030 82010a02 82010100 b187841f c20c45f5 bcab2597
a7ada23e 9cbaf6c1 39b88bca c2ac56c6 e5bb658e 444f4dce 6fed094a d4af4e10
9c688b2e 957b899b 13cae234 34c1f35b f3497b62 83488174 d188786c 0253f9bc
7f432657 5833833b 330a17b0 d04e9124 ad867d64 12dc744a 34a11d0a ea961d0b
15fca34b 3bce6388 d0f82d0c 948610ca b69a3dca eb379c00 48358629 5078e845
63cd1941 4ff595ec 7b98d4c4 71b350be 28b38fa0 b9539cf5 ca2c23a9 fd1406e8
18b49ae8 3c6e81fd e4cd3536 b351d369 ec12ba56 6e6f9b57 c58b14e7 0ec79ced
4a546ac9 4dc5bf11 b1ae1c67 81cb4455 33997f24 9b3f5345 7f861af3 3cfa6d7f
81f5b84a d3f58537 1cb5a6d0 09e4187b 384efa0f 02030100 01a38201 df308201
db303406 082b0601 05050701 01042830 26302406 082b0601 05050730 01861868
7474703a 2f2f6f63 73702e76 65726973 69676e2e 636f6d30 12060355 1d130101
ff040830 060101ff 02010030 70060355 1d200469 30673065 060b6086 480186f8
45010717 03305630 2806082b 06010505 07020116 1c687474 70733a2f 2f777777
2e766572 69736967 6e2e636f 6d2f6370 73302a06 082b0601 05050702 02301e1a
1c687474 70733a2f 2f777777 2e766572 69736967 6e2e636f 6d2f7270 61303406
03551d1f 042d302b 3029a027 a0258623 68747470 3a2f2f63 726c2e76 65726973
69676e2e 636f6d2f 70636133 2d67352e 63726c30 0e060355 1d0f0101 ff040403
02010630 6d06082b 06010505 07010c04 61305fa1 5da05b30 59305730 55160969
6d616765 2f676966 3021301f 30070605 2b0e0302 1a04148f e5d31a86 ac8d8e6b
c3cf806a d448182c 7b192e30 25162368 7474703a 2f2f6c6f 676f2e76 65726973
69676e2e 636f6d2f 76736c6f 676f2e67 69663028 0603551d 11042130 1fa41d30
1b311930 17060355 04031310 56657269 5369676e 4d504b49 2d322d36 301d0603
551d0e04 1604140d 445c1653 44c1827e 1d20ab25 f40163d8 be79a530 1f060355
1d230418 30168014 7fd365a7 c2ddecbb f03009f3 4339fa02 af333133 300d0609
2a864886 f70d0101 05050003 82010100 0c8324ef ddc30cd9 589cfe36 b6eb8a80
4bd1a3f7 9df3cc53 ef829ea3 a1e697c1 589d756c e01d1b4c fad1c12d 05c0ea6e
b2227055 d9203340 3307c265 83fa8f43 379bea0e 9a6c70ee f69c803b d937f47a
6decd018 7d494aca 99c71928 a2bed877 24f78526 866d8705 404167d1 273aeddc
481d22cd 0b0b8bbc f4b17bfd b499a8e9 762ae11a 2d876e74 d388dd1e 22c6df16
b62b8214 0a945cf2 50ecafce ff62370d ad65d306 4153ed02 14c8b558 28a1ace0
5becb37f 954afb03 c8ad26db e6667812 4ad99f42 fbe198e6 42839b8f 8f6724e8
6119b5dd cdb50b26 058ec36e c4c875b8 46cfe218 065ea9ae a8819a47 16de0c28
6c2527b9 deb78458 c61f381e a4c4cb66
quit
crypto ca certificate chain ASDM_TrustPoint0
certificate 825b0a53
308202c0 30820229 a0030201 02020482 5b0a5330 0d06092a 864886f7 0d010105
05003072 31143012 06035504 03130b65 70617468 2d617361 3032315a 30120603
55040513 0b4a4d58 31343531 4c314139 30180609 2a864886 f70d0109 08130b36
342e3134 2e38362e 3432302a 06092a86 4886f70d 01090216 1d657061 74682d61
73613032 2e657061 74686c65 61726e69 6e672e63 6f6d301e 170d3134 30323235
32313232 35345a17 0d323430 32323332 31323235 345a3072 31143012 06035504
03130b65 70617468 2d617361 3032315a 30120603 55040513 0b4a4d58 31343531
4c314139 30180609 2a864886 f70d0109 08130b36 342e3134 2e38362e 3432302a
06092a86 4886f70d 01090216 1d657061 74682d61 73613032 2e657061 74686c65
61726e69 6e672e63 6f6d3081 9f300d06 092a8648 86f70d01 01010500 03818d00
30818902 818100b4 95aafc2d e42e5ae5 18bdaebb 757c1062 1a841b50 81fe1416
64477fdb e191122d 8ffd10e5 4e4259fd 3e7ee914 6ab0ef7f 1c6291b4 03400042
ea19a125 401a274e 7e123153 d1a20628 1f870ccd 8b53d059 0948c352 83555659
a6d8ea17 87c25e3e 68d1d910 6157f218 4720733f 533f5784 e740c252 79981a4b
c8cfa891 7469ef02 03010001 a3633061 300f0603 551d1301 01ff0405 30030101
ff300e06 03551d0f 0101ff04 04030201 86301f06 03551d23 04183016 8014b0c8
dcea285f e8e1df05 8cf6558a 44a4875a 32a5301d 0603551d 0e041604 14b0c8dc
ea285fe8 e1df058c f6558a44 a4875a32 a5300d06 092a8648 86f70d01 01050500
03818100 54840176 9be7ba91 9d2dfa04 b3bebc8a 77dac595 4abef8d0 1c277a28
ea3cbbc9 65375d40 788f1349 e996d0a9 2f6923ef b47713a5 e5d2a03e 557b2a0d
c3042510 0c2d2a86 2c20aa31 71c38e1c 1f4227ad c676ffeb 684dfde4 d85a0ee8
06ecc072 fe261a36 58ee85cb c5b16004 adebae26 8105605a c6efed38 0c43acfd
acb0c31d
quit
crypto ikev2 policy 1
encryption aes-256
integrity sha
group 5 2
prf sha
lifetime seconds 86400
crypto ikev2 policy 10
encryption aes-192
integrity sha
group 5 2
prf sha
lifetime seconds 86400
crypto ikev2 policy 20
encryption aes
integrity sha
group 5 2
prf sha
lifetime seconds 86400
crypto ikev2 policy 30
encryption 3des
integrity sha
group 5 2
prf sha
lifetime seconds 86400
crypto ikev2 policy 40
encryption des
integrity sha
group 5 2
prf sha
lifetime seconds 86400
crypto ikev2 enable outside client-services port 443
crypto ikev2 enable inside
crypto ikev2 remote-access trustpoint ASDM_TrustPoint0
crypto ikev1 enable outside
crypto ikev1 enable inside
crypto ikev1 policy 5
authentication pre-share
encryption 3des
hash sha
group 2
lifetime 86400
crypto ikev1 policy 10
authentication pre-share
encryption des
hash sha
group 2
lifetime 86400
telnet 192.168.5.3 255.255.255.255 inside
telnet timeout 5
ssh scopy enable
ssh 192.168.5.0 255.255.255.0 inside
ssh timeout 60
console timeout 0
management-access inside
dhcp-client update dns server both
dhcpd address 192.168.5.100-192.168.5.120 inside
dhcpd dns 192.168.5.4 8.8.4.4 interface inside
dhcpd update dns both override interface inside
dhcpd enable inside
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
ntp server 12.10.191.251 source outside prefer
ssl trust-point ASDM_TrustPoint0 outside
ssl trust-point ASDM_TrustPoint0 inside
webvpn
enable outside
enable inside
anyconnect image disk0:/anyconnect-win-3.1.05152-k9.pkg 1
anyconnect image disk0:/anyconnect-macosx-i386-3.1.05152-k9.pkg 2
anyconnect image disk0:/anyconnect-linux-64-3.1.05152-k9.pkg 3
anyconnect profiles Production_client_profile disk0:/Production_client_profile.xml
anyconnect enable
tunnel-group-list enable
group-policy DefaultRAGroup internal
group-policy DefaultRAGroup attributes
dns-server value 8.8.8.8 8.8.4.4
vpn-tunnel-protocol ikev1 ikev2 l2tp-ipsec
default-domain value
group-policy DfltGrpPolicy attributes
dns-server value 8.8.8.8
vpn-tunnel-protocol ikev1 ikev2 l2tp-ipsec ssl-client ssl-clientless
group-policy GroupPolicy_Production internal
group-policy GroupPolicy_Production attributes
wins-server none
dns-server value 8.8.8.8
vpn-tunnel-protocol ikev2 ssl-client
default-domain value
webvpn
anyconnect profiles value Production_client_profile type user
group-policy GroupPolicy_208.103.76.212 internal
group-policy GroupPolicy_208.103.76.212 attributes
vpn-tunnel-protocol ikev1 ikev2 l2tp-ipsec
username zzzzzzzzzzzzzz password pwoiKxeLmKvYDJf5 encrypted
username root password nSkWYNJFu52Wl56e encrypted
tunnel-group DefaultL2LGroup ipsec-attributes
ikev1 pre-shared-key *****
ikev2 remote-authentication pre-shared-key *****
ikev2 local-authentication pre-shared-key *****
tunnel-group DefaultRAGroup general-attributes
address-pool REMOTE_VPN_POOL
default-group-policy DefaultRAGroup
tunnel-group DefaultRAGroup ipsec-attributes
ikev1 pre-shared-key *****
tunnel-group DefaultRAGroup ppp-attributes
authentication ms-chap-v2
tunnel-group DefaultWEBVPNGroup general-attributes
address-pool REMOTE_VPN_POOL
authorization-server-group LOCAL
dhcp-server 192.168.5.1
authorization-required
tunnel-group Production type remote-access
tunnel-group Production general-attributes
address-pool REMOTE_VPN_POOL
default-group-policy GroupPolicy_Production
strip-realm
strip-group
tunnel-group Production webvpn-attributes
group-alias Production enable
tunnel-group 208.103.xxx.xxx type ipsec-l2l
tunnel-group 208.103.xxx.xxx general-attributes
default-group-policy GroupPolicy_208.103.xxx.xxx
tunnel-group 208.103.xxx.xxx ipsec-attributes
ikev1 pre-shared-key *****
ikev2 remote-authentication pre-shared-key *****
ikev2 local-authentication pre-shared-key *****
class-map inspection_default
match default-inspection-traffic
policy-map type inspect dns preset_dns_map
parameters
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect netbios
inspect rsh
inspect rtsp
inspect skinny
inspect esmtp
inspect sqlnet
inspect sunrpc
inspect tftp
inspect sip
inspect xdmcp
inspect ip-options
inspect icmp
service-policy global_policy global
prompt hostname context
service call-home
call-home reporting anonymous
call-home
contact-email-addr [email protected]
profile CiscoTAC-1
destination address http https://tools.cisco.com/its/service/oddce/services/DDCEService
destination address email [email protected]
destination transport-method http
subscribe-to-alert-group diagnostic
subscribe-to-alert-group environment
subscribe-to-alert-group inventory periodic monthly
subscribe-to-alert-group configuration periodic monthly
subscribe-to-alert-group telemetry periodic daily
Cryptochecksum:9f04ecc9900e65a838e26d06af93a5be
: end

Hello,
It seems you are establishing ikev1 site to site vpn to linksys router.
On linksys router you have configured phase 1 policy to use aes-256, g5 and sha-1 where as non of the ikev1 policy on asa match matchs with it. Configure ikev1 policy to match the parameters on ASA.
crypto ikev1 policy 15
authentication pre-share
encryption aes-256
hash sha
group 5
HTH
"Please rate helpful posts"

Maximum Payload

Similar Messages

Maybe you are looking for