| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
The bsr installation package is available has packages for Windows and Linux. For Linux, CentOS (RHEL, and for Linux it is distributed as an rpm package for RHEL (CentOS) 6.4 or higher rpm , a deb package and for Ubuntu 16.04 LTS or higher deb package are distributed, and a SUSE package. To obtain the an installation package, please contact Mantech Technology Research Institute (dev3@mantechbsr@mantech.co.kr).
| Note |
|---|
...
caution If bsr |
...
is installed and operated together with drbd |
...
, conflicts related to system resource use may occur. If drbd was previously installed on your system, you |
...
must uninstall it. |
Windows
...
Install
You can easily install it by running the installer for Windows and following the steps in guided by the installation wizard. After Once installation is complete, you will need to reboot restart your system.
...
Install Path
When the Once installation is completed successfully, the directory is will be configured as shown below.
bin
...
Binary executable files and script (bsrsupport, etc.) files, including the bsr service, are located here.
etc
...
Configuration file path.
jre
Path to the Java runtime
...
for the installation package.
...
log
Path to the bsr
...
log file.
| Info |
|---|
Windows ' bsr uses local TCP loopback ports 5678 and 5679 internally to perform TCP loopback communicationfor netlink and service purposes. To change this default port, you need to must change the key value in the following registry path and restart the system.
|
Load
The Windows bsr kernel module is automatically loaded when the OS kernel is loaded.
Service Config.
Automatically configured by the bsr installation package.
Uninstall
Uninstall it from Programs and Features in Control Panel. You must restart the system after uninstall.
Update
Updating is the process of deleting an old version of a program and then installing a new version of the program.
If you reinstall a new version of a the package while BSR bsr is installed, the update installation is performed automatically.
| Info |
|---|
Re-installing the existing version by deleting it from the program and function of the control panel can be cumbersome since rebooting is required after deletion. It is not recommended to update after deleting from the control panel. |
Delete
Deleting bsr can delete the bsr package from Programs and Features in Control Panel. The machine needs to be rebooted after deletion.
infowill be installed automatically. You must restart your system after updating.
| Note |
|---|
You can delete the program from the Control Panel and then reinstall it, but you must restart the system after uninstalling. If you immediately reinstall the program without restarting, a system crash may occur due to abnormal installation. Please note this. |
| Note |
|---|
LAN card replacement If the network LAN card is replaced after installing bsr |
...
, you must manually reapply the contents of Disable TCP Delayed ACK |
...
using the bsrcon /nodelayedack <resource> command. Failure to do so may result in performance degradation. |
RHEL
Kernel package compatibility
Linux
Linux distributes kernel modules and utility packages separately, so each must be installed individually and bsr services must be configured separately.
...
Secure boot support
...
Unlike Windows' ABI upward compatibility policy, in Linux, certain versions of Linux kernel packages are generally not compatible with higher kernel versions. Because new features and improvements are incompatible with each kernel version, installing kernel packages from older versions may cause compatibility issues. Even if the package is accidentally installed on a higher version kernel, serious problems such as kernel panic may occur during operation.
Likewise, unless specifically specified, bsr does not guarantee compatibility of lower version packages with higher kernels, and must be installed as a dedicated version of the bsr package built for a specific kernel version.
Install
Utility
| Info |
|---|
[root@bsr-01 x86_64]# rpm -ivh bsr-utils-1.6-A3.el7.x86_64.rpm |
Kernel module
| Info |
|---|
[root@bsr-01 bsr]# rpm -ivh kmod-bsr-1.6_3.10.0_957-A3.el7.x86_64.rpm |
Installing bsr kernel modules does not require a system restart.
Secure boot
If you are not considering configuring Secure Boot, skip this step.
During the kernel module installation process, the public key is installed in the /etc/pki/mantech/
...
path. To register (enroll) the public key in the UEFI console, first request registration (import) as follows.
| Info |
|---|
#mokutil --import /etc/pki/mantech/bsr_signing_key_pub.der input password: input password again: The password can be freely selected and will be applied after reboot. |
Installation
Kernel Module
...
Reboot after specifying the password. Enroll the public key in the UEFI console at reboot time.
Install path
/usr/sbin/
Binary executable files (bsradm, bsrcon, bsrmeta, bsrmon, bsrsetup, bsrsupport, bsrwatch) are located here.
/usr/lib/bsr/
Path to the script file (bsr service, notify).
/etc/bsr.d/
Path to the configuration file.
/var/log/bsr/
Path to the bsr log.
/usr/lib/modules/{kernel-version}.{version}.x86_64/extra/bsr/
Path to the bsr.ko module file.
Load
Load the bsr kernel module.
| Info |
|---|
# modprobe bsr # lsmod |grep bsr bsr 52113408 0 libcrc32c 16384 4 nf_conntrack,nf_nat,bsr,xfs |
| Info |
|---|
[root@bsr-01 bsr]# modinfo bsr [root@bsr-01 x86_64]# bsradm -V |
| Note |
|---|
If you fail to load the kernel module related to Secure Boot, refer to this link and proceed with the Secure Boot code signing process step by step. |
Service config.
To automatically start up the bsr resource whenever the system starts, you must enable the bsr service and configure the svc-auto-up option. The default value of svc-auto-up is yes.
RHEL 6
chkconfig bsr on
service bsr start
RHEL 7 or Ubuntu
systemctl enable bsr
systemctl start bsr
| Code Block |
|---|
resource r0 {
...
on hostname {
options {
svc-auto-up yes;
}
}
...
} |
Uninstall
Uninstall goes through the following process.
stop resource
service stop
Delete kernel module
delete utility
| Info |
|---|
bsradm down all systemctl stop bsr rpm -e kmod-bsr rpm -e bsr-utils |
Update
Updating involves deleting the already installed version and reinstalling it with a new version.
First, delete the product and then perform the following update processes in order.
Utility
| Info |
|---|
[root@bsr-01 bsr]# rpm -Uvh bsr-utils-1.6-A4.el7.x86_64.rpm |
Kernel module
| Info |
|---|
[root@bsr-01 bsr]# rpm -ivh Uvh kmod-bsr-1.6_3.10.0_957-A3A4.el7.x86_64.rpm |
Secure boot
This step only applies if Secure Boot is configured.
If the existing bsr module public key has already been registered, no update is required.
If the private key and public key for Secure Boot have been updated, you must perform the Secure Boot setup process again.
Ubuntu
Install
Required Package
The Ubuntu package uses Dynamic Kernel Module Support (DKMS), and the following package installation is required for thiswhich requires installation of the packages below.
| Info |
|---|
root@ubuntu:/home/mantech# apt-get install git build-essential debhelper dkms docbook-xsl help2man python-all python-dbus python-gobject dh-systemd flex autoconf automake |
...
Depending on the OS version, an error may occur because certain packages are not provided.
E: Package 'python-dbus' has no installation candidate
E: Unable to locate package python-gobject
E: Unable to locate package dh-systemd
Retry the installation, excluding the packages causing the error.
root@ubuntu:/home/mantech# apt-get install git build-essential debhelper dkms docbook-xsl help2man python-all flex autoconf automake
Utility
| Info |
|---|
root@ubuntu:/home/mantech# dpkg -i bsr-utils_1.6-A3_amd64.deb |
Kernel module
| Info |
|---|
root@ubuntu:/home/mantech# dpkg -i bsr-dkms_1.6-A3_all.deb |
If the installation fails due to a dependency problemissues, you can use resolve the dependency issues using the command below to solve the dependency problem and retryand try again.
| Info |
|---|
root@ubuntu:/home/mantech# apt-get -f -y install |
Utility
...
Installing the bsr kernel module does not require a system restart.
Secure boot
The dkms package automatically creates MOK and signs codes for third-party drivers in the final stage of installation.
If you are not considering configuring Secure Boot, skip this step.
The following screen is displayed during module installation to register the generated public key.
...
After selecting OK, enter the password to be used for MOK registration.
...
After rebooting the system, enter the UEFI console and register the public key to the system.
...
| Info |
|---|
|
Install path
/usr/sbin/
Binary executable files (bsradm, bsrcon, bsrmeta, bsrmon, bsrsetup, bsrsupport, bsrwatch) are located here.
/usr/lib/bsr/
Path to the script file (bsr service, notify).
/etc/bsr.d/
Path to the configuration file.
/var/log/bsr/
Path to the bsr log.
/usr/lib/modules/{kernel-version}-generic/updates/dkms/
Path to the bsr.ko module file.
Load
Load the bsr kernel module.
| Info |
|---|
# modprobe bsr # lsmod |grep bsr bsr 52113408 0 libcrc32c 16384 4 nf_conntrack,nf_nat,bsr,xfs |
| Info |
|---|
[root@bsr-01 x86_64]# rpm -ivh bsr-utils-bsr]# modinfo bsr |
Ubuntu
| Info |
|---|
root@ubuntu:/home/mantech# dpkg -i bsr-utils_1.6-A3_amd64.deb |
Load
Load the bsr module.
| Info |
|---|
[root@bsr-01 bsr]# modprobe bsr |
...
SMP mod_unload modversions [root@bsr-01 x86_64]# bsradm -V |
| Note |
|---|
If you fail to load the kernel module related to Secure Boot, refer to this link and proceed with the Secure Boot code signing process step by step. |
Service config.
If you want bsr to always start automatically at when the system startupstarts, you should configure must enable the bsr service and configure the svc-auto-up option. The default for value of svc-auto-up is yes.
...
CentOS 6
chkconfig bsr on
service bsr start
CentOS 7
| Info |
|---|
systemctl enable bsr systemctl start bsr |
| Code Block |
|---|
resource r0 {
...
on hostname {
options {
svc-auto-up yes;
}
}
...
} |
Information
After installation, check whether the installation is normal through module information.
Uninstall
Uninstall goes through the following process.
stop resource
service stop
delete kernel module
delete utility
| Info |
|---|
bsradm down all systemctl stop bsr dpkg -r bsr-dkms dpkg -r bsr-utils |
Update
Updating involves deleting the already installed version and reinstalling it with a new version.
First, Uninstall the product and then perform the following update processes in order.
Utility
| Info |
|---|
root@ubuntu:/home/mantech# dpkg -i bsr-utils_1.6-A4_amd64.deb |
Kernel module
| Info |
|---|
root@ubuntu:/home/mantech# dpkg -i bsr-dkms_1.6-A4_all.deb |
Secure boot
This step only applies if Secure Boot is configured.
If the existing bsr module public key has already been registered, no update is required.
If the private key and public key for Secure Boot have been updated, you must perform the Secure Boot setup process again.
SUSE
Install
Utility
| Info |
|---|
# rpm -ivh bsr-utils-1.6.5.1_sles12-sp4_20230621151754.rpm |
Kernel module
| Info |
|---|
# rpm -ivh bsr-kmp-default-1.6.5.1_sles12-sp4_4.12.14-94.41_20230621151754.rpm |
| Note |
|---|
Signature verification failed may occur when using the zypper command, select ignore and proceed with installation. # zypper install bsr-kmp-default-1.6.5.1_sles12-sp4_4.12.14-94.41_20230621151754.rpm … bsr-kmp-default-1.6.5.1_k4.12.14_94.41-1.x86_64 (Plain RPM files cache): Signature verification failed [6-File is unsigned] |
Installing the bsr kernel module does not require a system restart.
Secure boot
If you are not considering configuring Secure Boot, skip this step.
During the kernel module installation process, the public key is installed in the /etc/pki/mantech/ path. To register (enroll) the public key in the UEFI console, first request registration (import) as follows.
| Info |
|---|
#mokutil --import /etc/pki/mantech/bsr_signing_key_pub.der input password: input password again: |
Reboot after specifying the password. Enroll the public key in the UEFI console when rebooting begins.
Install path
/usr/sbin/
Binary executable files (bsradm, bsrcon, bsrmeta, bsrmon, bsrsetup, bsrsupport, bsrwatch) are located here.
/usr/lib/bsr/
Path to the script file (bsr service, notify).
/etc/bsr.d/
Path to the configuration file.
/var/log/bsr/
Path to the bsr log.
/lib/modules/{kernel-version}-default/updates/
Path to the bsr.ko module file.
Load
Load the bsr kernel module.
| Info |
|---|
# modprobe bsr # lsmod |grep bsr bsr 52113408 0 libcrc32c 16384 4 nf_conntrack,nf_nat,bsr,xfs |
| Note |
|---|
Because SUSE restricts the loading of modules without the supported flag, loading the bsr module basically fails. # modprobe bsr modprobe: ERROR: module 'bsr' is unsupported To allow loading of unsupported modules, use the --allow-unsupported option when running modprobe. # modprobe bsr --allow-unsupported |
| Info |
|---|
[root@bsr-01 bsr]# modinfo bsr [root@bsr-01 x86_64]# bsradm -V |
Update
Remove Old Version
Service stop
Delete kernel module
Delete utility
Kernel Module
CentOS
| Info |
|---|
[root@bsr-01 bsr]# rpm -Uvh kmod-bsr-1.6_3.10.0_957-A4.el7.x86_64.rpm |
Ubuntu
| Info |
|---|
root@ubuntu:/home/mantech# dpkg -i bsr-dkms_1.6-A4_all.deb |
Utility
CentOS
| Info |
|---|
| Note |
If you fail to load the kernel module related to Secure Boot, refer to the Kernel Module Packages Manual and proceed with the Secure Boot code signing process step by step. |
Service config.
If you want bsr to always start automatically when the system starts, you must enable the bsr service and configure the svc-auto-up option. The default value of svc-auto-up is yes.
| Info |
|---|
systemctl enable bsr systemctl start bsr |
| Code Block |
|---|
resource r0 {
...
on hostname {
options {
svc-auto-up yes;
}
}
...
} |
Uninstall
Uninstall goes through the following process.
stop resource
service stop
delete kernel module
delete utility
| Info |
|---|
bsradm down all systemctl stop bsr rpm -e bsr-kmp-default rpm -e bsr-utils |
Update
Updating involves deleting the already installed version and reinstalling it with a new version.
First, Uninstall the product and then perform the following update processes in order.
Utility
| Info |
|---|
# rpm -ivh bsr-utils-1.6-A4.el7.x86_645.1_sles12-sp4_20230621151754.rpm |
...
Kernel module
| Info |
|---|
root@ubuntu:/home/mantech# dpkg -i bsr-utils_# rpm -ivh bsr-kmp-default-1.6-A4_amd64.deb |
Delete
CentOS
| Info |
|---|
rpm -e kmod-bsr rpm -e bsr-utils |
Ubuntu
| Info |
|---|
dpkg -r bsr-dkms dpkg -r bsr-utils.5.1_sles12-sp4_4.12.14-94.41_20230621151754.rpm |
Secure boot
This step only applies if Secure Boot is configured.
If the existing bsr module public key has already been registered, no update is required.
If the private key and public key for Secure Boot have been updated, you must perform the Secure Boot setup process again.