wafs edge service dies

[mahesh18]

Hi all,

ws have this alarm  on waas

cceAlarmMajorRaised- Raise-Alarm: nodemgr: The wafs_edge service died.

Can some one explain me what this aalrm is about and what i need to check on waas

thanks

mahesh

[Bhavin Yadav]

Hi Mahesh,

Depending upon the version you are running and depending on other accompanying alarms, this may simply be a CIFS AO issue. if you are using 4.0.x code or using legacy CIFS AO please restart the WAFS service on edge device.

If you are running 4.1.x or later version, please verify that the CIFS AO is running. CLI command to check the accelerators:

sh accelerator

If you see that CIFS AO is shutdown for some reason, you can reset the accelerator in following way.

wae# conf t

wae(conf)# no accelerator wafs enable

wae(conf)# accelerator wafs enable

You can also check the alarm history and verify that there are not other alarms. CLI command:

sh alarm history detail

It is also possible that there may be hardware failure or corrupt disk based software. All those details can be analyzed if you can copy / paste output of following cli commands here:

sh alarm hist detail

sh accelerator

sh lic

sh ver

sh disk details

Hope this helps.

Regards.

PS: Please mark this question Answered, if this answers your question.

[mahesh18]

Hi bhavin,

here is output

Version: oe7341-4.1.7.11

Compiled 14:56:28 May 14 2010 by cnbuild

System was restarted on Sat Nov 20 15:57:29 2010.
The system has been up for 4 weeks, 5 hours, 38 minutes, 50 seconds.

version is higher. sh this cpmmand

sh accelerator

Accelerator     Licensed        Config State    Operational State
-----------     --------        ------------    -----------------
cifs            Yes             Disabled        Shutdown ***************************is this show that cifs ao is not 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
wafs-core       Yes             Disabled        Shutdown
wafs-edge       Yes             Enabled         Running

what is CIFS  AO stand for ?

here is other output

sh alarms his detail

     Op Sev Alarm ID             Module/Submodule     Instance
     -- --- -------------------- -------------------- --------------------
   1 C  Ma  servicedead          nodemgr              wafs_edge
     Dec 18 20:09:41.376 EST, Processing Error Alarm, #000007, 2000:330003
     nodemgr: The wafs_edge service died.

   2 R  Ma  servicedead          nodemgr              wafs_edge
     Dec 18 20:09:31.274 EST, Processing Error Alarm, #000007, 2000:330003
     nodemgr: The wafs_edge service died.

   3 C  Ma  servicedead          nodemgr              wafs_edge
     Dec  6 07:06:54.229 EST, Processing Error Alarm, #000006, 2000:330003
     nodemgr: The wafs_edge service died.

   4 R  Ma  servicedead          nodemgr              wafs_edge
     Dec  6 07:06:44.126 EST, Processing Error Alarm, #000006, 2000:330003
     nodemgr: The wafs_edge service died.

   5 C  Ma  servicedead          nodemgr              wafs_edge
     Dec  3 00:57:12.704 EST, Processing Error Alarm, #000005, 2000:330003
     nodemgr: The wafs_edge service died.

   6 R  Ma  servicedead          nodemgr              wafs_edge
     Dec  3 00:57:02.601 EST, Processing Error Alarm, #000005, 2000:330003
     nodemgr: The wafs_edge service died.

   7 C  Ma  servicedead          nodemgr              wafs_edge
     Nov 30 10:54:57.654 EST, Processing Error Alarm, #000004, 2000:330003
     nodemgr: The wafs_edge service died.

   8 R  Ma  servicedead          nodemgr              wafs_edge
     Nov 30 10:54:47.551 EST, Processing Error Alarm, #000004, 2000:330003
     nodemgr: The wafs_edge service died.

   9 C  Ma  servicedead          nodemgr              wafs_edge
     Nov 29 08:58:17.819 EST, Processing Error Alarm, #000003, 2000:330003
     nodemgr: The wafs_edge service died.

  10 R  Ma  servicedead          nodemgr              wafs_edge
     Nov 29 08:58:07.614 EST, Processing Error Alarm, #000003, 2000:330003
     nodemgr: The wafs_edge service died.

  11 C  Ma  servicedead          nodemgr              wafs_edge
     Nov 24 00:09:43.952 EST, Processing Error Alarm, #000002, 2000:330003
     nodemgr: The wafs_edge service died.

  12 R  Ma  servicedead          nodemgr              wafs_edge
     Nov 24 00:09:33.852 EST, Processing Error Alarm, #000002, 2000:330003
     nodemgr: The wafs_edge service died.

  13 C  Mi  servicestop          nodemgr              ntpd
     Nov 20 16:02:22.906 EST, Processing Error Alarm, #000001, 2000:330006
     nodemgr: The ntpd service stopped on request.

  14 R  Mi  servicestop          nodemgr              ntpd
     Nov 20 16:02:12.903 EST, Processing Error Alarm, #000001, 2000:330006
     nodemgr: The ntpd service stopped on request.

