Multiple domains via DHCP (option 15)

It seems Mac OS X (I use 10.4.10 but I suspect it affects many versions) is incompatible with receiving multiple domain names in a single string over DHCP Option 15.
If DHCP returns Option 15 with "exampledomain.com eng.exampledomain.com", then any lookup (using dig, ping, Microsoft Entourage, etc.) of a non-fully qualified domain name will fail.
You can see this in the /etc/resolv.conf file, which contains:
domain exampledomain.com eng.exampledomain.com
nameserver 10.X.X.1
nameserver 10.X.X.2
I know that putting multiple domains within the same "domain" option in DHCP is a proprietary hack but some networks still use this. Has anybody run into this and have they found a good resolution to make Mac OS X work with multiple domains?

While a single mailbox can be configured to receive on multiple addresses (called "proxy addresses" or "aliases"), the mailbox is configured with only one primary SMTP address (outbound address).  So if your requirement is to send
as the received address, you would not be able to do that with a single mailbox through normal means.
Some people have developed a workaround to the above limitation by configuring Outlook to use multiple POP3 accounts for a single mailbox.  See this link for additional details: 
http://blogs.technet.com/b/hot/archive/2012/04/26/how-to-add-an-alias-to-an-office-365-account-and-how-to-set-up-outlook-to-send-email-messages-as-this-alias.aspx
I would also be sure to look at the client requirements for Exchange Online.  The supported version of Outlook is going to be Outlook 2010 SP2.  Older versions may work but would not be supported.  Outlook 2003 would at best possibly
connect via POP3.
Joseph Palarchio http://www.itworkedinthelab.com

