Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

SATO GL408 Label Printers WLC 4402 6.0.188

Our end customer has many SATO GL408 Label Printers.   Periodically the printers need to be powered down to load some labels.  The majority of the time, these printers can associate with the wireless network no problem.  But, once in a while when the printer comes back online, it is not pingable.  There is no way to ping from the client to test if it is one way since these are static devices. All devices have static IP addresses.

When the above mentioned state occurs, we will see "8021X_REQD" for the Policy Manager State, listed under Client Properties.  The clients are configured for WPA/TKIP.  A reboot of the associated AP (1242AG) will allow packets to flow again.

Has anyone else experienced this behavior?  Is this a known bug? 

Client Properties are listed below.  Thank you in advance for your help.

(Cisco Controller) >show client detail 00:08:96:38:01:0c

Client MAC Address............................... 00:08:96:38:01:0c

Client Username ................................. N/A

AP MAC Address................................... 00:23:34:3f:7a:e0

Client State..................................... Associated    

Client NAC OOB State............................. Access

Wireless LAN Id.................................. 4 

BSSID............................................ 00:23:34:3f:7a:e3 

Connected For ................................... 9 secs

Channel.......................................... 11

IP Address....................................... X.X.X.X

Association Id................................... 63

Authentication Algorithm......................... Open System

Reason Code...................................... 1 

Status Code...................................... 0 

Session Timeout.................................. 0 

Client CCX version............................... No CCX support

Mirroring........................................ Disabled

QoS Level........................................ Gold

Diff Serv Code Point (DSCP)...................... disabled

802.1P Priority Tag.............................. disabled

WMM Support...................................... Disabled

Power Save....................................... OFF

Current Rate..................................... 54.0

Supported Rates.................................. 1.0,2.0,5.5,11.0,6.0,9.0,

    ............................................. 12.0,18.0,24.0,36.0,48.0,

    ............................................. 54.0

Mobility State................................... Local

Mobility Move Count.............................. 0

Security Policy Completed........................ No

Policy Manager State............................. 8021X_REQD

Policy Manager Rule Created...................... Yes

ACL Name......................................... none

ACL Applied Status............................... Unavailable

NPU Fast Fast Notified........................... No

Policy Type...................................... WPA1

Authentication Key Management.................... PSK

Encryption Cipher................................ TKIP-MIC

Management Frame Protection...................... No

EAP Type......................................... Unknown

Interface........................................ manufacturing

VLAN............................................. 202

Quarantine VLAN.................................. 0

Access VLAN...................................... 202

Client Capabilities:

      CF Pollable................................ Not implemented

      CF Poll Request............................ Not implemented

      Short Preamble............................. Implemented

      PBCC....................................... Not implemented

      Channel Agility............................ Not implemented

      Listen Interval............................ 20

      Fast BSS Transition........................ Not implemented

Fast BSS Transition Details:

Client Statistics:

      Number of Bytes Received................... 243021

      Number of Bytes Sent....................... 183997

      Number of Packets Received................. 2439

      Number of Packets Sent..................... 1351

      Number of EAP Id Request Msg Timeouts...... 0

      Number of EAP Request Msg Timeouts......... 0

      Number of EAP Key Msg Timeouts............. 4

      Number of Data Retries..................... 9

      Number of RTS Retries...................... 0

      Number of Duplicate Received Packets....... 0

      Number of Decrypt Failed Packets........... 672

      Number of Mic Failured Packets............. 0

      Number of Mic Missing Packets.............. 0

      Number of Policy Errors.................... 0

      Radio Signal Strength Indicator............ -54 dBm

      Signal to Noise Ratio...................... 45 dB

Nearby AP Statistics:

      HMI-AP-05(slot 0) .........................

antenna0: 10 seconds ago -77 dBm................. antenna1: 4294851290 seconds ago -128 dBm

      HMI-AP-04(slot 0) .........................

antenna0: 10 seconds ago -55 dBm................. antenna1: 4294851290 seconds ago -128 dBm

      HMI-AP-03(slot 0) .........................

antenna0: 10 seconds ago -66 dBm................. antenna1: 4294851290 seconds ago -128 dBm

      HMI-AP-02(slot 0) .........................

antenna0: 10 seconds ago -85 dBm................. antenna1: 4294851290 seconds ago -128 dBm

      HMI-AP-01(slot 0) .........................

antenna0: 10 seconds ago -67 dBm................. antenna1: 4294851290 seconds ago -128 dBm

3 REPLIES
New Member

Re: SATO GL408 Label Printers WLC 4402 6.0.188

Are you doing 802.1x on these devices?

Hall of Fame Super Gold

Re: SATO GL408 Label Printers WLC 4402 6.0.188

I'd check your RADIUS/TACACS server.  Reason Code of "1" means "Go Away".

New Member

Re: SATO GL408 Label Printers WLC 4402 6.0.188

RADIUS is not used on the WLAN in which these clients are associated.  They authenticate via Pre-shared Key (WPA/TKIP).

The odd behavior is when the WAP is rebooted, the client can then communicate with the network.

1168
Views
0
Helpful
3
Replies
CreatePlease to create content