log: %SISF-3-INTERNAL: sisf_shim_utils.c:316 Internal error, 0 length

[julio.aldana]

Hello

We have two WLC 5502 with 7.2.110.0. We are getting this logs in one of them:

*sisfSwitcherTask: Feb 21 09:10:13.205: %SISF-3-INTERNAL: sisf_shim_utils.c:316 Internal error, 0 length

*sisfSwitcherTask: Feb 21 09:10:10.149: %SISF-3-INTERNAL: sisf_shim_utils.c:316 Internal error, 0 length

*sisfSwitcherTask: Feb 21 09:09:59.135: %SISF-3-INTERNAL: sisf_shim_utils.c:316 Internal error, 0 length

*sisfSwitcherTask: Feb 21 09:09:49.327: %SISF-3-INTERNAL: sisf_shim_utils.c:316 Internal error, 0 length

*sisfSwitcherTask: Feb 21 09:09:48.231: %SISF-3-INTERNAL: sisf_shim_utils.c:316 Internal error, 0 length

*sisfSwitcherTask: Feb 21 09:09:47.917: %SISF-3-INTERNAL: sisf_shim_utils.c:316 Internal error, 0 length

*sisfSwitcherTask: Feb 21 09:09:44.207: %SISF-3-INTERNAL: sisf_shim_utils.c:316 Internal error, 0 length

*sisfSwitcherTask: Feb 21 09:09:41.774: %SISF-3-INTERNAL: sisf_shim_utils.c:316 Internal error, 0 length

*sisfSwitcherTask: Feb 21 09:09:37.685: %SISF-3-INTERNAL: sisf_shim_utils.c:316 Internal error, 0 length

*sisfSwitcherTask: Feb 21 09:09:37.001: %SISF-3-INTERNAL: sisf_shim_utils.c:316 Internal error, 0 length

*sisfSwitcherTask: Feb 21 09:09:34.493: %SISF-3-INTERNAL: sisf_shim_utils.c:316 Internal error, 0 length

It doesn't seem to be having any issues on performance, APs associate normally, clients work normally.. it floods the logs though ^^.

I would appreciate any help.

Thanks.

[David Watkins]

Any reference to SISF tasks are "generally" related to IPV6, but I'm not positive on "this" particular message.  Whether or not you have it enabled/disabled, or ACLs set up to block/allow, etc, IPV6 will pass through the WLC on 7.2.110.0, and can cause the 5508 to crash.

You can obtain the 7.3.112.0 releaes which has this fixed.  You can also then use, if desired, the IPV6 on/off knob so you can "truly" disable IPV6 if not being used.

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

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

You might want to check your WLC to see if it has actually crashed at all.

[Christian Quiroga]

Hi Friends,

On our WLC 2504 we see similar events in the log:

SISF BT Process: Mar 14 05:46:01.998: %SISF-3-INTERNAL: sisf_shim_utils.c:316 Internal error, 0 length

SISF BT Process: Mar 14 06:30:40.368: %SISF-3-INTERNAL: sisf_shim_utils.c:316 Internal error, 0 length

No crash info displayed by the controller.

Is this related to ipv6 also ?

Thanks.

[Scott Fella]

Per David's post it is related. Have you tried to follow his instructions by disabling ipv6? If your not experiencing any issues, I wouldn't worry about it.

Sent from Cisco Technical Support iPhone App

[julio.aldana]

Hi After upgrading to 7.4 logs changed from this

*sisfSwitcherTask: Feb 21 09:10:13.205: %SISF-3-INTERNAL: sisf_shim_utils.c:316 Internal error, 0 length

to this:

*apfOrphanSocketTask: Mar 15 09:47:32.466: #IPV6-3-INVALID_ADDR_ORPHAN: ipv6_net.c:715 Invalid ipv6 address ::, failed to do data gleaning.

*apfOrphanSocketTask: Mar 15 09:47:32.114: #IPV6-3-INVALID_ADDR_ORPHAN: ipv6_net.c:715 Invalid ipv6 address ::, failed to do data gleaning.

*apfOrphanSocketTask: Mar 15 09:47:32.114: #IPV6-3-INVALID_ADDR_ORPHAN: ipv6_net.c:715 Invalid ipv6 address ::, failed to do data gleaning.

Previous message occurred 2 times.

*apfOrphanSocketTask: Mar 15 09:47:31.606: #IPV6-3-INVALID_ADDR_ORPHAN: ipv6_net.c:715 Invalid ipv6 address ::, failed to do data gleaning.

*apfOrphanSocketTask: Mar 15 09:47:24.517: #IPV6-3-INVALID_ADDR_ORPHAN: ipv6_net.c:715 Invalid ipv6 address ::, failed to do data gleaning.

*apfOrphanSocketTask: Mar 15 09:47:24.515: #IPV6-3-INVALID_ADDR_ORPHAN: ipv6_net.c:715 Invalid ipv6 address ::, failed to do data gleaning.

Previous message occurred 2 times.

[Jeremy Lisenby]

I'm getting the same error filling my logs up as well Julio, any luck in resolving this?  I'm running different hw (2504 running 7.3.112).  Like you, it's not seemingly causing any issues, just would like to clear it from the logs.

[julio.aldana]

As I said after upgrading to 7.4 logs changed to

*apfOrphanSocketTask: Mar 15 09:47:32.466: #IPV6-3-INVALID_ADDR_ORPHAN: ipv6_net.c:715 Invalid ipv6 address ::, failed to do data gleaning.

They desappeared after we disabled IPv6 with config ipv6 disable.

[Jeremy Lisenby]

Thanks, I'd been getting the orphansockettask since upgrading.  Appreciate the reply, ipv6 disabled.

[pdxnetwork]

As per Cisco TAC....this is is a bug.   We had the same issue with 7.4.100.60.   We loaded 7.4.110 and this seems to have solved the issue.  

[Flavio Boniforti]

Hi there.

I'm running 7.4.110.0 on two WLCs and I get this error too:

#IPV6-3-INVALID_ADDR_ORPHAN: ipv6_net.c:765 Invalid ipv6 address ::, failed to do data gleaning.

Why should I disable IPv6 to get rid of this?

What countermeasure/fix is available?

Best regards,

Flavio

[Scott Fella]

Have you tried to disable ipv6 and see if that log message goes away?

Sent from Cisco Technical Support iPhone App