Solved: CIFS Operational State Disabled.

da.newman · ‎01-02-2012

Hi All

The CIFS service on a NME-WAE-502 is showing an "disabled" operational state however the Config State is "enabled" and reporting a "

cifs_ao_down" alarm. I've tried re-enabling the accelerated service via the CLI and the console reports that it is enabled however the operational state of the acceleratored service remains disabled.

WAE1#sh alarm

Critical Alarms:

----------------

Alarm ID Module/Submodule Instance

--------------- -------------------- ---------------

1 cifs_ao_down wafs WAFS

Major Alarms:

-------------

None

Minor Alarms:

-------------

Alarm ID Module/Submodule Instance

--------------- -------------------- ---------------

1 primary_interface CIFS_AO/primary_interface CIFS_AO

WAE1#sh license

License Name Status Activation Date Activated By

-------------- ----------- --------------- --------------

Transport not active

Enterprise active 05/22/2009 admin

Video not active

WAE1#sh cms info

Device registration information :

Device Id = 3806504

Device registered as = WAAS Application Engine

Current WAAS Central Manager = 10.###.###.##

Registered with WAAS Central Manager = 10.###.###.##

Status = Online

Time of last config-sync = Tue Jan 3 12:45:18 2012

CMS services information :

Service cms_ce is running

WAE1#sh acc

Accelerator Licensed Config State Operational State

----------- -------- ------------ -----------------

cifs Yes Enabled Disabled

epm Yes Enabled Running

http Yes Enabled Running

mapi Yes Enabled Running

nfs Yes Enabled Running

ssl Yes Enabled Running

video No Enabled Shutdown

WAE1#conf t

WAE1(config)#accelerator cifs enable

Enabled windows-print accelerator

Enabled cifs accelerator

WAE1(config)#

Does anyone know how to solve this issue?

Bhavin Yadav · ‎01-03-2012

OR try removing the Enterprise License and then after 5 minutes re-apply it.

View solution in original post

Bhavin Yadav · ‎01-03-2012

Hi Da,

can you post sh alarm history , sh ver and sh disk details output here ?

This may be due to CIFS partition mismatch.

Thanks.

da.newman · ‎01-03-2012

As requested:

WAE1#sh alarm history detail

Op Sev Alarm ID Module/Submodule Instance

-- --- -------------------- -------------------- --------------------

1 R Cr cifs_ao_down wafs WAFS

Dec 31 16:57:20.389 EST, Processing Error Alarm, #000002, 10000:1000003

CIFS Accelerator is down.

2 R Mi primary_interface CIFS_AO/primary_interface CIFS_AO

Dec 31 16:56:21.861 EST, Environment Alarm, #000001, 20000:20001

primary-interface miss-configured. cifs-ao will work in passthrough mode.

Op - Operation: R-Raised, C-Cleared

Sev - Severity: Cr-Critical, Ma-Major, Mi-Minor

WAE1#sh ver

Cisco Wide Area Application Services Software (WAAS)

Cisco Wide Area Application Services (accelerator-k9) Software Release 4.4.3b (build b2 Oct 20 2011)

Version: nme-wae-502-4.4.3b.2

Compiled 16:38:43 Oct 20 2011 by damaster

Device Id: 00:21:55:##:##:##

System was restarted on Sat Dec 31 16:49:10 2011.

The system has been up for 3 days, 2 hours, 38 minutes, 24 seconds.

WAE1#sh disk detail

Physical disk information:

disk00: Present 080606BB6200WBFM69UF (h01 c00 i00 l00 - Int DAS-SATA)

114470MB(111.8GB)

Mounted file systems:

MOUNT POINT TYPE DEVICE SIZE INUSE FREE USE%

/sw internal /dev/sdb1 991MB 698MB 293MB 70%

/swstore internal /dev/sdb2 991MB 562MB 429MB 56%

/state internal /dev/sdb3 3967MB 137MB 3830MB 3%

/local/local1 SYSFS /dev/sdb7 5951MB 808MB 5143MB 13%

/disk00-04 CONTENT /dev/sdb6 96995MB 33965MB 63030MB 35%

.../local1/spool PRINTSPOOL /dev/sdb8 991MB 16MB 975MB 1%

No RAID devices present.

Disk encryption feature is disabled.

Bhavin Yadav · ‎01-03-2012

Hi Da,

It looks like you are missing primary interface configuration on thie WAE. Run "sh run" and make sure it shows up primary interface either as g1/0 or g2/0.

CLI command: sh run | in primary

if there is not primary interface configured, please configure one of the g1/0 or g2/0 as primary and it should start working.

Regards.

Bhavin Yadav · ‎01-03-2012

CLI commands:

WAVE574-3#conf t

WAVE574-3(config)#primary-interface GigabitEthernet {1/0 OR 2/0}

WAVE574-3(config)#end

WAVE574-3#

Your config / sh run should look like this: IN MY CASE, I AM USING GIG 1/0 as ACTIVE PRIMARY INTERFACE.

WAVE574-3#sh run

! WAAS version 4.3.1 (build b6 Nov 13 2010)

!

device mode application-accelerator

!

hostname WAVE574-3

!

primary-interface GigabitEthernet 1/0

!

interface GigabitEthernet 1/0

ip address x.x.x.x x.x.x.x

exit

interface GigabitEthernet 2/0

shutdown

exit

da.newman · ‎01-03-2012

Thanks for the assistance so far Bhavin.

I've added the "primary-interface" command to the module however the alarm is still occuring. I've tried to re-enable the cifs accelerator service, it re-enables but the cifs oeprational state is still disabled.

primary-interface GigabitEthernet 1/0

!

interface GigabitEthernet 1/0

ip address 10.###.###.### 255.255.255.252

no autosense

bandwidth 1000

full-duplex

exit

interface GigabitEthernet 2/0

shutdown

exit

WAE1#sh alarms

Critical Alarms:

----------------

Alarm ID Module/Submodule Instance

--------------- -------------------- ---------------

1 cifs_ao_down wafs WAFS

Major Alarms:

-------------

None

Minor Alarms:

-------------

Alarm ID Module/Submodule Instance

--------------- -------------------- ---------------

1 primary_interface CIFS_AO/primary_interface CIFS_AO

Bhavin Yadav · ‎01-03-2012

Try reloading the box, if you can.

Bhavin Yadav · ‎01-03-2012

OR try removing the Enterprise License and then after 5 minutes re-apply it.