Upgrading IPS strings, ASA SSM-10 module

I am having a challenging time upgrading the ASA SSM-10 IPS module. I down loaded the IPS-sig-s327-req-e1.pkg to Win XP ftp server (my workstation). The instructions in following does not work: http://download-sj.cisco.com/cisco/ciscosecure/ips/6.x/sigup/IPS-sig-S327.readme.txt
"error: execUpgradeSoftware : Connect failed". Any suggestion would be appreciated.

I can connect the LAN switch directly to the inside interface of the ASA5510 firewall. Hosts can get Internet connectivity while cabled to the switch. However, when the LAN switch is connected to the port on the IPS module, there is no Internet connectivity. Any suggestions would be appreciated. The following is the sh configuration and sh int output.
sh con_[Jfiguration
Version 5.1(6)
! Current configuration last modified Sat Apr 05 12:28:11 2008
service interface
exit
service analysis-engine
virtual-sensor vs0
physical-interface GigabitEthernet0/1
exit
exit
service authentication
exit
service event-action-rules rules0
exit
service host
network-settings
host-ip 192.168.1.36/24,192.168.1.10
host-name ips
telnet-option enabled
--MORE--
access-list 0.0.0.0/0
exit
time-zone-settings
offset 0
standard-time-zone-name UTC
exit
exit
service logger
exit
service network-access
exit
service notification
exit
service signature-definition sig0
exit
service ssh-known-hosts
exit
service trusted-certificates
--MORE--
exit
service web-server
exit
ips# sh inter_[Jfaces _[2C
Interface Statistics
Total Packets Received = 6806
Total Bytes Received = 2001784
Missed Packet Percentage = 0
Current Bypass Mode = Auto_off
MAC statistics from interface GigabitEthernet0/1
Interface function = Sensing interface
Description =
Media Type = backplane
Missed Packet Percentage = 0
Inline Mode = Unpaired
Pair Status = N/A
Link Status = Up
Link Speed = Auto_1000
Link Duplex = Auto_Full
Total Packets Received = 6807
Total Bytes Received = 2001866
Total Multicast Packets Received = 0
Total Broadcast Packets Received = 0
Total Jumbo Packets Received = 0
Total Undersize Packets Received = 0
Total Receive Errors = 0
Total Receive FIFO Overruns = 0
Total Packets Transmitted = 6807
--MORE--
Total Bytes Transmitted = 2017118
Total Multicast Packets Transmitted = 0
Total Broadcast Packets Transmitted = 0
Total Jumbo Packets Transmitted = 0
Total Undersize Packets Transmitted = 0
Total Transmit Errors = 0
Total Transmit FIFO Overruns = 0
MAC statistics from interface GigabitEthernet0/0
Interface function = Command-control interface
Description =
Media Type = TX
Link Status = Down
Link Speed = N/A
Link Duplex = N/A
Total Packets Received = 126
Total Bytes Received = 14255
Total Multicast Packets Received = 0
Total Receive Errors = 0
Total Receive FIFO Overruns = 0
Total Packets Transmitted = 1
Total Bytes Transmitted = 64
Total Transmit Errors = 0
Total Transmit FIFO Overruns = 0

Similar Messages

  • How do I backup an IPS config (ASA-SSM-10)

    Hi,
    How do I backup an IPS config (ASA-SSM-10)?
    Thanks

    There is a copy command in the IPS CLI that can be used to copy the current configuration to a backup configuration on the sensor itself.
    Or to copy the current configuration to an FTP or SCP server.
    The copy command can then be used to copy a configuration from backup or from an FTP or SCP server back to the running configuration of the sensor.
    http://www.cisco.com/en/US/docs/security/ips/6.2/command/reference/crCmds.html#wp458440

  • Image recovery on 5520 IDS Module (ASA-SSM-10) TFTP timeout failure

    I have an ASA 5520 with an ASA-SSM-10 module in it for IDS.  It has (from what I can tell) never been used or configured.  In fact, I only recently found that it existed!  I would like to begin using it, starting with replacing the software image with the latest (I do NOT need any configuration from it now).
    Details ...
    KCH-ASA-Primary# sh module 1 details
    Getting details from the Service Module, please wait...
    ASA 5500 Series Security Services Module-10
    Model:              ASA-SSM-10
    Hardware version:   1.0
    Serial Number:      JAF10422581
    Firmware version:   1.0(11)2
    Software version:   6.0(1)E1
    MAC Address Range:  0018.b91b.69f1 to 0018.b91b.69f1
    App. name:          IPS
    App. Status:        Up
    App. Status Desc:
    App. version:       6.0(1)E1
    Data plane Status:  Up
    Status:             Up
    Mgmt IP addr:       172.17.1.20
    Mgmt web ports:     443
    Mgmt TLS enabled:   true
    The problem that I am having is that when I set it up to pull down the new software through TFTP, it just hangs and times out.
    KCH-ASA-Primary# hw module 1 recover config
    Image URL [tftp://10.10.10.9/IPS-sig-S789-req-E4.pkg]:
    Port IP Address [172.17.1.20]:
    VLAN ID [950]:
    Gateway IP Address [172.17.1.1]:
    KCH-ASA-Primary#
    And then ...
    KCH-ASA-Primary# debug module-boot
    debug module-boot  enabled at level 1
    KCH-ASA-Primary# hw module 1 recover boot
    The module in slot 1 will be recovered.  This may
    erase all configuration and all data on that device and
    attempt to download a new image for it.
    Recover module in slot 1? [confirm]
    Recover issued for module in slot 1
    KCH-ASA-Primary# Slot-1 215> Cisco Systems ROMMON Version (1.0(11)2) #0: Thu Jan                             26 10:43:08 PST 2006
    Slot-1 216> Platform ASA-SSM-10
    Slot-1 217> GigabitEthernet0/0
    Slot-1 218> Link is UP
    Slot-1 219> MAC Address: 0018.b91b.69f1
    Slot-1 220> ROMMON Variable Settings:
    Slot-1 221>   ADDRESS=172.17.1.20
    Slot-1 222>   SERVER=10.10.10.9
    Slot-1 223>   GATEWAY=172.17.1.1
    Slot-1 224>   PORT=GigabitEthernet0/0
    Slot-1 225>   VLAN=950
    Slot-1 226>   IMAGE=IPS-sig-S789-req-E4.pkg
    Slot-1 227>   CONFIG=
    Slot-1 228>   LINKTIMEOUT=20
    Slot-1 229>   PKTTIMEOUT=4
    Slot-1 230>   RETRY=20
    Slot-1 231> tftp [email protected] via 172.17.1.1
    KCH-ASA-Primary# Slot-1 232> TFTP failure: Packet verify failed after 20 retries
    Slot-1 233> Rebooting due to Autoboot error ...
    Slot-1 234> Rebooting....
    I know that I can reach 10.10.10.9 from 172.17.1.x.  And this is the present port IP of the device.  If I do a 'session1' and ping 10.10.10.9, I get replies.  I know my TFTP is working ... I use it for all of my switches for config backups and installing new IOS.  And watching my TFTP server window, I am not seeing any connection attempts.
    What am I doing wrong here?  :-(

    Thanks for your response. As I mentioned earlier in my email, I tried 2 different images (IPS-SSC_5-K9-sys-1.1-a-6.2-2-E4.img and IPS-SSM_10-K9-sys-1.1-a-7.1-5-E4.img) without any success. Since there are no packets coming from IPS on the TFTP server, I think the problem is something else.
    When I run the "debug cplane 255" command, I see some errors mentioned below:
    asa(config)# debug cplane 255
    debug cplane  enabled at level 255
    asa(config)#
    cp_connect: Connecting to card 1, socket 3, 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
    Is this a hardware issue?

  • Equivalent to show disk0: on ASA-SSM-10

    Hi, are you able to see the contents of the disk on an ASA-SSM-10 module? Like the show disk0: command on my 5510? I know it has an internal flash disk..Is that where the image and configuration files and software are located? Can one see these files and copy them to TFTP server?
    Cheers
    Phil

    Hi Philip,
    You can view this content through the service account of IPS. The downside will be that you can only access it with the supervision of TAC. If you want to see the configuration you can do a show config; if you want to see what version are you running you can do it through the show version command.
    HTH
    Luis Silva
    "If you need PDI (Planning, Design, Implement) assistance feel free to reach us"
    http://www.cisco.com/web/partners/tools/pdihd.html

  • Need assistance to configure ASA-SSM-10

    Hello All,
       Can someone assist me on setting up the IPS ASA-SSM-10 module in ASA 5520 firewall . I have just licensed the box. It would be great if someone can help me with relevant videos\docs to configure the SSM module to enable all the required IPS features for the box to run. I am running ASDM 6.4 and if anyone has the configs to enable via ASDM\CLI whichever is feasible is fine . Kindly assist .Below is the module details.
    ASA 5500 Series Security Services Module-10
    Model:              ASA-SSM-10
    Hardware version:   1.0
    Firmware version:   1.0(11)5
    Software version:   7.1(8)E4
    App. name:          IPS
    App. Status:        Up
    App. Status Desc:   Normal Operation
    App. version:       7.1(8)E4
    Data plane Status:  Up
    Status:             Up
    Regards,
    Karthik

    Do you need the syslogs to be sent or the Events.
    IPS sensors do not support syslog forwarding.  Syslog is fairly
    restrictive in size of messages and is not secure or reliable.
    sensor does support sending of events using SNMP
    (again with the same sets of restrictions:  not full data, clear text,
    not reliable).
    There is a physical ability to send events as traps.  It isn't
    recommended for many reasons (or lets say it isn't recommended in the
    same way that monitoring using SDEE is).  SNMP trap receivers generally
    aren't built to handle, say 200 events per second per device.  The
    sensor isn't capable of sending at the same event rate as it is with
    SDEE.  The traps are in clear text and are not reliably sent.  They
    don't contain the same amount of info as an SDEE event, and can't.
    If you need the events to  be sent to a database you can run cisco IME which can collect all the events generated by the IPS.
    Hope this helps.
    Sachin

  • Seeing errors & FIFO Overruns on the ASA-SSM-10

    Hello,
    A few of my customers are utilizing ASA-SSM-10 module running under ASA5510/20 hardware. The FW?s is part of the Failover configuration.
    The module is running in "promiscuous fail-open" mode and the class-map for the IPS is applied as global_policy with access-list monitoring all the interfaces and all protocols.
    In two independent cases, we are seeing errors on the Sensing interface GigabitEthernet0/1
    Total Receive Errors = 772089
    Total Receive FIFO Overruns = 3832
    I've already verified speed/duplex settings on the FW side and I don't see any errors that would probably be causing this behavior. The bandwidth on the all interfaces is also nowhere close to the rated 150Mbps/s inspection.
    Here is the scenario:
    Client1 - HA
    ASA 5510 Adaptive Security Appliance v7.2(2)19
    ASA 5500 Series Security Services Module-10 v5.1(6)E1
    Client2 - HA
    ASA 5520 Adaptive Security Appliance v7.2(2)10
    ASA 5500 Series Security Services Module-10 v5.1(6)E1
    Wondering if anyone has seen the behavior in their environment and what might be causing it?

    Hello Giorgi,
    Sometimes it may be server saturation, other connection problems proxy and so on. I recommend you to not put the hour for auto update to an exact time ie 2:00 PM or 1:00 AM try putting not even numbers like 9:17 or 10:41, and see if you continue getting these errors.
    Mike

  • ASA-SSM-10 Unresponsive

    Hi,
    I've installed an ASA-SSM-10 module into my ASA 5510 firewall but it's in "Unresponsive" state. I tried to reset and recover the module but nothing seems to work. Below you may find information about the system and details about what I did. Any help is greatly appreciated.
    Firewall:
    ASA5510-K8, 1024 MB RAM, CPU Pentium 4 Celeron 1600 MHz
    Internal ATA Compact Flash, 256MB
    System image file is "disk0:/asa843-k8.bin"
    Device Manager Version 6.4(3)
    IPS Module:
    ASA 5500 Series Security Services Module-10  ASA-SSM-10
    Hw Version: 1.0
    Sw Version: 6.2(2)E4
    SSM Application Version: 6.2(2)E4
    I have 2 IPS images at my TFTP server:
    IPS-SSC_5-K9-sys-1.1-a-6.2-2-E4.img
    IPS-SSM_10-K9-sys-1.1-a-7.1-5-E4.img
    I tried the command: hw-module module 1 reset
    At first module status changes to "Inıt" but after then it goes back to "Unresponsive"
    I used the command "hw-module module 1 recover configure" for 2 different images mentioned above by the same order and then tried:
    "hw-module module 1 recover boot"
    Module status changes to "Recover" and stays like that for hours. I've waited for 2 hours for 2 different images. And then I issued the command: hw-module module 1 recover stop and the module goes back to "Unresponsive" state.
    The Module's network interface is connected to the same switch where the TFTP server is connected. When I run a sniffer on the TFTP server (Linux, tcpdump), there's no TFTP activity. But I can use this TFTP server from ASA (Connected to the Inside interface).
    ASA Inside interface IP Address: X.X.X.1
    TFTP Server IP Address: X.X.X.8
    "show module 1 recover" command output:
    Module 1 recover parameters...
    Boot Recovery Image: Yes
    Image URL:           tftp://X.X.X.8/IPS-SSC_5-K9-sys-1.1-a-6.2-2-E4.img
    Port IP Address:     X.X.X.2
    Gateway IP Address:  X.X.X.1
    VLAN ID:             0
    (There are no VLANs used on this network.)

    Thanks for your response. As I mentioned earlier in my email, I tried 2 different images (IPS-SSC_5-K9-sys-1.1-a-6.2-2-E4.img and IPS-SSM_10-K9-sys-1.1-a-7.1-5-E4.img) without any success. Since there are no packets coming from IPS on the TFTP server, I think the problem is something else.
    When I run the "debug cplane 255" command, I see some errors mentioned below:
    asa(config)# debug cplane 255
    debug cplane  enabled at level 255
    asa(config)#
    cp_connect: Connecting to card 1, socket 3, 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
    Is this a hardware issue?

  • No AutoUpdate feature working on ASA-SSM-20

    Hi!
    Autoupdate feature is not working on ASA-SSM-20 module.
    We have configure:
    https://www.cisco.com//cgi-bin/front.x/ida/locator/locator.pl
    And/Or:
    https://198.133.219.25//cgi-bin/front.x/ida/locator/locator.pl
    And/Or:
    https://www.cisco.com/cgi-bin/front.x/ida/locator/locator.pl
    And/Or:
    https://198.133.219.25//cgi-bin/front.x/ida/locator/locator.pl
    We get this errors on the ASA-SSM-20 module:
    evError: eventId=1280563964539644086  vendor=Cisco  severity=error 
      originator:  
        hostId: sensor1 
        appName: mainApp 
        appInstanceId: 356 
      time: nov 17, 2010 08:15:45 UTC  offset=60  timeZone=GMT+01:00 
      errorMessage: AutoUpdate exception: Receive HTTP response failed [3,212]  name=errSystemError
    evError: eventId=1280563964539644079  vendor=Cisco  severity=error 
      originator:  
        hostId: sensor1 
        appName: mainApp 
        appInstanceId: 356 
      time: nov 17, 2010 08:10:02 UTC  offset=60  timeZone=GMT+01:00 
      errorMessage: http error response: 400  name=errSystemError
    Any Ideas?

    I am experiencing a similar issue currently with a new SSC-5 module.  I am working with TAC, however reposne has been slow.  I can see traffic with Wireshark for 198.133.219.25 but I never see the traffic for 198.133.219.243 that I was told to allow on the firewall.  I also found it confusing that I need to create exceptions on the firewall for outbound traffic to these two IP addresses when I do not have to make any exceptions for any other outbound traffic.
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-parent:"";
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin:0in;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:"Times New Roman";
    mso-bidi-theme-font:minor-bidi;}
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-parent:"";
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin:0in;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:"Times New Roman";
    mso-bidi-theme-font:minor-bidi;}
    Here is what I see:
    IPS_Sensor# show stat host
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-parent:"";
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin:0in;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:"Times New Roman";
    mso-bidi-theme-font:minor-bidi;}
    Auto Update Statistics
       lastDirectoryReadAttempt = 09:03:09 GMT-06:00 Wed Jan 19 2011
        =   Read directory: https://198.133.219.25//cgi-bin/front.x/ida/locator/locator.pl
        =   Error: AutoUpdate exception: HTTP connection failed [1,110]
       lastDownloadAttempt = N/A
       lastInstallAttempt = N/A
       nextAttempt = 11:00:00 GMT-06:00 Wed Jan 19 2011 Auxilliary Processors Installed
    IPS_Sensor# show clock
    .09:24:05 GMT-06:00 Wed Jan 19 2011
    I know this thread is a few months old, but am hoping to spark an interest here.
    Thanks.

  • ASA SSM IPS module upgrade won't work

    Hello all,
    I'm trying to upgrade the IPS sig's on an ASA5520 with a SSM IPS module. I'm trying to upgrade the system to 5.1.1 to further upgrade the device with no luck.
    I followed these steps provided by Cisco.com:
    1. Log in to the ASA.
    2. Enter enable mode:
    asa# enable
    3. Configure the recovery settings for ASA-SSM:
    asa (enable)# hw-module module 1 recover configure
    NOTE: If you make an error in the recovery configuration, use the
    hw-module module 1 recover stop command to stop the system reimaging
    and then you can correct the configuration.
    4. Specify the TFTP URL for the system image:
    Image URL [tftp://0.0.0.0/]:
    Example:
    Image URL [tftp://0.0.0.0/]: tftp://10.20.30.40/IPS-SSM-K9-sys-1.1-a-5.1-1.img
    5. Specify the command and control interface of ASA-SSM:
    Port IP Address [0.0.0.0]:
    Example:
    Port IP Address [0.0.0.0]: 11.21.31.41
    6. Leave the VLAN ID at 0.
    VLAN ID [0]:
    7. Specify the default gateway of the ASA-SSM:
    Gateway IP Address [0.0.0.0]:
    Example:
    Gateway IP Address [0.0.0.0]: 11.22.33.44
    8. Execute the recovery:
    asa# hw-module module 1 recover boot
    9. Periodically check the recovery until it is complete.
    NOTE: The status reads "Recovery" during recovery and reads "Up" when
    reimaging is complete.
    AFter #8 it just goes back to the enable prompt. A 'sh module' lists the device as 'recover' and hangs FOREVER.... I tested the TFTP server which the new image resides on, and the TFTP is working fine. I don't see any attempts or downloads from the TFTP server for over an hour.
    I opened a Ciscop TAC on this and not receiving alot of help...
    Please help!!!:)
    Thanks
    Chris Serafin
    [email protected]

    The recovery using this method can takes upwards of 30 minutes, and in some cases even longer.
    How long have you left the SSM in the "recovery" state?
    There may be something wrong in the config you entered. when that happens the SSM can go into a continuous reboot cycle trying to do the recovery.
    Execute "debug module-boot" on the console of the ASA.
    The debug output will show you the ROMMON output of the SSM itself. (The SSM has it's own ROMMON. The recovery boot command sends the settings made during the recover configure command to the SSM's ROMMON).
    If the ROMMON is experiencing a problem in trying to download the tftp image you should now see that ROMMON error message.
    Some typical problems I have seen:
    1) Wrong IP given for the sensor.
    2) Wrong IP given for the gateway (the gateway must exist on the same network as the sensor) this problem usually happens when using a non-standard netmasked network.
    3) Not having the sensor's command and control port plugged into the right network. The external port of the SSM itself is where the IP is being applied. You need to ensure that the extenral port of the SSM is plugged into the right network for that IP.
    4) The tftp server is not reachable from the network where the sensor's command and control port is attached. Some users think that if the ASA itself can reach the tftp server that the SSM will also be able to. This is not always the case. It is best to use a tftp server on the same network as the IP provided to the SSM. Or to test the tftp server from another machine on the same network as the SSM.
    5) The file name is wrong. Check the captialization especially.
    6) The file is not in the default directory on the tftp server. If the file is in a subdirectory you will need to add that subdirectory to the URL:
    tftp://10.20.30.40/subdirectoryname/filename
    7) The tftp is timing out.
    There are 2 things that can cause this:
    a) The tftp server is remote, and it takes too long to download the file. The ROMMON does have limits on the number of retries and per packet timeouts (but they are not user configurable). Try using a tftp server local to the SSM.
    b) The switch that the SSM connects to has spanning-tree running and spanning-tree does not complete before the SSM ROMMON times out for the tftp attempt. The tftp attempt happens immediately upon ROMMON startup and link up. But with a switch the switch port may be in a "Listen" or "Learn" state for 40 seconds before the box can actually talk on the network. In some cases the tftp download attempts started as soon as link up, and may timeout even before the spanning-tree completes. To work around this configure "spanning-tree portfast" on the switchport. Spanning-tree will connect the port into the vlan immediately rather than 40 seconds later.
    If it was a config problem when configuring the recovery settings, then there is a "recover stop" command on the ASA.
    It will stop the reboot cycle from happening.
    Let the module come up with the old image.
    Then correct your "recover configure" settings, and try the "recover boot" again.
    Another alternative:
    Stop the recovery "recover stop"
    Let it boot into the old image.
    If it was a 5.0 version, then you can actually upgrade to 5.1 using the sensor's own CLI "upgrade" command. It is actually the preferred method.
    The "recover" from the ASA will wipe the box clean and load a fresh image.
    The "upgrade" from the sensor will convert your 5.0 config into a 5.1 config while installing 5.1.
    5.1 upgrade file:
    IPS-K9-min-5.1-1g.pkg
    http://www.cisco.com/cgi-bin/tablebuild.pl/ips5
    It can be applied through the sensor's CLI upgrade command, or pushed directly through IDM, or applied by CSM.
    The "recover" should be limited to disaster recovery. When you can't access the SSM at all, or the files on the SSM have been corrupted.
    For normal upgrades you want to use "upgrade" files done through the sensor itelf (CLI, IDM, or CSM).

  • Upgrade IPS moudle on ASA to 6.0.3

    I upgraded the ips module ASA-SSM-20 on the ASA from 5.x to 6.0.3 lately. The ASA are setup as active/standby. i upgraded both modules successfully on each ASA. After the upgrade, i notice the ASA failover to the other partner about 10 times for the past day, particularly when traffic was high. Before the upgrade, i don't have this problem. Anyone run into this problem before, and any idea? thanks.

    Hi, I have the same problem by one our customer. I would like to compare my and your sw versions? We are using Cisco ASA ver 7.0.7GD, I tested it also on versions 7.2.2 and 7.2.3 the result is the same! Do you use also the IPS Firmware version: 1.0(11)2, Software version: 6.0(3)E1? Please could you write out from configuration "show failover state", do you see there also in the field "Last Failure Reason" = IPS Card Failure in both unit? I thing there should be some problem with the new IPS software! If you wish contact me!
    Best regards
    Jakub Chytracek
    [email protected]

  • IPS engine upgrade with failover ASA, now they don't match?

    We recently added a failover 5520 with the ASA-SSM-20, which matches the primary ASA/IPS. My question is I just upgraded the primary IPS to 5.1(5)-E1. It went fine, except now the failover IPS is still on 5.0(2). How do I update the failover IPS to match what's on the primary?
    Shouldn't this happen automatically since it is setup in a failover scenario? I have it cabled via a cross-over cable to the primary ASA.

    The SSM modules are managed completely separately from the firewalls; you need to upgrade & manage both of them individually, as well as apply the same configurations to each either separately, or via a group in either CSM or VMS...
    If the second SSM module hasn't been given its own IP, you can "session" into it from the standby firewall console and then give it it's own IP..
    If this helped, please rate the post :-)
    Thanks!
    ...Nick

  • IPS Signature DataBase - ASA IPS/IOS IPS/IPS 42xx/AIP-SSM

    Hi,
    Can anyone briefly tell me the signature database details (No of Signature) among the following devices,
    -->ASA IPS/IOS IPS/IPS 42xx/AIP-SSM.
    Thanks,

    IPS on ASA/PIX = just 50 or so common signatures
    AIP-SSM module = same signatures as Cisco 4200 series sensors. Little minor differences exist (like IPv6 signature support etc.)
    Please rate if helpful.
    Regards
    Farrukh

  • Upgrade ASA-SSM-10 via FTP

    Hi all,
    I am trying to upgrade an ASA-SSM-10 running version 5.1 software.
    I have set up an FTP server using Serv-u and can connect to it successfully.
    When I attempt to upgrade using the following command, I get the error below.
    sensor(config)# upgrade ftp://[email protected]//IPS/IPS-K9-6.0-3-E1.pkg
    The filename IPS-K9-6.0-3-E1.pkg is not a valid upgrade file type.
    Continue with upgrade? []: yes
    Error: execUpgradeSoftware : Connect failed
    I have tried 2 FTP servers and receive the same error I have tried 4 upgrade packages and receive the same error.
    Does anyone have any advice on how to fix this issue.
    Thank you
    Greg

    Your upgrade commands look correct. http://www.cisco.com/en/US/docs/security/ips/6.0/configuration/guide/cli/cliImage.html#wp1243115
    I've had some problems with Serv-U in the past year or so. I had to switch to FileZilla to perform my last upgrade.
    http://filezilla-project.org/
    - Bob

  • Monitor Inspection Load IPS ASA-SSM-20

    All,
      I am aware there is a feature request but don't see any updates.  Taking the chance here that its fallen through the cracks and someone has figured out another way to monitor inspection load on ASA-SSM-20 IPS.  We are currently running 7.0(5a)E4.  I want to be able to use Solarwinds Orion to monitor Inspection Load on our IPS devices.  Does anyone know if that is yet possible...if so how?
    Thanks!

    Bump +1

  • Update ASA-SSM-CSC-10 module

    Hi,
    I'm not able to update (reinstall) a ASA-SSM-CSC-10 module. I used the CLI-Command : "hw module 1 recover boot". But the module is still in the Recover-mode.
    Output from CLI (I used the image: csc6.1-b1519.bin):
    Slot-1 890> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    Slot-1 891> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    Slot-1 892> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    Slot-1 893> Received 59944272 bytes
    Slot-1 894> Launching TFTP Image...
    sclfw002# sh module
    Mod Card Type Model Serial No.
    0 ASA 5510 Adaptive Security Appliance ASA5510 JMX1032K16L
    1 ASA 5500 Series Content Security Services Mo ASA-SSM-CSC-10 JAF10290481
    Mod MAC Address Range Hw Version Fw Version Sw Version
    0 0018.195b.e68d to 0018.195b.e691 1.1 1.0(11)2 7.2(1)
    1 0018.7317.b44a to 0018.7317.b44a 1.0 1.0(11)2
    Mod SSM Application Name Status SSM Application Version
    Mod Status Data Plane Status Compatibility
    0 Up Sys Not Applicable
    1 Recover Not Applicable
    Could anybody help me?
    thanks
    Reto

    Are you able to stop the recovery from continuously running? Use "hw-module module 1 recover stop" to end it. Then try to reset it again (hw-module module 1 reset).
    If the module become unresponsive due to too long running in recover mode, big chances you need to reset the ASA. But try to reset/shut it down via ASA CLI first before decide to shutdown/powerup the whole box. This may be inevitable. During shutdown, remove the module, and power-up the ASA. Insert the module once the ASA is properly running, and check the status/mode again.
    Start the boot recovery process again, recover configure if necessary. If you need to stop it, issue "hw-module module 1 recover stop" within 45sec after the recover boot/configure started.
    HTH
    AK

Maybe you are looking for