CRS-10010: unable to discover DHCP server

Hy
I try to set up Grid Infrastructure using GNS. When running the root script
I get a Problem with dhcp.
Here an example of my problem:
[root@oranode1 bin]#
[root@oranode1 bin]# ./crsctl get clientid dhcp -cluname grid112 -viptype HOSTVIP -n oranode1
CRS-10007: grid112-oranode1-vip
[root@oranode1 bin]#
[root@oranode1 bin]# ./crsctl discover dhcp -clientid grid112-oranode1-vip
CRS-10010: unable to discover DHCP server in the network listening on port 67 for client ID grid112-oranode1-vip
CRS-4000: Command discover failed, or completed with errors.
[root@oranode1 bin]#
The dhcp server is tested by my admin.
Any Idea how to debug this problem ?
Thanks
Peter

Thanks , but this does not work
[root@oranode1 ~]# /u01/install/11.2.0.2/grid/runcluvfy.sh comp dhcp -clustername grid112
You must NOT be logged in as root (uid=0) when running /u01/install/11.2.0.2/grid/runcluvfy.sh.
[root@oranode1 ~]# su - grid
[grid@oranode1 ~]$ /u01/install/11.2.0.2/grid/runcluvfy.sh comp dhcp -clustername grid112
Verifying DHCP Check
PRVF-0055 : User "grid" does not have sufficient authorization to run this command
Verification of DHCP Check was unsuccessful on all the specified nodes.
[grid@oranode1 ~]$
do you know why?
Thanks
Peter

