From Chris.Davis at principia.edu Fri Jan 3 17:13:28 2025 From: Chris.Davis at principia.edu (Chris Davis) Date: Fri, 3 Jan 2025 17:13:28 +0000 Subject: [rancid] Rancid on Alma Linux Message-ID: <7C3BF332-B61B-4D1F-BA41-07D96AD70295@principia.edu> Sent this a bit ago, but haven?t seen it come through. So, trying again. Pretty sure I?ve seen my messages in the past. I?m currently running Rancid 3.7 and moving to Alma Linux, version 9, I believe. Does 3.7 support it? Wondering if I need to go to the current version of Rancid (3.13) or if it?s ok to just upgrade/migrate the OS. Any thoughts? Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From heas at shrubbery.net Fri Jan 3 23:27:24 2025 From: heas at shrubbery.net (heasley) Date: Fri, 3 Jan 2025 23:27:24 +0000 Subject: [rancid] Rancid on Alma Linux In-Reply-To: <7C3BF332-B61B-4D1F-BA41-07D96AD70295@principia.edu> References: <7C3BF332-B61B-4D1F-BA41-07D96AD70295@principia.edu> Message-ID: Fri, Jan 03, 2025 at 05:13:28PM +0000, Chris Davis: > Sent this a bit ago, but haven?t seen it come through. So, trying again. Pretty sure I?ve seen my messages in the past. > > I?m currently running Rancid 3.7 and moving to Alma Linux, version 9, I believe. Does 3.7 support it? Wondering if I need to go to the current version of Rancid (3.13) or if it?s ok to just upgrade/migrate the OS. I have not used Alma, but there should not be anything special about it, nor does rancid require anything special of the o/s. From Anchi.Zhang at nrg.com Tue Jan 14 18:21:42 2025 From: Anchi.Zhang at nrg.com (Zhang, Anchi) Date: Tue, 14 Jan 2025 18:21:42 +0000 Subject: [rancid] rancid -d -t fxos seems to choke on "connect fxos" on Multi-Instance FTD Application. In-Reply-To: References: Message-ID: sky-log1% hostnamectl | grep Operating Operating System: Oracle Linux Server 8.10 sky-log1% rancid --version /opt/rancid/bin/rancid version 3.13 calling Getopt::Std::getopts (version 1.12 [paranoid]), running under Perl version 5.26.3. [Now continuing due to backward compatibility and excessive paranoia. See 'perldoc Getopt::Std' about $Getopt::Std::STANDARD_HELP_VERSION.] Too few arguments: host name required sky-log1% rancid -d -t fxos sky-www-ftd-corp-prod loadtype: device type fxos loadtype: found device type fxos at /opt/rancid/etc/rancid.types.base:483 executing fxlogin -t 90 -c"show model;show inventory;dir /all;show mode;show managers;show network;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;show configuration" sky-www-ftd-corp-prod PROMPT MATCH: ^([^ >]*)(>|#) 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From heas at shrubbery.net Wed Jan 15 20:35:23 2025 From: heas at shrubbery.net (heasley) Date: Wed, 15 Jan 2025 20:35:23 +0000 Subject: [rancid] rancid -d -t fxos seems to choke on "connect fxos" on Multi-Instance FTD Application. In-Reply-To: References: Message-ID: 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? From Anchi.Zhang at nrg.com Wed Jan 15 21:10:52 2025 From: Anchi.Zhang at nrg.com (Zhang, Anchi) Date: Wed, 15 Jan 2025 21:10:52 +0000 Subject: [rancid] rancid -d -t fxos seems to choke on "connect fxos" on Multi-Instance FTD Application. In-Reply-To: References: Message-ID: Thank you for your reply. I modified rancid.types.base as below then all was good. We do not need the fxos info archived anyway. sky-log1% grep "fxos;command" rancid.types.base fxos;command;fxos::ShowModel;show model fxos;command;fxos::ShowInventory;show inventory fxos;command;fxos::DirSlotN;dir /all fxos;command;fxos::ShowMode;show mode fxos;command;fxos::ShowManagers;show managers fxos;command;fxos::ShowNetwork;show network fxos;command;fxos::ShowNetwork;show network-static-routes fxos;command;fxos::ShowNetwork;show network-dhcp-server #fxos;command;fxos::WriteTermFTD;show running-config #fxos;command;fxos::RunCommand;connect fxos; prompt changes #fxos;command;fxos::RunCommand;term len 0 #fxos;command;fxos::ShowFirmware;show system firmware detail #fxos;command;fxos::ShowChassis;show chassis detail #fxos;command;fxos::ShowChassis;show chassis inventory detail #fxos;command;fxos::ShowChassis;show chassis environment expand detail #fxos;command;fxos::WriteTerm;show configuration fxos;command;fxos::WriteTerm;show running-config From: heasley Sent: Wednesday, January 15, 2025 2:35 PM To: Zhang, Anchi 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? From heas at shrubbery.net Thu Jan 16 18:12:13 2025 From: heas at shrubbery.net (heasley) Date: Thu, 16 Jan 2025 18:12:13 +0000 Subject: [rancid] rancid -d -t fxos seems to choke on "connect fxos" on Multi-Instance FTD Application. In-Reply-To: References: Message-ID: Wed, Jan 15, 2025 at 09:10:52PM +0000, Zhang, Anchi: > Thank you for your reply. I modified rancid.types.base as below then all was good. We do not need the fxos info archived anyway. > > sky-log1% grep "fxos;command" rancid.types.base > fxos;command;fxos::ShowModel;show model > fxos;command;fxos::ShowInventory;show inventory > fxos;command;fxos::DirSlotN;dir /all > fxos;command;fxos::ShowMode;show mode > fxos;command;fxos::ShowManagers;show managers > fxos;command;fxos::ShowNetwork;show network > fxos;command;fxos::ShowNetwork;show network-static-routes > fxos;command;fxos::ShowNetwork;show network-dhcp-server > #fxos;command;fxos::WriteTermFTD;show running-config > #fxos;command;fxos::RunCommand;connect fxos; prompt changes > #fxos;command;fxos::RunCommand;term len 0 > #fxos;command;fxos::ShowFirmware;show system firmware detail > #fxos;command;fxos::ShowChassis;show chassis detail > #fxos;command;fxos::ShowChassis;show chassis inventory detail > #fxos;command;fxos::ShowChassis;show chassis environment expand detail > #fxos;command;fxos::WriteTerm;show configuration > fxos;command;fxos::WriteTerm;show running-config Great, but that does not help me fix the problem for others. Could someone address my questions that are below? > From: heasley > Sent: Wednesday, January 15, 2025 2:35 PM > To: Zhang, Anchi > > > > 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? From Anchi.Zhang at nrg.com Thu Jan 16 22:06:35 2025 From: Anchi.Zhang at nrg.com (Zhang, Anchi) Date: Thu, 16 Jan 2025 22:06:35 +0000 Subject: [rancid] rancid -d -t fxos seems to choke on "connect fxos" on Multi-Instance FTD Application. In-Reply-To: References: Message-ID: > -----Original Message----- > From: heasley > Sent: Thursday, January 16, 2025 12:12 PM > To: Zhang, Anchi > Cc: heasley ; rancid-discuss at www.shrubbery.net > Subject: Re: [rancid] rancid -d -t fxos seems to choke on "connect fxos" on > Multi-Instance FTD Application. > > CAUTION: This email originated from outside of the organization. Do not click > links or open attachments unless you recognize the sender and know the > content is safe. > > Wed, Jan 15, 2025 at 09:10:52PM +0000, Zhang, Anchi: > > Thank you for your reply. I modified rancid.types.base as below then all was > good. We do not need the fxos info archived anyway. > > > > sky-log1% grep "fxos;command" rancid.types.base > > fxos;command;fxos::ShowModel;show model > > fxos;command;fxos::ShowInventory;show inventory > > fxos;command;fxos::DirSlotN;dir /all fxos;command;fxos::ShowMode;show > > mode fxos;command;fxos::ShowManagers;show managers > > fxos;command;fxos::ShowNetwork;show network > > fxos;command;fxos::ShowNetwork;show network-static-routes > > fxos;command;fxos::ShowNetwork;show network-dhcp-server > > #fxos;command;fxos::WriteTermFTD;show running-config > > #fxos;command;fxos::RunCommand;connect fxos; prompt changes > > #fxos;command;fxos::RunCommand;term len 0 > > #fxos;command;fxos::ShowFirmware;show system firmware detail > > #fxos;command;fxos::ShowChassis;show chassis detail > > #fxos;command;fxos::ShowChassis;show chassis inventory detail > > #fxos;command;fxos::ShowChassis;show chassis environment expand detail > > #fxos;command;fxos::WriteTerm;show configuration > > fxos;command;fxos::WriteTerm;show running-config > > Great, but that does not help me fix the problem for others. Could someone > address my questions that are below? > > > From: heasley > > Sent: Wednesday, January 15, 2025 2:35 PM > > To: Zhang, Anchi > > > > > > 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? No. All Multi-Instance FTD deployments of ours experience the same. > > 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? Yes. connect fxos would work on single instance FTD. > Is there > another way to connect to the parent in the multi-instance environment? Yes. by direct ssh to the chassis fxos IP. sky-log1% grep sky-www-ftd-m /etc/hosts 10.141.3.48 sky-www-ftd-m # FJC274814ET sky-log1% fxlogin sky-www-ftd-m sky-www-ftd-m spawn ssh -c aes256-ctr -x -l admin sky-www-ftd-m admin at sky-www-ftd-m's password: Last login: Thu Jan 16 22:01:35 UTC 2025 from 10.141.3.229 on pts/0 Successful login attempts for user 'admin' : 4 Last login: Thu Jan 16 22:02:08 2025 from 10.141.3.229 Cisco Firepower Extensible Operating System (FX-OS) Software TAC support: http://www.cisco.com/tac Copyright (c) 2009-2019, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained in this software are owned by other third parties and used and distributed under license. Certain components of this software are licensed under the "GNU General Public License, version 3" provided with ABSOLUTELY NO WARRANTY under the terms of "GNU General Public License, Version 3", available here: http://www.gnu.org/licenses/gpl.html. See User Manual (''Licensing'') for details. Certain components of this software are licensed under the "GNU General Public License, version 2" provided with ABSOLUTELY NO WARRANTY under the terms of "GNU General Public License, version 2", available here: http://www.gnu.org/licenses/old-licenses/gpl-2.0.html. See User Manual (''Licensing'') for details. Certain components of this software are licensed under the "GNU LESSER GENERAL PUBLIC LICENSE, version 3" provided with ABSOLUTELY NO WARRANTY under the terms of "GNU LESSER GENERAL PUBLIC LICENSE" Version 3", available here: http://www.gnu.org/licenses/lgpl.html. See User Manual (''Licensing'') for details. Certain components of this software are licensed under the "GNU Lesser General Public License, version 2.1" provided with ABSOLUTELY NO WARRANTY under the terms of "GNU Lesser General Public License, version 2", available here: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html. See User Manual (''Licensing'') for details. Certain components of this software are licensed under the "GNU Library General Public License, version 2" provided with ABSOLUTELY NO WARRANTY under the terms of "GNU Library General Public License, version 2", available here: http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html. See User Manual (''Licensing'') for details. firepower-3110# sho configuration | in 10.141.3.48 set virtual-ip 10.141.3.48 set out-of-band static ip 10.141.3.48 netmask 255.255.255.0 gw 10.141.3.1 From randy at psg.com Thu Jan 16 22:53:19 2025 From: randy at psg.com (Randy Bush) Date: Thu, 16 Jan 2025 14:53:19 -0800 Subject: [rancid] FRR on debian Message-ID: anyone have rancid scraping debian and frr? randy