Similar Messages

  • How to replace DHCP server from domainA with DHCP from domainB?

    Hello fellow Administrators,
    We have one remote site with one subnet. There's domainA domain controller and about 100 domainA's client computers in that subnet. We're about to send 100 domainB's client computers there as well.
    There's also domainA's DHCP server running on the same subnet. DHCP scope options include domainA's domain name, gw and domainA's DNS server addresses.
    DomainA and DomainB belongs to separate forests and there's two-way trust between them. DomainA DNS has stubzone for DomainB and DomainB has stubzone for domainA. That's how
    clients can resolve hostnames of other domain.
    All domainA's clients in remote site will be replaced gradually with domainB's client computers, but this can take a long time.
    I want to note, that I cannot create second subnet for domainB at the moment.
    At some point, we need to deploy DHCP server to domainB's member server in the remote site. What are the steps I should take to replace existing domainA's DHCP server with domainB's DHCP server while still allowing clients from domainA and domainB to successfully
    find domain controller of their own domain and being able to resolve hostnames from both domains?

    When the devices on your network first request an IP address or reach the end of their leases (or you force them to check their lease is still valid) they will simply
    broadcast a request for a DHCP server, and will accept an offer from the first DHCP server
    to reply. 
    Multiple DHCP servers PT 1: Spanning multiple subnets.
    If you have several VLANs or physical network segments that are separated into different subnets, and you want to provide a DHCP service to devices in all those subnets then there are two ways of doing this.
    If the router / layer 3 switch separating them can act as a BOOTP/DHCP relay agent, then you can continue to keep all your DHCP server(s) in one or two central parts of your network and configure your DHCP server(s) to support multiple ranges of addresses.
    In order to support this, your router or layer 3 switch must support the BOOTP relay agent specification covered in section
    4 of RFC 1542.
    If your router does not support RFC 1542 BOOTP relay agents, or if some of your network segments are geographically dispersed over slow links, then you will need to place one or more DHCP server in each subnet. This ‘local’ DHCP server will only serve its own
    local segment’s requirements, and there is no interaction between it and other DHCP servers. If this is what you want then you can simply configure each DHCP server as a standalone server, with the details of the address pool for its own subnet, and not worry
    about any other DHCP servers on other parts of the network. This is the most basic example of having more than one DHCP server on the same network.
    http://www.arabitpro.com

  • Mesh AP joins learns controller IP via DHCP and joins different controller

    Hi ,
    I am testing 1552e mesh AP.It gets its IP information from a lucent qip dhcp server.the problem is this AP gets an IP address and obtained controller IP via option 43 but when it tries to join it goes to another controller not the one on option 43. I have entered the MAC address of this AP in 10.107.133.40 under security - MAC filtering here is the log:
    *Sep 24 12:59:58.959: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
    *Sep 24 13:00:00.015: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.107.133.40 obtained through DHCP
    *Sep 24 13:00:00.015: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.107.133.40 obtained through DHCP
    *Sep 24 13:00:00.015: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
    *Sep 24 13:00:09.015: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
    *Sep 24 13:00:19.015: %CAPWAP-3-ERRORLOG: Go join a capwap controller
    *Sep 24 13:00:19.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.124.133.40 peer_port: 5246
    *Sep 24 13:00:19.595: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.124.133.40 peer_port: 5246
    *Sep 24 13:00:19.595: %CAPWAP-5-SENDJOIN: sending Join Request to 10.124.133.40
    *Sep 24 13:00:19.603: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
    *Sep 24 13:00:19.603: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
    *Sep 24 13:00:19.603: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
    *Sep 24 13:00:19.603: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.124.133.40
    *Sep 24 13:00:24.595: %CAPWAP-5-SENDJOIN: sending Join Request to 10.124.133.40
    any idea?
    Thanks for any help

    Najaf,
    I am attaching a debug results if you are interested.
    Thanks,
    *Sep 24 19:30:50.595: %CAPWAP-5-SENDJOIN: sending Join Request to 10.124.133.40
    *Sep 24 19:31:31.115: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
    *Sep 24 19:31:31.115: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
    *Sep 24 19:31:31.115: %MESH-6-LINK_UPDOWN: Mesh station dca5.f4b8.302f link Down
    *Sep 24 19:31:31.115: %MESH-4-NO_POTENTIAL_PARENT: There are no potential parents
    *Sep 24 19:31:31.315: %MESH-6-ADJ_VIDB_LINK: Mesh neighbor dca5.f4b8.302f VIDB Virtual-Dot11Radio0 going down
    *Sep 24 19:31:31.319: %LINK-6-UPDOWN: Interface Virtual-Dot11Radio0, changed state to down
    *Sep 24 19:31:32.319: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Dot11Radio0, changed state to down
    *Sep 24 19:31:36.131: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:36.139: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:38.155: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:38.163: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:40.179: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:40.187: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:42.203: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:42.211: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:44.227: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:44.235: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:44.999: %CAPWAP-3-EVENTLOG: Wait DTLS timer has expired
    *Sep 24 19:31:44.999: %CAPWAP-3-EVENTLOG: Did not get join response
    *Sep 24 19:31:44.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.124.133.40:5246
    % CDP is not supported on this interface, or for this encapsulation
    *Sep 24 19:31:44.999: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.
    *Sep 24 19:31:44.999: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.
    *Sep 24 19:31:45.843: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
    *Sep 24 19:31:45.895: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:31:45.895: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:31:45.895: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:31:46.251: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:46.259: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:48.275: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:48.283: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:50.299: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:50.307: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:52.323: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:52.331: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:54.347: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:54.355: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:55.899: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
    *Sep 24 19:31:55.899: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:31:55.899: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:31:55.899: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:31:55.899: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:31:55.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1
    *Sep 24 19:31:55.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1
    *Sep 24 19:31:55.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2
    *Sep 24 19:31:56.371: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:56.379: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:58.395: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:31:58.403: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:00.419: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:00.427: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:02.443: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:02.451: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:04.467: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:04.475: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:05.899: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
    *Sep 24 19:32:05.899: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:32:05.899: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:32:05.899: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:32:05.899: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:32:05.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1
    *Sep 24 19:32:05.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1
    *Sep 24 19:32:05.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2
    *Sep 24 19:32:05.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0
    *Sep 24 19:32:06.491: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:06.499: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:08.515: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:08.523: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:10.539: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:10.547: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:12.563: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:12.571: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:14.587: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:14.595: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:15.899: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
    *Sep 24 19:32:15.899: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:32:15.899: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:32:15.899: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:32:15.899: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:32:15.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1
    *Sep 24 19:32:15.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1
    *Sep 24 19:32:15.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2
    *Sep 24 19:32:16.611: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:16.619: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:18.635: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:18.643: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:20.659: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:20.667: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:22.683: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:22.691: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:24.707: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:24.715: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:25.899: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
    *Sep 24 19:32:25.899: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:32:25.899: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:32:25.899: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:32:25.899: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:32:25.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1
    *Sep 24 19:32:25.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1
    *Sep 24 19:32:25.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2
    *Sep 24 19:32:25.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0
    *Sep 24 19:32:26.731: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:26.739: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:32:29.739: %MESH-6-ADJ_VIDB_LINK: Mesh neighbor dca5.f4b8.302f VIDB Virtual-Dot11Radio0 dot1x control
    *Sep 24 19:32:29.743: %LINK-6-UPDOWN: Interface Virtual-Dot11Radio0, changed state to up
    *Sep 24 19:32:30.743: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Dot11Radio0, changed state to up
    *Sep 24 19:32:35.899: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
    *Sep 24 19:32:35.899: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:32:35.899: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:32:38.899: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:32:41.899: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:32:41.899: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.40, type 1.
    *Sep 24 19:32:41.899: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.41, type 1.
    *Sep 24 19:32:41.899: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 42.117.52.200, type 2
    *Sep 24 19:32:51.899: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
    *Sep 24 19:32:51.899: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:32:51.899: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:32:51.899: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:32:51.899: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:32:51.899: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.40, type 1.
    *Sep 24 19:32:51.899: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.41, type 1.
    *Sep 24 19:32:51.899: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 42.117.52.200, type 2
    *Sep 24 19:32:51.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0
    *Sep 24 19:32:59.239: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.
    *Sep 24 19:32:59.239: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    *Sep 24 19:33:01.899: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
    *Sep 24 19:33:01.899: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4
    *Sep 24 19:33:01.899: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
    *Sep 24 19:33:01.899: %CAPWAP-3-ERRORLOG: Failed to process timer message.
    % CDP is not supported on this interface, or for this encapsulation
    *Sep 24 19:33:04.239: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.
    *Sep 24 19:33:04.299: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:33:04.339: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:33:04.339: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:33:04.339: %CAPWAP-3-EVENTLOG: Not waiting for DHCP options as resolve method on interface BVI1 is 4
    *Sep 24 19:33:04.339: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:33:04.339: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:33:04.339: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:33:04.339: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Ignoring WLC name lookup
    *Sep 24 19:33:07.855: %CAPWAP-3-EVENTLOG: ADDING IP 42.117.53.12, 255.255.255.0 resolvemethod  A, ip_dhcp_addr 1
    *Sep 24 19:33:07.855: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.
    *Sep 24 19:33:07.855: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    *Sep 24 19:33:07.927: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 42.117.53.12, mask 255.255.255.0, hostname APdca5.f4b8.5480
    *Sep 24 19:33:07.927: %CAPWAP-3-EVENTLOG: ADDING IP 42.117.53.12, 255.255.255.0 resolvemethod  A, ip_dhcp_addr 1
    *Sep 24 19:33:07.927: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.
    *Sep 24 19:33:07.927: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    % CDP is not supported on this interface, or for this encapsulation
    Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
    *Sep 24 19:33:12.927: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.
    *Sep 24 19:33:12.963: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
    *Sep 24 19:33:12.987: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:33:13.027: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:33:13.027: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:33:14.027: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:33:14.027: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:33:14.027: %CAPWAP-5-DHCP_OPTION_43: Controller address 42.117.52.200 obtained through DHCP
    *Sep 24 19:33:14.027: %CAPWAP-5-DHCP_OPTION_43: Controller address 42.117.52.200 obtained through DHCP
    *Sep 24 19:33:14.027: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
    *Sep 24 19:33:23.027: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
    *Sep 24 19:33:23.027: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1
    *Sep 24 19:33:23.027: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1
    *Sep 24 19:33:23.027: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2
    *Sep 24 19:33:23.027: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0
    *Sep 24 19:33:23.031: %CAPWAP-3-EVENTLOG: Discovery Response from 10.124.133.40
    *Sep 24 19:33:33.027: %CAPWAP-3-EVENTLOG: Selected MWAR 'AJB-C1-WLC5508-1' (index 0).
    *Sep 24 19:33:33.027: %CAPWAP-3-EVENTLOG: Ap mgr count=1
    *Sep 24 19:33:33.027: %CAPWAP-3-ERRORLOG: Go join a capwap controller
    *Sep 24 19:33:33.027: %CAPWAP-3-EVENTLOG: Choosing AP Mgr with index 0, IP = 0xA7C8528 , load = 0..
    *Sep 24 19:33:33.027: %CAPWAP-3-EVENTLOG: Synchronizing time with AC time.
    *Sep 24 19:33:33.000: %CAPWAP-3-EVENTLOG: Setting time to 19:33:33 UTC Sep 24 2013
    *Sep 24 19:33:33.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.124.133.40 peer_port: 5246
    *Sep 24 19:33:33.000: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Setup.
    *Sep 24 19:33:33.591: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.124.133.40 peer_port: 5246
    *Sep 24 19:33:38.591: %CAPWAP-3-EVENTLOG: Join request: version=117728256
    *Sep 24 19:33:38.591: %CAPWAP-3-EVENTLOG: Join request: hasMaximum Message Payload
    *Sep 24 19:33:38.591: %CAPWAP-5-SENDJOIN: sending Join Request to 10.124.133.40
    % CDP is not supported on this interface, or for this encapsulation
    *Sep 24 19:34:32.999: %CAPWAP-3-EVENTLOG: Wait DTLS timer has expired
    *Sep 24 19:34:32.999: %CAPWAP-3-EVENTLOG: Did not get join response
    *Sep 24 19:34:32.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.124.133.40:5246
    *Sep 24 19:34:32.999: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.
    *Sep 24 19:34:32.999: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.
    *Sep 24 19:34:33.039: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
    *Sep 24 19:34:33.059: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:34:33.099: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:34:33.099: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:34:43.099: %CAPWAP-3-EVENTLOG: Selected MWAR 'AJB-C1-WLC5508-1' (index 0).
    *Sep 24 19:34:43.099: %CAPWAP-3-EVENTLOG: Ap mgr count=1
    *Sep 24 19:34:43.099: %CAPWAP-3-ERRORLOG: Go join a capwap controller
    *Sep 24 19:34:43.099: %CAPWAP-3-EVENTLOG: Choosing AP Mgr with index 0, IP = 0xA7C8528 , load = 0..
    *Sep 24 19:34:43.099: %CAPWAP-3-EVENTLOG: Synchronizing time with AC time.
    *Sep 24 19:34:43.000: %CAPWAP-3-EVENTLOG: Setting time to 19:34:43 UTC Sep 24 2013
    *Sep 24 19:34:43.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.124.133.40 peer_port: 5246
    *Sep 24 19:34:43.000: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Setup.
    *Sep 24 19:34:43.591: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.124.133.40 peer_port: 5246
    *Sep 24 19:34:48.591: %CAPWAP-3-EVENTLOG: Join request: version=117728256
    *Sep 24 19:34:48.591: %CAPWAP-3-EVENTLOG: Join request: hasMaximum Message Payload
    *Sep 24 19:34:48.591: %CAPWAP-5-SENDJOIN: sending Join Request to 10.124.133.40
    *Sep 24 19:35:29.111: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
    *Sep 24 19:35:29.111: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
    *Sep 24 19:35:29.111: %MESH-6-LINK_UPDOWN: Mesh station dca5.f4b8.302f link Down
    *Sep 24 19:35:29.111: %MESH-4-NO_POTENTIAL_PARENT: There are no potential parents
    *Sep 24 19:35:29.311: %MESH-6-ADJ_VIDB_LINK: Mesh neighbor dca5.f4b8.302f VIDB Virtual-Dot11Radio0 going down
    *Sep 24 19:35:29.315: %LINK-6-UPDOWN: Interface Virtual-Dot11Radio0, changed state to down
    *Sep 24 19:35:30.315: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Dot11Radio0, changed state to down
    *Sep 24 19:35:34.127: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:34.135: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:36.151: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:36.159: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:38.175: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:38.183: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:40.199: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:40.207: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    % CDP is not supported on this interface, or for this encapsulation
    *Sep 24 19:35:42.223: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:42.231: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:42.999: %CAPWAP-3-EVENTLOG: Wait DTLS timer has expired
    *Sep 24 19:35:42.999: %CAPWAP-3-EVENTLOG: Did not get join response
    *Sep 24 19:35:42.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.124.133.40:5246
    *Sep 24 19:35:42.999: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.
    *Sep 24 19:35:42.999: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.
    *Sep 24 19:35:43.039: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
    *Sep 24 19:35:43.091: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:35:43.091: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:35:43.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:35:44.247: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:44.255: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:46.271: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:46.279: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:48.295: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:48.303: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:50.319: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:50.327: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:52.343: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:52.351: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:53.091: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
    *Sep 24 19:35:53.091: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:35:53.091: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:35:53.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:35:53.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:35:53.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1
    *Sep 24 19:35:53.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1
    *Sep 24 19:35:53.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2
    *Sep 24 19:35:54.367: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:54.375: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:56.391: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:56.399: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:58.415: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:35:58.423: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:00.439: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:00.447: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:02.463: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:02.471: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:03.091: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
    *Sep 24 19:36:03.091: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:36:03.091: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:36:03.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:36:03.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:36:03.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1
    *Sep 24 19:36:03.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1
    *Sep 24 19:36:03.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2
    *Sep 24 19:36:03.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0
    *Sep 24 19:36:04.487: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:04.495: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:06.511: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:06.519: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:08.535: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:08.543: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:10.559: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:10.567: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:12.583: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:12.591: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:13.091: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
    *Sep 24 19:36:13.091: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:36:13.091: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:36:13.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:36:13.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:36:13.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1
    *Sep 24 19:36:13.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1
    *Sep 24 19:36:13.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2
    *Sep 24 19:36:14.607: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:14.615: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:16.631: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:16.639: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:18.655: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:18.663: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:20.679: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:20.687: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:22.703: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:22.711: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:23.091: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
    *Sep 24 19:36:23.091: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:36:23.091: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:36:23.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:36:23.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:36:23.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1
    *Sep 24 19:36:23.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1
    *Sep 24 19:36:23.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2
    *Sep 24 19:36:23.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0
    *Sep 24 19:36:24.727: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:24.735: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:36:27.735: %MESH-6-ADJ_VIDB_LINK: Mesh neighbor dca5.f4b8.302f VIDB Virtual-Dot11Radio0 dot1x control
    *Sep 24 19:36:27.739: %LINK-6-UPDOWN: Interface Virtual-Dot11Radio0, changed state to up
    *Sep 24 19:36:28.739: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Dot11Radio0, changed state to up
    *Sep 24 19:36:33.091: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
    *Sep 24 19:36:33.091: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:36:33.091: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:36:36.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:36:39.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:36:39.091: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.40, type 1.
    *Sep 24 19:36:39.091: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.41, type 1.
    *Sep 24 19:36:39.091: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 42.117.52.200, type 2
    *Sep 24 19:36:49.091: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
    *Sep 24 19:36:49.091: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:36:49.091: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:36:49.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:36:49.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:36:49.091: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.40, type 1.
    *Sep 24 19:36:49.091: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.41, type 1.
    *Sep 24 19:36:49.091: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 42.117.52.200, type 2
    *Sep 24 19:36:49.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0
    *Sep 24 19:36:57.235: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.
    *Sep 24 19:36:57.235: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    *Sep 24 19:36:59.091: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
    *Sep 24 19:36:59.091: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4
    *Sep 24 19:36:59.091: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
    *Sep 24 19:36:59.091: %CAPWAP-3-ERRORLOG: Failed to process timer message.
    % CDP is not supported on this interface, or for this encapsulation
    *Sep 24 19:37:02.235: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.
    *Sep 24 19:37:02.295: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:37:02.335: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:37:02.335: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:37:02.335: %CAPWAP-3-EVENTLOG: Not waiting for DHCP options as resolve method on interface BVI1 is 4
    *Sep 24 19:37:02.335: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:37:02.335: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:37:02.335: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:37:02.335: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Ignoring WLC name lookup
    *Sep 24 19:37:05.851: %CAPWAP-3-EVENTLOG: ADDING IP 42.117.53.12, 255.255.255.0 resolvemethod  A, ip_dhcp_addr 1
    *Sep 24 19:37:05.851: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.
    *Sep 24 19:37:05.851: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    *Sep 24 19:37:05.923: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 42.117.53.12, mask 255.255.255.0, hostname APdca5.f4b8.5480
    *Sep 24 19:37:05.923: %CAPWAP-3-EVENTLOG: ADDING IP 42.117.53.12, 255.255.255.0 resolvemethod  A, ip_dhcp_addr 1
    *Sep 24 19:37:05.923: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.
    *Sep 24 19:37:05.923: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    % CDP is not supported on this interface, or for this encapsulation
    Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
    *Sep 24 19:37:10.923: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.
    *Sep 24 19:37:10.963: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
    *Sep 24 19:37:10.983: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:37:11.023: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:37:11.023: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:37:12.023: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:37:12.023: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:37:12.023: %CAPWAP-5-DHCP_OPTION_43: Controller address 42.117.52.200 obtained through DHCP
    *Sep 24 19:37:12.023: %CAPWAP-5-DHCP_OPTION_43: Controller address 42.117.52.200 obtained through DHCP
    *Sep 24 19:37:12.023: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
    *Sep 24 19:37:20.875: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
    *Sep 24 19:37:20.875: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1
    *Sep 24 19:37:20.875: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1
    *Sep 24 19:37:20.875: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2
    *Sep 24 19:37:20.875: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0
    *Sep 24 19:37:20.879: %CAPWAP-3-EVENTLOG: Discovery Response from 10.124.133.40
    *Sep 24 19:37:20.919: %CAPWAP-3-EVENTLOG: Discovery Response from 42.117.52.200
    *Sep 24 19:37:30.875: %CAPWAP-3-EVENTLOG: Selected MWAR 'AJB-C1-WLC5508-1' (index 0).
    *Sep 24 19:37:30.875: %CAPWAP-3-EVENTLOG: Ap mgr count=1
    *Sep 24 19:37:30.875: %CAPWAP-3-ERRORLOG: Go join a capwap controller
    *Sep 24 19:37:30.875: %CAPWAP-3-EVENTLOG: Choosing AP Mgr with index 0, IP = 0xA7C8528 , load = 0..
    *Sep 24 19:37:30.875: %CAPWAP-3-EVENTLOG: Synchronizing time with AC time.
    *Sep 24 19:37:31.000: %CAPWAP-3-EVENTLOG: Setting time to 19:37:31 UTC Sep 24 2013
    *Sep 24 19:37:31.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.124.133.40 peer_port: 5246
    *Sep 24 19:37:31.000: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Setup.
    *Sep 24 19:37:31.591: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.124.133.40 peer_port: 5246
    *Sep 24 19:37:36.595: %CAPWAP-3-EVENTLOG: Join request: version=117728256
    *Sep 24 19:37:36.595: %CAPWAP-3-EVENTLOG: Join request: hasMaximum Message Payload
    *Sep 24 19:37:36.595: %CAPWAP-5-SENDJOIN: sending Join Request to 10.124.133.40
    % CDP is not supported on this interface, or for this encapsulation
    *Sep 24 19:38:30.999: %CAPWAP-3-EVENTLOG: Wait DTLS timer has expired
    *Sep 24 19:38:30.999: %CAPWAP-3-EVENTLOG: Did not get join response
    *Sep 24 19:38:30.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.124.133.40:5246
    *Sep 24 19:38:30.999: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.
    *Sep 24 19:38:30.999: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.
    *Sep 24 19:38:31.039: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
    *Sep 24 19:38:31.059: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:38:31.099: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:38:31.099: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:38:41.099: %CAPWAP-3-EVENTLOG: Selected MWAR 'AJB-C1-WLC5508-1' (index 0).
    *Sep 24 19:38:41.099: %CAPWAP-3-EVENTLOG: Ap mgr count=1
    *Sep 24 19:38:41.099: %CAPWAP-3-ERRORLOG: Go join a capwap controller
    *Sep 24 19:38:41.099: %CAPWAP-3-EVENTLOG: Choosing AP Mgr with index 0, IP = 0xA7C8528 , load = 0..
    *Sep 24 19:38:41.099: %CAPWAP-3-EVENTLOG: Synchronizing time with AC time.
    *Sep 24 19:38:41.000: %CAPWAP-3-EVENTLOG: Setting time to 19:38:41 UTC Sep 24 2013
    *Sep 24 19:38:41.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.124.133.40 peer_port: 5246
    *Sep 24 19:38:41.000: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Setup.
    *Sep 24 19:38:41.595: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.124.133.40 peer_port: 5246
    *Sep 24 19:38:46.595: %CAPWAP-3-EVENTLOG: Join request: version=117728256
    *Sep 24 19:38:46.595: %CAPWAP-3-EVENTLOG: Join request: hasMaximum Message Payload
    *Sep 24 19:38:46.595: %CAPWAP-5-SENDJOIN: sending Join Request to 10.124.133.40
    APdca5.f4b8.5480#
    APdca5.f4b8.5480#
    APdca5.f4b8.5480#sh cap
    APdca5.f4b8.5480#sh capwap ?
      client    CAPWAP Client Information
      ids       CAPWAP IDS Information
      ip        CAPWAP IP configuration
      location  CAPWAP Location Information
      mcast     CAPWAP Mcast Information
      reap      CAPWAP FlexConnect Information
      rm        CAPWAP RM Information
    APdca5.f4b8.5480#sh capwap cli
    APdca5.f4b8.5480#sh capwap client ?
      callinfo   Lwapp client Call Info
      config     CAPWAP Client NV Config File
      detailrcb  Lwapp client rcb Info
      ha         CAPWAP Client HA parameters
      mn         CAPWAP Client 80211 MN
      rcb        CAPWAP Client RCB
      timers     CAPWAP Client Timers
      traffic    CAPWAP Client 80211 Traffic
    APdca5.f4b8.5480#sh capwap ?     
      client    CAPWAP Client Information
      ids       CAPWAP IDS Information
      ip        CAPWAP IP configuration
      location  CAPWAP Location Information
      mcast     CAPWAP Mcast Information
      reap      CAPWAP FlexConnect Information
      rm        CAPWAP RM Information
    APdca5.f4b8.5480#sh capwap
    *Sep 24 19:39:27.259: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
    *Sep 24 19:39:27.259: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
    *Sep 24 19:39:27.259: %MESH-6-LINK_UPDOWN: Mesh station dca5.f4b8.302f link Down
    *Sep 24 19:39:27.259: %MESH-4-NO_POTENTIAL_PARENT: There are no potential parents
    *Sep 24 19:39:27.459: %MESH-6-ADJ_VIDB_LINK: Mesh neighbor dca5.f4b8.302f VIDB Virtual-Dot11Radio0 going down
    *Sep 24 19:39:27.463: %LINK-6-UPDOWN: Interface Virtual-Dot11Radio0, changed state to down
    *Sep 24 19:39:28.463: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Dot11Radio0, changed state to down
    *Sep 24 19:39:32.275: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:32.283: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:34.299: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:34.307: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:36.323: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:36.331: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:38.347: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:38.355: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    % CDP is not supported on this interface, or for this encapsulation
    *Sep 24 19:39:40.371: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:40.379: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:40.999: %CAPWAP-3-EVENTLOG: Wait DTLS timer has expired
    *Sep 24 19:39:40.999: %CAPWAP-3-EVENTLOG: Did not get join response
    *Sep 24 19:39:40.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.124.133.40:5246
    *Sep 24 19:39:40.999: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.
    *Sep 24 19:39:40.999: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.
    *Sep 24 19:39:41.039: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
    *Sep 24 19:39:41.091: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:39:41.091: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:39:41.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:39:42.395: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:42.403: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:44.419: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:44.427: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:46.443: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:46.451: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:48.467: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:48.475: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:50.491: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:50.499: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:51.095: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
    *Sep 24 19:39:51.095: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:39:51.095: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:39:51.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:39:51.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:39:51.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1
    *Sep 24 19:39:51.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1
    *Sep 24 19:39:51.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2
    *Sep 24 19:39:52.515: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:52.523: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:54.539: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:54.547: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:56.563: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:56.571: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:58.587: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:39:58.595: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:00.611: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:00.619: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
    *Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1
    *Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1
    *Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2
    *Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0
    *Sep 24 19:40:02.635: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:02.643: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:04.659: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:04.667: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:06.683: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:06.691: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:08.707: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:08.715: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:10.731: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:10.739: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:11.095: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
    *Sep 24 19:40:11.095: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:40:11.095: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:40:11.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:40:11.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:40:11.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1
    *Sep 24 19:40:11.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1
    *Sep 24 19:40:11.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2
    *Sep 24 19:40:12.755: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:12.763: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:14.779: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:14.787: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:16.803: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:16.811: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:18.827: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:18.835: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:20.851: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:20.859: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:21.095: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
    *Sep 24 19:40:21.095: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:40:21.095: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:40:21.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:40:21.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:40:21.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1
    *Sep 24 19:40:21.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1
    *Sep 24 19:40:21.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2
    *Sep 24 19:40:21.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0
    *Sep 24 19:40:22.875: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:22.883: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:40:25.883: %MESH-6-ADJ_VIDB_LINK: Mesh neighbor dca5.f4b8.302f VIDB Virtual-Dot11Radio0 dot1x control
    *Sep 24 19:40:25.887: %LINK-6-UPDOWN: Interface Virtual-Dot11Radio0, changed state to up
    *Sep 24 19:40:26.887: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Dot11Radio0, changed state to up
    *Sep 24 19:40:31.095: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
    *Sep 24 19:40:31.095: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:40:31.095: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:40:34.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:40:37.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:40:37.095: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.40, type 1.
    *Sep 24 19:40:37.095: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.41, type 1.
    *Sep 24 19:40:37.095: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 42.117.52.200, type 2
    *Sep 24 19:40:47.095: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
    *Sep 24 19:40:47.095: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:40:47.095: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:40:47.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:40:47.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:40:47.095: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.40, type 1.
    *Sep 24 19:40:47.095: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.41, type 1.
    *Sep 24 19:40:47.095: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 42.117.52.200, type 2
    *Sep 24 19:40:47.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0
    *Sep 24 19:40:55.387: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.
    *Sep 24 19:40:55.387: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    *Sep 24 19:40:57.095: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
    *Sep 24 19:40:57.095: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4
    *Sep 24 19:40:57.095: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
    *Sep 24 19:40:57.095: %CAPWAP-3-ERRORLOG: Failed to process timer message.
    % CDP is not supported on this interface, or for this encapsulation
    *Sep 24 19:41:00.387: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.
    *Sep 24 19:41:00.447: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:41:00.487: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:41:00.487: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:41:00.487: %CAPWAP-3-EVENTLOG: Not waiting for DHCP options as resolve method on interface BVI1 is 4
    *Sep 24 19:41:00.487: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:41:00.487: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:41:00.487: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
    *Sep 24 19:41:00.487: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Ignoring WLC name lookup
    *Sep 24 19:41:04.003: %CAPWAP-3-EVENTLOG: ADDING IP 42.117.53.12, 255.255.255.0 resolvemethod  A, ip_dhcp_addr 1
    *Sep 24 19:41:04.003: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.
    *Sep 24 19:41:04.003: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    *Sep 24 19:41:04.075: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 42.117.53.12, mask 255.255.255.0, hostname APdca5.f4b8.5480
    *Sep 24 19:41:04.075: %CAPWAP-3-EVENTLOG: ADDING IP 42.117.53.12, 255.255.255.0 resolvemethod  A, ip_dhcp_addr 1
    *Sep 24 19:41:04.075: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.
    *Sep 24 19:41:04.075: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    % CDP is not supported on this interface, or for this encapsulation
    Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
    *Sep 24 19:41:09.075: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.
    *Sep 24 19:41:09.111: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
    *Sep 24 19:41:09.135: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:124:133:40
    *Sep 24 19:41:09.175: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
    *Sep 24 19:41:09.175: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
    *Sep 24 19:41:10.175: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:41:10.175: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway found 42.117.53.1
    *Sep 24 19:41:10.175: %CAPWAP-5-DHCP_OPTION_43: Controller address 42.117.52.200 obtained through DHCP
    *Sep 24 19:41:10.175: %CAPWAP-5-DHCP_OPTION_43: Controller address 42.117.52.200 obtained through DHCP
    *Sep 24 19:41:10.175: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
    *Sep 24 19:41:19.175: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
    *Sep 24 19:41:19.175: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1
    *Sep 24 19:41:19.175: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1
    *Sep 24 19:41:19.175: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2
    *Sep 24 19:41:19.175: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discover

  • How do I host multiple domains on a single Messaging Server?

    How do I host multiple domains on a single Messaging Server?
    <p>
    To host multiple domains on one Messaging Server, use the
    mailAlternateAddress attribute. If you want to host two domains
    (customer1.com and customer2.com) on your server mail1.domain.com,
    make sure that:
    The various domains (in DNS) point to the installed mail server
    (you must have the MX records that
    points mail for customer1.com to mail1.domain.com and
    customer2.com to mail1.domain.com)
    That each person receiving mail at customer1.com and
    customer2.com has an appropriate mailAlternateAddress
    attribute describing the appropriate email address. For
    instance, John Doe can have an email address (i.e. the value
    of the 'mail' attribute for the John Doe LDAP entry) of
    [email protected] and receive his mail on
    [email protected] (the value of the mailAlternateAddress
    attribute)
    With Messaging Server 3.5, mailAlternateAddress can take the
    form of @mail1.domain.com. If jdoe's mailAlternateAddress is
    set to @mail1.domain.com, mail sent to [email protected]
    will be delivered to [email protected]

    jaygatsby1123 wrote:
    So what exactly am I doing with virtual hosts?  There is a place for Aliases...  What would I put in the "Aliases" box?
    Any other host name that you want to resolve to the specified virtual host.  It's quite literally an alias.
    if you want www.example.com and www.example.org to end up at the same web site and you already have a virtual host — Apple refers to virtual hosts as sites — configured for www.example.com in Server.app, then you'd add www.example.org as an alias for the www.example.com virtual host (site).
    Virtual hosts are implemented in a web server using some details of the HTTP or HTTPS protocol, and what the web browser (client) specified.  The client gets handed an IP address or a domain name by the user, and the client then fetches the associated IP address for the target web server from the client's DNS services or local host database, and the client then connects to the IP address and passes over the text string that the user had requested — the IP address or domain name or even some local shortcut set up in the client system — via the HTTP or HTTPS protocol.  The web server receives and processes this arriving text string from the client, and uses it to select which web site to render back to the web client.   One subtle detail lurks here, too: the server's own DNS configuration really isn't involved in the selection of the virtual host.

  • Multiple domains and multiple IPs in the same MacMini Server

    I am sure that this topic has been faced already but I cannot find enough information to really dig into a solution.
    I have a macmini server with two IPs let say x.x.x.12 and x.x.x.13 .
    The server is set up on the first IP. It has his primary zone, machine record, mail aslias and www alias.
    Lets call the server domain server.domain1.com
    Everything works fine I have a couple of local users and a couple of LDAP users. Just to test the machine setup.
    I can send and receive emails using any of the users as [email protected]
    Now I would like to have another domain, domain2.com in the same server .
    The final goal is to have users under different domains. They have their own email box, calendar, etc.
    It will be preferable that I can share the same username with different domains. But I can live without that option.
    My first test was to have the second domain called server.domain2.com using the second IP. x.x.x.13 .
    For that I created another Primary Zone with domain2.com as machine record of x.x.x.13 . To use the second IP I simply create another Ethernet interface on the macmini.
    In the Mail -> Advance settings I added the host aliases as well as virtual hosting domains for domains2.com.
    With this setting I can send emails as [email protected] or [email protected] but when I replay to their messages I get a "Relay access denied" error from server.domain1.com .
    I also tryed another domain pointing to x.x.x.12, the same as server.domain1.com . I did not create any extra Primary Zone but the local host aliases and the virtual hosting domains.
    Same issue. I can send but I get a "Relay access " error.
    As you might notice I am a novice on servers settings. I just try to recreate a similar environment common to Virtual Hosting providers for my own website playground but I cannot cut through this email configuration obstacle.
    Any significant meaning that can be leading me to learn how to do it will be very very appreciated . (beside lynda,com tutorials that I followed already but do not mention multiple domains for mails).
    Thanks

    the problem I try to solve is to manage multiple domains in one MacMini Server.
    Having two IPs is secondary.
    I would like that each domains has his own users with emails, iCals, Wiki and web sites.
    The main problem is having emails to work for any additional domain beside the default one on the machine IP.
    I also got an additional IP address to be used on the same server hoping that it make things easier but apparently is making things more difficult.

  • Start multiple domains simultaneously on 1 Weblogic server installation?

    Is it okay to start and run multiple domains simultaneously. Better yet, when having multiple domains on 1 WLS server, should each domain have a different port number in order to be run simultaneously?
    Here's my scenario - I installed Oracle Business Intellgence, which by default installs and configures WLS server for certain Business Intelligence applications (BI Publisher). This instance was running fine and good and still is.
    Then I had another application, Oracle Data Integrator, which has a Console piece that requires a domain on WLS. So instead of modifying the existing domain for Oracle Business Intelligence, I created a new domain via the Configuration Wizard and selected those components for Oracle Data Integrator.
    therefore current domains:
    ...\domains\bifoundation_domain --> installed automatically as part of Oracle Business Intelligence
    ...\domains\odi11g --> I created this domain after I
    Now I have 2 domains under 1 WLS Server (windows 7 64bit), but if I startWeblogic.cmd for the bifoundation_domain, and I startWeblogic.cmd for the odi11g...then only the components for the bifoundation_domain become available via the WLS Console.
    Questions:
    - Can I run both domains simultaneously?
    - Should I have modified the bifoundation_domain to include Oracle Data Integrator component; therefore only having 1 domain but having everything run under that domain?
    - Does the Port for each domain matter? both bifounddation_domain and odi11g domain use ports 7001
    Are there any other considerations? Thanks much.

    Hi,
    It is perfectly OK to run multiple domains on a single Weblogic server installation. Only constraint would be you have enough capacity available on your server to start multiple instances.
    Things to note is, if your domain1 is running on listen address : port { localhost : 7001 } then your other domain should be configured on a different port say {localhost : 8001 }. If you want both domain to run on same port then go for virtual IP's to be plumbed on your physical network interface and configure as,
    domain1 - { ip1 : 7001 }
    domain2 - { ip2 : 7001 }
    this way you will can access both domain admin console on same port.
    Remember, Weblogic resources cannot be shared between domain, however a single nodemanager will be enough to monitor both the domains.
    * rank it if answer is helpful :) *
    Thanks,
    Ranjan

  • Multiple GWIAs : multiple domains too or not?

    First off, let me confess that this is near the end for our GW system. The reason for creating GWIAs in this manner is to migrate our users' email to another system via IMAP. We have ~6000 users and > 500GB of messages to move.
    With that being said...
    I have not been impressed with the GWIA and its ability to handle what is now "routine" message amounts. We were plagued with daily crashes (sometimes hourly) for months until we got a solution to impose the "imapreadlimit" switch in the GWIA configuration file. It has helped, but I doubt that in its current configuration, our current IMAP GWIA is able to cope with increased load. I am planning on building a few more GWIAs such that when it comes time to hit the button on the multiple-batch IMAP moves, we will have a half dozen or so GWIAs to handle the load. I am mostly concerned with the stability of the internet agents themselves, hence the large number of GWIAs. Novell's doc highly recommends to have the GWIA and domain to live on the same box, but it isn't required. I am faced with now creating a half dozen new domains (which also must sync changes between them and our main domain) in order to get more GWIAs. Or is this not really necessary?
    With my concerns being primarily the GWIAs' stability, is having multiple domains not as necessary? If having multiple GWIAs on multiple systems, what is the preferred method of linking them to a single domain (shared SMB mounts?), and is this problematic if multiple GWIAs would have that share mounted and could be reading/writing to it simultaneously?

    * nebben,
    you don't need GWIAs for IMAP, the GW8 POAs can do IMAP.
    http://www.novell.com/documentation/...a/ak8h81j.html
    Uwe
    Novell Knowledge Partner (NKP)
    Please don't send me support related e-mail unless I ask you to do so.

  • Multiple domains for tracker.js

    I'm using the personalization functionality of CQ 5.4, which appears to force a request for http://localhost:4502/libs/wcm/stats/tracker.js when pages load. According to the docs at http://dev.day.com/docs/en/cq/5-4/deploying/configuring_cq.html#OSGi Configuration in the Repository , I should be able to override this URL by adding some nodes to /apps/projectName. However, my tests seem to show that doing so for one project affects all sites on the server. In production, the client has a number of domains all running on one CQ instance.
    1) Is there a way to remove this request altogether without modifying any JSPs in the /libs folder, or inheriting/overriding them?
    2) Is there a way to support multiple domains?
    The best solution I've come up with so far is creating a generic domain like cq-tracking.clientName.com, and having all sites use that.

    See the following:
    http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00808c3c45.
    shtml
    *Perform Multi-Domain Searches (Optional) *
    *Optional.* The ASA currently does not support the LDAP referal
    mechanism for multi-domain searches (Cisco bug ID CSCsj32153).
    Multi-domain searches are supported with the AD in Global Catalog Server
    mode. In order to perform multi-domain searches, setup up the AD server
    for Global Catalog Server mode, usually with the these key parameters
    for the LDAP server entry in the ASA. The key is to use an
    ldap-name-attribute that must be unique across the directory tree.
    server-port 3268
    ldap-scope subtree
    ldap-naming-attribute userPrincipalName
    If global catalog server is not an option for you, you can always create two seperate SSL tunnel-groups and two seperate LDAP aaa-server groups and this would also allow you to do two AD domains (but the drawback is that you would have to inform the user which group they should select)
    -heather

  • Multiple Domains on NWDI

    Hi experts!
    I've started using NWDI, and i've noticed that i already have 23 tracks. I would like to group tracks by some kind of category.
    As far as i understand, the domain tab could function like a category to group my tracks.
    But when i go to "Domain Data" tab the field domain id is readonly and is a textbox.
    There is any way to create multiple domains, each one with ther own tracks?
    If not, there is some way to reproduce my requirements?
    I think installing CMS on another server is not really a good option because the code and development will not be integrated on one place, right?
    Thank you guys.

    Hi Nuno,
    I don't think you can group using domain tab.
    >There is any way to create multiple domains, each one with ther own tracks?
      No Option available in NWDI.
    Refer to http://help.sap.com/saphelp_nw70/helpdata/en/f2/7c04702864304bb38e0b1cd6667c2b/content.htm
    SAP NetWeaver Development Infrastructure (NWDI)
    Hope it helps
    Regards
    Arun

  • Windows Server - Run multiple domains under different accounts

    Hi,
    I have multiple domains on a Windows Server. I'd like to run these under separate accounts for security reasons.
    My options I have so far:
    1) Install all Admin servers and managed servers as windows services and set logon appropriately
    2) If possible, use multiple node manager instances, one for each domain and set the log on for each node manager windows service
    I like the idea of multiple node managers but I can't find any reference in the documentation about this. I'd rather not use option 1 as I won't be able to restart servers from the WebLogic Console
    Has anyone had to do this before?

    First option might be the cleanest .
    For second option make sure that there are separate Node_Manager home directory for different node manager instances.
    Edited by: atheek1 on Jun 19, 2010 4:55 AM

  • Supporting Multiple domains in IM&P with and Expressway deployment?

    Hello everyone. This is long winded but the context is needed to explain what I'm looking for. Any help is appreciated.
    My customer has piloted IM&P for 1 year now and is looking to take it to the next level. They purchased Expressway Core & Edge and they are looking to enable Mobile Remote Access, B2B Video and XMPP Federation. One issue is that the Jabber domain that was selected 1 year ago for the pilot was a local domain. The reason for this is because the multidomain support was not available at the time. Internally there are 3 domains. example.ca, examplesales.ca, and examplebanannas.com. Their Jabber ID they use today is example.root.local. I am reading through the guides and it seems as though IM&P allows you to map a JABBER ID to an email address or a directory URI. This will allow multiple presence domains within one Presence cluster. The problem is that it appears as though federation will not work through expressway core / edge if you use this method. Can this be confirmed?
    I am providing you these URL's only for guidance, to show you how I arrived at my situation where I’m asking for help on a configuration change to my customers IM&P settings.
    note the section on page 41 of the following guide http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/config_guide/X8-5/Mobile-Remote-Access-via-VCS-Deployment-Guide-X8-5-1.pdf
    One would presume that Multi-domain support is now supported with expressway core & edge. The caveat I found on page 4 of the following guide in relation to xmpp federation.
    http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/config_guide/XMPP-Federation-with-Cisco-VCS-and-IM-and-Presence-Service.pdf
    and page 10 of the following guide
    http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/config_guide/X8-5/XMPP-Federation-with-Cisco-VCS-and-IM-and-Presence-Service.pdf
    and this section
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/interdomain_federation/10_5_1/CUP0_BK_I07B7052_00_integration-guide-interdomain-federation-105/CUP0_BK_I07B7052_00_integration-guide-interdomain-federation-105_chapter_01010.html#CUP0_RF_CAF8AEDD_00
    Expressway-E does not support XMPP address translation (of email addresses, for example). If you are using Expressway-E for XMPP federation, you must use native presence Jabber IDs from IM and Presence Service.
    This being said
    Based on my findings, I believe Cisco now supports multi-domain setup for IM&P with the "caveat" federation still doesn't work. My customer is not happy with this but still would like to proceed with the rest of the benefits that MRA brings to the table for their Jabber deployment. 
    To support the above scenario it is my understanding I need to make an adjustment to the configuration of IM&P. As I stated when I opened the case my customer’s current IM&P domain is “example.root.local” their JID is made up of [email protected]. It’s my understanding we cannot use this domain and activate MRA so we need to adjust everyone’s JID to be a Publicly routable DNS name. Since everyone that has a JABBER account also has an email account I was thinking we map the JID to the email. I’m trying to understand how to get from where we are to where we need to be. I found this guide but it doesn’t talk about the effects of doing this on a live system setup the way my customer is setup.
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/interdomain_federation/10_5_1/CUP0_BK_I07B7052_00_integration-guide-interdomain-federation-105/CUP0_BK_I07B7052_00_integration-guide-interdomain-federation-105_chapter_01100.html
    I am also not certain this is the setting I’m looking for. I believe what I need to change is actually on the Presence server under the domains section I found this
    Domains Configuration
    Use the controls on this window to view and edit domains managed by the IM and Presence Service. Previously, the IM and Presence Service supported a single domain. With this release, you can specify multiple domains.
    Before You Begin
    To take advantage of multiple IM and Presence Service domains, you must choose Directory URI as the IM address scheme on the Advanced Presence Settings window. If the IM address scheme is set to UserID@domain, the default domain is used for the IM and Presence Service. The status of the IM Address Scheme setting is displayed at the top of the window in the Status box. The Status box contains a link to the Advanced Presence Settings window.
    Is this what I need to do?

    Hello everyone. This is long winded but the context is needed to explain what I'm looking for. Any help is appreciated.
    My customer has piloted IM&P for 1 year now and is looking to take it to the next level. They purchased Expressway Core & Edge and they are looking to enable Mobile Remote Access, B2B Video and XMPP Federation. One issue is that the Jabber domain that was selected 1 year ago for the pilot was a local domain. The reason for this is because the multidomain support was not available at the time. Internally there are 3 domains. example.ca, examplesales.ca, and examplebanannas.com. Their Jabber ID they use today is example.root.local. I am reading through the guides and it seems as though IM&P allows you to map a JABBER ID to an email address or a directory URI. This will allow multiple presence domains within one Presence cluster. The problem is that it appears as though federation will not work through expressway core / edge if you use this method. Can this be confirmed?
    I am providing you these URL's only for guidance, to show you how I arrived at my situation where I’m asking for help on a configuration change to my customers IM&P settings.
    note the section on page 41 of the following guide http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/config_guide/X8-5/Mobile-Remote-Access-via-VCS-Deployment-Guide-X8-5-1.pdf
    One would presume that Multi-domain support is now supported with expressway core & edge. The caveat I found on page 4 of the following guide in relation to xmpp federation.
    http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/config_guide/XMPP-Federation-with-Cisco-VCS-and-IM-and-Presence-Service.pdf
    and page 10 of the following guide
    http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/config_guide/X8-5/XMPP-Federation-with-Cisco-VCS-and-IM-and-Presence-Service.pdf
    and this section
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/interdomain_federation/10_5_1/CUP0_BK_I07B7052_00_integration-guide-interdomain-federation-105/CUP0_BK_I07B7052_00_integration-guide-interdomain-federation-105_chapter_01010.html#CUP0_RF_CAF8AEDD_00
    Expressway-E does not support XMPP address translation (of email addresses, for example). If you are using Expressway-E for XMPP federation, you must use native presence Jabber IDs from IM and Presence Service.
    This being said
    Based on my findings, I believe Cisco now supports multi-domain setup for IM&P with the "caveat" federation still doesn't work. My customer is not happy with this but still would like to proceed with the rest of the benefits that MRA brings to the table for their Jabber deployment. 
    To support the above scenario it is my understanding I need to make an adjustment to the configuration of IM&P. As I stated when I opened the case my customer’s current IM&P domain is “example.root.local” their JID is made up of [email protected]. It’s my understanding we cannot use this domain and activate MRA so we need to adjust everyone’s JID to be a Publicly routable DNS name. Since everyone that has a JABBER account also has an email account I was thinking we map the JID to the email. I’m trying to understand how to get from where we are to where we need to be. I found this guide but it doesn’t talk about the effects of doing this on a live system setup the way my customer is setup.
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/interdomain_federation/10_5_1/CUP0_BK_I07B7052_00_integration-guide-interdomain-federation-105/CUP0_BK_I07B7052_00_integration-guide-interdomain-federation-105_chapter_01100.html
    I am also not certain this is the setting I’m looking for. I believe what I need to change is actually on the Presence server under the domains section I found this
    Domains Configuration
    Use the controls on this window to view and edit domains managed by the IM and Presence Service. Previously, the IM and Presence Service supported a single domain. With this release, you can specify multiple domains.
    Before You Begin
    To take advantage of multiple IM and Presence Service domains, you must choose Directory URI as the IM address scheme on the Advanced Presence Settings window. If the IM address scheme is set to UserID@domain, the default domain is used for the IM and Presence Service. The status of the IM Address Scheme setting is displayed at the top of the window in the Status box. The Status box contains a link to the Advanced Presence Settings window.
    Is this what I need to do?

  • Multiple domains hosted on one OSX Server

    Hi guys,
    Does anyone know if it is possible to host more than one domain name on OSX server?
    A client of mine runs a number of businesses and is considering Snow Leopard Server, and wants to have multiple email domains and websites hosted on one server. Also per-account contacts sync and calendar sync would be useful, does anyone know if that's available?
    Thanks!
    W.

    You can certainly host multiple domains on Mac OS X Server. There are a few options depending on how you want it to work.
    If all the usernames are the same across all domains (e.g. [email protected] is the same person as [email protected]) then just change the mail server configuration to match all the domains in the mydestination parameter in /etc/postfix/main.cf.
    If the domains are different (e.g. [email protected] is not the same account as [email protected]) then you have two options - one is to use the postfix model (which requires command-line management), the other is to add the email addresses in the shortname section for each user.
    You may have some issues integrating contacts and calendars, though - if you take the postfix model then the users won't exist in Open Directory and won't have a calendar/contact link, etc.
    If you follow the shortname model then you have one directory with all users in all domains and you'll need to work to separate them out if you need to.

  • DHCP Option Tags are not being applied...

    Hi,
    About to loose my mind... basically we are working towards a small WYSE Thin Client deployment in our environment.  The WYSE clients require to receive certain DHCP Option Tags to find the WCM server of which they receive their configuration from.  Same
    applies to the WDM Server as well.  The problem is no matter what we do, our test client is not receiving the custom option tags we've defined in our DHCP server.  
    DHCP Servers:
    vlan41
    10.40.1.206
    10.40.1.207
    Test Client:
    vlan46 - ip helpers defined on the switch
    Set to receive the same ip address from the DHCP server through the reservation route.
    Option Tags:
    186 - WDM Server - 10.40.1.184
    195 - WCM Server - 10.40.1.185
    196 - WCM Path - / 
    I've installed Wire Shark on the test client to monitor the DHCP activity.  The above custom options tags are not being pushed on to the client.  
    The Router, DNS Server and Domain Tags are being pushed.  So it's working but also not working????!!!
    Anybody with some insight to this problem?

    Hi hpaul_p
    In all fairness I'm about to give up... the vendor is not coming up with a solution and constantly blaming Microsoft.  To further test and confirm this wasn't a network issue, I've setup a secondary test environment using a 4 port switch, a client and
    a DHCP server.  Same results!!!  I'm really running out of time, so my work around is this:  I've setup a SRV records pointing to the WCM server... in your case this would be SRV record for the WDM server.  I've disabled the auto
    discovery functionality of the WDM Agent, for some reason it seems to be clashing with the WCM agent.  Since you will be using WDM only, don't disable auto discovery, tick the DNS SRV record from the Discovery Settings under the client agent. 
    I'm going to add the clients to the WDM server manually through their ip addresses so don't need auto discovery. From what I gather from the manuals the WCM searches for the repository or conifg servers in this order:  1. SRV 2.DNS (A record)
    3.DHCP (Options), I bet it's the same with WDM.  Though SRV and DNS methods has their limitations, if you will be using the default paths and credentials it shouldn't be a problem.  This is all I have have.  Steven Song I've forwarded you the
    DHCP database, if you find any problems with it please let me know.

  • Multiple Domain pointing to sub-domains on my local machine.

    Here what I am hoping to do:
    I have multiple sub-domains (only some listed below) setup on my local computer that I use to access local testing folders. I would like to also be able to access these domains from outside my network. Also I have an airport extreme which is forwarding http traffic to my Mac. (That works, I have tested it.) So far I have been able to get basic forwarding to my root sites folder to work, but not the sub-domains.
    How can I setup my system so that people can use different no-ip.com urls to get to different sub-domains or folders on my Mac?
    Below is my virtual hosts in apache, my /etc/host file and a my no-ip.com domain is: ***.serve**.com
    Thank you so much for all your help.
    -Alex
    [email protected]
    /etc/host:
    # Host Database
    # localhost is used to configure the loopback interface
    # when the system is booting. Do not change this entry.
    127.0.0.1 localhost
    255.255.255.255 broadcasthost
    ::1 localhost
    127.0.0.1 gweather.akutech.local
    apache vhosts:
    ### Section 3: Virtual Hosts
    # VirtualHost: If you want to maintain multiple domains/hostnames on your
    # machine you can setup VirtualHost containers for them. Most configurations
    # use only name-based virtual hosts so the server doesn't need to worry about
    # IP addresses. This is indicated by the asterisks in the directives below.
    # Please see the documentation at
    # <URL:<a class="jive-link-external-small" href="http://">http://httpd.apache.org/docs-2.0/vhosts/>
    # for further details before you try to setup virtual hosts.
    # You may use the command line option '-S' to verify your virtual host
    # configuration.
    #edit /etc/hosts add new servers sudo pico /etc/hosts
    # Use name-based virtual hosting.
    # NameVirtualHost *
    ### WebDAV Server
    Alias /dav/ "/Users/alexku/Sites/ TESTING/dav/"
    DAVLockDB davlocks/DAVLockDB
    <Directory "/Users/alexku/Sites/ TESTING/dav/">
    DAV On
    AuthName 'WebDAV'
    AuthType Basic
    AuthUserFile /Applications/MAMP/conf/apache/.htpasswd
    require valid-user
    Options -Indexes
    </Directory>
    ##AKUTECH HOSTS LOCAL
    NameVirtualHost *
    #MAIN
    <VirtualHost *>
    DocumentRoot "/Users/alexku/Sites/"
    ServerName localhost
    <Directory "/Users/alexku/Sites/">
    Order allow,deny
    Allow from all
    AllowOverride All
    Options All
    </Directory>
    </VirtualHost>
    #GORDON SCHOOL WEATHER
    <VirtualHost *>
    DocumentRoot "/Users/alexku/Sites/weather.gordonschool.org/"
    ServerName gweather.akutech.local
    <Directory "/Users/alexku/Sites/weather.gordonschool.org/">
    Order allow,deny
    Allow from all
    AllowOverride All
    Options All
    </Directory>
    </VirtualHost>
    p.s Sorry for the odd formating of the files.

    You cannot have multiple "<VirtualHost *>" directives. This indicates to apache that the following configuration is the default, and you can't have multiple defaults.
    The solution is to change this line to indicate which site you're configuring.
    For example:
    <VirtualHost some.site.com:80>
     # configuration for some.site.com here
    </VirtualHost>
    <VirtualHost other.site.com:80>
     # configuration for other.site.com here
    </VirtualHost>
    <VirtualHost *>
     # catch-all defaults for unknown sites
    </VirtualHost>

  • Domain Controller, DHCP, DNS Migration from 2008 r2 to 2012 Essentials

    I would like to migrate Domain Controller, DHCP, and DNS functions to a new 2012 Essentials server in a 2008 r2 domain.  I would like  the 2008 r2 server to remain as applications server.  Is it possible to do this?  I've seen in TechNet
    a reference to this type of migration, but am concerned about the reference that after 21 days the 2008 will shut down.  Is it that the server will shut down or the Domain Controller function on the 2008 will shut down? I will need the 2008 setup as is
    for our application server, so I want to be sure that the migration will not interfer with that.

    As long as your existing server is not also an SBS or other Essentials server, it'll be fine. The shutdown after 21 days occurs when multiple SBS or Essentials servers are on the same domain.

Maybe you are looking for

  • Logical System Name of an Idoc Sender

    Hi, I have seen that For Idoc senders the the Logical System name associated with the sending Client has to be SAP+System Id(For example SAPE05 where System Id = E05). Is it mandatory? If so how can I have multiple clients in a sender Idoc systems se

  • Mini Bridge: how to clear recent files/folders?

    Hi all, I am a new user of Photoshop CS5.1 Extended and have a question about Mini Bridge. My OS is Windows 7 Ultimate 64-bit, and I'm using the 64-bit version of Photoshop. My question is: how do I clear the Recent Files and Recent Folders lists fro

  • Form objects in email not working

    Hi All, I have designed a JSP which is sending survey form in an email to my clients in which I have put some form objects like radio button, text area, and a submit button. Few of my clients receive email with destorted form, or they are not able to

  • Why does my AOL keep resetting it self only on this browser

    I will have my AOL email up on my Firefox Browser and every so often the AOL email will just reset itself and say "you have mail", and close whatever mail I had open. If it was new mail it will put it in the old mail file. This is not happening when

  • Error message on opening "assertion failed" what do I do?

    The program started working normally but when I was in the middle of adding pictures to a catalogue and creating smart images I accidentally switched light room off and since then I cannot switch it back on. I get the error message "assertion failed"