Partner TAC Tips Call Content - April 2011

Version 6

    May 2, 2011 Update 

    Slide titled "MSE Issues" in the attached file has been updated to reflect the points raised by Ron at Pre-production MSE upgrade from 6.0.75.0 code

     

     

    Tips from Cisco wireless TAC escalation, by Jake Fussell, Aaron Leonard, Pari Thiagasundaram, and Pushkar Sambhoos, presented on April 26, 2011.

     

    Recording:

    Click the link below to play it:

     

    https://cisco.webex.com/ciscosales/lsr.php?AT=pb&SP=TC&rID=51330472&rKey=0631efdf7aaae5bc&act=pb

     

    Partner Wireless TAC Tips-20110426 1504-1
    Tuesday, April 26, 2011 11:04 am New York Time
    1 Hour 10 Minutes

     

     

    Q&A Session for Partner Wireless TAC Tips

     

    Session Number: 206764889

    Date: 2011-4-26

    Starting time: 10:48

     

     

    ________________________________________________________________

     

     

       Ron Marosko - 11:10

    Q:  "Almost no reason to run..." is that another way of hinting that customers really should upgrade?

    Priority:  N/A 

                Aaron Leonard     - 11:11

              A:  Certainly they should upgrade to one of: 6.0 MR4, 7.0 MR0.5 or 7.0 MR1, if they are encountering any significant issues  

    ________________________________________________________________

     

     

       Nir  - 11:26

    Q:  FYI, I ran into this (OEAP and NAT) but it is not listed in the release notes of 7.0.116.0 as resolved.

    Priority:  N/A 

                Vic Nunes     - 11:27

              A:  answered in-line  

    ________________________________________________________________

     

     

       Payrtick Saldou  - 11:33

    Q:  What is the best way to authenticate 792x phones?  Certificates and use EAP-TLS? PEAP-MSCHAP?

    Priority:  N/A 

                Jacob Fussell     - 11:34

              A:  For phone authentication, it really depends on the company's security plan and how stringent they need it to be  

    ________________________________________________________________

     

     

       doug  - 11:33

    Q:  can elaborate on the challenges of using hi-gain antennas and 792x phones...

    Priority:  N/A 

                Jacob Fussell     - 11:35

              A:  The phone's Tx power would not be able to "throw" as far as the antenna's depending on how high gain and overlap etc. 

                Jacob Fussell     - 11:35

              A:  So you could possibly get into a near far type scenario  

    ________________________________________________________________

     

     

       doug  - 11:33

    Q:  can you elaborate?

    Priority:  N/A 

                Vic Nunes     - 11:42

              A:  answered in-line  

    ________________________________________________________________

     

     

       Kevin - 11:39

    Q:  Is the phone stuck in 'configuring ip' ES deployment for autonomous environments as well?  or only WLC?

    Priority:  N/A 

                Jacob Fussell     - 11:44

              A:  As Aaron mentioned, the stuck in "config ip" should occur on both unified and autonomous 

                Jacob Fussell     - 11:45

              A:  if someone does run into the "config ip" stuck condition, the only way to recover from that state is to power cycle the phone or remove the battery to power cycle  

    ________________________________________________________________

     

     

       Steve Lilley  - 11:53

    Q:  Will copies of this preso be available on the partner portal?

    Priority:  N/A 

                Vic Nunes     - 11:53

              A:   https://communities.cisco.com/groups/wireless-tac-tips  

    ________________________________________________________________

     

     

       Steve Lilley - 11:54

    Q:  Thanks guys!

    Priority:  N/A 

                Vic Nunes     - 11:55

              A:  np  

    ________________________________________________________________

     

     

       Samuel Clements - 11:56

    Q:  I've observed spurious RAID failures on MSE 3310 doing J MR1 database upgrade. Any insight on what's going on there?

    Priority:  N/A 

                Vic Nunes     - 11:58

              A:  Please follow-up with TAC 

                Pushkar Sambhoos     - 11:59

              A:  If you can email me the TAC SR number at psambhoo@cisco.com, I can take a look at this issue. Thanks.  

    ________________________________________________________________

     

     

       Samuel Clements - 11:59

    Q:  RAID failure SR 617532299. The built in RAID diagnostics tool showed the RAID as being okay.

    Priority:  N/A 

                Pari Thiagasundaram     - 12:04

              A:  Chris: This is a Cosmetic bug that I see from the SR that you had mentioned. CSCto52834  

    ________________________________________________________________

     

     

       Chris Brown - 11:59

    Q:  Sam is correct, I have seen the same but confirmed that it was not a valid failure through further troubleshooting. TAC is aware of the issue.

    Priority:  N/A 

                Pushkar Sambhoos     - 12:02

              A:  Thanks Chris. As I mentioned, I really haven't heard of this issue. It is quite possible that this is a known issue and some customers have run into it, So we will have to go back and dig up some TAC cases to see if it is a widespread problem.  

    ________________________________________________________________

     

     

       Steve Lilley - 12:08

    Q:  How about an update on Intel wireless client driver compatibilities?  I think Intel has 13.1, 13.2, 13.4, 13.5 versions out now...is the latest still the best, or is an earlier version/versions recommended?

    Priority:  N/A 

                Darren Douglas     - 12:15

              A:  addressed on call live