Tacacs issue

Unanswered Question
Jul 15th, 2008

Hi,

Can someone explain the issue below to me.

*Jul 15 16:40:16.677: TPLUS(0000023C)/0/WRITE: wrote entire 21 bytes request

*Jul 15 16:40:16.781: TPLUS(0000023C)/0/READ: socket event 1

*Jul 15 16:40:16.781: TPLUS(0000023C)/0/READ: read entire 12 header bytes (expect 6 bytes data)

*Jul 15 16:40:16.781: TPLUS(0000023C)/0/READ: socket event 1

*Jul 15 16:40:16.781: TPLUS(0000023C)/0/READ: read entire 18 bytes response

*Jul 15 16:40:16.781: T+: Version 192 (0xC0), type 1, seq 4, encryption 1

*Jul 15 16:40:16.781: T+: session_id 1607034059 (0x5FC964CB), dlen 6 (0x6)

*Jul 15 16:40:16.781: T+: AUTHEN/REPLY status:2 flags:0x0 msg_len:0, data_len:0

*Jul 15 16:40:16.781: T+: msg:

*Jul 15 16:40:16.781: T+: data:

*Jul 15 16:40:16.781: T+: End Packet

*Jul 15 16:40:16.785: TPLUS(0000023C)/0/63E21E64: Processing the reply packet

*Jul 15 16:40:16.785: TPLUS: Received authen response status FAIL (3)

*Jul 15 16:40:17.681: ISAKMP/xauth: reply attribute XAUTH_STATUS_V2 unexpected.

it is the last line that seems to be catching me out. The user account is setup in my unix TACACS server the same as the rest. ( new to this unix based tacacs stuff).

Hpe you can help

Regards

Stephen

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Loading.
Jagdeep Gambhir Tue, 07/15/2008 - 11:41

Stephen,

Can you test it with local authentication and see if that works.

Also let me know the IOS ver running on the router.

Regards,

~JG

stephen.stack Wed, 07/16/2008 - 00:45

Hi JG,

Thanks for quick response. It appears that i did not restart the tacacs process in the unix box properly, hence the change did not take effect.

It is all working now, thanks to my unix guru here.

Thanks again

Stephen

Actions

This Discussion