cOS Core 14.00 FAQ

Last modified on 22 Nov, 2021. Revision 20


FAQs

What appliances will be supported to run cOS Core 14.00?

The following existing models will support cOS Core 14.00

The new appliances introduced 2021 will only support cOS Core 14.00 or later:

Any appliance that is released after the release of cOS Core 14.00 will ONLY support cOS Core 14.00 or later.

Why will the new appliances only support cOS Core 14.00?

The new appliances will use a 64-bit version of cOS Core, this version is not possible to to downgrade to older versions as they are only available in 32-bit versions.

Is it difficult to upgrade from cOS Core 13.00 to 14.00?

No, it’s done in the same way as from 12.00 to 13.00 or upgrading from cOS Core 13.00.07 to 13.00.08. Remember to read the release notes for any version specific information.

Can the E or W-series appliances be upgraded to the 64-bit version of cOS Core 14.00?

No, appliances running the 32-bit firmware will not be possible to upgrade to the 64-bit version of cOS Core, also there is no real benefit as the E and W-series appliances are optimized for the 32-bit firmware.

What is the benefit of moving to 64-bit on the new appliances?

There are a number of benefits, mainly the possibility to use more memory, but also leverage new hardware features that is not available when using 32-bit.

Will there be differences between 32-bit and 64-bit cOS Core 14.00?

There is no visible difference between the two versions, except that the 64-bit version will be able to use more memory. Over a longer time period there might be diverging feature set on old appliances (running 32-bit) and new appliances (running 64-bit), where some features requiring 64-bit processing will only be available on newer appliances. But as long as possible Clavister will try to keep feature parity. There was a similar situtaion  with cOS Core 12.00 where some features did not work on IXP-based platforms (Clavister E5 and E7) due to hardware limitations. 

Is it complex to migrate from from a 32-bit appliances to a 64-bit appliance?

No, it’s not complex at all, it’s as easy as it was upgrading from Clavister E7 to Clavister NetWall E80.

How many vCPUs and memory does the different Virtual Appliances support?


32-bit Image (x86)64-bit Image (x86_64)64-bit Image (ARMv8)Comment
Number of vCPU Supported
1 vCPU
32-bit image: The image will run in interrupt mode.64-bit image: The image will can run in either interrupt mode or polling mode. 
2 vCPU
The image will run in polling mode.
3 vCPU

The image will run in polling mode and use one vCPU for interface offloading.
Recommended Memory
Min512 MB1 GB1 GBcOS Core and run with less memory if needed, but this is the recommended minimum for normal operation.
Max4 GB16 GB16 GB


What is the difference between interrupt and polling mode in Virtual Appliances?

The main difference between interrupt and polling is that in interrupt, the device notifies the CPU that it requires attention while, in polling, the CPU continuously checks the status of the devices to find whether they require attention. In brief, an interrupt is asynchronous whereas polling is synchronous. This means that when running polling mode the CPU load on the VM will always be 100%.

Which Virtual Appliance Image should I choose, 32-bit or 64-bit Virtual Appliance?

This depends on your need, if you need many small firewalls, using as little resources as possible you should select the 32-bit image, if you need high performance the 64-bit image with multiple vCPUs are abetter choice.

Related articles

Configure the Android OpenConnect client towards Clavister NetWall
5 Mar, 2021 sslvpn openconnect oneconnect android core
Using PCAP packet capture in cOS Core
21 Jun, 2021 core cli pcap netwall pcapdump
Problem with auto-created Core routes
22 Mar, 2021 core ipsec routing
A trusted webpage blocked by IP reputation
22 Jan, 2021 core ipreputation
Could not open outbound connection?
9 Mar, 2021 core ping connections
Configure Linux OpenConnect towards Clavister NetWall
5 Mar, 2021 sslvpn openconnect oneconnect linux core
Configuring SSL-VPN / OneConnect server on secondary Firewall IP address
8 Apr, 2021 core sslvpn oneconnect interfaces arp
Using Multicast DNS with cOS Core
24 May, 2021 core howto mdns multicast transparentmode airprint igmp dns
IPsec license usage calculation
14 Apr, 2021 core license ipsec
Does IPsecBeforeRules trigger before Access rules?
8 Sep, 2020 core ipsec rules access
Clavister SFP/SFP+ module compatibility
11 Apr, 2021 core sfp gbic hardware
Using Stateless Policies in cOS Core
16 Jun, 2021 core stateless rules netwall
NetWall virtual firewall creation under KVM on ARM
26 May, 2021 kvm core arm coscore netwall
Allowing Traceroute to and through cOS Core
15 Jan, 2021 core behaviour icmp ping traceroute
The meaning of the "Default_Access_Rule" log entry
25 Jan, 2021 brokenlink core arp log routing
How to setup a simple cloud-init environment for testing
30 Nov, 2020 howto core cloud-init dhcp
What is a "zombie" connection?
24 Mar, 2021 core connections
Assigning additional IPs to cOS Core Ethernet interfaces
7 May, 2021 core ethernet vlan arp garp
Allowing Path MTU discovery in cOS Core
9 Jul, 2021 core mtu netwall mtudiscovery
Freeing up more memory in the Firewall
18 Feb, 2021 core connections ipsec memory
Is Statless (FwdFast) faster than a normal IP policy?
27 Jan, 2021 core stateless routing brokenlink
Configure the OpenConnect-GUI client towards Clavister NetWall
5 Mar, 2021 sslvpn openconnect oneconnect macos windows linux core



Tags arm x86