Visco VIRL sometimes throw the following error stating KVM acceleration is not available on hosts running ESXi. KVM acceleration is not available INFO: Your CPU does not support KVM extensions KVM acceleration can NOT be used You can also run the kvm-ok command to find the status of KVM accleration. This is due to a missing setting on ESXi Guest OS and the following parameter needs to be added VM’s .VMX configuration file. Please make sure the VM is shut down before making the change. vhv.enable = “TRUE” You can also add this parameter to /etc/vmware/config of the host, but it is not imperative you should do it.
Like IPv4 Address space depletion, the 2-Byte (16 bit) BGP AS number is also running out. As per RFC4893 (BGP Support for Four-octet AS Number Space) 4-Byte Autonomous Systems (AS) numbers have been issued by the Regional Internet Registry (RIR).
2-Byte (16 Bit) Autonomous System Numbers
We have a total of 216 = 65536 Possible AS Numbers
Private AS Numbers: 64512 – 65534
Reserved AS Numbers: 59392 – 64511, 65535
4-Byte (16 Bit) Autonomous System Numbers
We have a total of 232 = 4,294,967,296 Possible AS Numbers
Any numbers ranging from 65536 to 4294967295 are considered 32Bit AS Numbers.
This is the IETF preferred notation of AS Numbers, where a 2-Byte AS Number such as 65535 is represented in the form of text in both command and CLI. Where a 4-Byte As number such as 65546 will be represented in the form of “65546”
As mentioned above, the ASDOT notation for the 2-Byte AS Numbers are represented in decimal format.
4-Byte AS Numbers is represented in the following format.