Forum Discussion
Altocumuluscommand clsh cpcfg on tenant velos
Hi
i want to upgrade tenant on velos, is it possible to used clsh cpcfg ?
as i know clsh for viprion only
f51Cumulonimbus
I sometimes use ChatGPT for my learning purposes. With these questions, I’m doing some research from my own background. I’m not sure if there’s anything wrong with this.
And I am trying to answer for "i want to upgrade tenant on velos, is it possible to used clsh cpcfg ? as i know clsh for viprion only"We’re using VELOS, and I’ve never used the cpfg command on those devices before. Any tips or tricks you can share would be awesome!
My answer is here
You are correct. The clsh command is traditionally used in VIPRION systems for cluster-wide operations. The cpcfg subcommand within clsh is specifically designed to copy configuration files across blades in a VIPRION chassis. However, Velos systems operate differently compared to VIPRION, as they are based on a different architecture and management model.
Here’s the link for the upgrade. I’d love to use the GUI version if possible.
- LiefZimmerman
Admin
Nikoolayy1 thanks for checking.
There may have been a short period of time where you saw dupes because IIRC there were some replies caught in SPAM and confusion led f51 to repost. When I released them they all dropped at once.--
f51 - using LLM tools (like ChatGPT) can be helpful but per our DevCentral Community Guidelines please indicate if/when you are providing a reply with LLM generated content.
For example:- [the following is AI generated content that I have edited]
or - [AI Gen assist content that I have not fully checked for accuracy]
- [the following is AI generated content that I have edited]
- f51
You are correct. The clsh command is traditionally used in VIPRION systems for cluster-wide operations. The cpcfg subcommand within clsh is specifically designed to copy configuration files across blades in a VIPRION chassis. However, Velos systems operate differently compared to VIPRION, as they are based on a different architecture and management model.
Here’s the link for the upgrade. I’d love to use the GUI version if possible.
https://techdocs.f5.com/en-us/velos-1-2-0/velos-systems-installation-upgrade/title-install-upgrade-software.html
- Nikoolayy1
MVP
f51 Are you an AI agent? 😀
Edit: I could be wrong but I think for my previous comment I saw the same reply like the first one but I don't see it anymore or I got confused and thought there is an AI automation in place.
- Nikoolayy1
f51 What you have provided him is for the chassis and partition upgrade and initial tenant installation. Anzine321 I suggested logging in the CLI of the tenant as for the tenants the architectural difference is not so important between Velos or Virprion as the tenants in Velos select a Primary Blade like I already mentioned and just checking as this is the most certain way to check this as I today simply logged in a tenant and "clsh" is there.
For the "Install Configuration option" F5 has documented this well enough Should I use Install Configuration when activating a new Boot Location? as if you are using the GUI, that will copy the config but by default you shouldn't even need this.
Anzine321Hi
thanks for advie
upgrade from GUI and Install Configuration option yes,
is it same as command clsh cpcfg ?
- f51
No, the clsh cpcfg command is not the same as the commands or procedures used for upgrading tenants on VELOS.
- Nikoolayy1
Hi , Have you checked that "clsh" really is not present on the tenant's CLI by logging into it and going into bash mode?
The tenants on Velos that are classical BIG-IP are like vCMP quests with a selected primary blade from the blade cluster etc. For NEXT it is different as it is just extra pods inside the Velos k8s system but no need to go there 🙂
For the controller and partition CLI even in bash mode I agree that this is the case as now there are 2 controllers and not a Primary blade like with Viprion but you can ssh to different blades as workaround Overview of access to the F5 VELOS system .
For your case as Velos last I checked still does not support upgrade of tenants from the HOST/partition you need to do it from the tenant and you can just see if clsh is present in the tenant CLI bash.