Op - Operation: R-Raised, C-Cleared
Sev - Severity: Cr-Critical, Ma-Major, Mi-Minor

sh disks details

RAID Physical disk information:
  disk00: Online                     3LM4RMW2    286102 MB
  disk01: Online                     3LM4PM2V    286102 MB
  disk02: Online                     3LM3GA1Y    286102 MB
  disk03: Online                     3LM4P11E    286102 MB

RAID Logical drive information:
  Drive 1:      RAID-5  Okay
                Enabled   (read-cache) Enabled (write-back)

Mounted file systems:
MOUNT POINT      TYPE       DEVICE                SIZE     INUSE      FREE USE%
/swstore         internal   /dev/sda2            991MB     711MB     280MB  71%
/state           internal   /dev/sda3           7935MB     212MB    7723MB   2%
/local/local1    SYSFS      /dev/sda7          33229MB    1354MB   31875MB   4%
/sw              internal   /dev/sda1            991MB     892MB      99MB  90%
/disk00-05       CONTENT    /dev/sda6         756337MB  524340MB  231997MB  69%
.../local1/spool PRINTSPOOL /dev/sda8            991MB      16MB     975MB   1%

Disk encryption feature is disabled.

iknow it has 4  disk drives what does raid 5 mean here?

thanks

[Bhavin Yadav · Accepted solution]

Hi Mahesh,

It seems like we have to work on your setup.

Reasons:

1. You are using 4.1.7 code which supports CIFS AO, the new CIFS optimziation.

2. You are using part of Legacy WAFS code - WAS edge only. The other one is core which is disabled.

From the logs, it seems like we need to disbale old legacy cifs and enable new CIFS AO.

here is how to do this.

1. Login to CM from GUI.

2. Under Device list - Go to Edit device and the under Legacy services, disable core and edge services. you may have to delete the core and edge devices before that.

3. Then enable new CIFS AO. CLI command:

     conf t

     accelera cifs enable

4. This will restart the CIFS connections.

Please note that this will be an intrusive test so it may affect the existing CIFS sessions.

In the end, make sure ...

1. all accelerators are enabled, except WAFS cor and WAFS edge.

2. no alarms are showing up.

Please make sure to apply above steps on the branch side or opposite side WAEs as you will have to enable new CIFS AO on all of the devices simultaneously. You can not run mix of old WAFS and new CIFS AO.

More details about legacy CIFS and new CIFS AO are here:

http://www.cisco.com/en/US/partner/prod/collateral/contnetw/ps5680/ps6870/waas_technical_faqs.pdf

Further, you may want to recreate the partitioning scheme to take advantage further.

CLI commands:

wae# disk delete-data-partitions

wae#reload

This will improve the performance but please note that this will wipe out your cache built up on WAE.

RAID 5 is the disk fault tolerance to give more data redundancy to wae.

Hope this helps.

Regards.