- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- Hyperthreading on VSX R80.10
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hyperthreading on VSX R80.10
I have upgraded one of my R77.30 VSX (VSLS) cluster to R80.10 using the CDT method. This cluster has 4 nodes.
The upgrade went fine but later I discovered that now Hyperthreading is ON. Before upgrade all Gateways have the status of SMT Soft disable. The gateways were showing 24 cores, now after the upgrade the SMT status is ON and I can see 48 cores.
I am trying to find out if this is a bug and if anyone else has experienced this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We didn't use CDT but "regular" CPUSE on gateways and that kept SMT off as before upgrade. That's on 15600 cluster. What's your HW?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
23800
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Really strange. Cant see how it would do it as it would screw up whole CoreXL set-up and failover between old and new wouldn't be seemless. But again - I never played with CDT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
CDT, only used once, is an automated way of upgrade.
For your upgrade did you follow an SK article?
Was there any downtime?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As said, we used CPUSE from command line (installer command set) since it's VSX and webui is not available.
In nutshell, update gateway object version in mgmt to R80.10 using vsx_util first, then use installer commands to update standby member, fail over and update other member using installer commands. Obviously I have skipped all the backups you should do before you start.
