Forum Discussion

Anzine321's avatar
Anzine321
Icon for Cirrus rankCirrus
Jun 16, 2025

ssh on slot1 failed f5 viprion

Hi

i finished move f5 viprion from old data center to new data center,

but i have a problem that i can not access ssh from the host only on slot 1,

when i generate qkview on slot 1 is not display only slot 2-4 available

how can i check this slot 1 because all of cluster is green and  runnning

is that related to management interface on slot 1 ?

4 Replies

  • Update

    interface management on blade 1 was down and now state up and i can access cluster management on slot 1

    but ssh from host 1  still failed,

    i tried to compare ssh and telnet on slot 2-4 work fine

    telnet to port 443 

    slot 1 : OK

    slot 2 : OK

    slot 3 : OK

    slot 4 : OK

    telnet port 22

    slot 1 : Not OK

    slot 2 : OK

    slot 3 : OK

    slot 4 : OK

    and on qkview only show slot 2-4 and slot 1 missing and i tried to opencase this issue

  • f51's avatar
    f51
    Icon for Cumulonimbus rankCumulonimbus

    Thank you for reply. If possible, access slot 1 via the serial console (direct console connection) and Check logs for errors:

    clsh tail -n 50 /var/log/ltm

    clsh tail -n 50 /var/log/messages

    Check Mgmt IP configuration if there any typo and also from a working blade (slot 2-4), run:

    clsh tmsh list sys management-ip

    and

    clsh tmsh show net interface

     

    If all else fails, try rebooting slot 1 

  • f51's avatar
    f51
    Icon for Cumulonimbus rankCumulonimbus

    Hi Anzine321​ 

    Here are a couple of cool points!

    • On VIPRION, each blade (slot) can have its own management interface, but typically only the primary blade (slot 1, or the current "active" blade) is directly accessible via the management IP.
    • The other slots (secondary blades) do not have separate management IPs by default; they are managed through the primary blade.
    • SSH access is usually only available on the primary blade’s management IP. If you want to access other blades, you typically SSH to the primary blade and then use the ssh slotX command to access other slots.

    Are you trying to SSH to the same management IP for all slots? If so, only slot 1 (the primary blade) will respond.

    Verify physical and logical connectivity for slot 1’s management interface.

    • each blade has ip cluster on host, i tried ssh to 2-4 work fine and only on slot 1 failed, and i tried to ssh with ip cluster and only on slot 1 failed, and then i tried telnet port 22 cluster ip on slot 1 and failed, another telnet to slot 2-4 work fine