Zum Inhalt wechseln


Foto

Tacacs Fehler


  • Bitte melde dich an um zu Antworten
3 Antworten in diesem Thema

#1 5232joe

5232joe

    Member

  • 345 Beiträge

 

Geschrieben 08. Januar 2016 - 07:03

Guten Morgen Forum,

 

auf einem WS-C2960S-24PS-L im logg file entdeckt.

 

bei anderen Cisco die selbe Config für die Tacacs Anbindung, hier keine Fehler ersichtlich - woran kann es liegen.

 

DANKE für Eure mithilfe

 

Jan  8 08:43:13.765: TPLUS: Sending AV start_time=1452242593
Jan  8 08:43:13.765: TPLUS: Sending AV priv-lvl=15
Jan  8 08:43:13.765: TPLUS: Sending AV cmd=show logging <cr>
Jan  8 08:43:13.765: TPLUS: Accounting request created for 469(hugoport)
Jan  8 08:43:13.765: TPLUS: using previously set server 192.168.146.2 from group tacacs+
Jan  8 08:43:13.765: TPLUS(000001D5)/0/NB_WAIT/3258EBC: Started 2 sec timeout
Jan  8 08:43:13.771: TPLUS(000001D5)/0/NB_WAIT: socket event 2
Jan  8 08:43:13.771: TPLUS(000001D5)/0/NB_WAIT: wrote entire 136 bytes request
Jan  8 08:43:13.771: TPLUS(000001D5)/0/READ: socket event 1
Jan  8 08:43:13.771: TPLUS(000001D5)/0/READ: Would block while reading
Jan  8 08:43:13.786: TPLUS(000001D5)/0/READ: socket event 1
Jan  8 08:43:13.786: TPLUS(000001D5)/0/READ: read entire 12 header bytes (expect 5 bytes data)
Jan  8 08:43:13.786: TPLUS(000001D5)/0/READ: socket event 1
Jan  8 08:43:13.786: TPLUS(000001D5)/0/READ: read entire 17 bytes response
Jan  8 08:43:13.786: TPLUS(000001D5)/0/3258EBC: Processing the reply packet
Jan  8 08:43:13.786: TPLUS: Received accounting response with status FAIL
Jan  8 08:43:37.531: TPLUS: Queuing AAA Accounting request 469 for processing
Jan  8 08:43:37.531: TPLUS: processing accounting request id 469
Jan  8 08:43:37.531: TPLUS: Sending AV task_id=632
Jan  8 08:43:37.531: TPLUS: Sending AV timezone=UTC
Jan  8 08:43:37.531: TPLUS: Sending AV service=shell
Jan  8 08:43:37.531: TPLUS: Sending AV start_time=1452242617
Jan  8 08:43:37.531: TPLUS: Sending AV priv-lvl=15
Jan  8 08:43:37.531: TPLUS: Sending AV cmd=configure terminal <cr>
Jan  8 08:43:37.531: TPLUS: Accounting request created for 469(hugoport)
Jan  8 08:43:37.531: TPLUS: using previously set server 192.168.146.2 from group tacacs+
Jan  8 08:43:37.537: TPLUS(000001D5)/0/NB_WAIT/3258EBC: Started 2 sec timeout
Jan  8 08:43:37.542: TPLUS(000001D5)/0/NB_WAIT: socket event 2
Jan  8 08:43:37.542: TPLUS(000001D5)/0/NB_WAIT: wrote entire 142 bytes request
Jan  8 08:43:37.542: TPLUS(000001D5)/0/READ: socket event 1
Jan  8 08:43:37.542: TPLUS(000001D5)/0/READ: Would block while reading
Jan  8 08:43:37.552: TPLUS(000001D5)/0/READ: socket event 1
Jan  8 08:43:37.552: TPLUS(000001D5)/0/READ: read entire 12 header bytes (expect 5 bytes data)
Jan  8 08:43:37.552: TPLUS(000001D5)/0/READ: socket event 1
Jan  8 08:43:37.552: TPLUS(000001D5)/0/READ: read entire 17 bytes response
Jan  8 08:43:37.552: TPLUS(000001D5)/0/3258EBC: Processing the reply packet
Jan  8 08:43:37.552: TPLUS: Received accounting response with status FAIL
Jan  8 08:43:44.305: %SYS-5-CONFIG_I: Configured from console by hugoport on vty0 (10.31.6.20)
Jan  8 08:43:49.789: TPLUS: Queuing AAA Accounting request 469 for processing
Jan  8 08:43:49.794: TPLUS: processing accounting request id 469
Jan  8 08:43:49.794: TPLUS: Sending AV task_id=633
Jan  8 08:43:49.794: TPLUS: Sending AV timezone=UTC
Jan  8 08:43:49.794: TPLUS: Sending AV service=shell
Jan  8 08:43:49.794: TPLUS: Sending AV start_time=1452242629
Jan  8 08:43:49.794: TPLUS: Sending AV priv-lvl=15
Jan  8 08:43:49.794: TPLUS: Sending AV cmd=show running-config <cr>
Jan  8 08:43:49.794: TPLUS: Accounting request created for 469(hugoport)
Jan  8 08:43:49.794: TPLUS: using previously set server 192.168.146.2 from group tacacs+
Jan  8 08:43:49.794: TPLUS(000001D5)/0/NB_WAIT/55300A4: Started 2 sec timeout
Jan  8 08:43:49.821: TPLUS(000001D5)/0/NB_WAIT: socket event 2
Jan  8 08:43:49.821: TPLUS(000001D5)/0/NB_WAIT: wrote entire 143 bytes request
Jan  8 08:43:49.821: TPLUS(000001D5)/0/READ: socket event 1
Jan  8 08:43:49.821: TPLUS(000001D5)/0/READ: Would block while reading
Jan  8 08:43:49.852: TPLUS(000001D5)/0/READ: socket event 1
Jan  8 08:43:49.852: TPLUS(000001D5)/0/READ: read entire 12 header bytes (expect 5 bytes data)
Jan  8 08:43:49.852: TPLUS(000001D5)/0/READ: socket event 1
Jan  8 08:43:49.852: TPLUS(000001D5)/0/READ: read entire 17 bytes response
Jan  8 08:43:49.852: TPLUS(000001D5)/0/55300A4: Processing the reply packet
Jan  8 08:43:49.852: TPLUS: Received accounting response with status FAIL
 

Gruss Hannes

#2 Otaku19

Otaku19

    Expert Member

  • 1.951 Beiträge

 

Geschrieben 08. Januar 2016 - 08:03

hm, was sagt das log am Server ?


Done: 640-801; 640-553; 642-524; 642-515; 642-892; 642-832; 642-504; 640-863; 642-627; 642-874; 642-785; ITIL v3 Foundation
Enterasys Systems Engineer; CompTIA Sec+; CompTIA Mobility+; CISSP; CISSP-ISSAP; Barracuda NGSE/NGSX; CISM


#3 r4z13l

r4z13l

    Newbie

  • 37 Beiträge

 

Geschrieben 13. Januar 2016 - 07:50

und kannst du den server per ping erreichen?

config des switches?



#4 5232joe

5232joe

    Member

  • 345 Beiträge

 

Geschrieben 18. Januar 2016 - 07:28

Morgen Forum,

 

der debug mode vom tacacs war eingeschaltet.

 

@ Board Veteran -  log am Server besagt, dass alles seine Richtigkeit hat.

@ newbie - somit erledigt sich deine frage mit dem ping.

 

Danke, Gruss hannes


Gruss Hannes