Hi Team,
Thanks, a lot guys for all your positive contribution, i eventually discovered that i didn't specify source IP(telnet Server Ip) after running "sho ip ssh' command as follows:
MyAruba(config)# sh ip ssh
SSH Enabled : Yes Secure Copy Enabled : No
TCP Port Number : 22 Timeout (sec) : 120
Rekey Enabled : No Rekey Time (min) : 60
Rekey Volume (KB) : 1048576
Host Key Type : RSA Host Key/Curve Size : 2048
Ciphers :
L5Z13(config)# sh ip ssh
SSH Enabled : Yes Secure Copy Enabled : No
TCP Port Number : 59987 Timeout (sec) : 120
Rekey Enabled : No Rekey Time (min) : 60
Rekey Volume (KB) : 1048576
Host Key Type : RSA Host Key/Curve Size : 2048
Ciphers : #######################################
MACs : $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
Ses Type | Source IP Port
--- -------- + ---------------------------------------------- -----
1 console |
2 telnet |
3 inactive |
4 inactive |
5 inactive |
6 inactive |
MACs : $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
Ses Type | Source IP Port
--- -------- + ---------------------------------------------- -----
1 console |
2 telnet |
3 inactive |
4 inactive |
5 inactive |
6 inactive |
After i declared source IP, then all came to life. i can now telnet and ssh and ping my VSF stuck back and forth.
Thanks alot team.
Brian
Original Message:
Sent: 8/12/2021 8:18:00 AM
From: parnassus
Subject: RE: Cannot Telnet, Ping or SSh access the Aruba 2930F VSF stuck
Hi, provided that access switches haven't IP Routing enabled and they have an IP address set on a propagated VLAN ID used for management purposes (indeed here we start with the assumption they are uplinked to Core and uplink ports allow the very same set of VLAN IDs) then using the Core IP address on that very VLAN ID as the Default Gateway is enough (automatically a default route is created).
From an access switch you should be able to ping/telnet/ssh the Core and vice-versa (if nothing else - ACL? - is blocking such services or their reachability from other segments of your network).
------------------------------
Davide Poletto
------------------------------
Original Message:
Sent: Aug 12, 2021 07:51 AM
From: Phillip Horn
Subject: Cannot Telnet, Ping or SSh access the Aruba 2930F VSF stuck
Did you set the default gateway on the unreachable switches?
I think You have to create a route and also add the gateway of the core on the switch so it will send the traffic
ip default route 0.0.0.0/0.0.0.0 10.225.145.1
ip default gateway 10.225.145.1
If you have another device on the same vlan as the switches you want to manage, the might also work
Ex
core
10.225.145.1
sw1
10.225.145.21
from the code, you can probably reach the access switch or if you have a workstation on that vl with 10.225.145.10 ip, that probably would work
------------------------------
Phillip Horn
Original Message:
Sent: Aug 11, 2021 01:50 AM
From: Brian Yusufu
Subject: Cannot Telnet, Ping or SSh access the Aruba 2930F VSF stuck
Yes, it is. But still i cannot reach them.
Original Message:
Sent: 8/6/2021 3:38:00 AM
From: Craig Syme
Subject: RE: Cannot Telnet, Ping or SSh access the Aruba 2930F VSF stuck
Firstly check SSH is indeed enabled, you can run the command 'show ip ssh' to determine this. Is IP Routing enabled?
------------------------------
Craig Syme
Original Message:
Sent: Aug 04, 2021 09:12 AM
From: Brian Yusufu
Subject: Cannot Telnet, Ping or SSh access the Aruba 2930F VSF stuck
Hi Team,
I have recently upgraded my network from 3com to Aruba 2930f switches and almost all my vastly placed cabinets i have Aruba switches configured with VSF Stucking and all have fibre trunk port patched to My Fabric core.
Everything is working fine but besides having enabled inbound telnet and SSH, i cannot ping nor telnet to those arubas from my office machine through the network. I can only access them via physical console cable.
Is there abything i am missing interms of how to enable telnet, ssh and ping to these aruba switches?
Regards,
Brian
------------------------------
Brian Yusufu
------------------------------