Skip to content

mgmt_vrf_namespace_tacacs: Tacacs enhancement on top of namespace sol…#428

Closed
kannankvs wants to merge 1 commit intosonic-net:masterfrom
kannankvs:mgmt_vrf_namespace_tacacs
Closed

mgmt_vrf_namespace_tacacs: Tacacs enhancement on top of namespace sol…#428
kannankvs wants to merge 1 commit intosonic-net:masterfrom
kannankvs:mgmt_vrf_namespace_tacacs

Conversation

@kannankvs
Copy link
Collaborator

- What I did
Enhanced the configuration for using --use-mgmt-vrf for tacacs server configuration on top of namespace based solution for management VRF.

- How I did it
Added checks for vrf and set the variable to "mgmt" if management VRF is enabled, else use "None". There is no change in the command syntax. Its just the value that is being passed for non-mgmt-vrf and for mgmt-vrf.

- How to verify it

  1. First, checkout the namespace solution once if the following two PRs are merged.
    (a) mgmt_vrf_namespace: management vrf using namespace solution sonic-buildimage#2405
    (b) mgmt_vrf_namespace: management vrf using namespace solution #422.
    Checkout this file aaa.py along with the files/image_config/hostcfgd/hostcfgd PR.
    With all these files, enable mgmt vrf using command "config vrf add mgmt" and configure tacacs client using following commands.
    (a) config aaa authentication login tacacs+
    (b) config tacacs authtype login
    (c) config tacacs passkey testing123
    (d) config tacacs add --use-mgmt-vrf serveripaddress
    Configure the tacacs server accordingly.
    Then, do SSH to the device and verify that the user is authenticated using tacacs server via the management VRF port eth0.

@kannankvs
Copy link
Collaborator Author

no more valid

@kannankvs kannankvs closed this Apr 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants