Security

last person joined: yesterday 

Forum to discuss Enterprise security using HPE Aruba Networking NAC solutions (ClearPass), Introspect, VIA, 360 Security Exchange, Extensions, and Policy Enforcement Firewall (PEF).
Expand all | Collapse all

4th Generation iPod Touch issues

This thread has been viewed 0 times
  • 1.  4th Generation iPod Touch issues

    Posted Aug 01, 2013 07:27 AM

    Hi,

     

    I am troubleshooting iPod T issues with them not working well on our hospital wireless network and want to try some of the debugging commands, in particular

     

    #configure terminal logging level debugging user-debug...

     

    However, coming from a Cisco background, I have big flashing red lights in my head at the word debugging, I am worried I might cause major issues with commands like this. 

     

    Is it alright to try this or should I think about a different stratergy?

     

    Many thanks.

     

    W



  • 2.  RE: 4th Generation iPod Touch issues

    EMPLOYEE
    Posted Aug 01, 2013 07:31 AM

    That's your go to command for troubleshooting user connectivity issues.
    It doesn't have the same performance impact as some debug commands in Cisco land, but you should still turn it off when you are finished.


    Sent from my BlackBerry Z10



  • 3.  RE: 4th Generation iPod Touch issues

    Posted Aug 01, 2013 07:36 AM

    Cheers for the fast reply.

     

    To turn it off is it just with a no prefix? like:

     

    #no configure terminal logging level debugging user-debug...



  • 4.  RE: 4th Generation iPod Touch issues

    EMPLOYEE
    Posted Aug 01, 2013 07:38 AM

    Correct! Just negate the command after you are already in global config mode (config t)

    (controller) # config t

    (controller) (config) # no logging level debugging user-debug


    Sent from my BlackBerry Z10



  • 5.  RE: 4th Generation iPod Touch issues

    Posted Aug 01, 2013 07:39 AM

     

    Another good thing when you run the user-debug <devicemac> is that you are only focusing the debugging on that particular device not against all devices.

     

    And like cappalli said it shouldn't impact the performance of your controller but make sure to turn it off after you are done.

     

    You can also use the show auth-tracebuf if it is related to an authentication issue