Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

how to remove a command that wont remove?

This thread has been viewed 6 times
  • 1.  how to remove a command that wont remove?

    Posted Feb 10, 2018 09:53 PM

    Ok got another wierd one...

    Somehow in my config i have the below:

    ip dhcp excluded-address 190.168.18.1 192.168.18.20
    This is wrong obviously.. it should be 192.168.18.1 192.168.18.20

     

    Hoever when I try to remove it with the gui I get:  

    Error processing command:no ip dhcp excluded-address 190.168.18.1 >> Failed to remove. Maximum DHCP address limit of 512 hit. You may want to exclude unused address ranges.
    I get the same error when I try to remove it via the CLI....
    How do I fix this?
     

     



  • 2.  RE: how to remove a command that wont remove?

    EMPLOYEE
    Posted Feb 10, 2018 10:06 PM

    Try this:

    no ip dhcp excluded-address 190.168.18.1 


  • 3.  RE: how to remove a command that wont remove?

    Posted Feb 11, 2018 09:28 AM

    Thanks but it does the same in the CLI as it does in the GUI

     

    #configure t
     (config) #no ip dhcp excluded-address 190.168.18.1
    Failed to remove. Maximum DHCP address limit of 512 hit. You may want to exclude unused address ranges.
    (config) #



  • 4.  RE: how to remove a command that wont remove?

    EMPLOYEE
    Posted Feb 11, 2018 09:31 AM

    Type "show running-configuration | include excluded" on the commandline so we can see exactly what is in the configuration.

     

    Also type "show ip dhcp database" so we can see what pool you have configured.  The problem could be with the pool..



  • 5.  RE: how to remove a command that wont remove?

    Posted Feb 11, 2018 09:45 AM

    Thanks again...

     

    show running-config | include excluded
    Building Configuration...
    ip dhcp excluded-address 190.168.18.1 192.168.18.20
    ip dhcp excluded-address 192.168.17.1 192.168.17.201

     

    show ip dhcp database
    DHCP enabled
    subnet 192.168.18.0 netmask 255.255.255.0 {
            default-lease-time 86400;
            max-lease-time 86400;
            option vendor-class-identifier  "ArubaAP";
            option vendor-encapsulated-options  "192.168.17.200";
            option domain-name-servers 8.8.8.8, 4.2.2.2;
            option routers 192.168.18.1;
            range 192.168.18.21 192.168.18.254;
            authoritative;
    }
    # AccessPoints
    subnet 192.168.19.0 netmask 255.255.255.0 {
            default-lease-time 259200;
            max-lease-time 259200;
            option vendor-class-identifier  "ArubaAP";
            option vendor-encapsulated-options  "192.168.17.200";
            option routers 192.168.19.1;
            range 192.168.19.2 192.168.19.254;
            authoritative;
    }
    # Legacy
    subnet 192.168.17.0 netmask 255.255.255.0 {
            default-lease-time 86400;
            max-lease-time 86400;
            option vendor-class-identifier  "ArubaAP";
            option vendor-encapsulated-options  "192.168.17.200";
            option domain-name-servers 8.8.8.8, 4.2.2.2;
            option routers 192.168.17.200;
            authoritative;



  • 6.  RE: how to remove a command that wont remove?

    Posted Feb 11, 2018 09:47 AM

    BTW this is a 3600 runnning 6.4.4.17_63295



  • 7.  RE: how to remove a command that wont remove?
    Best Answer

    EMPLOYEE
    Posted Feb 11, 2018 10:01 AM

    In a last act of desperation, you might want to save the running configuration off of the controller via ftp, tftp, etc, edit it and re-upload it.  (it would require a reboot, unfortunately).

     

    I am not sure why it is not working...



  • 8.  RE: how to remove a command that wont remove?

    Posted Feb 11, 2018 10:15 AM

    Thanks that was what I was gonna do as a last ditch effort....



  • 9.  RE: how to remove a command that wont remove?
    Best Answer

    Posted Feb 11, 2018 12:00 PM

    That did it... downlowaded the config, modified it and put it back...All is well now..Thanks..