Aip-ssm-10 cplane error

Hello,
I have problem with my IPS module in ASA5510. After central power failure the module stopped work.
Status of module is  "Unresponsive" (over show module command). All attempts to get it live ended with this status.
I tried "hw-module module 1 reset", "hw-module module 1 recover", replace and insert module with reload of appliance, but no success.
During this tests I set  "debug cplane 255" and saw this messages:
cp_connect: Connecting to card 1, socket 7, port 7000
cp_connect: Error - cp_connect() returned -1
cp_check_connection: handle -1, conflicts with connection 1 (-1)
cp_check_connection: handle -1, conflicts with connection 2 (-1)
cp_check_connection: handle -1, conflicts with connection 3 (-1)
cp_update_connection: Error updating connection_id 0
Do you know anybody what it means? I tried to find any information on the web about it, but no success
Unfortunately, this device isn't already under contract, so I cannot open the case.
I cannot reconcile with the idea that it is a hardware failure and module is dead.
Thanks for any advice.
Radek

Either your module is sick or the backplane on your 5510 has problems.
Do you have another 5500 chassis to put this module into to test?
- Bob

Similar Messages

  • Configuring SNMP Trap receiver on AIP-SSM sensor

    I receive the following error message from my ASA5520 firewall when attempting to forward SNMP traps from my AIP-SSM20 sensor to a server on my Inside interface that is configured to receive SNMP traps:
    ASA-4-418001: Through-the-device packet to/from management-only network is denied: udp src management: 10.3.21.2/32768 dst Inside: PPC0ES/162
    Can I reconfigure the management IP address of the AIP-SSM sensor to connect to the Inside interface instead of the management vlan or does my SNMP server have to reside on the management vlan with the sensor?

    Hi Subodh,
    Yes, the AIP-SSM can operate in either inline (IPS) or promiscuous (IDS) mode. I would recommend you start by reviewing the following config guide, which shows you how to configure the ASA to pass traffic to the SSM for inspection:
    http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00807335ca.shtml
    If you have any other specific questions, feel free to post back.
    Hope that helps.
    -Mike

  • Upgrade AIP SSM with Signature Engine 4 file

    When I tried to upload Signature Engine 4 file (IPS-engine-E4-req-7.0-2.pkg),  using FTP server both by CLI and IDM, to new AIP SSM sensor, I got the following  error message:
    Cannot upgrade software on the sensor - socket error:110.
    When I tried to do the same by using these steps: IDM --> Configuration  --> Sensor Management --> Update Sensor --> choose Update is located on  this client --> choose the "IPS-K9-7.0-2-E4.pkg" file --> hit the "Update  Sensor" button, I got the following error message
    The current signature level is S480.The current signature level must be  less than s480 for this package to install.
    Here is the output for sh ver command
    AIP_SSM# sh version
    Application Partition:
    Cisco Intrusion Prevention System, Version 7.0(2)E4
    Host:
        Realm Keys          key1.0
    Signature Definition:
        Signature Update    S480.0                   2010-03-24
    OS Version:             2.4.30-IDS-smp-bigphys
    Platform:               ASA-SSM-10
    Serial Number:          JAF1514BAHS
    Licensed, expires:      07-Jun-2012 UTC
    Sensor up-time is 21 days.
    Using 695943168 out of 1032495104 bytes of available memory (67% usage)
    system is using 17.4M out of 38.5M bytes of available disk space (45% usage)
    application-data is using 45.4M out of 166.8M bytes of available disk space (29% usage)
    boot is using 41.6M out of 68.6M bytes of available disk space (64% usage)
    application-log is using 123.5M out of 513.0M bytes of available disk space (24% usage)
    MainApp            B-BEAU_2009_OCT_15_08_07_7_0_1_111   (Ipsbuild)   2009-10-15T08:09:06-0500   Running
    AnalysisEngine     BE-BEAU_E4_2010_MAR_25_02_09_7_0_2   (Ipsbuild)   2010-03-25T02:11:05-0500   Running
    CollaborationApp   B-BEAU_2009_OCT_15_08_07_7_0_1_111   (Ipsbuild)   2009-10-15T08:09:06-0500   Running
    CLI                B-BEAU_2009_OCT_15_08_07_7_0_1_111   (Ipsbuild)   2009-10-15T08:09:06-0500
    Upgrade History:
      IPS-K9-7.0-2-E4   02:00:07 UTC Thu Mar 25 2010
    Recovery Partition Version 1.1 - 7.0(2)E4
    Host Certificate Valid from: 30-May-2011 to 30-May-2013
    Any idea what could be the problem?
    Regards,

    Based on your show version, you already have E4, what is it that you are trying to do?
    Mike

  • Remote Connectivity Issues to AIP-SSM-10

    Hi,
    I have a ASA-5520 with AIP-SSM Module in it. I have done the basic "setup" on the module and assigned it an IP address. I am using IME to connect to the IPS module. The ASA-IPS is at a remote location and has a private IP address. I have a linux server in the same subnet as the IPS IP address. I am connecting to that server remotely through SSH and doing port forwarding to connect to IPS IP address. When I start IME and connect to the locally forwarded port it connects to my IPS module perfactly fine. Please see the attached screen capture "IME_IPS_Error-1.gif" and the column where it says "event status : connected". So far so good, now I click on "configuration" tab and I get an error, please see the "IME_IPS_Error-2.gif" for the error detail. Can anyone send me some pointers to resolve this issue?
    Thanks

    I was able to resolve the issue. Earlier (when I had trouble) I was doing a port forwarding as localhost:10031=>IPS:443 and IME was connecting to localhost:10031. So I was getting to the IPS/IME home page and the device status was connected but when I clicked on "Configuration" tab I got error.
    To resolve the issue I did the port forwarding as follows:
    127.0.0.102:443=>IPS:443 and then IME was connecting to 127.0.0.102:443 and everything worked fine. Looks like earlier when I clicked on "Configuration" it tried/redirected to connect to localhost:443 intead of localhost:10031. I have attached the network diagram and the screen captures of the resolution.

  • IPS Labs using AIP SSM 10

    Hi,
    Can anybody send me a lab with a scenario for IPS using AIP SSM 10 and and if they could be for both CLI as well as by using ASDM. Also, when I was trying to access IPS using ASDM, I was getting an error message "Error connecting to sensor. Failed to load sensor-Error getting config data from following modules analysisEngine signatureDefinition networkAccess host". Can anybody please give me a solution for it.
    Thanks.

    Cisco had orginally planned to add a "keep alive" signature to 6.0. but that feature got dropped. The intent was to fire off a signature every few mins as long as the sensor was seeing valid traffic. The absence of seeing this signature should trigger some attention to a downed sensor.
    You can write a custom sig, but you have to be able to detect the loss of that event to be of value.

  • AIP-SSM module hung

    I have recently confgured my AIP-SSM-20 module in my firewalls (ASA 5540) which are configured in HA(Active/Standby).This implementation i have done on 13th June. It was working fine.
    Now, i have observerd that the AIP-SSM-20 module in the primary firewall had gone to unresponsive state.
    Below is the status of show module and show failover command.
    FW1-5540# sh module
    Mod Card Type                                    Model              Serial No.
      0 ASA 5540 Adaptive Security Appliance         ASA5540            JMX1234L11F
      1 ASA 5500 Series Security Services Module-20  ASA-SSM-20         JAF1341ADPS
    Mod MAC Address Range                 Hw Version   Fw Version   Sw Version
      0 0021.d871.77ab to 0021.d871.77af  2.0          1.0(11)4     8.0(3)6
      1 0023.ebf6.11ce to 0023.ebf6.11ce  1.0          1.0(11)5     6.2(2)E4
    Mod SSM Application Name           Status           SSM Application Version
      1 IPS                            Not Applicable   6.2(2)E4
    Mod Status             Data Plane Status     Compatibility
      0 Up Sys             Not Applicable
      1 Unresponsive       Not Applicable
    FW1-5540# sh failover
    Failover On
    Failover unit Primary
    Failover LAN Interface: FAILOVER GigabitEthernet0/2 (up)
    Unit Poll frequency 1 seconds, holdtime 15 seconds
    Interface Poll frequency 5 seconds, holdtime 25 seconds
    Interface Policy 1
    Monitored Interfaces 3 of 250 maximum
    Version: Ours 8.0(3)6, Mate 8.0(3)6
    Last Failover at: 09:06:14 UTC Jun 15 2010
            This host:
                    This host: Primary - Failed
                    Active time: 191436 (sec)
                    slot 0: ASA5540 hw/sw rev (2.0/8.0(3)6) status (Up Sys)
                      Interface DMZ_LAN (10.192.153.13): Normal (Waiting)
                      Interface INTRANET (10.192.154.13): Normal (Waiting)
                      Interface management (0.0.0.0): Link Down (Waiting)
                    slot 1: ASA-SSM-20 hw/sw rev (1.0/6.2(2)E4) status (Unresponsive/Down)
                      IPS, 6.2(2)E4, Not Applicable
            Other host: Secondary - Active
                    Active time: 192692 (sec)
                    slot 0: ASA5540 hw/sw rev (2.0/8.0(3)6) status (Up Sys)
                      Interface DMZ_LAN (10.192.153.5): Unknown (Waiting)
                      Interface INTRANET (10.192.154.5): Unknown (Waiting)
                      Interface management (0.0.0.0): Unknown (Waiting)
                    slot 1: ASA-SSM-20 hw/sw rev (1.0/7.0(2)E4) status (Up/Up)
                      IPS, 7.0(2)E4, Up
    Stateful Failover Logical Update Statistics
            Link : Unconfigured.
    I have tried using the
    hw-module module 1 reset
    to reset the IPS module but the status is always unresponsive.
    Its production environment where i cannnot expirement much. Ned help to rectify the problem.

    Hi Scott, 
    I have almost same problem of sbgcsd in my customer. I'm deploying two ASA-5512 in failover configuration. One day, after almost 2 months testing project in a lab, when we install in customer's datacenter the systems presented following errors:
      ciscoasa2(config)# failover
            Detected an Active mate
      ciscoasa2# Mate NOT PRESENT card in slot 1 is different from mine IPS5512
    I tried to discover what was happened with IPS modulo, then I saw error in IPS status: "Unresponsive".
      ciscoasa2# sh module ips
      Mod  Card Type                                    Model              Serial No.
       ips Unknown                                      N/A                FCH1712J7UL
      Mod  MAC Address Range                 Hw Version   Fw Version   Sw Version
       ips 7cad.746f.8796 to 7cad.746f.8796  N/A          N/A 
      Mod  SSM Application Name           Status           SSM Application Version
       ips Unknown                        No Image Present Not Applicable  
      Mod  Status             Data Plane Status     Compatibility
       ips Unresponsive       Not Applicable 
      Mod  License Name   License Status  Time Remaining
       ips IPS Module     Disabled        perpetual
    According with Cisco Foruns I tried to "Reloading, Shutting Down, Resetting, and Recovering AIP-SSM" (*) using "hw-module module " command. But unfortunatelly ASA didn't accept this command. See below:
      ciscoasa2# hw-module module 1 reload
                 ^
      ERROR: % Invalid input detected at '^' marker
    What happened with this command (hw-module) ? Maybe is a problem in Software version ? When I entered "sh flash" command I saw that didn't exist any software for AIP-SMM module:
      ciscoasa2# sh flash
      --#--  --length--  -----date/time------  path
       11  4096        Sep 12 2013 13:56:54  log
       21  4096        Sep 12 2013 13:57:10  crypto_archive
      100  0           Sep 12 2013 13:57:10  nat_ident_migrate
       22  4096        Sep 12 2013 13:57:10  coredumpinfo
       23  59          Sep 12 2013 13:57:10  coredumpinfo/coredump.cfg
      101  34523136    Sep 12 2013 14:00:14  asa861-2-smp-k8.bin
      102  17851400    Sep 12 2013 14:04:36  asdm-66114.bin
      103  38191104    Apr 24 2014 12:59:58  asa912-smp-k8.bin
      104  6867        Apr 24 2014 13:01:20  startup-config-jcl.txt
      105  24095116    Jun 17 2014 14:54:14  asdm-721.bi
    But another ASA (#1) have image:
    ciscoasa1# sh flash
    --#--  --length--  -----date/time------  path
       11  4096        Sep 10 2013 06:42:56  log
       21  4096        Apr 17 2014 03:13:12  crypto_archive
      123  5276864     Apr 17 2014 03:13:12  crypto_archive/crypto_eng0_arch_1.bin
      110  0           Sep 10 2013 06:43:12  nat_ident_migrate
       22  4096        Sep 10 2013 06:43:12  coredumpinfo
       23  59          Sep 10 2013 06:43:12  coredumpinfo/coredump.cfg
      111  34523136    Sep 10 2013 06:44:24  asa861-2-smp-k8.bin
      112  42637312    Sep 10 2013 06:45:46  IPS-SSP_5512-K9-sys-1.1-a-7.1-4-E4.aip <===
    But I am not sure if this image is really the right image do AIP-SSM in ASA#2. But anyway I copy (through a simple TFTP server) from ASA#1 to ASA#2 , but after this, the same problem ramained ! 
    Because I didn't applied the Failover condition to system. 
    What can I do now ?
    Thank you very much in advance.
    Leonardo_Melo.(CCAI-JCL-Brazil).

  • Problems with license upgrade on AIP-SSM

    Hi guys:
    I have a problem with my AIP-SSM, recently I download the latest license and I need to install in my AIP but when I try to do this I receive this error:
    "errSystemError-idsPackageMgr: digital signature of the update file was not valid, use CCO to replace corrupted file"
    So I download the license again, because maybe was corrupted, but I receive the same error at the time I want to install it.
    Does anybody knows what this error means?
    Regards

    It sounds like you are attempting to install a .lic license-key file via the Update Sensor section (which is used for software upgrades/updates instead). If you are trying to install a .lic license-key file, you can do that from IDM or IME's Configuration > Sensor Management > Licensing section. Ensure the Update From: option is set to License File, then click the Browse Local… button and locate/select the .lic license-key file on your local client machine. Finally, click the Update License button to upload and install the license-key file onto the sensor.
    If you try to install a .lic license-key file via the Update Sensor section, then you will encounter the error message you noted.

  • Failure to Upgrade the software of my AIP-SSM-20

    Dear all,
    I have failed to upgrade the software of my AIP-SSM-20 on the ASA. The AIP-SSM-20 had an Image of version IPS-K9-5.1-7-E1.pkg and I tried to upgrade it to IPS-K9-6.1-1-E2.pkg but after the upgrade the AIP-SSM-20 became unusable. I can no longer log on  to the IPS Module from the ASA. When I initiated a connection to the module with session 1 command, the systems says card in slot 1 did not respond to system request. I decided to restored the system image from the ASA by using the hw-module module 1 recover configure and hw-module module 1 recover boot commands but has so far failed.When  I issued the command hw-module module 1 boot command, the status of the IPS shows recover and would be in that state even for days.And my TFTP server shows that it is transfering the images to the IPS.
    I don't know where I have gone wrong and I would be very happy if somebody can give me a procedure that would help me to re-image the software of the IPS.
    Any help would be highly appreciated.
    Claude Fozao

    Halijen has already send you a link to reimage,let me briefly answer what a system image and upgrade files are and the difference between them
    The System Image files are meant to be used only when a complete erasing of the sensor's image is needed.  This is generally because the installed files were corrupted, or so old that it would be easier to start over and make it look like it came from the factory; than to use the standard "upgrade" files.So in case you are doing reimaging than use .img files which are system reimage files
    In more than 90% of the cases, most customers will want to "upgrade" rather than do a System Image.  The "upgrade" is done from within the sensor itself, and will both load the higher version as well as convert your current configuration to work with the newer version.it uses .pkg files
    A usual poblem with the System Re-imaging process is that the card winds up in a boot loop because of an error.  When ROMMON detects an error it reboots and tries the same steps again which usually winds up with the same error which causes a reboot, etc.....
    So determining if the card is in a reboot loop, and what the error is would be the next step in your debugging process.
    Execute "debug module-boot".  Enter "hw-module module 1 recover stop".   Wait for a few minutes, and then enter "hw-module module 1 recover boot".
    The output from ROMMON on the SSM will be seen on your ASA connection.Look at the configuration being passed to the SSM's ROMMON and look for any bad entries.Watch to see if it able to download the System Image file, or if it continuously reboots.
    If it continuously reboots, then look to see what error message is seen just prior to the reboot.
    Some common problems:
    1) Typos in IP address, gateway, tftp server IP, or system image filename.
    2) If the tftp server is on the same subnet as the SSM's IP Address, then try leaving the Gateway address blank since it is not needed.
    3) Remember that the IP Address is for the external interface of the SSM.  So be sure you are using an address that is applicable for the network where you are pluggin in the SSM's external interface.
    4) If the TFTP Server is on another subnet, then be sure there is a route to the other network.  If having to route back through the ASA, then ensure that the ASA will allow TFTP packets to pass through the ASA.  (The ASA could wind up blocking the TFTP packets depending on the ASA configuration)
    5) Be sure the file can be downloaded from the TFTP server.  Check the file permissions, and the directory where the file is located.   From your desktop try to downlaod the file from the tftp server.  This will ensure you are using the correct directory and that the file has correct permissions.  Once common problem is that the file may be /tftpboot/sensorfiles/IPS-SSM_20-K9-sys-1.1-a-6.1-1-E1.img.  But because the tftp server automatically starts in /tftpboot, you may need to NOT specify it for the file and instead just use: sensorfiles/IPS-SSM_20-K9-sys-1.1-a-6.1-1-E1.img
    6) Check to make sure the file is not corrupted by running an md5sum and checking it against the value listed on cisco's web site.

  • AIP-SSM-10 auto update issue

    Hi! experts
    I using AIP-SSM-10 module on ASA 5540
    But it is not working auto update signature.
    So I `m going to attach " show statistics host" result.
    Can you tell me some help?
    Thanks in advance
    Auto Update Statistics
    lastDirectoryReadAttempt = 07:34:50 UTC Tue Oct 20 2009
    = Read directory: https://198.133.219.25/cgi-bin/ida/locator/locator.pl
    = Error: AutoUpdate exception: HTTP connection failed [1,0]
    lastDownloadAttempt = N/A
    lastInstallAttempt = N/A
    nextAttempt = 04:00:00 UTC Wed Oct 21 2009

    It is clear that mgmt ifaces are able to connect to the Internet but if they may connect to inet via proxy you must configure proxy-server.

  • AIP-51505:  General Validation Error - SFTP transport - validation disabled

    Configuration :
    internal DC with SFTP
    external DC with SFTP (via proxy)
    Business Protocol          Custom Document over Generic Exchange
    MLR 12? (patch 8703404)
    3 environments have the same tip.properties
    2 environments pick up and send all files successfully.
    I cannot see a difference between the deployments that is causing the validation error.
    [also in all three B2B's are an ebXML and AS2 trading partner configuration]
    The 3rd generates validation errors for all files (14) in the b2b.log and sends some (1-7).
    Note that the sent ones change, if a failed one is retried in the source directory, sometimes it is sent successfully.
    In the failing/validating deployment there is no validation for (cut and pasted from UI screens) :
    Document Protocol Revision Details = Translation Enabled False Validation Enabled False
    Document Types (Document Definition Details for each document def) = Is Translation Enabled False Is Validation Enabled     False
    tip.properties (environment where error occurs) :
    #valid valudes for DiagnosticLevel:
    #DEBUG, INFORMATION, WARNING, ERROR, FATAL.
    #default logging level
    oracle.tip.DiagnosticLevel = ERROR
    #default component log level for B2B Engine
    b2b.oracle.tip.DiagnosticLevel = ERROR
    # following logging properties to be set back to false after resolving Sequence 98
    # oracle.tip.adapter.b2b.logPayload = true
    # oracle.tip.adapter.b2b.packaging.logDecryptMessage = true
    b2b.oracle.tip.DiagnosticLevel.Repository = ERROR
    b2b.oracle.tip.DiagnosticLevel.BusinessLogicLayer
    b2b.oracle.tip.DiagnosticLevel.B2B
    b2b.oracle.tip.DiagnosticLevel.ModelValidation
    b2b.oracle.tip.DiagnosticLevel.ValidationRule
    b2b.oracle.tip.DiagnosticLevel.TechStack
    b2b.oracle.tip.DiagnosticLevel.Deployment
    b2b.oracle.tip.DiagnosticLevel.Reports
    b2b.oracle.tip.DiagnosticLevel.UI
    #default component level logging for UI
    ui.oracle.tip.DiagnosticLevel = ERROR
    #specify component log leel to override default;
    ui.oracle.tip.DiagnosticLevel.Repository = ERROR
    ui.oracle.tip.DiagnosticLevel.BusinessLogicLayer
    ui.oracle.tip.DiagnosticLevel.B2B
    ui.oracle.tip.DiagnosticLevel.ModelValidation
    ui.oracle.tip.DiagnosticLevel.ValidationRule
    ui.oracle.tip.DiagnosticLevel.TechStack
    ui.oracle.tip.DiagnosticLevel.Deployment
    ui.oracle.tip.DiagnosticLevel.Reports
    ui.oracle.tip.DiagnosticLevel.UI
    oracle.tip.adapter.b2b.encoding=UTF-8
    # Diagnostic Service defaults
    oracle.core.ojdl.OrganizationId = oracle.com
    oracle.core.ojdl.ComponentId = tip
    oracle.core.ojdl.HostingClientId = beta
    oracle.core.ojdl.BufferSize = 100000
    oracle.core.ojdl.FlushInterval = 5000
    # Specific diagnostic settings
    oracle.tip.LogDirectory = /space/sw/oracle/products/ias/b2b/ip/log
    oracle.tip.LogMaxSegmentSize = 10000000
    oracle.tip.LogType = text
    # option to save old log when rebounding the service
    oracle.tip.LogSave = true
    # B2B Info
    oracle.tip.adapter.b2b.NumOfWFListeners = 1
    oracle.tip.adapter.b2b.NumOfIPListeners = 1
    oracle.tip.adapter.b2b.WFAgentName = OUTAGENT
    oracle.tip.adapter.b2b.RMIPort = 5111
    oracle.tip.adapter.b2b.RMIInstance = IP
    #oracle.tip.adapter.b2b.WalletLocation = file:/etc/ORACLE/WALLETS/oracle/ora_wallet.txt
    oracle.tip.adapter.b2b.ContinueValidationOnError = true
    oracle.tip.adapter.b2b.MultipleIdentifications=false
    oracle.tip.adapter.b2b.allTPInOneDirectory=true
    oracle.tip.adapter.b2b.DocumentRouting=false
    #oracle.tip.adapter.b2b.edi.identifyFromTP = Interchange | Group | Exchange
    #oracle.tip.adapter.b2b.transportTrace = /space/sw/oracle/products/ias/b2b/ip/log/transport.trc
    #oracle.tip.adapter.b2b.edi.ignoreValidation=InterchangeReceiverID,InterchangeSenderID,GroupReceiverID,GroupSenderID,GroupSenderQual,GroupReceiverQual,InterchangeSenderQual,InterchangeReceiverQual
    #report Certificate validation as ERROR or WARNING; default value is ERROR
    #oracle.tip.adapter.b2b.tpa.validateCertificate= ERROR | WARNING
    #oracle.tip.adapter.b2b.document.NoValidation = inbound | outbound
    # HTTP Proxy Host and Proxy Port
    oracle.tip.adapter.b2b.ProxyHost =
    oracle.tip.adapter.b2b.ProxyPort =
    # MaxCachedSessions is set to 0 means no ExecutionContext
    # is stored in HTTP session (IP cache is empty).Line below overwrites default
    # value equals to 5 when 5 concurrent users could store context in their sessions
    # By commenting that line you might turn IP cache on.
    oracle.tip.ui.MaxCachedSessions = 0
    # Suppression of Validation Warnings
    oracle.tip.buslogic.validation.SuppressWarnings=false
    # Callout directory
    oracle.tip.callout.directory=%s_calloutDirectory%
    # persistence directory
    oracle.tip.runtime.persistence.dirName=%s_persistenceDir%
    # enable ONS reverse ping
    enableONS=true
    # Optional property which user can set to specify saved report encoding e.g. UTF-8, UTF-16LE etc
    # By default this property is not set, in this case the saved report csv file
    # will be generated by using the native encoding
    # Users can set this parameter to change the encoding of the generated saved report csv file
    #savedReportEncoding=UTF-8
    # Please don't modify the following properties
    # Connection Info
    username=%s_intgDBUser%
    password=%s_intgDBPasswd%
    #connect=jdbc:oracle:thin:@%s_intgDBHost%:%s_intgDBPort%:%s_intgDBSid%
    drivertype = thin
    tnsentry = inst1
    host = %s_intgDBHost%
    port = %s_intgDBPort%
    sid = %s_intgDBSid%
    oracle.tip.connection.useRepositoryAPI=on
    oracle.tip.connection.oraclehome=/space/sw/oracle/products/ias/b2b
    # property specific to Deployment
    oracle.tip.deploy.workflow_username=%s_wfUsername%
    oracle.tip.deploy.workflow_passwd=%s_wfPasswd%
    oracle.tip.deploy.workflow_tnsname=%s_wfTnsname%
    # UI user authorization
    authorization = true
    # encryption key used for securing secrets in the schema.
    oracle.tip.security.key=Be8ejb7yOX3rSefEr5pxBl49WLc0Iej9VeI8jykdjRfv
    ##oracle.tip.adapter.b2b.WalletLocation = /sw/oracle/products/ias/b2b/Apache/Apache/conf/ssl.wlt/default/b2bwallet
    #oracle.tip.adapter.b2b.WalletLocation = /sw/oracle/products/ias/101202/ib/Apache/Apache/conf/ssl.wlt/default/b2bwallet
    oracle.tip.adapter.b2b.WalletLocation =file:/sw/oracle/products/ias/b2b/Apache/Apache/conf/ssl.wlt/default/b2bwallet/ewallet.txt
    # performance best practices
    oracle.tip.adapter.b2b.sleepTimeout=1
    oracle.tip.repos.RowSize=100
    oracle.tip.adapter.b2b.receiveTimeout=1
    oracle.tip.adapter.b2b.TPACache=true
    The b2b.log from the failing environment has some lines not seen in the other two environments (the lines referring to MimePackaging:unpack) :
    2010.04.29 at 19:07:14:295: Thread-11: B2B - (DEBUG)
    Protocol = SFTP
    Version = 2.0
    Transport Header
    filename:SA_ENVSTATUSES.txt
    filesize:1
    file_ext:.txt
    filename_format:%TO_PARTY%_%DOCTYPE_NAME%_%TIMESTAMP%.txt
    fullpath:/mnt/maximage_prd/sa_transfer/SA_ENVSTATUSES.txt
    timestamp:Thu Jan 15 09:29:53 PST 1970
    2010.04.29 at 19:07:14:295: Thread-11: BusinessLogicLayer - (DEBUG) New ExecutionContext has been created
    2010.04.29 at 19:07:14:296: Thread-11: BusinessLogicLayer - (DEBUG) setRuntimeActiveandQuiescing()
    2010.04.29 at 19:07:14:296: Thread-11: BusinessLogicLayer - (DEBUG) Recieve a new PersistencyService
    2010.04.29 at 19:07:14:299: Thread-11: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Design
    2010.04.29 at 19:07:14:300: Thread-11: BusinessLogicLayer - (DEBUG) Push Stack: queryConfiguration
    2010.04.29 at 19:07:14:300: Thread-11: BusinessLogicLayer - (DEBUG) Pop Stack: queryConfiguration
    2010.04.29 at 19:07:14:300: Thread-11: BusinessLogicLayer - (DEBUG) A new PersistencyService is created
    2010.04.29 at 19:07:14:340: Thread-11: BusinessLogicLayer - (DEBUG) setRuntimeActiveandQuiescing()
    2010.04.29 at 19:07:14:341: Thread-11: B2B - (DEBUG) DBContext beginTransaction: Enter
    2010.04.29 at 19:07:14:341: Thread-11: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
    2010.04.29 at 19:07:14:341: Thread-11: B2B - (DEBUG) DBContext beginTransaction: Leave
    2010.04.29 at 19:07:14:341: Thread-11: B2B - (DEBUG) InterfaceListener:onMessage - Invoke inbound callout - null - null
    2010.04.29 at 19:07:14:341: Thread-11: B2B - (DEBUG) InterfaceListenersyncAckEBMSchecking header names
    2010.04.29 at 19:07:14:341: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(2 params) Enter
    2010.04.29 at 19:07:14:342: Thread-11: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
    2010.04.29 at 19:07:14:343: Thread-11: BusinessLogicLayer - (DEBUG) Push Stack: createDataStorage
    2010.04.29 at 19:07:14:345: Thread-11: BusinessLogicLayer - (DEBUG) Pop Stack: createDataStorage
    2010.04.29 at 19:07:14:346: Thread-11: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
    2010.04.29 at 19:07:14:346: Thread-11: BusinessLogicLayer - (DEBUG) Push Stack: createWireMessage
    2010.04.29 at 19:07:14:348: Thread-11: BusinessLogicLayer - (DEBUG) Pop Stack: createWireMessage
    2010.04.29 at 19:07:14:348: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(2 params) Exit
    2010.04.29 at 19:07:14:348: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:onMessage sendEventtrue
    2010.04.29 at 19:07:14:359: Thread-11: B2B - (DEBUG) DBContext commit: Enter
    2010.04.29 at 19:07:14:362: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Enter
    2010.04.29 at 19:07:14:362: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Enter
    2010.04.29 at 19:07:14:362: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
    2010.04.29 at 19:07:14:363: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Leave
    2010.04.29 at 19:07:14:363: Thread-10: BusinessLogicLayer - (DEBUG) setRuntimeActiveandQuiescing()
    2010.04.29 at 19:07:14:363: Thread-10: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processEvents Enter
    2010.04.29 at 19:07:14:363: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processEvents begin transaction
    2010.04.29 at 19:07:14:363: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Enter
    2010.04.29 at 19:07:14:363: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Leave
    2010.04.29 at 19:07:14:363: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleMessageEvent Enter
    2010.04.29 at 19:07:14:363: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:incomingContinueProcess Enter
    2010.04.29 at 19:07:14:363: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:getWireMessage Enter
    2010.04.29 at 19:07:14:364: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
    2010.04.29 at 19:07:14:364: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: queryWireMessage
    2010.04.29 at 19:07:14:364: Thread-11: B2B - (DEBUG) DBContext commit: Transaction.commit()
    2010.04.29 at 19:07:14:364: Thread-11: B2B - (DEBUG) DBContext commit: Leave
    2010.04.29 at 19:07:14:365: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: queryWireMessage
    2010.04.29 at 19:07:14:365: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:getWireMessage Exit
    2010.04.29 at 19:07:14:366: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:formTransportMessage Enter
    2010.04.29 at 19:07:14:367: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:formTransportMessage Exit
    2010.04.29 at 19:07:14:367: Thread-10: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Enter
    2010.04.29 at 19:07:14:369: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Identify Business Protocol
    2010.04.29 at 19:07:14:370: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:identifyExchange Enter
    2010.04.29 at 19:07:14:370: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:identifyExchange Exit
    2010.04.29 at 19:07:14:370: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:identifyExchange Enter
    2010.04.29 at 19:07:14:370: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:identifyExchange SOAPAction is [null]
    2010.04.29 at 19:07:14:370: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Do Unpack using the BP specific package class
    2010.04.29 at 19:07:14:370: Thread-10: B2B - (DEBUG) MimePackaging:unpack:Enter
    2010.04.29 at 19:07:14:370: Thread-10: B2B - (DEBUG) MimePackaging:doUnpack:Enter
    2010.04.29 at 19:07:14:371: Thread-10: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:Enter
    2010.04.29 at 19:07:14:371: Thread-10: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:encoding = UTF-8
    2010.04.29 at 19:07:14:371: Thread-10: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:oracle.tip.adapter.b2b.packaging.Component@391da0
    2010.04.29 at 19:07:14:371: Thread-10: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:Exit
    2010.04.29 at 19:07:14:371: Thread-10: B2B - (DEBUG) MimePackaging:unpack:Exit
    2010.04.29 at 19:07:14:371: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Decode the Incoming Message into B2B Message
    2010.04.29 at 19:07:14:371: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Enter
    2010.04.29 at 19:07:14:372: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Number of Components = 1
    2010.04.29 at 19:07:14:372: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage Transport Protocol = {SFTP}
    2010.04.29 at 19:07:14:372: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage filename = SA_ENVSTATUSES.txt
    2010.04.29 at 19:07:14:372: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage FILE_FORMAT = TO_PARTY - SA
    2010.04.29 at 19:07:14:372: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage FILE_FORMAT = DOCTYPE_NAME - ENVSTATUSES
    2010.04.29 at 19:07:14:373: Thread-10: B2B - (ERROR) Error -: AIP-51505: General Validation Error
         at oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin.decodeIncomingMessage(GenericExchangePlugin.java:408)
         at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1477)
         at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2576)
         at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2446)
         at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2401)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
         at java.lang.Thread.run(Thread.java:534)
    2010.04.29 at 19:07:14:373: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
    2010.04.29 at 19:07:14:373: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Enter
    2010.04.29 at 19:07:14:373: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error message is Error -: AIP-51505: General Validation Error
    2010.04.29 at 19:07:14:373: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired Enter
    2010.04.29 at 19:07:14:373: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired {filename=SA_ENVSTATUSES.txt, filesize=1, file_ext=.txt, filename_format=%TO_PARTY%_%DOCTYPE_NAME%_%TIMESTAMP%.txt, fullpath=/mnt/maximage_prd/sa_transfer/SA_ENVSTATUSES.txt, timestamp=Thu Jan 15 09:29:53 PST 1970}
    2010.04.29 at 19:07:14:374: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired returning false
    2010.04.29 at 19:07:14:374: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException FA not required
    2010.04.29 at 19:07:14:374: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Error Message: Error -: AIP-51505: General Validation Error
    2010.04.29 at 19:07:14:374: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
    2010.04.29 at 19:07:14:374: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message found
    2010.04.29 at 19:07:14:374: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
    2010.04.29 at 19:07:14:375: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState enum0 not null
    2010.04.29 at 19:07:14:375: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message error information

    Thank you for the suggestion, unfortunately, I cannot get it to work.
    I've updated the IDC transport server to 3 different filename_formats, and tried the corresponding files, with correct names to match the filename_format.
    After updating the IDC I validated the trading partner (host).
    I then updated the agreement using the updated IDC, and validated the agreement.
    I then validated the host again.
    Then I created a new deployment.
    And still received the error.
    I then deleted the old IDC and created a new IDC and new agreement and new deployment, trying 3 different "Internal delivery channel filename format" values (updating and validating the agreement and host trading partner each time).
    And still received the error.
    No matter what I set EITHER the IDC "filename format" OR "Internal delivery channel filename format", the b2b.log always reports :
    filename_format = %TO_PARTY%_%DOCTYPE_NAME%_%TIMESTAMP%.txt
    e.g.
    2010.05.16 at 18:05:02:758: Thread-15: B2B - (DEBUG)
    Protocol = SFTP
    Version = 2.0
    Transport Header
    filename:SA_DRUGS_10.txt
    filesize:1
    file_ext:.txt
    filename_format:%TO_PARTY%_%DOCTYPE_NAME%_%TIMESTAMP%.txt
    fullpath:/mnt/maximage_prd/sa_transfer/SA_DRUGS_10.txt
    timestamp:Thu Jan 15 09:54:18 PST 1970
    When I try a file with a revision number, e.g. SA_DRUGS_10.txt the log shows :
    2010.05.16 at 18:05:03:602: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage FILE_FORMAT = TO_PARTY - SA
    2010.05.16 at 18:05:03:603: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage FILE_FORMAT = DOCTYPE_NAME - DRUGS
    2010.05.16 at 18:05:03:603: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage FILE_FORMAT = TIMESTAMP - 10
    2010.05.16 at 18:05:03:895: Thread-14: B2B - (ERROR) Error -: AIP-51505: General Validation Error
    which makes sense as "10" is not a timestamp.
    If I exclude the revision, using SA_DRUGS.txt the log shows :
    2010.05.16 at 18:27:03:543: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage Transport Protocol = {SFTP}
    2010.05.16 at 18:27:03:544: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage filename = SA_DRUGS.txt
    2010.05.16 at 18:27:03:544: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage FILE_FORMAT = TO_PARTY - SA
    2010.05.16 at 18:27:03:544: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage FILE_FORMAT = DOCTYPE_NAME - DRUGS
    2010.05.16 at 18:27:03:545: Thread-14: B2B - (ERROR) Error -: AIP-51505: General Validation Error
    So, the timestamp gets ignored (as there is no "_" delimiter), but it still fails, probably because there is no timestamp in the filename.
    So, why won't the UI correctly set the IDC filename_format or Internal filename_format ?

  • AIP-51505: 5084: XEngine error - Invalid data.

    Hi All,
    I am getting invalid data error when posting a EDI 855 from BPEL to iB2B.
    I have done the following already: set validation to false and verified the XML against the xsd using XMLSpy.
    Any idea what can be wrong?
    Thanks in advance,
    Suresh
    2007.09.25 at 14:08:14:877: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:getControlNumberFromEDIRepository CtlNum (TP): Interchange = 1101, Functional Group = 1101, Transaction Set = 1097
    2007.09.25 at 14:08:14:877: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Enter
    2007.09.25 at 14:08:14:877: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl fullOutboundBatching = false
    2007.09.25 at 14:08:14:878: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl validateEnvelope = false
    2007.09.25 at 14:08:14:878: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Leave
    2007.09.25 at 14:08:17:023: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:reset Enter
    2007.09.25 at 14:08:17:023: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:reset Leave
    2007.09.25 at 14:08:17:023: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument XML = 1
    2007.09.25 at 14:08:17:024: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument no result from XDataToNative
    2007.09.25 at 14:08:17:024: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sErrorGuid = {F35AFE03-C479-4F96-B4F1-2EF36DABC5FE}
    2007.09.25 at 14:08:17:024: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sDescription = Invalid data.
    2007.09.25 at 14:08:17:024: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sBrDescription = 5084: XEngine error - Invalid data.
    2007.09.25 at 14:08:17:024: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ErrorLevel sParameterValue = 0
    2007.09.25 at 14:08:17:025: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = Name sParameterValue = XData2Native
    2007.09.25 at 14:08:17:025: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ecdn_guid_ sParameterValue = {4A4CF358-6B92-11DC-82C1-00142223EF95}
    2007.09.25 at 14:08:17:025: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ecindex sParameterValue = 0
    2007.09.25 at 14:08:17:025: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ec_error_scope sParameterValue = Document
    2007.09.25 at 14:08:17:025: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument added Hash Key = {4A4CF358-6B92-11DC-82C1-00142223EF95}
    2007.09.25 at 14:08:17:025: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument batch Position = 0
    2007.09.25 at 14:08:17:026: Thread-22: B2B - (ERROR) Error -: AIP-51505: General Validation Error
         at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2021)
         at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1219)
         at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:725)
         at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:906)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:655)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:353)
         at java.lang.Thread.run(Thread.java:534)
    2007.09.25 at 14:08:17:026: Thread-22: B2B - (ERROR) Error -: AIP-51505: General Validation Error
         at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2021)
         at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1219)
         at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:725)
         at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:906)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:655)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:353)
         at java.lang.Thread.run(Thread.java:534)
    2007.09.25 at 14:08:17:027: Thread-22: B2B - (ERROR) Error -: AIP-51505: General Validation Error
         at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2062)
         at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1219)
         at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:725)
         at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:906)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:655)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:353)
         at java.lang.Thread.run(Thread.java:534)
    2007.09.25 at 14:08:17:027: Thread-22: B2B - (ERROR) Error -: AIP-51505: General Validation Error: Error -: AIP-51505: General Validation Error
         at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2062)
         at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1219)
         at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:725)
         at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:906)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:655)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:353)
         at java.lang.Thread.run(Thread.java:534)
    Caused by: Error -: AIP-51505: General Validation Error
         at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2021)
         ... 6 more
    2007.09.25 at 14:08:17:027: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage B2BDomainException
    2007.09.25 at 14:08:17:027: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updating Error Message: Error -: AIP-51505: General Validation Error
    2007.09.25 at 14:08:17:028: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
    2007.09.25 at 14:08:17:029: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message not found.
    2007.09.25 at 14:08:17:029: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
    2007.09.25 at 14:08:17:032: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
    2007.09.25 at 14:08:17:032: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updating Native Event Tbl Row
    2007.09.25 at 14:08:17:032: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
    2007.09.25 at 14:08:17:033: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
    ** DbAccess:updateNativeEvtTblRow:tip_wireMsg wiremsg not found
    2007.09.25 at 14:08:17:034: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException notifying App
    2007.09.25 at 14:08:17:034: Thread-22: B2B - (DEBUG) Engine:notifyApp Enter
    2007.09.25 at 14:08:17:036: Thread-22: B2B - (DEBUG) Enqueue Engine AQJMSCorrelationID = 3AE6A497D52861F3E0400302290324BA
    2007.09.25 at 14:08:17:036: Thread-22: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
    <Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <correlationId>4de21f37c68d8a74:-3030dba5:11538f2ec0d:-7cfc</correlationId>
    <b2bMessageId>4de21f37c68d8a74:-3030dba5:11538f2ec0d:-7cfc</b2bMessageId>
    <errorCode>AIP-51505</errorCode>
    <errorText>5084: XEngine error - Invalid data.</errorText>
    <errorDescription>
    <![CDATA[Machine Info: (phantom.ciena.com)
    Invalid data.  ]]>
    </errorDescription>
    <errorSeverity>2</errorSeverity>
    </Exception>
    2007.09.25 at 14:08:17:036: Thread-22: B2B - (DEBUG) AQJMSCorrelationID = 3AE6A497D52861F3E0400302290324BA
    2007.09.25 at 14:08:17:041: Thread-22: B2B - (DEBUG) Engine:notifyApp Exit
    2007.09.25 at 14:08:17:041: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updated the Error Message Successfully: Error -: AIP-51505: General Validation Error
    2007.09.25 at 14:08:17:042: Thread-22: B2B - (DEBUG) DBContext commit: Enter
    2007.09.25 at 14:08:17:046: Thread-22: B2B - (DEBUG) DBContext commit: Transaction.commit()
    2007.09.25 at 14:08:17:046: Thread-22: B2B - (DEBUG) DBContext commit: Leave
    2007.09.25 at 14:08:17:046: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Exit
    xml 855:
    <Transaction-855 xmlns:ns1="urn:oracle:integration:b2b:ED4636190E8D48CB88002EE2393BAFD6" xmlns="urn:oracle:integration:b2b:ED4636190E8D48CB88002EE2393BAFD6">
    <ns1:Segment-ST>
    <ns1:Element-143>855</ns1:Element-143>
    <ns1:Element-329>36770001</ns1:Element-329>
    </ns1:Segment-ST>
    <ns1:Segment-BAK>
    <ns1:Element-353>00</ns1:Element-353>
    <ns1:Element-587>AT</ns1:Element-587>
    <ns1:Element-324>QW-09122007-T2</ns1:Element-324>
    <ns1:Element-373>20070924</ns1:Element-373>
    <ns1:Element-373_1>20070924</ns1:Element-373_1>
    </ns1:Segment-BAK>
    <ns1:Segment-CUR>
    <ns1:Element-98>PE</ns1:Element-98>
    <ns1:Element-100>USD</ns1:Element-100>
    </ns1:Segment-CUR>
    <ns1:Loop-PO1>
    <ns1:Segment-PO1>
    <ns1:Element-350>004.000</ns1:Element-350>
    <ns1:Element-330>2</ns1:Element-330>
    <ns1:Element-355>EA</ns1:Element-355>
    <ns1:Element-212>1.1</ns1:Element-212>
    <ns1:Element-235>IN</ns1:Element-235>
    <ns1:Element-234>009-2002-734</ns1:Element-234>
    <ns1:Element-235_1>VN</ns1:Element-235_1>
    <ns1:Element-234_1>76814</ns1:Element-234_1>
    </ns1:Segment-PO1>
    <ns1:Loop-ACK>
    <ns1:Segment-ACK>
    <ns1:Element-668>IA</ns1:Element-668>
    </ns1:Segment-ACK>
    </ns1:Loop-ACK>
    <ns1:Loop-SCH>
    <ns1:Segment-SCH>
    <ns1:Element-380>2</ns1:Element-380>
    <ns1:Element-355_1>EA</ns1:Element-355_1>
    <ns1:Element-374_5>079</ns1:Element-374_5>
    <ns1:Element-373>20070924</ns1:Element-373>
    </ns1:Segment-SCH>
    </ns1:Loop-SCH>
    </ns1:Loop-PO1>
    <ns1:Loop-PO1>
    <ns1:Segment-PO1>
    <ns1:Element-350>002.000</ns1:Element-350>
    <ns1:Element-330>2</ns1:Element-330>
    <ns1:Element-355>EA</ns1:Element-355>
    <ns1:Element-212>1.1</ns1:Element-212>
    <ns1:Element-235>IN</ns1:Element-235>
    <ns1:Element-234>009-2002-375</ns1:Element-234>
    <ns1:Element-235_1>VN</ns1:Element-235_1>
    <ns1:Element-234_1>76752</ns1:Element-234_1>
    </ns1:Segment-PO1>
    <ns1:Loop-ACK>
    <ns1:Segment-ACK>
    <ns1:Element-668>IA</ns1:Element-668>
    </ns1:Segment-ACK>
    </ns1:Loop-ACK>
    <ns1:Loop-SCH>
    <ns1:Segment-SCH>
    <ns1:Element-380>2</ns1:Element-380>
    <ns1:Element-355_1>EA</ns1:Element-355_1>
    <ns1:Element-374_5>079</ns1:Element-374_5>
    <ns1:Element-373>20070924</ns1:Element-373>
    </ns1:Segment-SCH>
    </ns1:Loop-SCH>
    </ns1:Loop-PO1>
    <ns1:Loop-PO1>
    <ns1:Segment-PO1>
    <ns1:Element-350>003.000</ns1:Element-350>
    <ns1:Element-330>2</ns1:Element-330>
    <ns1:Element-355>EA</ns1:Element-355>
    <ns1:Element-212>1.1</ns1:Element-212>
    <ns1:Element-235>IN</ns1:Element-235>
    <ns1:Element-234>009-2002-710</ns1:Element-234>
    <ns1:Element-235_1>VN</ns1:Element-235_1>
    <ns1:Element-234_1>76744</ns1:Element-234_1>
    </ns1:Segment-PO1>
    <ns1:Loop-ACK>
    <ns1:Segment-ACK>
    <ns1:Element-668>IA</ns1:Element-668>
    </ns1:Segment-ACK>
    </ns1:Loop-ACK>
    <ns1:Loop-SCH>
    <ns1:Segment-SCH>
    <ns1:Element-380>2</ns1:Element-380>
    <ns1:Element-355_1>EA</ns1:Element-355_1>
    <ns1:Element-374_5>079</ns1:Element-374_5>
    <ns1:Element-373>20070924</ns1:Element-373>
    </ns1:Segment-SCH>
    </ns1:Loop-SCH>
    </ns1:Loop-PO1>
    <ns1:Loop-CTT>
    <ns1:Segment-CTT>
    <ns1:Element-354>3</ns1:Element-354>
    </ns1:Segment-CTT>
    </ns1:Loop-CTT>
    <ns1:Segment-SE>
    <ns1:Element-96>14</ns1:Element-96>
    <ns1:Element-329>36770001</ns1:Element-329>
    </ns1:Segment-SE>
    </Transaction-855>

    Hello,
    Can you please restart the b2b server and apply the latest patch. If the problem still persist send us the export.
    Rgds,Ramesh

  • Oracle B2B :(AIP-51505 : 5082: XEngine error - Guideline look-up failed)

    I am getting following error message on the remote host when I try to enque .
    In the error report (B2b Console)
    AIP-51505 : 5082: XEngine error - Guideline look-up failed
    I have already verified and re-verified the document properties/properties/revision on the Oracle B2B console.
    I think this error is related to
    2008.01.28 at 15:54:12:156: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = Webmd
    2008.01.28 at 15:54:12:156: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Enter
    2008.01.28 at 15:54:12:156: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit NodeGUID = {0BF5065C-F83C-441C-A8AA-C85CF4197931} position = 0
    2008.01.28 at 15:54:12:156: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Leave
    2008.01.28 at 15:54:12:156: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
    2008.01.28 at 15:54:12:156: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@15fc672
    2008.01.28 at 15:54:12:156: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
    2008.01.28 at 15:54:12:156: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = TransactionPurposeCode, val = [13]
    2008.01.28 at 15:54:12:156: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [null]
    2008.01.28 at 15:54:12:156: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Value doesn't match, doc parameter is null
    2008.01.28 at 15:54:12:156: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = TransactionID, val = [270]
    2008.01.28 at 15:54:12:156: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [270]
    2008.01.28 at 15:54:12:156: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Transaction]
    Would you know which config in Oracle B2B contain the TransactionPurposeCode ?
    Thanks for help

    Hello,
    Please let us know the Business protocol and also send the b2b.log in DEBUG mode to [email protected]
    Rgds,Ramesh

  • Do I need two AIP-SSM modules if I am configuring failover?

    Is it possible to use a single AIP-SSM module in two ASA's that are configured in Active/Standby mode?
    I would like to configure the module in the first ASA with the fail-open setting.  Then, if the first ASA fails, I could then physically remove the AIP-SSM module and place it in the second ASA.
    Would there be any problems configuring it this way?
    Would the active/standby ASA's complain that there is only one AIP-SSM module?
    Thanks in advance.

    Hello Julio. My name is Rogelio, and I would appreciate your answer on a related matter, because I will have to execute the initial configuration of a failover pair, each one with its own IPS module.
    Question: let´s suppose that I execute a basic setup (admin username/password, IP address, mask, gateway), on the IPS module of the active ASA firewall. ¿Will this configuration be replicated to the IPS module of the secondary unit?
    Your kind answer will be greatly appreciated.
    Best regards...

  • How to buy license? for AIP-SSM-10 ?

    Hi all
    how to buy license? for AIP-SSM-10 ?
    1. CON-SU1-AS1A1PK9 this is Cisco SMARTnet Support for AIP-SSM-10
    2. do I need smartnet for ASA ?
    3. what is part number of license ?
    ASA5510test# session 1
    Opening command session with slot 1.
    Connected to slot 1. Escape character sequence is 'CTRL-^X'.
    login: cisco
    Password:
    ***NOTICE***
    This product contains cryptographic features and is subject to United States
    and local country laws governing import, export, transfer and use. Delivery
    of Cisco cryptographic products does not imply third-party authority to import,
    export, distribute or use encryption. Importers, exporters, distributors and
    users are responsible for compliance with U.S. and local country laws. By using
    this product you agree to comply with applicable laws and regulations. If you
    are unable to comply with U.S. and local laws, return this product immediately.
    A summary of U.S. laws governing Cisco cryptographic products may be found at:
    http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
    If you require further assistance please contact us by sending email to
    [email protected].
    ***LICENSE NOTICE***
    There is no license key installed on the SSM-IPS10.
    The system will continue to operate with the currently installed
    signature set.  A valid license must be obtained in order to apply
    signature updates.  Please go to http://www.cisco.com/go/license
    to obtain a new license or install a license.
    sensor#
    sensor# sh ver
    Application Partition:
    Cisco Intrusion Prevention System, Version 6.0(6)E3
    Host:
        Realm Keys          key1.0
    Signature Definition:
        Signature Update    S399.0                   2009-05-06
        Virus Update        V1.4                     2007-03-02
    OS Version:             2.4.30-IDS-smp-bigphys
    Platform:               ASA-SSM-10
    Serial Number:          ........
    No license present
    Sensor up-time is 21 min.
    Using 655507456 out of 1032499200 bytes of available memory (63% usage)
    application-data is using 39.7M out of 166.8M bytes of available disk space (25%
    usage)
    boot is using 37.6M out of 68.6M bytes of available disk space (58% usage)
    MainApp          N-NUBRA_2009_JUL_15_01_10_6_0_5_57   (Ipsbuild)   2009-07-15T01
    :15:08-0500   Running
    AnalysisEngine   N-NUBRA_2009_JUL_15_01_10_6_0_5_57   (Ipsbuild)   2009-07-15T01
    :15:08-0500   Running
    CLI              N-NUBRA_2009_JUL_15_01_10_6_0_5_57   (Ipsbuild)   2009-07-15T01
    :15:08-0500
    Upgrade History:
      IPS-K9-6.0-6-E3   17:48:06 UTC Wed Jul 15 2009
    Recovery Partition Version 1.1 - 6.0(6)E3
    sensor#

    Hi,
    CON-SU1-AS2A10K9 contract if for ASA+IPS bundle. If AIP-SSM-10 ws purchased as a spare the contract would be CON-SU1-ASIP10K9.
    I am not sure whether or not this Cisco Service for IPS contract can be  used to cover just the AIP-SSM-10 if it was purchased as part of a  Bundle instead of a Spare.
    I would recommend that you check with your Cisco reseller or Cisco  Sales Representative.
    Sourav

  • Using ASA5510 AIP-SSM in IDS mode

    Hi,
    I' ve a Cisco ASA5510 with  AIP-SSM and I wold like to use it like a one-armed IDS for connect them to a span port of a switch in my network,
    without the traffic passing through the Firewall.
    I've try to configure it and connect the interface inside (fast0/1) to the span port, I create the policy for permit  all the traffic to the  Sensor but it doesn't work, no packet recived on sensor.
    somebody can help me?
    thanks

    Unfortunately you can't use the AIP-SSM in an ASA with a spanning switch like you could with the 4200 series appliances.
    The reason is that the ASA was built to be a firewall, and no matter how much of that functionality you turn off, it still needs to see TCP and UDP conversations flowing thru the ASA in order to pass that traffic to the AIP-SSM sensor (I tired very hard to see if I could get around this limitation, but you can't).
    The best you can hope to do is put the ASA in-line (I know this reduces reliability) and turn off as much of the firewall configs you can. Then you can promisciously monitor the traffic passing thru teh ASA with teh AIP-SSM.
    It's not ideal, but it's the cheapest IPS sensor in Cisco's line up right now.
    - Bob

Maybe you are looking for