Similar Messages

  • Unable to contact DHCP server. Lenovo 3000 K100 w/Gigabit LAN and Windows Vista

    I tried ipconfig release/renew command and got "Unable to contact DHCP server." message.
    Any help is greatly appreciated.
    S
    Message Edited by seniaFarber on 05-30-2008 03:51 AM

    Hi Destrijderen5,
    Have you tried reinstalling and then uninstalling ZoneAlarm?
    Maliha (I don't work for lenovo)
    ThinkPads:- T400[Win 7], T60[Win 7], IBM 240[Win XP]
    IdeaPad: U350
    Apple:- Macbook Air [Snow Leopard]
    Did someone help you today? Compliment them with a Kudos!
    Was your question answered today? Mark it as an Accepted Solution! 
      Lenovo Deutsche Community     Lenovo Comunidad en Español 
    Visit my YouTube Channel

  • Unable to find DHCP-server after 5 minutes?

    When I turn on my MacBook and jack in the network cable, the network and internet works perfectly. But after 5 minutes somehow it loses the ip-address gained from the dhcp-server and assigns his own ip-address. Trying to refresh dhcp settings doesn't work, and when I restart my mac, it works again... for 5 minutes, then it loses it's connection again.
    I have 2 pc's connected to the same switch and they function beyond 5 minutes, so the problem is definitely with the mac. Does anyone have a clue what this could be?
    MacBook   Mac OS X (10.4.7)  

    Dag, Koen
    feestelijk inhalen (is that used correctly, here?)
    Does your mac have any PPPoE settings configured in the SystemPreferences>Network>Built_In>..PPPoE tab...?
    My guess is that you don't need anything other than standard TCP/IP settings.
    Let us know, alstublieft?

  • Can't access internet-unable to contact DHCP server?

    Help! i'm a total computer flunkie so please not too much computer jargon-my husband accidentally cut our phone line which cut out our DSL and when he respliced it the internet started working on our builtin wireless laptop but not on our desktop that is using the WRT54G wireless router and compact Wireless G USB adapter.  None of our computers are near our phone line.  I tried to renew IPconfig through CMD screen but it gives me this error: uable to contact your DHCP server. Request has timed out.  I tried reinstalling the adapter but that didn't work.  Do I need to change something on the router by connecting our laptop to it? Please help!! This is driving me crazy Thanks!

    Go to your device manager (Right click My Computer, then click Properties, then device manager should be under hardware tab), check and make sure your wireless adapter driver is installed well.
    Then access to your router's web management page, ensure that the DHCP setting is set correctly. Might try to reboot your router after that. Finally try to acquire the IP address from your desktop computer again.
    You can also try to assign the IP, netmask, gateway, DNS manually on the desktop computer if still failing to get the IP from DHCP server.
    Hope helps..
    picoHat
    Home Network, Wireless Network and Computer Networking Made Easy

  • X3000 Router - Unable to contact DHCP Server

    I have been experiencing this problem for about a week or two...
    Every couple of hours all of my computers and devices on the network lose their network connectivity and no matter what you do on the pc, nothing works...
    But as soon as you restart the router... everything works fine again...
    I have reset the router configuration, re-loaded the firmware and even changed the dhcp settings and the problem persists...
    Anyone have a solution?

    I would like to ask few questions, before I suggest you for any troubleshooting steps. Like- does it happen in both wired and wireless network? You can try the following combination of settings:-
    A] With the help of Cisco Connect Software (if at all you have installed the router with the help of this software)
              1] Open the software and go to the option which says "Router Settings"
              2] Then click on the option which says "Advanced Settings" which will take you to the router's configuration page.
             3] Then go to the Wireless tab, keep network mode as mixed, and make Channel Width to 20 MHz only and Channel to 6, 9, 11..
             4] Lower the MTU (Maximum Transmission Unit) from 1500 to 1400 or less (usually found on your router's main/ basic setup page)
    B] If you haven't installed Cisco Connect then you can log on to the router's user interface using its default IP address in the browser which is 192.168.1.1 and type in 'admin' as the password leaving the user name field blank. This will take you to the router's web interface and then follow steps as mentioned above to make the changes.
    Then check the connectivity status…

  • Unable to bring up crs on rac node 2 after server reboot

    Hi,
    We have a 2 node rac architecture. We are only able to bring up Node 1 on the cluster, whereas node 2 is failing. Here are some points::
    1. After the server reboot, node 2 crs crs/resources weren't starting up apart from OHAS.
    2. We again stopped both the CRS and tried bringing up CRS on node 2 initially and succeeded. But now node 1 wasn't coming up.
    3. Again brought down both nodes' CRS and tried bringing up CRS on node1 and succeded but asm wasn't showing the Diskgroups. So we changed pfile to include asm_diskstring from ORCL* to /dev/oracleasm/disks and we could lsdg in asm now.So started all the instances from node 1 now. Apart from this, again node 2 CRS wasn't starting. From alertlog I saw "CRS-1714:Unable to discover any voting files, retrying discovery in 15 seconds;". But we were able to query voting disks initially. What has gone wrong now??
    ./crsctl status res -t -init
    NAME           TARGET  STATE        SERVER                   STATE_DETAILS
    Cluster Resources
    ora.asm
          1        OFFLINE OFFLINE
    ora.cluster_interconnect.haip
          1        ONLINE  OFFLINE
    ora.crf
          1        ONLINE  ONLINE       kusmnd0r
    ora.crsd
          1        ONLINE  OFFLINE
    ora.cssd
          1        ONLINE  OFFLINE                               STARTING
    ora.cssdmonitor
          1        ONLINE  ONLINE       kusmnd0r
    ora.ctssd
          1        ONLINE  OFFLINE
    ora.diskmon
          1        OFFLINE OFFLINE
    ora.evmd
          1        ONLINE  OFFLINE
    ora.gipcd
          1        ONLINE  ONLINE       kusmnd0r
    ora.gpnpd
          1        ONLINE  ONLINE       kusmnd0r
    ora.mdnsd
          1        ONLINE  ONLINE       kusmnd0r
    This is the history of activitites. Kindly someone throw light on this please.
    Thanks,
    Anirban.

    It is on a raw device.
    Healthy node::
    ls -ltrh /dev/vote*
    brw-rw---- 1 crsdwqa dbadwqa 120, 1057 Nov  6 11:32 /dev/vote3
    brw-rw---- 1 crsdwqa dbadwqa 120, 1025 Nov  6 11:32 /dev/vote1
    brw-rw---- 1 crsdwqa dbadwqa 120, 1041 Nov  6 11:32 /dev/vote2
    Affected Node::
    ls -ltrh /dev/vote*
    brw-rw-r-- 1 crsdwqa dbadwqa 120, 1025 Nov  4 12:06 /dev/vote1
    brw-rw-r-- 1 crsdwqa dbadwqa 120, 1041 Nov  4 12:06 /dev/vote2
    brw-rw-r-- 1 crsdwqa dbadwqa 120, 1057 Nov  5 04:42 /dev/vote3
    Regards,
    Anirban.

  • Unable to get ip address from DHCP server for Aironet 1130AG Access Point

    I have a network in which DHCP server is enabled. I have read the installation guide also there it is mentioned that 1130G Access point will not have any staic ip assigned to it.So it will automatically get the ip from the DHCP server from the network. I have connected that from the network but it is unable to get the ip address from the same. The same thing i have configured in the netgear it is coming fine. I have seen the sonic wall and used the IPSU tool also from checking the ip address from Mac Address but i am not able to get the same. Please provide me some tips to check where i am wrong in configuration because the first web page also not coming because of the ip address.

    narendra,
    I would suggest that the AP be connected to a laptop or desktop pc that would run a local dhcp server with a small scope setup...plenty of free ones on the web(this pc would obviously not be connected to your currnet network). This way you can watch the dhcp server hand the AP it's address (this can take a few minutes). Once you have the address use it to access the GUI and give the AP a static address (I find it good pratice to give all my autonomous AP's static addresses for ease of troubleshooting)...Hope that helps.

  • AVAYA IP Phones unable to get an IP address from DHCP server.

    I installed new SRW208P switch and I mada an uplink connection with SRW 2024 switch (using GE port).
    when I am trying to connect AVAYA IP Phone to the SRW208P port, the set trying to get an IP address from the DHCP server and failed to get it.
    some times after 10 minutes, it get the IP address, but all the machines (PCs) connected to the same switch (SRW208P) hange.
    Note: the PCs an IP Phones are connected with separate UTP cables to the access switch.
    Is there any suggestions to solve this issue, please.
    Regards, 

    The issue is that your machine is not being assigned an IP address / was unable to reach the DHCP server to receive one. The 169.254.x.x IP your machine is showing isn't assigned from DHCP, it's assigned by the local machine and is referred to as an APIPA
    address.
    So something is preventing your machine from reaching your DHCP server, which could one of a number of things. In the first instance I'd suggest having a look at
    http://epan36.blogspot.co.uk/2012/09/eventid-1001-dhcp-your-computer-was-not.html which lists several of things that could cause this error and things you can try in order to resolve it.
    If none of those work, can you confirm whether you have any other machines connecting via the same method on the network, which might indicate whether this is an issue at the machine end or somewhere between the machine and DHCP server?

  • DHCP Discover reaches Server but Server doesn't respond

    I have setup DHCP on my domain controller. It's authorized, configured with an active scope, etc.  When I perform a DHCP renew from a client, I can see the DHCP discover frame reaching the server (verified the client MAC within the frame). However,
    the DHCP server never responds with an Offer. When I look at the DHCP server log in \system32\dhcp there is no mention of any requests, denied or otherwise...nothing. I have disable the Windows Firewall and the Sophos security agents to make sure the Windows
    Filtering Platform isn't dropping the frame before it reaches the DHCP Server service. I'm kind of stuck on figuring out what's happening.
    Any suggestions?

    Hi  Ewood70 ,
    First ,we need to ensure DHCP service is running .
    Open Services and check if
    DHCP Server is running .
    Then ,we need to check DHCP audit logging is enabled .
    Here are the steps :
    Open DHCP .
    In the console tree
    ,expand the DHCP server .
    Click
    IPv4 (or IPv6) .
    On the
    Action menu ,click Properties .
    On the
    General tab ,select Enable DHCP audit logging ,and then click
    OK .
    At last ,we can check the events of DHCP server to find out the problem .
    Open Server Manager and click
    DHCP Server .We could see the events on the right .
    Best Regards,
    Leo
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • WLC 5508 Internal DHCP server issues

    Hi,
    I am hoping to get your feedback around the dhcp issues I am facing with Two Centrally Switched Wireless LANs. I have tried to explain the setup and the problems below and would appreciate it if anyone can suggest a solution for the problems I am facing:
    The setup is as follows:
    - I have a WLC 5508 which has been configured with 4 SSIDs, out of which 2 are using Central Authentication and Switching.
    - I have an LWAP connected to the WLC in HREAP mode.
    - WLC is configured as the DHCP server for clients connecting to the SSID 'Guest'. For the rest, I am using external dhcp server.
    - Only one scope for Guest Interface is setup on the WLC. 
    Problems:
    1. As far as I know, for WLC to act as internal dhcp server, it is mandatory to have the proxy enabled, but the Clients connecting to SSID 'Internet' are
    unable to get an ip address from the external dhcp server, if dhcp proxy is enabled on the WLC. If i disable the proxy, it all works fine.
    2. DHCP does not release the ip addresses assigned to clients even after they are logged out.
    3. If a machine which was earlier connected to 'Guest' SSID connects to the 'Internet' SSID, it requests the same ip it was assigned by the WLC which it was assigned under 'Guest', but gets tagged with the Vlan configured on the management interface.  
    ************Output from the Controller********************
    (Cisco Controller) >show sysinfo
    Manufacturer's Name.............................. Cisco Systems Inc.
    Product Name..................................... Cisco Controller
    Product Version.................................. 7.0.116.0
    Bootloader Version............................... 1.0.1
    Field Recovery Image Version..................... 6.0.182.0
    Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
    Build Type....................................... DATA + WPS + LDPE
    (Cisco Controller) >show interface summary
    Interface Name                   Port Vlan Id  IP Address         Type        Ap Mgr        Gu                                                                            
    est
    guest                                        1    301      10.255.255.30    Dynamic   No              No                                                                            
    management                          1    100      172.17.1.30        Static          Yes            No                                                          
    service-port                              N/A  N/A      192.168.0.1       Static         No               No                                                                            
    virtual                                        N/A   N/A      10.0.0.1              Static         No               No                                                                            
    (Cisco Controller) >show wlan summary
    Number of WLANs.................................. 4
    WLAN ID  WLAN Profile Name / SSID               Status    Interface Name
    1        LAN                                    Enabled   management
    2        Internet                               Enabled   management
    3        Managment Assets          Enabled   management
    4        Guest                                  Enabled   guest
    (Cisco Controller) >show dhcp detailed guest
    Scope: guest
    Enabled.......................................... Yes
    Lease Time....................................... 86400 (1 day )
    Pool Start....................................... 10.255.255.31
    Pool End......................................... 10.255.255.254
    Network.......................................... 10.255.255.0
    Netmask.......................................... 255.255.255.0
    Default Routers.................................. 10.255.255.1  0.0.0.0  0.0.0.0
    DNS Domain.......................................
    DNS.............................................. 8.8.8.8  8.8.4.4  0.0.0.0
    Netbios Name Servers............................. 0.0.0.0  0.0.0.0  0.0.0.0
    (Cisco Controller) >show interface detailed management
    Interface Name................................... management
    MAC Address...................................... e8:b7:48:9b:84:20
    IP Address....................................... 172.17.1.30
    IP Netmask....................................... 255.255.255.0
    IP Gateway....................................... 172.17.1.1
    External NAT IP State............................ Disabled
    External NAT IP Address.......................... 0.0.0.0
    VLAN............................................. 100
    Quarantine-vlan.................................. 0
    Active Physical Port............................. 1
    Primary Physical Port............................ 1
    Backup Physical Port............................. Unconfigured
    Primary DHCP Server.............................. 172.30.50.1
    Secondary DHCP Server............................ Unconfigured
    DHCP Option 82................................... Disabled
    ACL.............................................. Unconfigured
    AP Manager....................................... Yes
    Guest Interface.................................. No
    L2 Multicast..................................... Enabled
    (Cisco Controller) >show interface detailed guest
    Interface Name................................... guest
    MAC Address...................................... e8:b7:48:9b:84:24
    IP Address....................................... 10.255.255.30
    IP Netmask....................................... 255.255.255.0
    IP Gateway....................................... 10.255.255.1
    External NAT IP State............................ Disabled
    External NAT IP Address.......................... 0.0.0.0
    VLAN............................................. 301
    Quarantine-vlan.................................. 0
    Active Physical Port............................. 1
    Primary Physical Port............................ 1
    Backup Physical Port............................. Unconfigured
    Primary DHCP Server.............................. Unconfigured
    Secondary DHCP Server............................ Unconfigured
    DHCP Option 82................................... Disabled
    ACL.............................................. Unconfigured
    AP Manager....................................... No
    Guest Interface.................................. No
    L2 Multicast..................................... Enabled
    (Cisco Controller) >show dhcp leases
           MAC                IP         Lease Time Remaining
    00:21:6a:9c:03:04    10.255.255.46    23 hours 52 minutes 42 seconds        <<<<<<< lease remains even when the client is disconnected.
    *********Example of Client connected to the right Vlan with an ip address from the incorrect interface. *************
    (Cisco Controller) >show client detail 00:21:6a:9c:03:04
    Client MAC Address............................... 00:21:6a:9c:03:04
    Client Username ................................. N/A
    AP MAC Address................................... a0:cf:5b:00:49:c0
    AP Name.......................................... mel
    Client State..................................... Associated
    Client NAC OOB State............................. Access
    Wireless LAN Id.................................. 2                 <<<<<<<<   'Internet' SSID
    BSSID............................................ a0:cf:5b:00:49:ce
    Connected For ................................... 319 secs
    Channel.......................................... 36
    IP Address....................................... 10.255.255.46      <<<<<<< IP address assigned from the 'Guest' Interface or dhcp scope on the WLC
    Association Id................................... 1
    Authentication Algorithm......................... Open System
    Reason Code...................................... 1
    Status Code...................................... 0
    Session Timeout.................................. 1800
    Client CCX version............................... 4
    Client E2E version............................... 1
    QoS Level........................................ Silver
    802.1P Priority Tag.............................. disabled
    WMM Support...................................... Enabled
    Power Save....................................... OFF
    Mobility State................................... Local
    Mobility Move Count.............................. 0
    Security Policy Completed........................ Yes
    Policy Manager State............................. RUN
    Policy Manager Rule Created...................... Yes
    ACL Name......................................... none
    ACL Applied Status............................... Unavailable
    Policy Type...................................... N/A
    Encryption Cipher................................ None
    Management Frame Protection...................... No
    EAP Type......................................... Unknown
    H-REAP Data Switching............................ Central       <<<<<<<<<
    H-REAP Authentication............................ Central       <<<<<<<<<<
    Interface........................................ management
    VLAN............................................. 100           <<<<<<<<<<< right Vlan
    Quarantine VLAN.................................. 0
    Access VLAN...................................... 100

    Hi All,
    I have a similar issue where Wireless clients are not receiving automatic addressing from an internal DHCP server. I have multiple interfaces configured on the WLC which are connected to separate VLANS. The manually specified DHCP primary server entry is the same on all interfaces. Some clients are able to authenticate and receive automatic IP configuration but some clients are failing the address assignment process. I have checked connectivity between the WLC and DHCP server, this is confirmed as working. When I carry out a "debug dhcp packet enable", I get the following outputs which seems as if the DHCP discover request from the client is skipped. Your thoughts and inputs on this are appreciated.
    DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option len (including the magic cookie) 76
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: message type = DHCP DISCOVER
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 116 (len 1) - skipping
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 61 (len 7) - skipping
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: requested ip = 169.254.223.5
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 12 (len 13) - skipping
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: vendor class id = MSFT 5.0 (len 8)
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 55 (len 11) - skipping
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 43 (len 2) - skipping
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP options end, len 76, actual 68
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP Forwarding DHCP packet (332 octets) packet DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option len (including the magic cookie) 76
    Thanks,
    Raj Sandhu

  • No contact with DHCP server when using VPN Client

    Pretty weird problem I discovered recently.
    We use the VPN Client to connect to a 1841 router. Everything works fine except for one small thing.
    The client do not send out _any_ traffic if the destination is the ip-address of the DHCP-server the client got its original ip-address from.
    This is verified by Wireshark. A ping on the client do not produce any ESP packets towards the VPN concentrator. No matter what traffic you try actually.
    Discovered this when wanting to use Remote Desktop towards the Windows Server that is the local DHCP server and was not able to connect. Then tested ping and still no response. That made me look closer and found out that I could not communicate at all with the DHCP server.
    As I said, pretty weird.
    Anyone else have seen this? Anyone have a solution? Right now I use OpenVPN instead when I need to control that server.
    - Roger

    Hi and thanks for responding.
    Nothing here apart from being unable to send any packets to the dhcp-server. No problem sending to any other system on the same subnet. The same happens when I connect my pc to another subnet that is served by another dhcp-server. Then I can not connect to _that_ dhcp-server. I can then of course connect to the previous dhcp-server.
    I mean _no_ packets are generated out the client at all if the destination are your dhcp-server. No problem with the packet being blocked by a firewall or anything like that. Ping another system on the same subnet as the dhcp-server and the client happily generates ESP packets and sends them to the vpn-concentrator.
    I do not know if it was clear enough in the first post so I am saying it here: the vpn-concentrator gives out the ip for the vpn connection. The dhcp-server I can not connect to is the server that gives the client its ip-address _before_ starting up the vpn client.
    We use this vpn system so the IT personell will be able to connect to restricted resources from their laptops anywhere in the network, also when using wireless.
    This was discovered when one admin wanted to connect from his laptop to a server that also happened to be the dhcp-server that had given his laptop his ip address before he used vpn.
    Should be easy enough for anyone else to test. Just ping your dhcp-server after starting the vpn connection. No RFC 1918 addresses of course, there must be a route from your vpn-concentrator to your dhcp-server and at least icmp echo must be open through any firewall/acl.
    The vpn version is 4.8.00.0440 on Windows XP configured to not allow local LAN access. I might test this with other versions/OS'es when I have the time.
    Regards,
    - Roger

  • Unable to install SQL Server 2012 on my Surface 3 computerr w/Windows 8.1 as the OS

    Another user,
    Cheer08, has replied to a thread you have subscribed to in the
    SQL Server Express Forum.
    Here are the error messages:
    Error 2
    Error 1
    Hello,
    This error is related to Microsoft Visual C++ 2005. Could you try to download and install Microsoft Visual C++ 2005 with service pack 1 (SP1) included:
    http://www.microsoft.com/en-us/download/details.aspx?id=5638 (x86 or 32-bit)
    http://www.microsoft.com/en-us/download/details.aspx?id=18471
    (x64 or 64-bit)
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com
    Thread Title Unable to install SQL Server 2012 on my Surface 3 computerr w/Windows 8.1 as the OS.
    Started by: FenixRising
    Reply:
    Fenix, this is SQL Server forum. Regarding the Visual C++ 2005 SP1 Redistributable setup issue, you need to post question in
    visual studio forum to get better help.
    After installing Visual C++ 2005 SP1 Redistributable successfully,are you able to install SQL Server? If not, share us SQL Server setup logs. This link
    https://msdn.microsoft.com/en-us/library/ms143702(v=sql.110).aspx will help you View and Read SQL Server Setup Log Files
    Im going to run it now. Get back to you.

    Hi,
        I am unable to install SQL Server 2012. I have the install log, but I don't can't read them.
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2053898239
      Start time:                    2015-02-08 23:03:01
      End time:                      2015-02-08 23:07:31
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for Adv_SSMS:        Use the following information to resolve the error, and then try the setup process again.
      Next step for SSMS:            Use the following information to resolve the error, and then try the setup process again.
      Next step for RS:              Use the following information to resolve the error, and then try the setup process again.
      Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.
      Next step for FullText:        Use the following information to resolve the error, and then try the setup process again.
      Next step for Replication:     Use the following information to resolve the error, and then try the setup process again.
    Machine Properties:
      Machine name:                  RLC_WORK
      Machine processor count:       4
      OS version:                    Future Windows Version
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered  Configured
      SQL Server 2012                                                         
    Client Tools Connectivity                1033                                     
    11.2.5058.0     No         Yes       
      SQL Server 2012                                                         
    Client Tools Backwards Compatibility     1033                                     
    11.2.5058.0     No         Yes       
      SQL Server 2012                                                         
    Client Tools SDK                         1033                                     
    11.2.5058.0     No         Yes       
      SQL Server 2012                                                         
    SQL Server Data Tools                    1033                 Express Edition     
    11.2.5058.0     No         Yes       
      SQL Server 2012                                                         
    LocalDB                                  1033                
    Express Edition      11.0.2100.60    No         Yes       
    Package properties:
      Description:                   Microsoft SQL Server 2012
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      Installation location:         C:\76766b629842c4dc54646a47c04202\x64\setup\
      Installation edition:          Express
      Slipstream:                    True
      SP Level                       2
    Product Update Status:
      Success: KB 2958429
    Product Updates Selected for Installation:
      Title:                         Service Pack 2
      Knowledge Based Article:       KB 2958429
      Version:                       11.2.5058.0
      Architecture:                  x64
      Language:                      1033
      Update Source:                 Slipstream
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      true
      AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Disabled
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    true
      ENU:                           true
      ERRORREPORTING:                true
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, RS, SSMS, ADV_SSMS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SQLEXPRESS
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      IACCEPTSQLSERVERLICENSETERMS:  true
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    SQLEXPRESS
      INSTANCENAME:                  SQLEXPRESS
      ISSVCACCOUNT:                  NT AUTHORITY\Network Service
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          AllFeatures_WithDefaults
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              DefaultSharePointMode
      RSSVCACCOUNT:                  NT Service\ReportServer$SQLEXPRESS
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           RLC_WORK\Robert
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  true
      TCPENABLED:                    0
      UIMODE:                        AutoAdvance
      UpdateEnabled:                 true
      UpdateSource:                  Slipstream
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150208_230228\ConfigurationFile.ini
    Detailed results:
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                Microsoft .NET Framework 3.5
      Component error code:          0x85940001
      Error description:             Error while enabling Windows feature : NetFx3, Error Code : -2146498270 , Please try enabling Windows feature : NetFx3 from Windows management tools and then run
    setup again. For more information on how to enable Windows features , see http://go.microsoft.com/fwlink/?linkid=227143
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0x681D636F%401428%401&EvtType=0x681D636F%401428%401
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                Microsoft .NET Framework 3.5
      Component error code:          0x85940001
      Error description:             Error while enabling Windows feature : NetFx3, Error Code : -2146498270 , Please try enabling Windows feature : NetFx3 from Windows management tools and then run
    setup again. For more information on how to enable Windows features , see http://go.microsoft.com/fwlink/?linkid=227143
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0x681D636F%401428%401&EvtType=0x681D636F%401428%401
      Feature:                       Reporting Services - Native
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                Microsoft .NET Framework 3.5
      Component error code:          0x85940001
      Error description:             Error while enabling Windows feature : NetFx3, Error Code : -2146498270 , Please try enabling Windows feature : NetFx3 from Windows management tools and then run
    setup again. For more information on how to enable Windows features , see http://go.microsoft.com/fwlink/?linkid=227143
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0x681D636F%401428%401&EvtType=0x681D636F%401428%401
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                Microsoft .NET Framework 3.5
      Component error code:          0x85940001
      Error description:             Error while enabling Windows feature : NetFx3, Error Code : -2146498270 , Please try enabling Windows feature : NetFx3 from Windows management tools and then run
    setup again. For more information on how to enable Windows features , see http://go.microsoft.com/fwlink/?linkid=227143
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0x681D636F%401428%401&EvtType=0x681D636F%401428%401
      Feature:                       Full-Text and Semantic Extractions for Search
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                Microsoft .NET Framework 3.5
      Component error code:          0x85940001
      Error description:             Error while enabling Windows feature : NetFx3, Error Code : -2146498270 , Please try enabling Windows feature : NetFx3 from Windows management tools and then run
    setup again. For more information on how to enable Windows features , see http://go.microsoft.com/fwlink/?linkid=227143
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0x681D636F%401428%401&EvtType=0x681D636F%401428%401
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                Microsoft .NET Framework 3.5
      Component error code:          0x85940001
      Error description:             Error while enabling Windows feature : NetFx3, Error Code : -2146498270 , Please try enabling Windows feature : NetFx3 from Windows management tools and then run
    setup again. For more information on how to enable Windows features , see http://go.microsoft.com/fwlink/?linkid=227143
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0x681D636F%401428%401&EvtType=0x681D636F%401428%401
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150208_230228\SystemConfigurationCheck_Report.htm
    Fenix

  • DHCP Setup across multiple VLANs on RV325 - DHCP Server only working on VLAN 1

    I have multiple VLAN subnets defined on my RV325 - when I try and utilize a DHCP Server on each VLAN, it only seems to be issuing IP Addresses to clients on VLAN ID 1.  When I first set this up months ago, I thought I had tested it providing IP Addresses via the other subnets.  Now that I am trying to do so, it isn't working "as expected".  Example - I am using VLAN 25 as the GuestWireless subnet utilizing a separate 802.11n WAP that is set to Bridge connections to the IP Address of the VLAN interface.  Devices are able to connect to the WAP, but end up with a self-assigned IP Address 169.x.x.x address.  There has to be an easy fix to this, but I seem to be "stuck" figuring out what it is…pointers/redirects appreciated.  Thanks!

    Thanks - I've already reviewed that information before I posted.  I've been working with DHCP since the mid-90's, so I'm comfortable with the settings/configuration I need to leverage to make this work via other means using various Network-based OSes.
    I'm wondering if there are other options in configuring this device that can impact the ability to dynamically serve IP addresses on a VLAN/subnet-by-VLAN/subnet basis.
    As I did more testing, I discovered when I reserved an IP Address via the IP & MAC Binding option within the DHCP Settings, those devices would receive their static reservations and work as expected, so the problem seems to be leveraging the DHCP Pool for devices connecting to VLANs other that VLAN 1.
    Any ideas as to why the DHCP Pool's are "non-functioning" for the other VLANs is greatly appreciated...
    Each VLAN is setup with a separate DHCP Server configuration as shown below:
    VLAN ID = 1 (Default, Inter VLAN Routing = Enabled, LAN1-6 = Untagged, LAN7=Tagged, LAN8=Excluded, LAN9-14 Untagged)
    Device IP Address = 172.16.xxx.1
    Subnet Mask = 255.255.255.0
    DHCP Mode = DHCP Server
    Remote DHCP Server = 0.0.0.0
    Client Lease Time = 1440 min
    Range Start = 172.16.xxx.100
    Range End = 172.16.xxx.199
    DNS Server = Use DNS as Below
    Static DNS 1 = 208.67.222.222
    Static DNS 2 = 208.67.220.220
    WINS Server = 0.0.0.0
    Correctly serving IP Addresses via DHCP (both static and dynamic) to Wired devices & Wireless devices connecting through WAP (set to Bridge)
    VLAN ID = 25 (GuestWireless, Inter VLAN Routing = Disabled, LAN1-LAN7 = Excluded, LAN8 = Untagged, LAN9-14 = Excluded)
    Device IP Address = 172.16.yyy.1
    Subnet Mask = 255.255.255.0
    DHCP Mode = DHCP Server
    Remote DHCP Server = 0.0.0.0
    Client Lease Time = 1440 min
    Range Start = 172.16.yyy.100
    Range End = 172.16.yyy.199
    DNS Server = Use DNS as Below
    Static DNS 1 = 208.67.222.222
    Static DNS 2 = 208.67.220.220
    WINS Server = 0.0.0.0
    NOT serving dynamic IP Addresses via DHCP to Wired devices & Wireless devices connecting through WAP (set to Bridge)
    Static DHCP Reservations setup via IP & MAC Binding settings DO WORK in terms of providing the assigned static IP Address to the client.  Inbound/Outbound traffic to Internet works for devices with Static DHCP Reservations.
    VLAN ID = 100 (Voice, Inter VLAN Routing = Disabled, LAN1-6 Excluded, LAN7 = Untagged, LAN8-14 = Excluded)
    Device IP Address = 192.168.zzz.1
    Subnet Mask = 255.255.255.0
    DHCP Mode = DHCP Server
    Remote DHCP Server = 0.0.0.0
    Client Lease Time = 1440 min
    Range Start = 192.168.zzz.100
    Range End = 192.168.zzz.199
    DNS Server = Use DNS as Below
    Static DNS 1 = 208.67.222.222
    Static DNS 2 = 208.67.220.220
    WINS Server = 0.0.0.0
    NOT serving dynamic IP Addresses via DHCP to Wired devices & Wireless devices connecting through WAP set to Bridge
    Static DHCP Reservations setup via IP & MAC Binding settings DO WORK in terms of providing the assigned static IP Address to the client.  Inbound/Outbound traffic to Internet works for devices with Static DHCP Reservations.

  • DNS/DHCP app no longer sees DNS/DHCP server.

    When I moved the majority of my Netware 6 servers to OES-NW last year, I started using iManager to handle admin duties for DNS and DHCP.
    With a planned move to OES-L coming up, I tried accessing both services using the DNS/DHCP java console.
    While I am able to log into that console, I am unable to see my DNS/DHCP server or any of the expected components for either service (DHCP pools, zone records, etc...).
    I have tried both the console that is installable from the server and the newer LDAP-based version.
    I have tried both 32 and 64-bit versions on XP and Windows 7, respectively.
    Since I want to move those services to OES/Linux and the java console is the only mechanism that can administrate the services on that platform, I am perplexed.
    My needs are simple, and I could easily move those duties to a SUSE server or even a Windows server, but that is not my preference.
    Any ideas on where to begin troubleshooting are welcome.

    On 06.08.2012 21:56, gathagan wrote:
    >
    > When I moved the majority of my Netware 6 servers to OES-NW last year, I
    > started using iManager to handle admin duties for DNS and DHCP.
    >
    > With a planned move to OES-L coming up, I tried accessing both services
    > using the DNS/DHCP java console.
    >
    > While I am able to log into that console, I am unable to see my
    > DNS/DHCP server or any of the expected components for either service
    > (DHCP pools, zone records, etc...).
    >
    > I have tried both the console that is installable from the server and
    > the newer LDAP-based version.
    > I have tried both 32 and 64-bit versions on XP and Windows 7,
    > respectively.
    >
    > Since I want to move those services to OES/Linux and the java console
    > is the only mechanism that can administrate the services on that
    > platform, I am perplexed.
    > My needs are simple, and I could easily move those duties to a SUSE
    > server or even a Windows server, but that is not my preference.
    >
    > Any ideas on where to begin troubleshooting are welcome.
    You have more than one DNS-DHCP locator object in your tree, and the
    console is picking up a/the empty one. Find the proper object (look at
    the other tab in consoleone or imanager to see if it's connected with
    servers zones and the like), and delete the superflouos ones.
    This is an *extremely* common problem when OES gets introduced into a
    tree, as it by default creates new locator objects in the server
    container, if it's not configured otherwise.
    CU,
    Massimo Rosen
    Novell Knowledge Partner
    No emails please!
    http://www.cfc-it.de

  • Guest VLAN unable to get DHCP IP address from Anchor Controller

    Hello everybody,
    In our test set up, we have two WLC 5508 Controllers connected via Checkpoint UTM-1 firewall Inside and DMZ Interfaces. Both the WLC controllers are connected to the firewall via Cisco 3750 switch. On the Local (Inside) Controller, guest SSID is enabled and attached to the wireless management Interface. On the remote anchor controller, guest SSID is enabled and attached to the Management Interface as well. The following configs are replicated on both the Controllers.
    SSID Name - guest
    Interface - Management ( VLAN 10 on Local and VLAN 20 on remote) -
    Mobility Group: Same configs at both ends
    SSID Anchor : Anchor SSID on local and local SSID on Anchor.
    AP: CAPWAP 3502 Management Subnet
    SSID Security etc all defaults and matching on  both ends
    Checkpoint Firewall Rules: Allowed 16666-7, IP 97 etc on the firewall
    Checkpoint Inside/DMZ to Outside(Internet) is NAT enabled.
    EoIP Tunnel Status: Up, UP - Both ends
    Mping - OK
    eping - OK
    WLC Sofware Version on Local - 7.0.98.0
    WLC Sofware Version on Local - 7.0.116.0
    DHCP Scope: Definitions on Anchor Controller and Guest Anchor SSID points to the Anchor management IP as the Primary DHCP server.
    Management IP Subnet on Local: 10.x.x.x
    Management IP Subnet on Anchor: 172.x.x.x
    The problem definition as follows:
    When guest SSID associates to the local AP, the guest SSID never gets a DHCP address assigned from the Anchor Controller and the following debugs are obtained.
    1. WLAN ID 1 (for Guest SSID Number) delete message appears in the Controller message logs, but the SSID does not DHCP from the local Management Subnet and i can see DHCP request via the tunnel to the Anchor WLC as follows:
    DHCP Socket Task: Feb 24 17:20:46.612: 64:b9:e8:33:2d:13 DHCP received op BOOTREQUEST (1) (len 308,vlan 0, port 13, encap 0xec03)
    *DHCP Socket Task: Feb 24 17:20:46.612: 64:b9:e8:33:2d:13 DHCP processing DHCP DISCOVER (1)
    *DHCP Socket Task: Feb 24 17:20:46.612: 64:b9:e8:33:2d:13 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
    *DHCP Socket Task: Feb 24 17:20:46.612: 64:b9:e8:33:2d:13 DHCP   xid: 0x49c54774 (1237665652), secs: 42, flags: 0
    *DHCP Socket Task: Feb 24 17:20:46.612: 64:b9:e8:33:2d:13 DHCP   chaddr: 64:b9:e8:33:2d:13
    *DHCP Socket Task: Feb 24 17:20:46.612: 64:b9:e8:33:2d:13 DHCP   ciaddr: 0.0.0.0,  yiaddr: 0.0.0.0
    *DHCP Socket Task: Feb 24 17:20:46.612: 64:b9:e8:33:2d:13 DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0
    *DHCP Socket Task: Feb 24 17:20:46.612: 64:b9:e8:33:2d:13 DHCP successfully bridged packet to EoIP tunnel
    2. Similar debugs on the Anchor controller yields the following results;
    Cisco Controller) >*DHCP Socket Task: Feb 25 04:30:25.488: 64:b9:e8:33:2d:13 DHCP options end, len 72, actual 64
    *DHCP Socket Task: Feb 25 04:36:44.246: 64:b9:e8:33:2d:13 DHCP received op BOOTREQUEST (1) (len 308,vlan 20, port 1, encap 0xec05)
    *DHCP Socket Task: Feb 25 04:36:44.246: 64:b9:e8:33:2d:13 DHCP processing DHCP DISCOVER (1)
    *DHCP Socket Task: Feb 25 04:36:44.246: 64:b9:e8:33:2d:13 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
    *DHCP Socket Task: Feb 25 04:36:44.246: 64:b9:e8:33:2d:13 DHCP   xid: 0x49c54778 (1237665656), secs: 52, flags: 0
    *DHCP Socket Task: Feb 25 04:36:44.246: 64:b9:e8:33:2d:13 DHCP   chaddr: 64:b9:e8:33:2d:13
    *DHCP Socket Task: Feb 25 04:36:44.246: 64:b9:e8:33:2d:13 DHCP   ciaddr: 0.0.0.0,  yiaddr: 0.0.0.0
    *DHCP Socket Task: Feb 25 04:36:44.246: 64:b9:e8:33:2d:13 DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0
    *DHCP Socket Task: Feb 25 04:36:44.246: 64:b9:e8:33:2d:13 DHCP successfully bridged packet to DS
    *DHCP Socket Task: Feb 25 04:36:53.208: 64:b9:e8:33:2d:13 DHCP received op BOOTREQUEST (1) (len 308,vlan 20, port 1, encap 0xec05)
    *DHCP Socket Task: Feb 25 04:36:53.208: 64:b9:e8:33:2d:13 DHCP processing DHCP DISCOVER (1)
    *DHCP Socket Task: Feb 25 04:36:53.208: 64:b9:e8:33:2d:13 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
    *DHCP Socket Task: Feb 25 04:36:53.208: 64:b9:e8:33:2d:13 DHCP   xid: 0x49c54778 (1237665656), secs: 61, flags: 0
    *DHCP Socket Task: Feb 25 04:36:53.208: 64:b9:e8:33:2d:13 DHCP   chaddr: 64:b9:e8:33:2d:13
    *DHCP Socket Task: Feb 25 04:36:53.208: 64:b9:e8:33:2d:13 DHCP   ciaddr: 0.0.0.0,  yiaddr: 0.0.0.0
    *DHCP Socket Task: Feb 25 04:36:53.208: 64:b9:e8:33:2d:13 DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0
    *DHCP Socket Task: Feb 25 04:36:53.208: 64:b9:e8:33:2d:13 DHCP successfully bridged packet to DS
    *apfOrphanSocketTask: Feb 25 04:37:49.931: 34:51:c9:59:b1:c7 Invalid MSCB state: ipAddr=169.254.254.148, regType=2, Dhcp required!
    Is there any thing missing in the wireless configs and or the firewall rules as i could not see DHCP request back from the Anchor Controller. Also, after DHCP is obtained, the web authentication request will be redirected to an Amigopod device for authentication. In this case is the redirect URL congiguration to be performed only on the Anchor Controller or is this to be replicated on both the Local and Anchor Controllers.
    Thanks and Regards.

    The DHCP issue is resolved if external DHCP server is configured on a 3750 switch connected to the WLC and the default gateway for DHCP points to the Firewall, which is in the data path between the Inside and Anchor Controllers. DHCP is essentially bridged (no Proxy setting now) from the EoIP tunnel to the Distribution system network. We will test this solution on pilot production and then consider upgrading to 7.0.116.0, as there are about six offices running 7.0.98.0, which will need to be upgraded. 
    For L3 security,  configuration is set up on both the controllers for external captive portal redirection.I will try this only on the Anchor and revert.
    Thanks again very much for all your help.

Maybe you are looking for