[rancid] rancid -d -t fxos seems to choke on "connect fxos" on Multi-Instance FTD Application.

[heasley]

Tue, Jan 14, 2025 at 06:21:42PM +0000, Zhang, Anchi:
> HIT COMMAND:>  show model
>     In ShowModel: >  show model
> HIT COMMAND:> show inventory
>     In ShowInventory: > show inventory
> HIT COMMAND:> dir /all
>     In DirSlotN: > dir /all
> HIT COMMAND:> show mode
>     In ShowMode: > show mode
> HIT COMMAND:> show managers
>     In ShowManagers: > show managers
> HIT COMMAND:> show network
>     In ShowNetwork: > show network
> sky-www-ftd-corp-prod: missed cmd(s): show network-static-routes, show network-dhcp-server, show running-config, connect fxos, term len 0, show system firmware detail, show chassis detail, show chassis inventory detail, show chassis environment expand detail
> sky-www-ftd-corp-prod: End of run not found
> sky-www-ftd-corp-prod: clean_run is false
> sky-www-ftd-corp-prod: found_end is false
> !
> 
> sky-log1% fxlogin sky-www-ftd-corp-prod
> sky-www-ftd-corp-prod
> spawn ssh -c aes256-ctr -x -l admin sky-www-ftd-corp-prod
> 
> Password:
> Last login: Thu Dec 12 22:33:36 UTC 2024 from 10.141.3.229 on pts/1
> 
> Copyright 2004-2023, Cisco and/or its affiliates. All rights reserved.
> Cisco is a registered trademark of Cisco Systems, Inc.
> All other trademarks are property of their respective owners.
> 
> Cisco Firepower Extensible Operating System (FX-OS) v2.14.1 (build 131)
> Cisco Secure Firewall 3110 Threat Defense v7.4.1 (build 172)
> 
> > connect fxos
> Cannot connect to FXOS from Multi-Instance FTD Application.
> >

What do you mean by choke?  It appears from the logs that you included
that it did not hang.  But, it did not find the subsequent commands
and/or 'connect fxos' output that it expected and therefore failed.

Is this new behavior, such as following an o/s upgrade?

I do not have any fx-os boxes myself, so you need to help me understand
the environment.  From the docs, multi-instance is a container-like
mechanism and 'connect fxos' connects to the parent o/s.  Is that
correct?  Is there another way to connect to the parent in the
multi-instance environment?