source specific ssh from EXOS-15.3.1.4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎10-13-2015 04:01 AM
Hi All,
Is it possible to give source while doing ssh from Extreme switch to some external node.
Like we give source using from in traceroute or ping.
Thanks
Is it possible to give source while doing ssh from Extreme switch to some external node.
Like we give source using from in traceroute or ping.
Thanks
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎10-13-2015 07:13 AM
Hi Harkanwaljeet,
Cli has no such option till EXOS 15.7 ,just verified.
Test logs :
=========
* Lab-sw # ssh2 12.0.1.28 ?
Execute the command
command to be executed on the remote host
* Lab-sw # ssh2 12.0.1.28
-------------- route-server.ip.att.net ---------------
--------- AT&T IP Services Route Monitor -----------
The information available through route-server.ip.att.net is offered
by AT&T's Internet engineering organization to the Internet community.
This router maintains eBGP peerings with customer-facing routers
throughout the AT&T IP Services Backbone:
IPv4: IPv6: City:
12.122.124.12 2001:1890:ff:ffff:12:122:124:12 Atlanta, GA
12.122.124.67 2001:1890:ff:ffff:12:122:124:67 Cambridge, MA
12.122.127.66 2001:1890:ff:ffff:12:122:127:66 Chicago, IL
12.122.124.138 2001:1890:ff:ffff:12:122:124:138 Dallas, TX
12.122.83.238 2001:1890:ff:ffff:12:122:83:238 Denver, CO
12.122.120.7 2001:1890:ff:ffff:12:122:120:7 Fort Lauderdale, FL
12.122.125.6 2001:1890:ff:ffff:12:122:125:6 Los Angeles, CA
12.122.125.44 2001:1890:ff:ffff:12:122:125:44 New York, NY
12.122.125.106 2001:1890:ff:ffff:12:122:125:106 Philadelphia, PA
12.122.125.132 2001:1890:ff:ffff:12:122:125:132 Phoenix, AZ
12.122.125.165 2001:1890:ff:ffff:12:122:125:165 San Diego, CA
12.122.126.232 2001:1890:ff:ffff:12:122:126:232 San Francisco, CA
12.122.125.224 2001:1890:ff:ffff:12:122:125:224 Seattle, WA
12.122.126.9 2001:1890:ff:ffff:12:122:126:9 St. Louis, MO
12.122.126.64 2001:1890:ff:ffff:12:122:126:64 Washington, DC
*** Please Note:
Ping and traceroute delay figures measured here are unreliable, due to the
high CPU load experienced when complicated show commands are running.
For questions about this route-server, send email to: jayb@att.com
*** Log in with username 'rviews', password 'rviews' ***
Password:
If you think this functinality is essential and want this to be supported in later versions, you may open a feature request and follow below link open a case with GTAC:
https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-contact-Extreme-Networks-Global-Tec...
Thanks & Regards
Syed Nishath Rahmathullah
Cli has no such option till EXOS 15.7 ,just verified.
Test logs :
=========
* Lab-sw # ssh2 12.0.1.28 ?
Execute the command
command to be executed on the remote host
* Lab-sw # ssh2 12.0.1.28
-------------- route-server.ip.att.net ---------------
--------- AT&T IP Services Route Monitor -----------
The information available through route-server.ip.att.net is offered
by AT&T's Internet engineering organization to the Internet community.
This router maintains eBGP peerings with customer-facing routers
throughout the AT&T IP Services Backbone:
IPv4: IPv6: City:
12.122.124.12 2001:1890:ff:ffff:12:122:124:12 Atlanta, GA
12.122.124.67 2001:1890:ff:ffff:12:122:124:67 Cambridge, MA
12.122.127.66 2001:1890:ff:ffff:12:122:127:66 Chicago, IL
12.122.124.138 2001:1890:ff:ffff:12:122:124:138 Dallas, TX
12.122.83.238 2001:1890:ff:ffff:12:122:83:238 Denver, CO
12.122.120.7 2001:1890:ff:ffff:12:122:120:7 Fort Lauderdale, FL
12.122.125.6 2001:1890:ff:ffff:12:122:125:6 Los Angeles, CA
12.122.125.44 2001:1890:ff:ffff:12:122:125:44 New York, NY
12.122.125.106 2001:1890:ff:ffff:12:122:125:106 Philadelphia, PA
12.122.125.132 2001:1890:ff:ffff:12:122:125:132 Phoenix, AZ
12.122.125.165 2001:1890:ff:ffff:12:122:125:165 San Diego, CA
12.122.126.232 2001:1890:ff:ffff:12:122:126:232 San Francisco, CA
12.122.125.224 2001:1890:ff:ffff:12:122:125:224 Seattle, WA
12.122.126.9 2001:1890:ff:ffff:12:122:126:9 St. Louis, MO
12.122.126.64 2001:1890:ff:ffff:12:122:126:64 Washington, DC
*** Please Note:
Ping and traceroute delay figures measured here are unreliable, due to the
high CPU load experienced when complicated show commands are running.
For questions about this route-server, send email to: jayb@att.com
*** Log in with username 'rviews', password 'rviews' ***
Password:
If you think this functinality is essential and want this to be supported in later versions, you may open a feature request and follow below link open a case with GTAC:
https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-contact-Extreme-Networks-Global-Tec...
Thanks & Regards
Syed Nishath Rahmathullah
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎10-13-2015 04:19 AM
Hi,
I am afraid that is not an option.
here is the command syntax for SSH and there is not an option to mention a source IP.
ssh2 {cipher cipher} {mac mac} {port portnum} {compression [on | off]} {user
username} {username} [host | ipaddress] {remote command } {vr vr_name}
I am afraid that is not an option.
here is the command syntax for SSH and there is not an option to mention a source IP.
ssh2 {cipher cipher} {mac mac} {port portnum} {compression [on | off]} {user
username} {username} [host | ipaddress] {remote command } {vr vr_name}
