Roam Testing to Millisecond

Unanswered Question
Jun 20th, 2010

Is there a way to change the controller time stamp to include milliseconds in the CLI? Or, is there another way to test roaming to the millisecond?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 2 (3 ratings)
Loading.
dancampb Mon, 06/21/2010 - 07:04

If you have autonomous AP's just setup the logging to show the millisecond with "service timestamps log datetime msec"

If you have a controller the debug client output shows the milliseconds.

Elliott Shawd Thu, 06/24/2010 - 05:39

I can't see the milliseconds on the controller debug. I get:

Thu Jun 24 08:33:51 2010: 00:16:6f:6e:88:15 10.34.72.133 RUN (20) Change state to START (0) last state RUN (20)

Thu Jun 24 08:33:51 2010: 00:16:6f:6e:88:15 10.34.72.133 START (0) Initializing policy

We are running code 4.2.207.0.

jfraasch Thu, 06/24/2010 - 08:46

In routers it would be:

service timestamps debug date local msec

service timestamps log date local msec

This will add the msecs to the log and debug lines.


James

Elliott Shawd Thu, 06/24/2010 - 08:56

That doesn't work for me. I don't get those options.

(ak650-wism-s4-2) config>service timestamps debug ?       

datetime       Timestamp debug messages with standard date and time.

disable        Do not timestamp debug messages.

uptime         Timestamp debug messages with time since last reset.

(ak650-wism-s4-2) config>service timestamps debug datetime ?

(ak650-wism-s4-2) config>service timestamps debug datetime

(ak650-wism-s4-2) config>service timestamps log

datetime       Timestamp log messages with standard date and time.

disable        Do not timestamp log messages.

uptime         Timestamp log messages with time since last reset.

(ak650-wism-s4-2) config>service timestamps log datetime ?

(ak650-wism-s4-2) config>service timestamps log datetime

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode