WAAS alarm simulation

Hi team,
one theoretical question:
is there any way how to simulate (generate) the following WAAS alarms in the lab enviroments, please ?
•             Disk early-prediction failure
•             Disk failure
•             Cache disk full
•             Cache disk overloaded
•             TFO overloaded (TCP connection limit reached)
•             Alarm overload state
I believe that traffic generator will not help here as it cannot generate enough TCP sessions.
Many thanks!
Regards,
Stan

Hi Stan,
For the Disk Failure alarm, you can simply remove a disk from your appliance and it should trigger it.
The rest of them will be difficult to trigger at will.
For the TFO overloaded, a simple script that spawns telnet sessions through the WAAS should allow you to reach this state. To see how many you would need, you can have a look at the "sh tfo detail" output.
Hope this helps.
Regards,
Nicolas

Similar Messages

  • What IOS file to use for upgrading WAAS?

    I've got several 7341s, 522s, and 612s all running 4.17 (waas-4.1.7.11-K9.bin).  I'd like to upgrade to the new 4.2.3, but there are now four different codes; ie. waas-accelerator-4.2.3.7-K9, waas-accerlator-4.2.3.7-npe-K9, waas-universal-4.2.3.7-K9, waas-universal-4.2.3.7-npe-K9. Which ones do I use? Is there a matrix somewhere that describes the different code types?

    Here is the URL for the file name breakdown.
    http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v423/release/notes/ws423xrn.html#wp90088
    Standard Image Files
    WAAS software version 4.2.3 includes the following standard primary software image files:
    •waas-universal-4.2.3.7-k9.bin—Universal  software image that includes Central Manager and Application  Accelerator functionality. You can use this type of software file to  upgrade either a Central Manager or an Application Accelerator device.
    •waas-accelerator-4.2.3.7-k9.bin—Application  Accelerator software image that includes Application Accelerator  functionality only. You can use this type of software file to upgrade  only an Application Accelerator device, including those on a WAAS on  SM-SRE module. This software image file is significantly smaller than  the Universal image. Kdump analysis functionality is not included in the  Accelerator-only image.
    •waas-sre-installer-4.2.3.7-k9.zip—SM-SRE  install zip file that includes all the files necessary to install WAAS  on the SM-SRE module.
    The following additional files are also included:
    •waas-rescue-cdrom-4.2.3.7-k9.iso—WAAS software recovery CD image.
    •waas-x86_64-4.2.3.7-k9.sysimg—Flash memory recovery image for 64-bit platforms (WAVE-274/474/574 and WAE-674/7341/7371 devices).
    •waas-4.2.3.7-k9.sysimg—Flash memory recovery image for 32-bit platforms (all other devices).
    •waas-kdump-4.2.3.7-k9.bin—Kdump analysis component that you can install and use with the Application Accelerator software image.
    •waas-alarm-error-books-4.2.3.7.zip—Contains the alarm and error message documentation. No Payload Encryption (NPE) Image Files
    WAAS software version 4.2.3 includes NPE primary software image files  that have the disk encryption feature disabled. These images are  suitable for use in countries where disk encryption is not permitted.  NPE primary software image files include the following:
    •waas-universal-4.2.3.7-npe-k9.bin—Universal  NPE software image that includes Central Manager and Application  Accelerator functionality. You can use this type of software file to  upgrade either a Central Manager or an Application Accelerator device.
    •waas-accelerator-4.2.3.7-npe-k9.bin—Application  Accelerator NPE software image that includes Application Accelerator  functionality only. You can use this type of software file to upgrade  only an Application Accelerator device, including those on a WAAS on  SM-SRE module. This software image file is significantly smaller than  the Universal image. Kdump analysis functionality is not included in the  Accelerator only image.
    •waas-sre-installer-4.2.3.7-npe-k9.zip—SM-SRE  install zip file that includes all the NPE files necessary to install  WAAS on the SM-SRE module.
    The following additional files are also included:
    •waas-rescue-cdrom-4.2.3.7-npe-k9.iso—WAAS NPE software recovery CD image.
    •waas-x86_64-4.2.3.7-npe-k9.sysimg—Flash  memory NPE recovery image for 64-bit platforms (WAVE-274/474/574 and  WAE-674/7341/7371 devices).
    •waas-4.2.3.7-npe-k9.sysimg—Flash memory NPE recovery image for 32-bit platforms (all other devices).
    •waas-kdump-4.2.3.7-npe-k9.bin—NPE  Kdump analysis component that you can install and use with the  Application Accelerator software image.
    •waas-alarm-error-books-4.2.3.7-npe.zip—Contains the NPE alarm and error message documentation.
    Thanks
    Eric Rose

  • WAAS WAE Alarm 'mstore_key_retrieval'

    Hello,
    I am supporting an environment that has 30+ remote WAEs deployed with a CM at the HQ.
    All remote WAE's Versions = Cisco Wide Area Application Services (universal-k9) Software Release 4.2.3b (build b4 Oct  4 2010)
    HQ's CM version = Cisco Wide Area Application Services (universal-k9) Software Release 4.4.3 (build b4 Aug 22 2011)
    On 4 of these WAEs, I currently am receiving encryption key alarms:
    WAE#show alarms detail support
    Critical Alarms:
            Alarm ID                 Module/Submodule               Instance
       1 mstore_key_retrieval      cms                          ssl_mstore_key          
         Apr 11 18:36:16.026 CDT, Processing Error Alarm, #000002, 3000:700008
         Unable to generate and/or retrieve SSL managed store encryption key from the Key Manager
         /alm/crit/cms/mstore_key_retrieval_failure:
             CMS/Management agent failed to generate and/or retrieve SSL managed store encryption key from Key Manager.
         Explanation:
             This alarm indicates one of following issues: Central
             Manager device(s) is not reachable.  Secure store on
             Central Manager is initialized but not open.  Key Manager
             process on Central Manager device is not running or failing
             to respond.  Key Manager is unable to process key
             generation or retrieval request.   If this issue is
             present, the WAE device will not be able to process  a
             configuration update received from the Central Manager if
             it  contains SSL certificate/key information.
         Action:
             Check if Central Manager device is reachable (TCP
             connections from the WAE to the Central Manager on port
             443) Check following log files for additional information
             about the error: /local1/errorlog/kc.log on WAE
             /local1/errorlog/km/km.log on CM
       2 mstore_key_failure        sslao                        mstore_key_failure      
         Apr 11 18:39:07.518 CDT, Processing Error Alarm, #000006, 26000:26002
         Failed to open SSL store due to failure in getting key from Central Manager.
         /alm/crit/sslao/mstore_key_failure:
             SSL managed secure store key retrieval failure.
         Explanation:
             The SSL accelerator is unable to get the SSL secure store
             key from the Central Manager.
         Action:
             Check the connection with the Central Manager.
    The explanations and actions match the alarm book , but in addition to that, in the Cisco WAAS Monitoring Guide, it also states:
    Alarm 700008 (mstore_key_retrieval_failure) CMS/Management agent failed to generate and/or retrieve SSL managed store encryption key from Key Manager.
    Severity: Critical
    Category: Processing
    Description: This alarm indicates one of following issues:
    –The WAAS Central Manager device is not reachable
    –Secure store on WAAS Central Manager is initialized but not open
    –The Key Manager process on the WAAS Central Manager device is not running or failing to respond
    –Key Manager cannot process key generation or retrieval request. If this issue is present, the WAAS device cannot process a configuration update received from WAAS Central Manager if it contains SSL certificate and key pair information.
    Action: Check to see if the WAAS Central Manager device is reachable (TCP connections from the WAE to the WAAS Central Manager on port 443). Check the following log files for additional information about the error:
    –On WAE: /local1/errorlog/kc.log on WAE
    –On WAAS Central Manager: /local1/errorlog/km/km.log
    Action: Fix the clock on the device or the primary WAAS Central Manager.
    For a complete list of alarm conditions, see the Alarm Book located in the WAAS 4.2.1 Software Download area on Cisco.com.
    Using this information, I've checked the following:
    TCP 443 is reachable from the WAE to the CM (I can telnet from each WAE to the CM on TCP 443)
    Time is correct on the WAEs and CM ('show ntp status' and 'show clock' are consistent)
    Secure store on CM is open ('show cms secure-store' on the CM shows that the mode is in 'Open' state),
    Verified that the key manager process is running (Looking at the CM's KM log shows plenty of action that it's working for other WAEs)
    Here is some information I gathered from the WAEs' kc.log files and the CM's km.log (slightly scrubbed):
    From the WAEs' kc.log files:
    pool-1-thread-1] INFO  CommClientAbstractRPC - Send key retrieval request to CM 10.x.x.x for token d1b77e45-ce60-4332-a92d-3d3cb17d35cf
    pool-1-thread-1] WARN  CommClientAbstractRPC - Received error response from KM(20,No key found for token d1b77e45-ce60-4332-a92d-3d3cb17d35cf from device 17111)
    From the CM's km.log file:
    [pool-1-thread-4] INFO - retrieveKey request, token=d1b77e45-ce60-4332-a92d-3d3cb17d35cf from device WAE1/17111
    [pool-1-thread-4] INFO - Checking secure store open
    [pool-1-thread-4] INFO - Loading KEK from data server
    [pool-1-thread-4] INFO - ticket 17111 (1327767406332, 1327767392433, 13899, 10000)
    [pool-1-thread-4] WARN - No key found for token d1b77e45-ce60-4332-a92d-3d3cb17d35cf from device 17111
    *** Going through these logs, I've seen other devices have the same issue, and eventually a WAE records the following:
    [main] ERROR DeviceInfo - /state/node.dat (No such file or directory)
    java.io.FileNotFoundException: /state/node.dat (No such file or directory)
    at java.io.FileInputStream.open(Native Method)
    at java.io.FileInputStream.<init>(Unknown Source)
    at java.io.FileInputStream.<init>(Unknown Source)
    at com.cisco.waas.kc.DeviceInfo.retrieveNodeInfo(DeviceInfo.java:65)
    at com.cisco.waas.kc.DeviceInfo.<init>(DeviceInfo.java:47)
    at com.cisco.waas.kc.DeviceInfo.getInstance(DeviceInfo.java:37)
    at com.cisco.waas.kc.comm.CommClientAbstractRPC.retrieveKey(CommClientAbstractRPC.java:149)
    at com.cisco.waas.kc.RetrieveKeyCommand.execute(RetrieveKeyCommand.java:43)
    at com.cisco.waas.cli.CLICommand.execute(CLICommand.java:114)
    at com.cisco.waas.cli.AbstractCLI.process(AbstractCLI.java:28)
    at com.cisco.waas.kc.KeyClient.main(KeyClient.java:40)
    [main] ERROR DeviceInfo - /state/node.dat (No such file or directory)
    java.io.FileNotFoundException: /state/node.dat (No such file or directory)
    at java.io.FileInputStream.open(Native Method)
    at java.io.FileInputStream.<init>(Unknown Source)
    at java.io.FileInputStream.<init>(Unknown Source)
    at com.cisco.waas.kc.DeviceInfo.retrieveNodeInfo(DeviceInfo.java:65)
    at com.cisco.waas.kc.DeviceInfo.<init>(DeviceInfo.java:47)
    at com.cisco.waas.kc.DeviceInfo.getInstance(DeviceInfo.java:37)
    at com.cisco.waas.kc.comm.CommClientAbstractRPC.initKey(CommClientAbstractRPC.java:40)
    at com.cisco.waas.kc.InitKeyCommand.execute(InitKeyCommand.java:40)
    at com.cisco.waas.cli.CLICommand.execute(CLICommand.java:114)
    at com.cisco.waas.cli.AbstractCLI.process(AbstractCLI.java:28)
    at com.cisco.waas.kc.KeyClient.main(KeyClient.java:40)
    *** Followed with what appears to be a new SSL key being generated ***:
    [main] INFO  DeviceInfo - loaded device info, hash  H04Fer5il3b/9oanDZXx/7aBnIo=
    [pool-1-thread-1] DEBUG CMProber$ProbeWorker - Sending CM probe request to CM 10.x.x.x
    [pool-1-thread-1] DEBUG CMProber$ProbeWorker - CM 10.x.x.x returned :primary:4.4.3.0.4
    [pool-1-thread-1] DEBUG CMProber$ProbeWorker - Primary CM address 10.x.x.x version 4.4.3.0.4
    [main] DEBUG CommClientAbstractRPC - CM version 4.4.3
    [main] INFO  CommClientAbstractRPC - Send key initialization request to CM 10.x.x.x key type SSL
    [main] INFO  CommClientAbstractRPC - Received new token for generated key SSL/cbe3d6fc-875e-4b61-baeb-528c55cb3597
    [main] INFO  DeviceInfo - loaded device info, hash  H04Fer5il3b/9oanDZXx/7aBnIo=
    [pool-1-thread-1] INFO  CommClientAbstractRPC - Send key retrieval request to CM 10.0.65.234 for token cbe3d6fc-875e-4b61-baeb-528c55cb3597
    [main] INFO  CommClientAbstractRPC$1 - Successfully retrieved key from CM for token cbe3d6fc-875e-4b61-baeb-528c55cb3597
    *** And the CM records the following ***:
    [pool-1-thread-4] INFO - initKey request from device WAE2/30129 key type SSL
    [pool-1-thread-4] INFO - Checking secure store open
    [pool-1-thread-4] INFO - Loading KEK from data server
    [pool-1-thread-4] INFO - Return crypto of type : 0
    [pool-1-thread-4] INFO - Checking secure store open
    [pool-1-thread-4] INFO - Loading KEK from data server
    [pool-1-thread-4] INFO - Loading KEK from data server
    [pool-1-thread-4] INFO - Generated new key WAE2/SSL token cbe3d6fc-875e-4b61-baeb-528c55cb3597
    I'm wanting to know why this occurs on some boxes and not others, and what triggers the process for a WAE to stop repeatedly sending key retrieval requests with a token that the CM has repeatedly replies with the key not being found and performing an initial key request.
    Thanks!

    Hi all, I got into the same issue and looking at a solution I found a way to clear those alarms whithout re-registering the WAE/WAVE. Here it goes...
    WAE##sh accelerator
    Accelerator     Licensed        Config State    Operational State
    cifs            Yes             Enabled         Running
    epm             Yes             Enabled         Running
    http            Yes             Enabled         Running
    mapi            Yes             Enabled         Running
    nfs             Yes             Enabled         Running
    ssl             Yes             Enabled         Disabled  ---> your SSL AO is probably down due the issue
    video           No              Enabled         Shutdown
    WAE#sh alarms
    Critical Alarms:
            Alarm ID                 Module/Submodule               Instance
       1 mstore_key_retrieval      cms                          ssl_mstore_key
       2 mstore_key_failure        sslao                        mstore_key_failure
    Major Alarms:
    None
    Minor Alarms:
    None
    WAE#crypto pki managed-store initialize
    All certificate/private keys in SSL managed store will be deleted and optimized SSL traffic will be interrupted. Are you sure you want to continue(yes/no)? [no]:yes
    Restarting SSL accelerator. Done.
    After a couple of minutes alarms will be cleared and SSLAO will be back UP.
    WAE#sh accelerator
    Accelerator     Licensed        Config State    Operational State
    cifs            Yes             Enabled         Running
    epm             Yes             Enabled         Running
    http            Yes             Enabled         Running
    mapi            Yes             Enabled         Running
    nfs             Yes             Enabled         Running
    ssl             Yes             Enabled         Running
    video           No              Enabled         Shutdown
    WAE#sh alarms
    Critical Alarms:
    None
    Major Alarms:
    None
    Minor Alarms:
    None
    In case you have the issue in the Core WAE (where the cms secure-store is opened), you might need to initialize it.
    Regards,
    Fernando

  • How to delete the alarm "Certificate is near expiration" on multiple WAEs using WAAS CM

    Hi,
    We are getting "Certificate is near expiration" alarm on more than  200 WAEs . Instead of deleting the expired certificates manually from each device,
    how to delete this alarms/certificates on all the devices from WAAS CM ?
    Please advice..
    Regards,
    Ameen.

    Ameen,
    I believe there is script that you could use to address this issue on multiple devices at once.
    Please open a TAC case so that TAC Engineer would assist with this.
    For a single WAE, it is documented here.
    https://supportforums.cisco.com/thread/2010020
    Thanks
    Anil

  • Waas 594 dre-cache full alarm

    One of our appliances is having this major alarm!
    Major Alarms:
            Alarm ID                 Module/Submodule               Instance
       1 disk_full                 DRE
         Sep 15 01:41:41.880 UTC, Equipment Alarm, #000018, 11000:690481
         Cache disk is full
         /alm/maj/DRE/disk_full:
             Cache disk is full.
         Explanation:
             The actual size of the DRE file system is less than the
             assigned disk space size for DRE. This is a system
             configuration error.
         Action:
             Check disk allocation for DRE and DRE file system size.
             Assigned DRE disk space in the 'show dre' CLI output is
             shown as Total DRE cache diskspace. The DRE file system
             size is shown in the show disk detail CLI output as mount
             point /dre1 with CONTENT type.
                 Useful commands:
                    show dre
                    show statistics dre detail
                    sh disks detail
                    disk config
    I cannot see the dre partition in sh disk details
    Mounted file systems:
     MOUNT POINT    TYPE       DEVICE                  SIZE     INUSE      FREE USE%
    /sw            internal   /dev/md0               1983MB     828MB    1155MB  41%
    /swstore       internal   /dev/md1               1983MB     851MB    1132MB  42%
    /state         internal   /dev/md2               5951MB     248MB    5703MB   4%
    /local/local1  SYSFS      /dev/md4              14878MB     630MB   14248MB   4%
    /vbspace       GUEST      /dev/data1/vbsp      173588MB     128MB  173460MB   0%
    /state/likewise/sw
                   internal   /dev/md0               1983MB     828MB    1155MB  41%
    /state/likewise/local/local1
                   internal   /dev/md4              14878MB     630MB   14248MB   4%
    /local/local1/spool
                   PRINTSPOOL /dev/data1/spool        991MB      32MB     959MB   3%
    /obj1          CONTENT    /dev/data1/obj       101177MB     972MB  100205MB   0%
    /ackq1         internal   /dev/data1/ackq        1189MB       0MB    1189MB   0%
    /plz1          internal   /dev/data1/plz         2379MB       1MB    2378MB  
    Any ideas? please advise and thanks!
    Regards

    Hi again,
    Yes you should follow the procedure outlined in step 10,11,12 & 13 as described here :
    http://www.cisco.com/c/en/us/td/docs/app_ntwk_services/waas/wave/installation/594-694/guide/WAVE-594_HIG/594op2.html#wp1056708
    Otherwise the DRE process doesn't know the correct amount of disk space.
    Please be aware that the DRE cache & CIFS cache (and other saved information) is deleted.
    Best regards
    Finn Poulsen

  • WAAS conection limit alarm

    Hi,
    I have a waas solution implemented, where the both (Datacenter and Edge) are in inline mode. The WAE in Datacenter side is viewing all connections from the others sites of the WAN where there is not a WAE in there, so that connections are in PT becouse "Not Peer".
    These days we started to see a minor alarm: "1 max_conn_overload sysmon accl=TFO". We don't see this alarm from the Edge WAE, only from Datacenter WAE.
    Could be that DC WAE takes in account the PT connections? if the answer is yes, Can this overload make that the WAE stop the optimization when new connections arrive until the number of connections go down?
    Thanks in advanced!!!
    Celeste
    These days we started to see a minor alarm: "1 max_conn_overload sysmon accl=TFO". We don't see this alarm from the Edge WAE, only from Datacenter WAE.
    Could be that DC WAE take in account the PT connections? if the answer is yes, Can this overload makes that the WAE stops the optimization when new connections arrive until the number of connections goes down?

    Thanks for the update, can you check one more thing on your WAE-Tronador box? can you do the following command?
    find-pattern match "Routing Loop" syslog.txt
    We are looking for the following enteries similar to "opt_syn_rcv: Routing Loop
    detected - Packet has our own devid. Packet dropped."
    Also, do "sh stat auto" and look for the entry:
    Auto discovery Miscellaneous
    SYNs found with our device id: XX
    If you see that counter incrementing, you may be hitting DDTS: CSCsx68058 "Routing loops at the core can cause TFO overload on the WAE " If this is the case, then you need to inspect you interception at the core to ensure that you are not re-intercepting traffic egressing the WAE on the router.
    Let me know if this is the case or we can keep searching.
    Thanks,
    Dan

  • Configuring WAN Simulator with WAAS

    Hi all,
    I have a remote site in Pune India and I am trying to set up a WAN simulator to simulate the WAN link with WAAS to Pune. Below is the topology and questions.
    Server farm <-- WAN simulator PC --> 3750 layer 3 switch <-- client PCs
    Questions:
    1 - Where would I place the WAAS device ?
    2 - I only have one spare WAE for this test. Can this scenario work with only one WAE ? or do I need two WAEs (one on each side) for WAAS to work ?
    3 - Do I need a Central Controller for WAAS to function ?
    Thanks in advance !!! I appreciate any inputs / suggestions !!
    Danny

    Hi Danny,
    On the second WAE, you need to configure WCCP just like its configured on first WAE. And WCCP will
    redirect traffic to both of these WAE's.
    There are Two Algorithms for redirecting traffic,
    - Hash
    - Mask
    WCCP intercepted traffic is forwarded to WAE based on bucket placement algorithm, hashing or masking with
    IP addresses.
    This link explains on wccp redirection,
    http://www.cisco.com/en/US/docs/solutions/Enterprise/Data_Center/WAASDC11.html#wp95583
    Attached pdf file explains in detail on wccp and redirection methods,
    Hope this helps,
    Best Regards,
    Rahul

  • Major Alarm: WAE clock needs to be synchronized with the primary CM to make time-sensitive features like statistics, status monitoring and event scheduling work correctly.

    Hi all,
    Although all the edges and CM have the same ntp configuration , I still have this  major alarm on three Edge-WAAS even after synchronization .
    Is it possible to learn more about this - what caused it, ect.
    Any ideas on how to proceed? (software version 4.1.3.b)

    Excuse my english , i'm not native speaker .
    Alarm doesn't disappear  even after 24 h from the synchronization .
    These are the outputs of commands entered in the same time on the WAE and the CM :
    Output on the WAE :
    Edge-BrancheOffice#sh  alarm
    Critical Alarms:
    None
    Major Alarms:
         Alarm ID             Module/Submodule     Instance
       1 cms_clock_alarm      cms                                     
    Minor Alarms:
    None
    Edge-BrancheOffice#sh clock
    Local time: Fri Feb  1 10:42:07 GMT 2013
    Edge-BrancheOffice#sh ntp stat
    ntp enabled
    ntp authentication disabled
    server list:
    Server           Key
    192.168.6.7      -
         remote           refid                st t when poll reach   delay   offset  jitter
    ==============================================================================
    192.168.6.7     192.168.6.6      3 u  112  128  375  245.491  13739.6   5.756
    Edge-BrancheOffice#
    Output on the CM :
    CM-manager#sh clock
    Local time: Fri Feb  1 10:30:36 GMT 2013
    CM-manager#sh ntp stat
    ntp enabled
    ntp authentication disabled
    server list:
    Server           Key
    192.168.6.7      -
         remote           refid           st t   when   poll   reach     delay      offset        jitter
    ==============================================================================
    192.168.6.7    192.168.6.6      3 u    -       128  377      0.608      713549.     20.935
    CM-manager#
    Thank you .

  • WAAS - Disk Space Error

    Hi all,
    Is this Syslog Error Message affecting statistics in % Compression?
    What is the cause of this ? It is tunned, or should be automaticaly resolved?
    Best Regards,
    Bruno Petrónio
    *** Output ***
    2009 Jul 30 11:33:13 wae so_dre: %WAAS-RE-3-690464: (74488:2) RE File Manager error: filemgr_state::do_io (segments) call pwrite(90, 0x51e7e008, 65536, 68485120): No space left on device
    2009 Jul 30 11:33:13 wae so_dre: %WAAS-RE-3-690432: (74673:2) FileMgr failed in writing data-segment start at id=834779, error=0xfffffc09--Disk is full
    2009 Jul 30 11:33:13 wae so_dre: %WAAS-RE-3-690464: (112823:2) RE File Manager error: filemgr_state::do_io (segments) call pwrite(90, 0x5140e008, 65536, 69271552): No space left on device
    2009 Jul 30 11:33:13 wae so_dre: %WAAS-RE-3-690432: (112995:2) FileMgr failed in writing data-segment start at id=834791, error=0xfffffc09--Disk is full
    wae#show disks details
    Physical disk information:
    disk00: Present WD-WCANY3489733 (h02 c00 i00 l00 - Int DAS-SATA)
    238472MB(232.9GB)
    disk01: Present WD-WCANY3489714 (h02 c00 i01 l00 - Int DAS-SATA)
    238472MB(232.9GB)
    Mounted file systems:
    MOUNT POINT TYPE DEVICE SIZE INUSE FREE USE%
    /sw internal /dev/md0 991MB 912MB 79MB 92%
    /swstore internal /dev/md1 991MB 459MB 532MB 46%
    /state internal /dev/md2 5951MB 191MB 5760MB 3%
    /local/local1 SYSFS /dev/md4 11903MB 601MB 11302MB 5%
    .../local1/spool PRINTSPOOL /dev/data1/spool 991MB 32MB 959MB 3%
    /obj1 CONTENT /dev/data1/obj 125975MB 1013MB 124962MB 0%
    /dre1 CONTENT /dev/data1/dre 59515MB 59514MB 1MB 99%
    /ackq1 internal /dev/data1/ackq 1189MB 32MB 1157MB 2%
    /plz1 internal /dev/data1/plz 2379MB 65MB 2314MB 2%
    Software RAID devices:
    DEVICE NAME TYPE STATUS PHYSICAL DEVICES AND STATUS
    /dev/md0 RAID-1 NORMAL OPERATION disk00/00[GOOD] disk01/00[GOOD]
    /dev/md1 RAID-1 NORMAL OPERATION disk00/01[GOOD] disk01/01[GOOD]
    /dev/md2 RAID-1 NORMAL OPERATION disk00/02[GOOD] disk01/02[GOOD]
    /dev/md3 RAID-1 NORMAL OPERATION disk00/03[GOOD] disk01/03[GOOD]
    /dev/md4 RAID-1 NORMAL OPERATION disk00/04[GOOD] disk01/04[GOOD]
    /dev/md5 RAID-1 NORMAL OPERATION disk00/05[GOOD] disk01/05[GOOD]
    Disk encryption feature is disabled.
    wae# sho disks failed-disk-id
    Disk location Serial Number
    wae# sho disks failed-sectors
    disk00
    =========
    (none)
    disk01
    =========
    (none)
    wae#

    Thank You very much Zach,
    It seems to be the case.
    It was a Demo in a client, which in some time we decide to upgrade the memory, cause a persistent tfo limition alarm.
    The final results were not good about % of Optimization and Compression/Traffic Reduction.
    But, what the hell, we are always learning !
    Thanks a lot.
    Bruno Petrónio

  • WCCP missing assignment alarm for service id

    Hello
    our central manager frequently reports for one WAE
    WCCP missing assignment alarm for service id: 62.
    WCCP missing assignment alarm for service id: 61.
    But the WAE seems to run nornal and we can't find eny problem and event on the WAE (7341 device). By screening the CCO documentaion we also couldn't find any explanation for this error log.
    We have an installation with app. 30 WAEs/WAVEs in with software release 4.2.3. 
    Could you please provide us some hints for troubleshooting.
    Many thanks in advance!

    Hello
    I have the same issue and I noticed when we install a new location with two waves and wccp, it has for some reason an impact on exicting waves running in wccp mode:
    the alarm ''WCCP missing assignment alarm for service id: 61 or 62'' riased on locations that were already in production.
    new location : 192.168.X.21 is one of  the new wave, 192.168.X.219 is the 2nd wave.A.B.C.D is the router loopback ip address
    A.B.C.D
    Existing waves (on different locations) already running in WCCP are : 192.168.Y.64.
    Router (192.168.M.52) for another location where waves : 192.168.M.50 & 192.168.M.52 are already in service: Loopback ip is E.F.G.H
    any idea why configuring wccp in one location has an impact on other locations
    thnak you in advance
    2011 Dec 14 08:55:41 N064WAP1009 wccp: %WAAS-WCCP-5-500008: A new view from the router 192.168.M.52 with the given change number: 12. Service 61.2011 Dec 14 08:55:41 N064WAP1009 wccp: %WAAS-WCCP-5-500012: New router notified. Rtr_Id A.B.C.D for service 61.2011 Dec 14 08:55:41 N064WAP1009 wccp: %WAAS-WCCP-5-500014: New device notified 192.168.X.219 for service 61.2011 Dec 14 08:55:41 N064WAP1009 wccp: %WAAS-WCCP-5-500026: New entry being created for 192.168.X.219 is seen by router A.B.C.E for service 61.2011 Dec 14 08:55:41 N064WAP1009 wccp: %WAAS-WCCP-5-500008: A new view from the router 192.168.M.52 with the given change number: 12. Service 62.2011 Dec 14 08:55:41 N064WAP1009 wccp: %WAAS-WCCP-5-500012: New router notified. Rtr_Id A.B.C.D for service 62.2011 Dec 14 08:55:41 N064WAP1009 wccp: %WAAS-WCCP-5-500014: New device notified 192.168.X.219 for service 62.2011 Dec 14 08:55:41 N064WAP1009 wccp: %WAAS-WCCP-5-500026: New entry being created for 192.168.X.219 is seen by router A.B.C.E for service 62.2011 Dec 14 08:55:54 N064WAP1009 wccp: %WAAS-WCCP-5-500008: A new view from the router 192.168.M.52 with the given change number: 13. Service 61.2011 Dec 14 08:55:54 N064WAP1009 wccp: %WAAS-WCCP-5-500014: New device notified 192.168.X.21 for service 61.2011 Dec 14 08:55:54 N064WAP1009 wccp: %WAAS-WCCP-5-500026: New entry being created for 192.168.X.21 is seen by router A.B.C.E for service 61.2011 Dec 14 08:55:54 N064WAP1009 wccp: %WAAS-WCCP-5-500008: A new view from the router 192.168.M.52 with the given change number: 13. Service 62.2011 Dec 14 08:55:54 N064WAP1009 wccp: %WAAS-WCCP-5-500014: New device notified 192.168.X.21 for service 62.2011 Dec 14 08:55:54 N064WAP1009 wccp: %WAAS-WCCP-5-500026: New entry being created for 192.168.X.21 is seen by router A.B.C.E for service 62.2011 Dec 14 08:56:09 N064WAP1009 wccp: %WAAS-WCCP-4-500016: No assignment sent: 192.168.Y.64 is not seen by all routers for service 612011 Dec 14 08:56:09 N064WAP1009 wccp: %WAAS-WCCP-4-500016: No assignment sent: 192.168.Y.64 is not seen by all routers for service 622011 Dec 14 08:58:55 N064WAP1009 wccp: %WAAS-WCCP-3-500078: Raising WCCP missing assignment alarm: WCCP missing assignment alarm for service id: 61.2011 Dec 14 08:58:55 N064WAP1009 wccp: %WAAS-WCCP-3-500078: Raising WCCP missing assignment alarm: WCCP missing assignment alarm for service id: 62.2011 Dec 14 08:59:03 N064WAP1009 wccp: %WAAS-WCCP-5-500008: A new view from the router 192.168.M.52 with the given change number: 14. Service 61.2011 Dec 14 08:59:03 N064WAP1009 wccp: %WAAS-WCCP-5-500008: A new view from the router 192.168.M.52 with the given change number: 14. Service 62.2011 Dec 14 08:59:19 N064WAP1009 wccp: %WAAS-WCCP-4-500016: No assignment sent: 192.168.Y.64 is not seen by all routers for service 612011 Dec 14 08:59:19 N064WAP1009 wccp: %WAAS-WCCP-4-500016: No assignment sent: 192.168.Y.64 is not seen by all routers for service 622011 Dec 14 08:59:31 N064WAP1009 wccp: %WAAS-WCCP-5-500028: Removing web cache 192.168.X.21 due to timeout for service 61.2011 Dec 14 08:59:31 N064WAP1009 wccp: %WAAS-WCCP-5-500028: Removing web cache 192.168.X.21 due to timeout for service 62.2011 Dec 14 09:01:53 N064WAP1009 wccp: %WAAS-WCCP-5-500008: A new view from the router 192.168.M.52 with the given change number: 15. Service 61.2011 Dec 14 09:01:53 N064WAP1009 wccp: %WAAS-WCCP-5-500014: New device notified 192.168.X.21 for service 61.2011 Dec 14 09:01:53 N064WAP1009 wccp: %WAAS-WCCP-5-500026: New entry being created for 192.168.X.21 is seen by router E.F.G.H for service 61.2011 Dec 14 09:01:53 N064WAP1009 wccp: %WAAS-WCCP-5-500008: A new view from the router 192.168.M.52 with the given change number: 15. Service 62.2011 Dec 14 09:01:53 N064WAP1009 wccp: %WAAS-WCCP-5-500014: New device notified 192.168.X.21 for service 62.2011 Dec 14 09:01:53 N064WAP1009 wccp: %WAAS-WCCP-5-500026: New entry being created for 192.168.X.21 is seen by router E.F.G.H for service 62.2011 Dec 14 09:02:09 N064WAP1009 wccp: %WAAS-WCCP-4-500016: No assignment sent: 192.168.Y.64 is not seen by all routers for service 612011 Dec 14 09:02:09 N064WAP1009 wccp: %WAAS-WCCP-4-500016: No assignment sent: 192.168.Y.64 is not seen by all routers for service 62

  • Displaying strings in a table from boolean alarms.

    Hello all.  I have been using Labeled 8.5 now for about 6 months.  I absolutely love NI because of all the support and forum discussion that exists compared to other software makers I have used in the past.
    Here is my concern.  I have been giving the task of updating this old system and its software to LabVIEW.  What I do is read about 100 alarm bits from a PLC.  Each alarm will have a string attached describing what the alarm is in plain english.  What I need to do using LabVIEW is then display numerous things.  If no alarms are triggered, then nothing will be shown.  If an alarm has been triggered (boolean), show the alarm code (string), the string describing it (string), if it is still triggered (boolean), has it been acknowledged (boolean), a date stamp, and a time stamp. 
    Now what I am stuck on.  I have spent a few weeks trying to come up with a logical way of doing this other than having 100 boolean icons on my front panel.  I have an ok grasps on LV but not a real indepth one (so many features for me).  The time stamp will show when the alarm was first triggered and not change after that.  When an alarm is triggered, you have the option to acknowledge it.  If the alarm was then acknowledged and the alarm is no longer going off, it will disappear off the screen.  Likewise it would stay on if acknowledged but the bit is still triggered. 
    My most recent idea was to build a table by combining all the strings together into an array and displaying it like that.  If not triggered, it would pass blank through the array thus not showing anything.  I then became stuck on though the acknowledge feature.  I wanted to have it so that you could click the alarm boolean on the table and it would pop up a second VI asking if you wanted to acknowledge.  Then I realized that since the boolean is going to be turned into a string to be displayed on the table, you couldn't just click on it to open up that specific boolean. 
    Basically I am asking if there is an easier way to do this other than what I have been thinking of?  For what I know of LabVIEW software, I feel that it wasn't really built to do this tasks, but that won't help me get it done, lol.  I want some form of a table to be on the frontpage, without a ton of clutter.  Something that if no alarm is going off, it would leave the screen pretty blank actually other than maybe for table headers.  Chaos of the code itself is not that big of a deal.  Thanks for taking the time to read this posts either way.
    Solved!
    Go to Solution.

    Hi Drez,
    An array of clusters, with the cluster having a string and a
    Boolean, will enable you to display the alarm string and provide a way for the
    user to click on the Boolean to acknowledge. Check the attached VI. Click on “Simulate
    Alarms” and then click on any of the “Acknowledge” button. It should display a
    dialog box.
    I made an half attempt at simulating this, but you get the idea
    Attachments:
    Simulate_Alarms.vi ‏22 KB

  • Home alarm

    hello, this is my first post here. i am a student and new to labview. last few days i went through lots of basic tutorial. my plane is to make a full home automation system (not for my college project) with heating control and lights and buglar alarm. but i will start with alarm first. i break down alarm part in 2 part(hardware and software). i have few question about them for you guys who know this staff very well. i am using labview 2010.
    hardware:
    1. i am planning to use a DAQ system with digital i/o board preffer one with usb. which one will be better option?
    2. normally close pir sensor and door contract. how to sense the pir(1/0 logic)?
    3. user interface like pda/embedded cpu with touch screen? which one would be best and cheapest option?
    software:
    1. what is the best practice to scan an i/o port(for pir and door contact)?
    2. what would be the best way to use a passward to disalarm and alarm and edit the system like zone set to watch?
    here is my front panel........ and thanks in advance, i will come back with more question.

    Hi,
     I would start with the basics first. Try to do the most simple things. It looks like you are on a tight budget, and considering your timing requirements are very simple, I think the USB-6008 would work well. Forget about the advanced User Interface like the touch screen you mentioned, for now.
    Good for you for taking several tutorials! There are many FREE on the NI site. Look at the tutorials for simulating a DAQ device (6008 or other), if you want to proceed before purchasing one. And just start very simple,  make a VI that would look for a DI/O signal to go high or low on the DAQ and respond by turning on an LED on the front Panel.
    Can you attach  the VI of the front panel and block diagram of the image you atached?
    Alan

  • WAAS CM Https Issue

    Hi All
    We've logged a TAC Case for this but I thought I would post something here to  see if I could get any extra help. We have the following issue.
    We have a fleet of WAAS optimisers at a multitude of sites, with a CM in one of our data centres. Using Compuware VAS we have picked up the following issue. The Optimisers are initiating HTTPS conversations with the CM, and we are seeing Client RTT times for this traffic going into the days on the compuware VAS monitoring tool. Which frankly doesn't make sense.
    Now looking back the issue for last week seems to have originiated at the same time on the same day for all the optimisers I have looked at. With a small amount of traffic between the optimisers and the CM for a few days, with the Client RTT increasing
    The traffic is about 2/3rd client to 1/3rd server, and only in the very low kbs.
    I am trying to ascertain if this is a real problem or if it is our Compuware VAS monitoring system not reporting correctly. As there are no issues with client traffic, and we are able to manage the devices properly, there does not appear to be any alarms in the CM in regards to this either.
    This also appears to be a recurring issue.

    I would recommend that you try to do a cms deregister force on the accelerator, and delete it from the central manager GUI. Then try re-registering to the CM and see if that will fix the issues.
    Thanks,
    Dan

  • WAAS EMAP Optimization issue

    Dear Team,
    In WAAS Setup we are not seeing any Optimized EMAPI connection and below error is showing in Alarm section  for all Edge WAE devices.
    Wansecure encountered a peering service configuration error: ssl peering service configuration mismatch with peer device id 88:f0:31:b3:6e:c8. The following protocol acceleration can fail: SSL-AO, ICA (if using Wansecure) and Encrypted MAPI.
    We have verified the SSL peering configuration between Edge and core device and not found found any mismatch between them. Please suggest how we can resolve this issue.
    Regards,
    Ranjith

    Hi,
    Try the following on all the WAAS devices participating in the flow. (Core + edge)'
    WAAS #sh acc wansecure
    Accelerator Licensed Config State Operational State
    wansecure Yes Enabled Running
    WAN Secure:
    Accelerator Config Item Mode Value
    SSL AO User enabled
    Secure store User enabled
    Peer SSL version User default
    Peer cipher list User configured
    Peer cert User default <<<<Should be same for all devices
    Peer cert verify User enabled
    Follow the doc below.
    http://www.cisco.com/c/en/us/td/docs/app_ntwk_services/waas/waas/v501/configuration/guide/cnfg/policy.html#wp1156757
    Hope that resolves the issue.
    Regards,
    Abhishek
    CCIES 35269

  • WAAS 4.1.1.23 secured_client detected

    why is the above error regarded as a major error? when it is an information message only.
    It means there is a secured mapi client detected
    also I cannot find the release notes for WAAS 4.1.1a.10 I take it there are some fixes not in 4.1.1.23

    The release notes for 4.1.1a10 are included in the general 4.1.1 notes. See http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v411/release/notes/ws411rn.html
    I took a look at that alarm and it is documented that it is a major level. If you have MAPI enabled, the product is telling you it cannot accelerate these clients. So do you have some of your clients encrypted and some not? If this is common and it continues to cause the alarm to show, I'm sure we can submit a request to make the alarm informational only.
    Dan

Maybe you are looking for