No worry about the delay, these Nexus 5548P switches are in such a physical environment, that we could not do some of your task you suggested, unfortunately. Anyway they do not solve the question, is there any other methor to get it work.
I even removed the existing tacacs+ configuration from the box, then I re configured it (by using the configuration statemens used for these working ones), no help.
As earlier said in my post, that the Nexus 5548P stopped to send out any outbound tcp/49 tacacs+ session requests. (this were obtained from the tcpdump taken from firewall, which is def.gateway for Nexus management).
when trying to logon (with tacacs userid/pw) the following error message is resulted to gatekeeper (SSH) session establishment when entring the UID + strong password....
Remote AAA servers unreachable_local authentication failed.png
A 2-4
we do use mgmt vrf for VPC peer, not for the box management. the management interface is SVI, which has a firewall (not changed) as a Gateway, and all the other sessions, logging to the external security log servers, NTP, ssh, and things like incoming/outgoing ssh sessions are working well, but no any tacacs request is leaving the box.
The version we are running: version 5.0(3)N2(2a) (bootflash:/n5000-uk9.5.0.3.N2.2a.bin) since beging of November.
Satisfactions from the N 5548 boxes are somewhat the only good thing is the price of the 10G interface port, which is not a cheap, but more a less expensive the Catalyst 6500s have.
