Skip to main content

DOT11-4-MAXRETRIES


DOT11-4-MAXRETRIES: Packet to client XXXX.XXXX.XXXX reached max retries, removing the client.

What you describe can be:
1. Bad RF coverage, so no matter what code version, it will remain happening. Get a "sh dot11 asssoc all" to see the signal level
2. Radio issue (bug), which may need troubleshooting. Easiest is to load latest code, and test from there.
3. Interference that is causing client to miss frames and/or AP not to hear correctly the ACK
You can change the retry feature, do this:
1. go to enable mode
2. go to config (conf t)
3. in do0
4. packet ret 64 drop

AP-02#sh run int do0
Building configuration...

Current configuration : 456 bytes
!
interface Dot11Radio0
 no ip address
 no ip route-cache
 !
 encryption mode wep mandatory
 !VAIBHAVWIRELESSAP01
 !

0
 packet retries 64 drop-packet

Also add this command if required (config-if)# channel least-congested"

Comments

  1. Dot11-4-Maxretries >>>>> Download Now

    >>>>> Download Full

    Dot11-4-Maxretries >>>>> Download LINK

    >>>>> Download Now

    Dot11-4-Maxretries >>>>> Download Full

    >>>>> Download LINK 2X

    ReplyDelete

Post a Comment

Popular posts from this blog

Schedule Automatic backup config in Cisco Nexus

Schedule Automatic backup config in Cisco Nexus Nexus-Sw1(config)#feature scheduler   //Enable scheduler service in Nexus Nexus-Sw1(config)#scheduler job name backup-daily      // Job Name Nexus-Sw1(config)#scheduler aaa-authentication username abcd password abcd@123     // AAA - Authentication for Job created above (If AAA configured) Nexus-Sw1(config)#scheduler job name backup-daily copy running-config tftp://192.168.1.23/$(SWITCHNAME)-cfg.$(TIMESTAMP)         //IP of TFTP SERVER , file will saved with switch name and timestamp exit Nexus-Sw1(config)#scheduler schedule name backup-daily   // Setup Schedule to run for the JOB Nexus-Sw1(config-schedule)# time ?   daily    Specify a daily schedule   monthly  Specify a monthly schedule   start    Specify a future time schedule   weekly   Specify a weekly schedule...

Duplicate IP Address has been Detected Rule

A duplicate IP address has been detected on the network Rule Knowledgebase Summary This rule generates an alert when Windows® detects that he local machine’s IP address is in conflict with one or more identical IP addresses on the network. Until the IP address conflict is resolved, remote clients and applications may have difficulty accessing resources on any of the effected computers. Additionally, the local computer may not be able to access network resources. Related Events This rule generates an alert whenever the following events occur and are recorded in the System Event Log: The system detected an address conflict for IP address %2 with the system having network hardware address %3. The local interface has been disabled. Source: TCPIP; Event ID: 4198; The system detected an address conflict for IP address %2 with the system having network hardware address %3. The local interface has been disabled. Source: TCP...

Shunned packet Error on Cisco ASA Firewall

           Shunning/Blocking on IPS for  ASA/PIX/IOS Router Configuration Example   Advanced Threat Detection feature – This feature does a bunch of things. It detects and alerts on activity that might be related to a Denial of Service attack or Scanning reconnaissance. Optionally, the ASA can automatically shun/block hosts that are detected as a scanning threat. Threat detection also can gather threat statistics for display on the new Firewall Dashboard inside the ASDM GUI. Top 10 graphs, charts, and lists for things like access list hits, services most used, and top IP SRC and IP DST hosts are tracked. On Cisco routers and Catalyst 6500 series switches, ARC creates blocks by applying ACLs or VACLs. ACLs and VACLs apply filters to interfaces, which includes direction, and VLANs, respectively in order to permit or deny traffic. . The PIX Firewall, FWSM, and ASA do not use ACLs or VACLs. The built-in shu...