Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TACACS+]: Add config command for TACACS+ source address #171

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

liuqu
Copy link

@liuqu liuqu commented Dec 14, 2017

- What I did

  • Add config command for TACACS+ source address

- How to verify it

  • Check "TACPLUS|global" table in configDB
127.0.0.1:6379[4]> hgetall TACPLUS|global
1) "src_ip"
2) "100.1.1.1"

- New command output (if the output of a command-line utility has changed)

# config tacacs src_ip 100.1.1.1    
# show tacacs
TACPLUS global auth_type pap (default)
TACPLUS global src_ip 100.1.1.1
TACPLUS global timeout 3
TACPLUS global passkey test123

TACPLUS_SERVER address 10.65.254.222
               priority 1
               tcp_port 49

-->

* Add config command to specify TACACS+ source address
  command: config tacacs src_ip <ip_address>

  Signed-off-by: Chenchen Qi <chenchen.qcc@alibaba-inc.com>
vdahiya12 added a commit to vdahiya12/sonic-utilities that referenced this pull request Jul 23, 2021
…dors (sonic-net#171)

This PR refactors the firmware information MUX_CABLE_INFO output to return the following fields for each target.

{
"version_active": "",
"version_inactive": "",
"version_next": "",
}
So by calling this for all the 3 MCU's TOR1, TOR2 and NIC we can get the below result.
which would be stored in state db table MUX_CABLE_INFO

{
"version_nic_active": "0.6MS",
"version_nic_inactive": "0.5MS",
"version_nic_next": "0.6MS",
"version_self_active": "0.5MS",
"version_self_inactive": "0.6MS",
"version_self_next": "0.6MS",
"version_peer_active": "0.6MS",
"version_peer_inactive": "0.6MS",
"version_peer_next": "0.6MS",
} 

Signed-off-by: vaibhav-dahiya <vdahiya@microsoft.com>
mihirpat1 pushed a commit to mihirpat1/sonic-utilities that referenced this pull request Sep 15, 2023
… split the get_part_number and get_vendor API's (sonic-net#171)

This PR adds a stub function definition with details as to how it should be implemented by a Y cable vendor.

Description
Added a stub function definition with a doc string describing how it should be implemented
Cleaning up and split some API's for vendors

Motivation and Context
Firmware upgrade is a functionality that vendors need to implement, this PR adds the definition
and a description of how the implementation of this firmware_upgrade API should be

How Has This Been Tested?
Will be tested once implemented
for cleanup API's opened a python shell and executed API's for correctness

Signed-off-by: vaibhav-dahiya <vdahiya@microsoft.com>
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