Jumpstart through DHCP and dhcp interface files.
Hi,
I am jumpstarting a sparc machine through dhcp.
after the installation starts dhcp is running in adopt mode (/sbin/dhcpagent -a).
But its not creating primary dhcp.interface files (ex:/etc/dhcp.hme0). where as primary ethernet interface files are getting created through sysidtool.
Any idea?
Thanks alot,
JNR.
Firstly, you will need an ssh client, I assume your school computer is a Windows box. You may find that it already has something like PuTTY installed. Alternatively there are some Java web based clients you can use like this one, although I've never used any so I can't comment on their quality.
At the server end (your home) you will need to make sure that your PC has a static DHCP lease so it always has the same IP on your LAN, that your NAT is forwarding TCP port 22 to that IP, and your firewall is allowing incoming connections on that port. You will also need to know your public IP (the one that's visible on the internet). Most home broadband connections have a dynamic IP so you may want to investigate some kind of dynamic DNS service like No-IP or DynDNS. Routers often have support for these so they will automatically update if your IP changes, best to check your router first so you can choose one it supports.
Be aware that there are security considerations here, ssh is pretty secure but nothing can be guaranteed 100% bulletproof. Some kind of virtual private network (VPN) may be a better idea but you probably won't be able to get that set up at school, they can be a pain at the best of times.
Doesn't Windows allow people to install stuff in the Windows equivalent of /home? I know very little about Windows
Similar Messages
-
Mail doesn't attach files through dragging and dropping the files!
Help please,
Mail doesn't attach files through dragging and dropping the files on OS X ML, it crashes for a while !!Open Disk Utility and Repair disk permissions on the First Aid tab.
Then, Restart and boot into Recovery Mode by holding down cmd-r on restart until you see a gray screen. When the Mac boots, you will be presented with some options. Choose Disk Utility and select your Hard drive volume (Macintosh HD is the default name). Then, on the First Aid tab, click Repair Disk (not permissions).
If that doesn't help, you could try installing the 10.8.2 combo updater from the Apple Downloads site:
http://support.apple.com/kb/DL1581 -
What are the endpoints attributes collected by NAC Profiler through SNMP and DHCP?
Hi Everyone,
Please help on this.
I want to know what are the endpoints attributes collected by NAC Profiler to discover and profile the endpoints.through SNMP protocol and DHCP protocol.
Also if anybody can explain a simple used case on this.
Please guide me on this.
Thanks in advance.
Thanks,
Abuzar.Hi,
SNMP
=====
NetMap queries network devices via SNMP for:
System information
Interface information
Bridge information
802.1X information (PAE MIB)
Routing/IP information
CDP MIB Information
This information is used to Build and maintain a model of the network topology and endpoint discovery.
NetMap uses SNMP Get, GetNext and GetBulk (when available) requests to query the SNMP agents running on the network infrastructure devices to gather specific Management Information Base (MIB) objects about their status based on device type (Layer 2 or Layer 3).
In addition to polling each network device for all MIB data at a regular interval, NetMap may also be commanded to poll port-specific information when the NAC Profiler system is notified that an endpoint has joined or left the network via SNMP traps sent by devices at the network edge, switches typically.
Upon receipt and verification of a link state (link up, link down) or MAC notification trap, NetTrap will notify the NAC Profiler Server that a change has occurred on the network edge (endpoint joined or left a network port). If the trapping device is in the NAC Profiler configuration, the NetMap component module assigned to poll the device that sent the trap will be commanded by the Server module to initiate a poll of the device's port information to determine the change to the endpoint topology that resulted in the trap being sent by the network device.
The information gathered by NetMap is processed by the Server accordingly to update the network topology, noting the endpoint joining or leaving a port. Note that NetMap SNMP polling of network devices resulting from a trap is localized to the port specified in the trap. This is unlike the regular polling that occurs at the frequency specified for each device type (L2 and L3) which gathers all SNMP information from the device used by the NAC Profiler system.
DHCP:
=====
The NetWatch module listens for traffic including DHCP traffic.
The module will collect all the DHCP information on the traffic collected, like mac address, ip address, DHCP Vendor Class Identifier in DHCP request, host name in DHCP request, requested specified options in DHCP request (option 55) and full list of DHCP options supported by the DHCP client as specified in the DHCP request.
All the endpointe data can then be used to map endpoints with profiles.
HTH,
Tiago
If this helps you and/or answers your question please mark the question as "answered" and/or rate it, so other users can easily find it. -
Network Routings not imported through "Bill and Routing Interface" program
Hi,
I wanted to import Network routing to Shop Floor Manager hence I am using bom_op_routings_interface and then I am running "Bill and Routing Interface" program. But import program is errored with "You do not have access to items of type standard, so you may not be able to insert, update or delete routings ot this item type".
Highly appreciate if any one clarify why this error is issued by Import program.
Thanks in advance.
Subramanyam.Please see if the solution in (BOM API Bom_Rtg_Pub.Process_Rtg is not Creating or Updating Maintenance Routings [ID 761976.1]) helps.
Thanks,
Hussein -
Is it better to list each machine and interface as a separate entry in 10.5.7 DHCP or make a single entry with multiple interfaces?
I am looking at grouping my Wireless AP, instead of having to list each one separately.
For example:
MAIN-MDF00-01
XX:XX:XX:XX:XX:XX 10.0.2.1
Or
MDF-AP
XX:XX:XX:XX:XX:XX 10.0.2.1
XX:XX:XX:YY:YY:YY 10.0.2.2Joe,
Currently you cannot base the anchoring on the AP group. It is only based on the SSID.
Now, do you really need to split up the guest into different subnets? Or are you concerned about the AP groups?
If you truly need to break up the guest to different subnets, then you would need to create different SSID on the internal and anchor controller. Then on the anchor, link to the appropriate interface.
If you are concerned about the AP group, don't be. Just because you are using the AP group, doesn't meant that all the guest ssid can't link to the same interface, they can. You can even create a dummy interface on the internal WLC, so that if the anchoring doesn't work, they do not get an address.
Cheers,
Steve
If this helps you and/or answers your question please mark the question as "answered" and/or rate it, so other users can easily find it. -
Accessing OS/390 through Java and reading VSAM files
I hope this is the apporiate forum for this question. I am fairly new to Java but am interested in learning about using Java to connect to a mainframe and read a VSAM file. So my questions are:
1.) Where can I find information on this on this topic
2.) Would this require database drivers, and if so, are there any open source drivers for reading VSAM
Thanks for your help,
JohnYou can get an evaluation copy of WebSphere Information Integrator Classic Federation for z/OS v8.2. This will include JDBC clients for Windows and Unix platforms as well as a z/OS data server component that can access the VSAM data. .
There are two ways to order an evaluation copy:
Through the IBM zSeries account rep
Via the Shop zSeries Web site -
I have recently turned on the Radius server, and it seems to work fine, and has taken control of my Airport base station which is great. I only have one problem which is that the DHCP info provided by the server to the clients only seems to give one of the 2 DNS addresses that I have listed in the DHCP server info section. This is rather frustrating as it worked fine with WPA!
Any thoughts?I just upgraded from a 2008 domain to 2012. I followed all the best practices, set up new 2012 DC and transferred all roles to it then removed the 2008 server. I just have the one DC at the moment and it's running both DNS and DHCP. Ever since we've had some odd DNS issues which usually require a reboot of the server to fix. Now at this point I'm digging through DNS and DHCP and seeing that a lot of client IP addresses are not matching up. DNS does not have the correct IP's for several clients. How can I fix dns?
This topic first appeared in the Spiceworks Community -
Solaris 10 x86 u5 dhcp and jumpstart install fail
hello
I have problem in solaris 10 u5 jumpstart install.
I can use jumpstart install with dhcp and get a static ip address (assigned by dhcp server) before solaris 10 u3.
But now I can't use jumpstart install in solaris 10 u5 without setting up a static ip address in sysidcfg.
I have many x86 machines.
If I have to set up every different sysidcfg for every machine when I install a new machine.
I will get into big trouble.
here is my sysidcfg
###### sysidcfg #######
system_locale=en_US
timeserver=localhost
timezone=Asia/Taipei
terminal=sun-color
security_policy=NONE
root_password=xxxxxxxx
nfs4_domain=example.com
network_interface=primary { hostname=solaris
default_route=192.168.100.254
netmask=255.255.255.0
protocol_ipv6=no}
name_service=DNS {domain_name=example.com
name_server=192.168.100.1
search=example.com}
Edited by: cheung79 on 2008/4/19 ?? 5:29I think that you should modify the script discovery-install, so you'll be able to create the sysidcfg file dynamically. I had the same problem as you and there is a possibility to add some arguments to the boot command that you execute at the ok prompt. These arguments can be defined in the discovery-install script. It's quite easy.
Regards,
Przemek -
Advice on constructing a test engine and formatting a spreadsheet test file to perform command line interface testing on a range of products through telnet or serial interface and output pass/fail results.
If I understand correctly, you want to do the following:
1. Create one or more tab-delimited files that specify a series of query strings (that LabVIEW will send to your products) and expected reply strings (that LabVIEW will look for in response to each query)
2. Run your LabVIEW program (the test engine) and have it execute one or more test scripts from file using either TCP/IP or serial communication to your units under test
3. Track how many of the queries are met with the expected response, and output an indication of whether each step passed or failed
If this is close to correct, then I've attached a sample test file and LabVIEW VI as an example; I chose the TCP/telnet method because it allowed me to use the ni.com Web site to simulate my tes
t hardware. If you happen to own the LabVIEW Internet Toolkit, there's a VI called "Telnet Play Script" in the Telnet palette that does something fairly similar using TCP. The same general model would also work for Serial communications.
Hope it helps,
John Lum
Attachments:
test_engine.zip 24 KB -
Advice on constructing a test engine and formatting a spreadsheet test file to perform command line interface testing on a range of products through telnet or serial interface and output pass/fail results.
Hello j. smith,
TestStand gives you the ability to create "sequence files" which are lists of tests to be run sequentially or in parallel. These tests can be written in any language: LabVIEW VIs, C/C++ DLLs, EXEs, ActiveX objects, .NET Assemblies, etc.
You can run your TestStand sequence files from a command-line prompt using the following syntax:
\bin\SeqEdit.exe" /quit -run
This will launch the TestStand Sequence Editor (and optionally prompt you for TestStand login information if you have this configured), run your sequence file, then exit.
If you're using the TestStand process model, it can output your results to a report file or database if you configure this. To use a TestStand process mo
del to execute your sequence file, use the following syntax:
\bin\SeqEdit.exe" /quit -runEntryPoint
Here's an example:
C:\>"C:\Program Files\National Instruments\TestStand 3.0\bin\SeqEdit.exe" /quit -runEntryPoint "Single Pass" "C:\Program Files\National Instruments\TestStand 3.0\Examples\Demo\C\computer.seq"
Note that multiple sequences and sequence files can be specified on the command line.
TestStand supports remote sequence execution using DCOM (Distributed COM), which is an east way to remotely execute tests. But as for running tests or commands through a telnet or serial interface, you would have need to check Windows documentation on how to execute command-line remotely like this.
David Mc.
NI Applications Engineer -
DHCP request through accesspoint and router
This is how our setup is like:
Laptops => Cisco 1100 AP(static IP) => Wired LAN (Subnet 1) => Cisco Router => Wired LAN (Subnet 2) => DHCP server
What i would like is that the DHCP-request from our laptops is forwarded/relayed through the AP and Router to the DHCP-server and back.
We dont want to use the AP's internal DHCP server but centralise this.
At the moment i'v configured the AP through CLI and added the following command: ip dhcp-server xx.xx.xx.xx
Where xx is the IP of the DHCP server
On the Router i'v added the command ip helper-address xx.xx.xx.xx
Where xx is the IP of the DHCP server
Don't know if this is the correct way, but i do know it isn't working.
Some help is realy appreciated.
Grx,
JorisYou need at least the following connectivity for DHCP relay to work.
Between the DHCP relay agent and the DHCP server:
- UDP Port 67 <-> UDP Port 67
Between the DHCP server and the DHCP client:
- UDP Port 67 <-> UDP Port 68 (renewing/releasing a lease)
- ICMP echo (Most DHCP servers check if an IP is still free)
On the Cisco router you can use some debugging commands
to check that relaying works.
(This might produce a lot of output, careful on a production system.)
#term mon
#debug ip dhcp server packet
#debug ip dhcp server events
For Subnet 1 with the router's IP 10.0.0.1 and two configured
DHCP servers (192.168.0.1, 192.168.9.1) as "ip helper" a successfull
exchange looks like this:
DHCPD: DHCPREQUEST received from client 0100.aabb.bbcc.cc.
DHCPD: setting giaddr to 10.0.0.1.
DHCPD: BOOTREQUEST from 0100.aabb.bbcc.cc forwarded to 192.168.0.1.
DHCPD: BOOTREQUEST from 0100.aabb.bbcc.cc forwarded to 192.168.9.1.
DHCPD: forwarding BOOTREPLY to client 00aa.bbbb.cccc.
DHCPD: Forwarding reply on numbered intf
DHCPD: creating ARP entry (10.0.0.49, 00aa.bbbb.cccc).
DHCPD: unicasting BOOTREPLY to client 00aa.bbbb.cccc (10.0.0.49).
#undebug all
I would also try to ping the router's IP in Subnet 1 and a client
with a fixed IP in Subnet 1 from the server. (The DHCP server uses
this to check if a lease is actually free before handing it out)
Otherwise it's time for packet sniffing on the DHCP server
and the client. (snoop, tcpdump, ethereal) -
I have a router 2821 with two Internet links over "one" ethernet port. For this, I configured the interface GigabitEthernet0/1 in two subinterfaces with Vlans (interface GigabitEthernet0/1.998 and interface GigabitEthernet0/1.999). Betwen the router and the internet modens (ADSL and Cable) I have a Catalyst 2950T with the respective Vlans.
My problem is with the interface GigabitEthernet0/1.998 that is connected to cable modem (Motorola). This interface doesn´t receive IP address in the BVI interface via DHCP. If I place a workstation or the interface GigabitEthernet0/1 without Vlan configuration and switch the IP address is ok.
Bridging configuration because with the 'ip address dhcp' under interface GigabitEthernet0/1.998 doesn´t receive the ip address with the cable modem. If I place other dhcp server (Linux) with this configuration in the interface GigabitEthernet0/1.998 the IP address is ok. Bridging because cable modem.
With the BVI configuration, the dhcp client on the interface already received the IP, but after one or two days trying. In this midle time, the service provider doesn´t have allocated none IP and mac-address.
It has some suggestion, the problem is with the BVI interface or with the switch configuration (mac-address switch x mac-address router for the service provider)? What is the good design for this??
>>Confs router
interface GigabitEthernet0/1
no ip address
interface GigabitEthernet0/1.998
description "connected to WAN vlan ID 998 - Cable Modem"
encapsulation dot1Q 998
bridge-group 1
interface GigabitEthernet0/1.999
description "connected to WAN vlan ID 999 - ADSL"
encapsulation dot1Q 999
ip address 10.0.0.2 255.255.255.248
interface BVI1
ip address dhcp
>>Confs switch
interface FastEthernet0/17
description c2821 outside
switchport trunk allowed vlan 998,999
switchport mode trunk
interface FastEthernet0/18
description adsl
switchport access vlan 999
interface FastEthernet0/19
description cable
switchport access vlan 998
>>
Feb 9 03:00:28.685: Retry count: 2 Client-ID: cisco-0013.1a7f.0a89-BV1
Feb 9 03:00:28.685: Client-ID hex dump: 636973636F2D303031332E316137662E
Feb 9 03:00:28.685: 306138392D425631
Feb 9 03:00:28.685: Hostname: c2821
Feb 9 03:00:28.685: DHCP: SDiscover: sending 292 byte length DHCP packet
Feb 9 03:00:28.685: DHCP: SDiscover 292 bytes
Feb 9 03:00:28.685: B'cast on BVI1 interface from 0.0.0.0
Feb 9 03:00:31.497: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x23ECA7F
Feb 9 03:00:32.685: DHCP: SDiscover attempt # 3 for entry:
Feb 9 03:00:32.685: Temp IP addr: 0.0.0.0 for peer on Interface: BVI1
Feb 9 03:00:32.685: Temp sub net mask: 0.0.0.0
Feb 9 03:00:32.685: DHCP Lease server: 0.0.0.0, state: 1 Selecting
Feb 9 03:00:32.685: DHCP transaction id: 1798
Feb 9 03:00:32.685: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs
Feb 9 03:00:32.685: Next timer fires after: 00:00:04
Feb 9 03:00:32.685: Retry count: 3 Client-ID: cisco-0013.1a7f.0a89-BV1
Feb 9 03:00:32.685: Client-ID hex dump: 636973636F2D303031332E316137662E
Feb 9 03:00:32.685: 306138392D425631
Feb 9 03:00:32.685: Hostname: c2821
Feb 9 03:00:32.685: DHCP: SDiscover: sending 292 byte length DHCP packet
Feb 9 03:00:32.685: DHCP: SDiscover 292 bytes
Feb 9 03:00:32.685: B'cast on BVI1 interface from 0.0.0.0
Feb 9 03:00:36.685: DHCP: QScan: Timed out Selecting state
Feb 9 03:00:43.741: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xA87C56C3
Feb 9 03:00:43.773: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xA87C56C3%Unknown DHCP problem.. No allocation possible
Feb 9 03:00:45.821: DHCP: Waiting for 20 seconds on interface BVI1
Feb 9 03:00:47.381: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFF724762
Feb 9 03:00:49.737: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x18D646E9
Feb 9 03:01:00.897: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x5583DDD0The Cable Service Provider is receiving the mac-address of interface fast
ethernet 0/19 of switch. Are there how the switch doesn´t send this information
and the SP receive de mac-address of router? -
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 helpNajaf,
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 -
Dhcp and pcmcia NIC startup (SOLVED)
Hello;
I'm pretty impressed with Arch up to now, but am having a problem with the pcmcia NIC. I'm sure it's some simple config problem, but I haven't been able to figure it out.
I'm using a Network Everywhere NP100, which uses the axnet driver. No problems there. I have it set as eth0="dhcp".
It works fine, but when I restart the box, or start up from a cold start, dhcp isn't assigning an IP, and during boot, network fails on start. After the box is up and running, I have to remove the card from the slot and reinsert it to get dhcp to assign an IP.
I haven't seen this problem with other distros, so I know it can be fixed, not not sure how. Below is my rc.conf, maybe somebody can spot something I'm missing?
HARDWARECLOCK="UTC"
TIMEZONE=EST5EDT
KEYMAP=us
CONSOLEFONT=
USECOLOR="yes"
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# Networking
HOSTNAME="Arch-laptop"
# Module to load at boot-up (in this order)
# (prefix a module with a ! to disable it)
MODULES=(!usbserial !ide-scsi snd-es1968 yenta-socket pcmcia ohci_hcd ehci_hcd pcspkr parport_pc parport irtty_sir sir_dev irda crc_ccitt i2c_piix4 i2c_core uhci_hcd usbcore tsdev evdev rsrc_nonstatic pcmcia_core snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc gameport snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore rtc)
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# (prefix an interface in INTERFACES with a ! to disable it)
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
lo="lo 127.0.0.1"
eth0="dhcp"
INTERFACES=(lo eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# (prefix a route in ROUTES with a ! to disable it)
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Daemons to start at boot-up (in this order)
# (prefix a daemon with a ! to disable it)
DAEMONS=(dbus hal pcmcia syslog-ng crond network !netfs !hotplug)
# End of file
Any suggestions would be appreciated.# When you boot the machine the first time it is just fine?
No it has this problem every time the machine is started.
# Do you really have to remove the card from the slot, isn't 'cardctl eject' enough?
Removing and reinserting the card is faster than typing out a command so that's what I do.
# Does it work with static IP?
Don't know, router is set up as DHCP and haven't tried changing it to static. As it's a mobile machine, I'd prefer it works using dhcp.
# Does your machine own another nic, so the race who will become eth0 could be won by an ethernet card?
No, I just have the one NIC at the moment. I have a wireless pcmcia NIC as well, but haven't installed/configured it yet as I don't use it much and would like to solve this ethernet problem first.
#By the way, which kernel modules own the axnet drivers?I can't see any matching module in rc.conf's modules section, and you have hotplug disabled.
It's owned by pcmcia, which loads the module itself when the card is detected. This is working perfectly and the driver modules loads no problem. As far as I can tell the problem seems to be with the network daemon itself, but I could be mistaken about this.
I disabled hotplug for the moment while I try to figure this out. At first I thought hotplug was the culprit but even with it disabled the problem remains. I just haven't bothered to re-enable hotplug as I already have all the modules loading through rc.conf anyway and it speeds up booting.
Hope the additional info may help figure this out. I'm stumped. -
Solaris 10 zone configuration with sysidcfg and dhcp and hostname
Hi
Excuse me if I look like a n00b... it's probably because I'm a n00b.
I've been struggling in the dark for more than 2 days now and I'm wondering if I'm thinking about this all wrong...
I have stand-alone server where I need to run zones. I want to create zones and automagically configure them at boot (read: by running a script). So here's what I need...
A zone
starting from unconfigured state
whose hostname is not the same as the zone name
using corporate DHCP to get its IP address
with DNS config coming from the DHCP server
registering its address the DNS
with a preconfigured root password
(I don't own the corporate DHCP or DNS servers, I can't put my own DHCP or DNS servers on the network.)
I would lke to create the zone, throw some config at it, then boot the zone and walk away. I am using zones with exclusive-IP. I can construct the zones and manually configure them once they're started to have DHCP, my own name, registered IP address with DNS and everything else I have specified above. But I don't want to do it manually...
Sysidcfg seems to do some of what I want but not entirely.
In sysidcfg I can set the root_password, the primary interface using DHCP, DNS server. I can't set a hostname in sysidcfg AND use configure it for DHCP. So the hostname is not what I want it to be after the zone is started and ready to go. The DHCP server is providing the DNS configuration, Solaris does not seem to honour it, but i'll ignore that for the moment.
I have tried various combinations of using sysidcfg, /etc/nodename, /etc/hostname.+interface+ and /etc/dhcp.+interface+ but I can't find any combination that actually works.
I can write to the zonestorage/etc/nodename to set the nodename, that works. But it does not match the DHCP address, so I get prompted for a new name service because it can't find a DNS entry for the name.
I can write to the zonestorage/etc/hostname.+interface+ and /etc/dhcp.+interface+ (to get the system to register its name with the DNS server after getting its DHCP address) but then I get a system with no root password and no DNS configuration, even though they are set in the sysidcfg file.
I can write a script that gets part of the way using sysidcfg and /etc/... files, then boots the zone and then runs a bunch of voodoo via zlogin commands to fix all the stuff that couldn't be done 'properly', but that's not a 'boot and walk away' environment. I can write a script that uses sysidcfg and hacks around with other files in /etc (like nsswitch.conf, resolv.conf), but that just feels likes a dirty hack to fix something that wasn't done properly in the first place.
So where am I going wrong and how do I do it right (within the constraints defined)? Why can't I configure, boot and walk away?
ThanksThanks abrante
Thanks for your response!
I don't think the config is messed up after the installation. I think the installation is fine, it's just not what I want :-)
I'm trying to decouple the zonename from the system name and get DNS registrations working. After installation, a DHCP client can get its hostname from DNS but I'm trying to do it the other way around. I want the DHCP client specify its own hostname, get an address from the DHCP server and then register its hostname with DNS. If the system gets its name from DNS/DHCP then I have to configure those to provide the system name and I don't own the DHCP/DNS infrastructure. These zones are for a development/QA environment, so we create and reconfigure these frequently. Hence the need to specify the system name within the zone and register that name in the DNS.
I have tried fiddling with the PARAM_REQUEST_LIST but it does not seem to be working as I expect. :-$ Removing 12 did not help with setting the hostname from the system. DNS does not have a registered name for this system anyway, so even if it tried to get a name for this system, it would get nothing.
I also do want the DHCP to change the DNS server and domain name, but this does not happen even though my dhcpagent includes 6 and 15 in the PARAM_REQUEST_LIST. I still have to set them in the sysidcfg file because it is always ignored in Solaris (S10u8 with 10_Recommended 30-Jul-2010)
As stated, I know I can hack around with the system after it has booted. But I'm trying to configure the system before it starts and let it take care of itself and not have to touch it. Frankly I'm surprised that the sysidcfg does not allow you to set a hostname name when you are using DHCP, that the default DHCP configuration does not register the system name with the DNS server, and the DNS config from the DHCP response is ignored. Even a sys-unconfiged system requires DNS configuration during initial boot, when I know that the DHCP response contains DNS information.
FYI: Windows systems using DHCP work as expected in this respect by default, i.e. set system name, use DHCP --> system gets address from corporate DHCP, DNS settings are set from DHCP information, DNS registration is made for system name.
I'm working around this at the moment... I call my zone by the system name I want, I hardcode the DNS settings in the sysidcfg file and I create the hostname.+nic+ and dhcp.+nic+ files in the zone storage to get the system to register its name with DNS, them boot.
Edited by: cydonian on Aug 19, 2010 7:45 PM
Maybe you are looking for
-
Add Obstacle and Health in Android Runner Game
I am making a runner game in air for android actionscript 3. It has two buttons. One for Jumping and one for running. It runs to the right. As my character runs to the right the background also scrolls to the left. Now the problem is I need to add so
-
Human task expression builder (10.1.3.1 GA)
When I open up the Expression builder while inside the humanTask builder/editer/whatchamacallit I cannot see any BPEL variables. The Title displayed in the Expression builder is schema (vs the BPEL variables I see elsewhere). This gives me access to
-
Purchased Adobe product will not install/Help!
I purchased the SummerElements Special / Photoshop Elements 10 & Premiere Elements 10. I have tried most of last night trying to install Premiere Elements 10. I no longer have any Idea what to do! [email address removed]
-
Cisco Works error URN_NOT_FOUND : urn "JRM":Not found !!
Hi, I have a Cisco works server running LMS 2.6 version.Server was working fine without any issues.Suddenly i started facing an issue when i try to create a Netconfig Job.The error i am facing is " Error occured while processing.Possible Cause: URN_
-
please explain the different types in LSMW. what is the advantage in using them.