Welcome to Netcordia Connection Sign in | Join | Help
in Search

Radius issue with 2.4.

Last post 10-31-2008 2:38 PM by lbdwag. 4 replies.
Page 1 of 1 (5 items)
Sort Posts: Previous Next
  • 09-26-2008 2:47 PM

    Radius issue with 2.4.

     After upgrading I am getting the following errorwhile trying to login using a RADIUS account:

    300 User Exception
    Invalid Role 'shell:priv-lvl=15'

    I know that setting is for access to our Cisco switches, this was in there before the upgrade. Anyone have an idea about how to fix this, without removing it from the radius accounts.

  • 09-26-2008 3:15 PM In reply to

    Re: Radius issue with 2.4.

     If I do the'test account' it passes:

     

    2008-09-26 15:02:50 - Processing Started
     
    2008-09-26 15:02:50 ------------------------------------------------------ 
    2008-09-26 15:02:50 +++ BEGIN testing access to authentication servers +++ 
    2008-09-26 15:02:50 
    2008-09-26 15:02:50 +++ Attempting login to: 
    2008-09-26 15:02:50 +++ server = '##.##.##.#' 
    2008-09-26 15:02:50 +++ user = 'account' 
    2008-09-26 15:02:50 
    2008-09-26 15:02:51 +++ Attempt send access request packet 
    .....
    .....
    2008-09-26 15:02:51 +++ Attempt receive reply packet 
    .....
    .....
    2008-09-26 15:02:51 
    2008-09-26 15:02:51 +++ Access Accepted +++ 
    2008-09-26 15:02:51 +++ NetMRI-UserRole: SysAdmin, shell:priv-lvl=15 
    2008-09-26 15:02:51 
    2008-09-26 15:02:51 +++ END testing access to authentication servers +++ 
     
    2008-09-26 15:02:51 - Processing Completed

     

  • 10-16-2008 2:26 PM In reply to

    Re: Radius issue with 2.4.

    I have also figured out that only local account that can login is the 'admin' account.
  • 10-31-2008 2:27 PM In reply to

    • dpatten
    • Top 25 Contributor
    • Joined on 09-18-2007
    • Annapolis, MD

    Re: Radius issue with 2.4.

    lbdawg, I am not sure whether you firgured this out or not yet.  But it appears your policy has a cisco attribute configured, check your IAS and make sure that your Radius policy for your NetMRI does not include that attribute, '...level-15."

    Netcordia
    Sys. Admin
  • 10-31-2008 2:38 PM In reply to

    Re: Radius issue with 2.4.

    What I figured out is that NetMRI freaks out with the shell:priv-lvl=15 entry.

    I ended up making 2 policies, one that only applies to Cisco devices and then on for anything else (ala NetMRI). The Cisco policy contains the lvl=15 entry, the onther does not. This stops NetMRI from ever seeing it. Just odd that it had worked but then 'broke' only during login.

    I had ment to get back in to update this but i've been busy... ;)

Page 1 of 1 (5 items)