cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1958
Views
0
Helpful
3
Replies

FWSM NP Issue (np_logger_query request)

Dear All,

We have two Cisco 6513 switches with each one FWSM module. FWSM Working as an Active/Passive. After upgrading the FWSM software from 3.1(4) to 3.2(15). This issue has occured second time(on both modules). But we never face this issue before upgrade. Following is the issue:


Both FWSM became Active/Active and shows 'Secondary-failed'. Following are the logs we are getting from problematic FWSM:

FWSM2# show conn
ERROR: Unable to get connection information from NPs0 in use, 0 most used
Network Processor 1 connections
ERROR: np_logger_query request for Show Connections failed Network Processor 2 connections
ERROR: np_logger_query request for Show Connections failedMulticast sessions:
Network Processor 1 connections
ERROR: np_logger_query request for Show Connections failed Network Processor 2 connections
ERROR: np_logger_query request for Show Connections failedIPv6 connections:

FWSM2# clear np all stats
ERROR: np_logger_query request for clearing Slow Path Stats failedERROR: Failed to Clear Slow Path D300 Stats


ERROR: np_logger_query request for clearing Slow Path Stats failedERROR: Failed to Clear Slow Path D300 StatsERROR: np_logger_query request for clearReassemblyStats failedERROR: Failed to clear AAA uCode Stats

FWSM1# show xlate       
FWSM1# np_logger_query request for Show Xlate failed

FWSM2# show np blocks
                 MAX   FREE   THRESH_0   THRESH_1   THRESH_2
NP1 (ingress)  32768  32768         0          0                0
    (egress)  521206 521206          0            0                 0
NP2 (ingress)  32768  32768          0          0                0
    (egress)  521206 521206          0            0                 0
NP3 (ingress)  32768    112     700334       12188         517
    (egress)  521206 521205          0             0               0

I have found the bug 'CSCsr94408' relating to this issue. But there is only a workaroung to reload the FWSM. I reloaded it and It solved.

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsr94408

FWSM2# show np blocks
                 MAX   FREE   THRESH_0   THRESH_1   THRESH_2
NP1 (ingress)  32768  32768          0          0          0
    (egress)  521206 521204           0          0          0
NP2 (ingress)  32768  32768          0          0          0
    (egress)  521206 521206           0          0          0
NP3 (ingress)  32768  32768          0          0          0
    (egress)  521206 521206           0          0          0

And these  are the 4.0(4) release notes in which this bug was fixed:

http://www.cisco.com/en/US/docs/security/fwsm/fwsm40/release/notes/fwsmrn40.html#wp173021

Can anyone tell me what could be the reason behind this issue?


Regards,

Anser

3 Replies 3

Kureli Sankar
Cisco Employee
Cisco Employee