Comware

 View Only
  • 1.  I am trying integrate AAA with this HPE FlexFabric 5950 Switch Series HWTACACS to CISCO ISE TACACS +

    Posted May 03, 2019 12:37 PM

    I am trying integrate AAA with this HPE FlexFabric 5950 Switch Series HWTACACS to CISCO ISE TACACS +

    Can anyone help?



  • 2.  RE: I am trying integrate AAA with this HPE FlexFabric 5950 Switch Series HWTACACS to CISCO ISE TACACS +

    Posted May 08, 2019 06:42 PM

    hwtacacs scheme tacacs-ec
    primary authentication 10.20.20.231 key simple XXXXXXXXXX       ----------IP CISCO ISE PRIMARY
    primary accounting 10.20.20.231 key simple XXXXXXXXXX
    primary authorization 10.20.20.231 key simple XXXXXXXXXX
    secondary authentication 10.33.20.231 key simple XXXXXXXXXX  ----------IP CISCO ISE SECONDARY
    secondary accounting 10.33.20.231 key simple XXXXXXXXXX
    secondary authorization 10.33.20.231 key simple XXXXXXXXXX
    user-name-format without-domain
    nas-ip 10.20.11.130  ----------IP SWITCH
    #
    domain cppm-ec
    authentication login hwtacacs-scheme tacacs-ec local
    authorization login hwtacacs-scheme tacacs-ec local
    accounting login hwtacacs-scheme tacacs-ec local
    #
    domain default enable cppm-ec

    #
    user-interface vty 0 15
    authentication-mode scheme
    user-role network-admin
    user-role network-operator
    idle-timeout 0 0
    protocol inbound ssh
    #
    ssh server enable
    public-key local create rsa



  • 3.  RE: I am trying integrate AAA with this HPE FlexFabric 5950 Switch Series HWTACACS to CISCO ISE TACACS +

    Posted May 09, 2019 10:20 PM
    Thx for the help

    I had try all those command it work.
    Current I face a issue on the Cisco ise.
    The log of the live tacacs give me a error msg of 13017 received TACACS+ packet from unknow network device or aaa client


  • 4.  RE: I am trying integrate AAA with this HPE FlexFabric 5950 Switch Series HWTACACS to CISCO ISE TACACS +

    Posted May 16, 2019 08:22 AM

    The above configuration is fine and looks good.  Looks like something at Tacacs+ is causing this problem.. better to open a Tac with Cisco.