Client DHCP issues with 4400 WLC

Authentication to ACS working okay.
Clients are unable to obtain an IP from DHCP.
DHCP server is configured on a dynamic interface but is on a different subnet located in a branch office. DHCP scope is running on a 4500 switch in the branch.
Is it preferable to have DHCP running on the internal WLC or a DHCP server close to the WLC rather than at the remote location?
TIA

Usually you don't want to have a dhcp server on a remote site, but it also should work as long as wired users are able to obtain an IP from the remote dhcp server. Preferred, like I said is to have a local dhcp, but if that doesn't work for you, then configuring the wlc to bbe a dhcp isn't a bad think either. Some like to have more control over the dhcp.

Similar Messages

  • DHCP issue with mobility anchor

    Hi Guys,
    I am having a bit of trouble to get the DHCP to work in my configuration. basically I have configured one SSID on two WLCs (running same version of code), I configured WLC 1 as anchor  controller and configured itself as mobility anchor (local), and on foreign controller (WLC2), I have configured the anchor as a mobility anchor. I have added both of the WLCs in each other's mobility list, however WLC1 and 2 are not in the same mobility group. clients are getting IP address through an external DHCP server.
    the problem is that when I used the management interface for the WLAN, I could get IP address through DHCP without any problem, however if I use another dynamic interface created for the SSID, then I could not get IP address anymore. I did another test with two WLCs configured in the same mobility group, then everythnig works fine. I have double checked my configuration for the dynamic interface but could not find anything wrong.
    so my question is
    is it possible to do auto anchoring configuration with two WLCs in different mobility group (different mobility group name), since based on my test management interface works,  but another dynamic interface did not work. in the configuration guide, it says: "you must add controllers to the mobility group member list before you can designate them as mobiolity anchors for a WLAN", does that mean the mobility group name has to be the same for both of the WLCs? if that's the case why does management interface worked?
    thanks in advance for you help.

    Hi Nicolas,
    thanks for your reply, i guess that's where the problem is - I could not ping the dynamic interface from the DHCP server. (eping and mping works fine)
    however I could ping the dynamic interface of the foreign controller (i have created another dynamic interface on the same subnet on the foreign controller, i understand it's not really necessary since we getting IP in the range defined on the anchor controller). the only difference between the two controllers is that the foreign controller enabled LAG, and only connected to the core swithc number 1, but the anchor controlelr is not (it has two connections to two core switches respectively).
    so does this mean I can not use this controller to be a anchor controller if it has two connections to two differnet switches? if yes is there any documentation on this point?
    Thanks very much for your help.

  • 10.5 DHCP issues with Wireless - self assigned IPs?

    We're having an issue with Mac OSX 10.5.4 clients, running the latest software updates, not getting an IP address via DHCP on our wireless network.
    We're using Cisco APs, with multiple VLANs & SSIDs. They authenticate, but get automatic self-assigned IP addresses. None of our PC clients are experiencing this issue, nor older 10.4.x OSX clients. This looks like a bug, from what I was able to discover:
    http://forums.macrumors.com/showthread.php?t=384947
    Is Apple aware of this, and/or working on a fix? I've seen many issues over the last year or so with Airport clients and wireless connectivity..

    This is a "user to user" help forum that is designed as a self-help system, independent of Apple's Technical Support system. No one here can say what Apple knows or is doing about a specific issue (pure speculation is discouraged). We share experience and suggest possible solutions or workarounds.
    One way to ensure that your issue is brought to Apple's attention is to use their feedback form for OSX - http://www.apple.com/feedback/macosx.html
    Since the link you posted is from late last year, there have been many updates to Leopard. Some of the updates mention network reliability. Even though Apple has stated that the Pram chips don't control network connections, I have had some luck by Zapping The Pram - http://support.apple.com/kb/HT1379 - Remember to check your System Prefs for things like date/time settings after you Zap.

  • 10.2.8 client login issues with 10.3.9 server

    Hi we have just updated our computer lab to 10.2.8 client computers and a 10.3.9 server but I am having issues with the client computer loging into the server I am using LDAPv3 and when I try to have a user login to the server from the client at the login screen I get the login window shake.I can login fine from a 10.3.9 client computer.Any advice would be appreciated.Thanks in advance

    Check your 10.2.8 machines Directory Access and make sure LdapV2 is not checked and also that Ldap V3 is checked and configured correctly. I found that if I had both Ldapv2 and v3 on my 10.2.8 clients could not log in. 10.3 clients only have the option for Ldap V3, so it is not an issue.

  • Lync internal clients have issues with external meetings

    We have a pretty easy Lync setup in our company, 2 FE servers in a Enterprise pool, one Edge server (in a pool. we will add edge servers later) and a Reverse proxy (Databases on a SQL server of course). Everything seems to be working well internally. We
    have not deployed Enterprise voice yet but that is coming later. Our issue is when our internal clients try to join a meeting from another company. They can join the meeting and IM but as soon as they try to start Voice, they get kicked out of the call. Internal
    meetings work fine with voice and video. They can join the meeting using Lync Web App but that is not a satisfactory solution for this. The company that hosted the meeting said users from other companies can join with the lync client without issue. I am a
    remote employee and I can join using audio and video from my home. I have tried tracing the issue with the lync client logs but they make little sense to me. My question is, how does the information flow from internal clients to an external meeting> Is
    it through the AV service in the Edge? 
      We have opened the firewalls wide open as a test (closed again of course) and it does not seem to be a firewall issue. Can anyone point me in the right direction?

    To both of you, thanks but the articles do not help me. We can host meetings in our Lync 2013 organization without issue and it seems that others from outside can join with either Lync client or LWA. Our remote users connect via Lync client without a VPN
    and have no issues with IM, Audio, video or sharing. The issue is connecting to another companies Lync meeting from inside our network. You can connect but as soon as you try to enable audio, you get kicked out. I have seen another post that describes the
    issue but there is no solution there either. As I said in the original post, we ran a test where we temporarily opened both the internal and external firewalls wide open for the Edge and Reverse Proxy servers and it had no effect whatsoever so I conclude it
    probably is not a firewall issue. Since Edwin verified what I believed in that the communication from the internal clients does go through our companies Edge server when joining a meeting with another company, it leads me to believe that this is
    a setup issue with the Edge server but I have followed the setup documents and nothing seems out of place. Our edge server is a virtual server. I  am wondering if this could be related to it or maybe this is just the way things are. Can anyone
    tell me that their internal users can join a meeting hosted by another company? We have open federation setup at this time and since the company that hosted the meeting claims to have had users from other companies in meetings without issue, I assume their
    SRV records work.

  • 10.6 Server, 10.8 Clients (ML) issues with Contacts & Mail

    I'm seeing issues with Mail in ML and contacts and our 10.6 server. All users are on a network home directories and using the Address Book service on the server. Mail and Contacts fail/work intermintently when both of them are running. Stopping and restarting either program may solve the problem.
    Users of 10.7 clients see no issues. Only users of 10.8 ML have problems with Mail and Contacts. Its very obvious that Contacts and Mail are having issues with each other. I can remove the contents of the Address Book in the local user's library and and relaunch Contacts to run with out problems. As soon as you start Mail problems arise quickly.
    While Mail is accessing the address database it will demonstrate long delays.
    Any direction or help is much appreciated!

    This is a known bug of ML. The operating system is not compatible with AFP home directories. You will notice that FaceTime won't work either. In addition, there are sandbox problems, preferences problems and performance issues.
    In my experience, the only possible workaround is to convert all forks and Extended Attributes in the home directories to AppleDouble files and then switch from AFP to NFS. This can result in Spotlight issues, but otherwise, all applications will work fine and much faster.

  • FlexConnect AP Deployment- Clients having issues with DHCP

    I have 7 2602I access points deployed and operating in FlexConnect.  We are doing both local switching and local authentication.  These AP's are in a FlexConnect Group with local Radius server defined as the primary server in the Flex Group.  This has been working for a few days.  The vlan these users are getting DHCP is local and there is a local DHCP server.  There is also a backup DHCP server at the central site. 
    We are beginning to get reports of users having problems connecitng to wireless.  Authentications asre successful, but when I look at the WLC, I notice they are not getting an IP address.  They either show 0.0.0.0, or the default address 169.254.12.2.  Some are connecting, and some do not.  This issue is very intermittent.  I will also add, this location does have periods of high latency, hence the reason we are doing local switching/local auth.  This client eventually got an IP address, but it took a while.
    We never had any issues unitl we deployed in Flex mode.  I could switch these Ap's back to local mode(central switch/central auth) and this problem would never occur.  Any ideas? Thanks.

    I agree that in local auth mode the WLC does not learn as much info, but if you check learn IP address under the WLAN it will learn it and can be seen from monitor clients.
    Although authentications are successful, I have not ruled out some sort of local auth issue.
    One other thing to note, we got a debug client and the first dhcp request went to the local dhcp server, then a request to the backup dhcp at HQ. however the dhcp request was fulfilled by the local dhcp server. The local server appears to be working correctly, and there are plenty of addresses available.
    Sent from Cisco Technical Support iPhone App

  • WLC DHCP issue with 6500

    Hi,
    I configured WLC as DHCP server and is working fine when connected to 3750 core switch. The AP's and clients are getting IP address.
    When the same WLC is connected to 6500 , the DHCP is not working from WLC . The same port of 6500 switch  is verified by connecting a 3750 switch as dhcp server and AP as well as clients are getting IP.
    DHCP snooping and port security is not enabled in the 6500 and the configuration is simple. The WLC is untagged and the 6500 port is a trunk port with 242 as native VLAN.
    Please help

    Dear Surendra,
    Please see the answers in line.
    1.As per your previous post, if we connect WLC to 3750 core everything works fine.. so in this case, i assume that we have INTERFACE VLAN on the switch and then the management interafce on the WLC are in the same subnet?? correct??
    "Yes , All are in the same Vlan . Interface VLAN and management interface are in same subnet."
    2. Similarly, if we swap the 3750 with 6500, it doesnt work.. in this case.. have you created the interface vlan on the 6500 in the same subnet as that of management interface of the WLC??
    " Yes, the 6500 has vlan interface without IP. The same way we configured 3750 "
    Or
    3.are we not swapping the 6500 and we are connecting the WLC to the WLC to the 6500 and then this 6500 to the 3750??
    "We connected WLC LAP to 3750 and the dhcp of wlc is working fine.. When WLC & AP connected to 6500 , the WLC DHCP is not working. We verified the 6500 port by coonecting 3750 as DHCP server and WLC is connected to 3750 and all were working fine. When WLC is directly connected to 6500 , the LAP is not joing to WLC. When static IP is given to LAP, the LAP joined WLC but the clients were not getting IP."
    4.Layer 2 means... interface VLAN on the switch and the WLC management and the AP DHCP pool are all in the same subnet. correct?
    "Yes all are in the same subnet"
    Thanks for your efforts.
    Regards,
    Savad

  • Issue with 2504 WLC and 2602 AP. need help please.

    Somehow the AP does not associates with the 2504 controller.
    What could possibily be the issue.
    Thanks in advance.
    Anyway,  Here is the log from the AP.
    AP log
    ===========================================================
    *Mar  1 00:30:35.551: %CAPWAP-5-DHCP_OPTION_43: Controller address 192.168.120.4 obtained through DHCP
    *Mar  1 00:30:35.551: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
    *Mar  1 00:30:44.551: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
    *Mar  1 00:30:44.551: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'SNGNY-WLC1'running version 7.0.220.0 is rejected.
    *Mar  1 00:30:44.551: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.
    *Mar  1 00:30:44.551: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.
    *Mar  1 00:30:44.551: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
    *Mar  1 00:30:44.551: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.120.4
    ===========================================================
    show version output from the Access Point
    =========================================================
    AP0006.f6ec.be2a#show ver
    Cisco IOS Software, C2600 Software (AP3G2-RCVK9W8-M), Version 15.2(2)JB, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2012 by Cisco Systems, Inc.
    Compiled Tue 11-Dec-12 00:07 by prod_rel_team
    ROM: Bootstrap program is C2600 boot loader
    BOOTLDR: C2600 Boot Loader (AP3G2-BOOT-M) LoaderVersion 12.4(25e)JA1, RELEASE SOFTWARE (fc1)
    AP0006.f6ec.be2a uptime is 33 minutes
    System returned to ROM by power-on
    System image file is "flash:/ap3g2-rcvk9w8-mx/ap3g2-rcvk9w8-xx"
    Last reload reason:
    This product contains cryptographic features and is subject to United
    States and local country laws governing import, export, transfer and
    use. Delivery of Cisco cryptographic products does not imply
    third-party authority to import, export, distribute or use encryption.
    Importers, exporters, distributors and users are responsible for
    compliance with U.S. and local country laws. By using this product you
    --More--
    *Mar  1 00:33:46.071: %CAPWAP-3-ERRORLOG: Invalid event 38 & state 2 combination.
    *Mar  1 00:33:46.171: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.120.98, mask 255.255.255.0, hostname AP0006.f6ec.be2a
    agree to comply with applicable laws and regulations. If you are unable
    to comply with U.S. and local laws, return this product immediately.
    A summary of U.S. laws governing Cisco cryptographic products may be found at:
    http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
    If you require further assistance please contact us by sending email to
    [email protected].
    cisco AIR-CAP2602I-A-K9    (PowerPC) processor (revision A0) with 180214K/81920K bytes of memory.
    Processor board ID FGL1704ZC0Q
    PowerPC CPU at 800Mhz, revision number 0x2151
    Last reset from power-on
    LWAPP image version 7.4.1.37
    1 Gigabit Ethernet interface
    32K bytes of flash-simulated non-volatile configuration memory.
    Base ethernet MAC Address: 00:06:F6:EC:BE:2A
    Part Number                          : 73-14588-02
    PCA Assembly Number                  : 800-37899-01
    PCA Revision Number                  : A0
    PCB Serial Number                    : FOC165188Y4
    Top Assembly Part Number             : 800-38356-01
    Top Assembly Serial Number           : FGL1704ZC0Q
    Top Revision Number                  : A0
    Product/Model Number                 : AIR-CAP2602I-A-K9  
    Configuration register is 0xF
    ========================================================

    Blake's right.  Your WLC is running 7.0.X code which does not support the AP2600.  Check the Release Notes and look under Software Release Support for Access Points to determine what suitable firmware your WLC can support your AP.

  • Dynamic VLAN assignment issue with ACS & WLC

    I have configured an ACS (v4.2) & a WLC 4402 (5.2.193.0) according to the document listed at: http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008076317c.shtml
    When I attempt to authenticate a user in the ACS local user database, I receive an auth failure.  I have enabled debugging in the WLC's CLI and I see that I get an authentication failure from the ACS.  Upon reviewing the ACS's 'failed attempts' log, I see the username I attempt to authenticare with but it reports 'CN user unknown' even though this user is the local database.
    During troubleshooting, I discovered that if I modify the AAA client for the WLC and change it to 'Cisco Aironet' rather than 'Cisco Airespace', authentication works perfectly, the proper user is authenticated to the local database and I am able to connect to the SSID.  The only issue is that because I'm now using Aironet instead of Airespace, the IETF attributes 064, 065, and 081 (VLAN, 802, and the VLAN ID respectively) do not properly assign the VLAN that the user needs to be on.
    Am I missing something?

    I determined that a NAP was blocking my authentication using Airespace and can successfully authenticate with both Aironet and Airespace now.  I also reviewed the debug output of both types of connections and I can see the proper attributes coming through, but the wireless clients just won't assign to the right VLAN interface.
    I've reviewed all of the configuration settings per the document about 40 or 50 times now and I am certain I'm not missing anything.  I do indeed have override enabled but the configured interface 'management' is still the one the user is assigned to every time, even in the client connection details under the monitor tab.  ARGH!!

  • Wireless dhcp issue after upgrading WLC to 7.6.100

    Hi All,
    We have upgraded our controllers to version 7.6.100. After upgrading, the access points also upgraded their version to 15.2(4)JB3. But, the problem is that after this process the APs do not get IP. It stays on this state:
    *Sep 26 03:55:36.334: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
    Not in Bound state.
    The DCHP configuration is OK, since it is working in other two controllers we have and that we are not upgrading untill this issue is solved.
    If we connect the APs via console and configure a static IP and controller's IP, the AP registers and works fine. But, the access points are located in 20 remote sites, so we would like to avoid going site by site.
    Has anyone suffered this issue and knows how to "recover" those access points?
    Thank you very mucho for your help!

    Hi,
    Thank you for your answer conraddaniel.
    But, our issue was an error on the DHCP. The DHCP server pool for the APs was configured with lease time infinite (on a Cisco 6500). After capturing the packets and debugging on the AP we realized that the AP were receiving wrong values:
    DHCP: Scan: Renewal time: 2147483647
    DHCP: Scan: Rebind time: 536870911
    So, on the AP debugging we saw:
    DHCP: Scan: Renewal time larger than Rebind time
    On Cisco documentation:
    T1 Timer(Renewal) After a certain portion of the lease time has expired, you attempt to contact the server that initially granted the lease in order to renew the lease so its IP address can still be used.
    T2 Timer(Rebinding) If renewal with the original leasing server fails, because, for example, the server was taken offline, then you ideally try to rebind to any active DHCP server and try to extend its current lease with any server that allows it to do so.
    These T1 and T2 timers can be any values, but must be less than the IP address lease duration. T1 Timer must be less than T2. Generally T1 is set to 50 percent of the lease duration and T2 is set to 87.5 percent of the lease duration. Use this rule to set T1 and T2 timers.
    On the previous version of the WLC, the DHCP was configured in the same way and we confirmed that the APs received same times, but they ignored those wrong values.
    The workaround was to modify the lease time of the DHCP pool (1 day). This way, both timers had valid values and the APs accepted the DHCP OFFER. We still do not know why with lease infinite these timers have wrong values (a bug?).

  • Ethernet Bridging - Client DHCP issue

    Good Afternoon,
    We are having a strange issue taht i am sure others have run into before.
    Currently we have a WLC 5508 with 2 1552 Outdoor Mesh APs running code 7.4.100.0.
    We one configured as RAP and one as MAP. This is essentially setup just as a backhaul (trunk link). We ahve the RAP setup as Normal and the MAP setup for Trunk. We have configured to pass all VLANs we need (pruning). The mesh link works as expected the only issue is when we try to connect a client to a access port (VLAN 18)  on a switch the MAP side (ethernet bridged). We are unable to get a IP address assigned.
    However. We can statically configure an address in that network and Unicast traffic works just fine. It appears the broadcast traffic is not making it across the Mesh link.
    Thoughts?                  

    With mesh, you do not need to enable ethernet bridging at all.  All the traffic should tunnel back to the WLC as if the mesh ap was a local mode ap.  Make sure that if you are using AP Groups that the WLAN to vlan mappings are correct.  The other thing is that you should be on v7.4.121.0 and also make sure you have uploaded the latest FUS 1.9.0.0 onto the WLC for stability.  I have mesh networks on both v7.4.121.0 and v7.6.120.0, working just fine.
    Scott

  • LDAP issues with 5508 WLC

    I have deployed two wlans with two LDAP servers and different OU configurantion in each LDAP.
    WLC5508 software 7.2.110
    wlan id 1 is set to LDAP server1
    wlan id 4 is set to LDAP server2
    tests
    user server1 connect to wlan1
    user server1 connect to wlan4    - this should not happen
    user server2 connect to wlan4
    user server2 connect to wlan1     - this should not happen                  
    This scenario already work fine on WLC 4400 with software 7.0.116
    Anyone already has a similar problem?
    thanks,
    Murilo Cavallini

    Both DataBase is created on the same AD, but this Server has 2 network interface.
    wlan1 is set to LDAP Server2: IP address 10.19.198.254
    show ldap 2
    Server Index..................................... 2
    Address.......................................... 10.19.198.254
    Port............................................. 389
    Enabled.......................................... Yes
    User DN.......................................... OU=Convidados,DC=wlan,DC=tvg,DC=com,DC=BR
    User Attribute................................... sAMAccountName
    User Type........................................ Person
    Retransmit Timeout............................... 2 seconds
    Bind Method ..................................... Anonymous
    *LDAP DB Task 1: Oct 25 09:13:08.716: Attempting user bind with username CN=didatagm,OU=GloboMobile,DC=wlan,DC=tvglobo,DC=com,DC=br
    Server Index..................................... 2
    Address.......................................... 10.19.198.254
    Port............................................. 389
    Enabled.......................................... Yes
    User DN.......................................... OU=Convidados,DC=wlan,DC=tvg,DC=com,DC=BR
    User Attribute................................... sAMAccountName
    User Type........................................ Person
    Retransmit Timeout............................... 2 seconds
    Bind Method ..................................... Anonymous
    wlan2 is set to LDAP Server1: IP address 10.19.198.176
    show ldap 1
    Server Index..................................... 1
    Address.......................................... 10.19.198.176
    Port............................................. 389
    Enabled.......................................... Yes
    User DN.......................................... OU=Mobile,DC=wlan,DC=tvg,DC=com,DC=BR
    User Attribute................................... sAMAccountName
    User Type........................................ Person
    Retransmit Timeout............................... 2 seconds
    Bind Method ..................................... AnonymousServer Index..................................... 1
    Address.......................................... 10.19.198.176
    Port............................................. 389
    Enabled.......................................... Yes
    User DN.......................................... OU=Mobile,DC=wlan,DC=tvg,DC=com,DC=BR
    User Attribute................................... sAMAccountName
    User Type........................................ Person
    Retransmit Timeout............................... 2 seconds
    Bind Method ..................................... Anonymous
    This is the problem that I can see:
    Auth. Request is sent:
    *LDAP DB Task 2: Oct 25 09:13:08.710: ldapAuthRequest [2] called lcapi_query base="OU=Convidados,DC=wlan,DC=tvg,DC=com,DC=BR"       type="Person" attr="sAMAccountName" user="didatagm" (rc = 32 - No such object)
    Binding with the user with database:
    *LDAP DB Task 1: Oct 25 09:13:08.716: Attempting user bind with username CN=didatagm,OU=Mobile,DC=wlan,DC=tvg,DC=com,DC=br
    WLC is requesting for LDAP SERVER2 and is binding for LDAP SERVER1. This issue is occuring only sometimes.
    thanks a lot.

  • 10.1.3.3 JDev web service client proxy: Issue with XSD:anySimpleType

    Hi,
    One of our Web services XSD elementss has "anySimpleType" as the type:
    <xsd:element name="Value" type="xsd:anySimpleType" minOccurs="0" nillable="true"/>
    The client proxy is generated using JDev 10.1.3.3. We observed that the corresponding Java object is created with "String" data type:
    protected java.lang.String value;
    exp.setValue("100");
    We need to be able to pass arguments with other simple types as well (E.g. Decimal). We tried changing the auto generated code, but weren't successful.
    Any pointers in this regard are much appreciated.
    Thanks,
    Phani

    Hi all,
    can anyone please respond to my issue. Its sort of urgent.
    thanks,

  • Cross-client activation issue with LBWE

    Hi,
    I am running into the same problem as the following links:
    Problem with setup table fillup
    Cross-client problem
    We have the configuration client 300 and the loading client 310. The structures in client 100 are active but are inactive in client 310. The first link says that I have to go into LBWE in the loading client to activate the structures, but I have the same issue relating to the second link. This is happening in the DEV system.
    Is the fix for the second issue relating to Basis who would allow me to do the activation on the loading client - opening the system for me to activate? Or is it the Developer's issue to find the workaround?
    I don't see why the restriction on the configuration for DEV client systems. This is for BW related Configuration issues and nothing is relating to SAP Business Configuration that had to be so restricted.
    Please advise how to get the inactive structures to be active in the loading client.
    Thanks

    Hi,
    It is a very common issue.  You can solve it by logging in to 310 client, going to SCC1 transaction and replicating changes from the transport orders that you created in the other DEV client.
    It's like transporting from one DEV client to the other, but please note that the request does not need to be released.
    I hope this helps.
    Best regards,
    Maximiliano Ariel López

Maybe you are looking for