| Table of Contents |
|---|
The bsr installation package has packages are available for Windows and Linux, separated into rpm packages for CentOS (RHELand for Linux it is distributed as an rpm package for RHEL (CentOS) 6.4 and later and deb packages or higher, a deb package for Ubuntu 16.04 LTS and lateror higher, and a SUSE package. To obtain the an installation packagespackage, please contact Mantech Technical Lab.Technology Research Institute (bsr@mantech.co.kr).
| Note |
|---|
Cautions BSR conflicts with DRBD for system resource usage when caution If bsr is installed and operated together with drbd, conflicts related to system resource use may occur. If DRBD drbd was previously installed on your system, you must uninstall it should be removed. |
Windows
...
Installation
You can easily install it by running the installer for Windows and following the steps guided by the installation wizard. Once the installation is complete, you 'll will need to reboot restart your system.
Install
...
Path
After a successful installationOnce installation is completed successfully, the directory will be organized configured as shown below.
bin
The location of the binary programs that make up BSRBinary executable files and script (bsrsupport, etc.) files, including the bsr service, are located here.
etc
The path to the configuration filesConfiguration file path.
jre
The path Path to the Java runtime environment for the installation package.
...
log
The path Path to the bsr service binary.The bsr service performs initialization tasks for performing replication. Careful control of the service is required because replication can be interrupted if the service is interrupted.log file.
| Info |
|---|
Windows bsr uses TCP loopback ports 5678 and 5679 for netlinks netlink and servicesservice purposes. To change these portsthis port, you must change the key value of the key in the following registry path and restart the system.Path
|
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 package with BSR the package while bsr is installed, the update installation is done will be installed automatically.
...
You must restart your system after updating.
| Note |
|---|
You can also reinstall delete the program after deleting it from the Control Panel and then reinstall it, but be sure to you must restart the system after deletionuninstalling. If you proceed directly to reinstalling immediately reinstall the program without restarting, you should be careful because the system crashes a system crash may occur due to abnormal installation. Please note this. |
Uninstall
You can delete the BSR package from Programs and Features in Control Panel. You must reboot the machine after deletion.
Replacing a NIC
...
| 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
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 added to incompatible with each kernel version, installing kernel packages from older versions of kernel packages may cause compatibility issues. Installation may not be possible, or even if installedEven 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 support guarantee compatibility of lower version packages with higher kernels unless specifically specified. That is, you must install , and must be installed as a dedicated version of the bsr package built for your 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 is disabled on your system, you don't need to set up Secure Boot.
...
, skip this step.
During the kernel module installation process, the public key is installed in the /etc/pki/mantech/ path during the kernel module installation process. In order to enroll that . To register (enroll) the public key in the UEFI console, we first request registration (import it ) as follows.
| Info |
|---|
#mokutil --import /etc/pki/mantech/bsr_signing_key_pub.der input password: input password again: |
Reboot after specifying the password. At reboot time, enroll Enroll the corresponding 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.
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.
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 -Uvh kmod-bsr-1.6_3.10.0_957-A4.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), which requires the installation of the following 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 issueissues, you can use resolve the dependency issues using the command below to resolve the dependency issue and try again.
| Info |
|---|
root@ubuntu:/home/mantech# apt-get -f -y install |
Installing the bsr kernel module does not require a system restart.
Secure
...
boot
The dkms package automatically generates MOKs and code signing creates MOK and signs codes for third-party drivers at in the end final stage of the installation.
If SecureBoot is disabled on your systemyou are not considering configuring Secure Boot, skip this step.
The following screen below is displayed during module installation to register the generated public key.
...
After selecting OK, enter the password that will to be used for MOK registration.
...
After rebooting the system, enter the UEFI console and register the public key with to the system.
...
| Info |
|---|
|
Module Load
...
|
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 bsr]# modinfo bsr [root@bsr-01 x86_64]# bsradm -V |
| Note |
|---|
If you fail to load the BSR kernel module fails related to loadSecure Boot, refer to the manual code signing process in the Secure Boot Signing in Ubuntu article to walk through the signing process this link and proceed with the Secure Boot code signing process step by step. |
Service
...
config.
If you want BSR bsr to always start up automatically when the system starts, you must enable the BSR 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
| Info |
|---|
systemctl enable bsr systemctl start bsr |
| Code Block |
|---|
resource r0 {
...
on hostname {
options {
svc-auto-up yes;
}
}
...
} |
Uninstall
Uninstalling Uninstall goes through the following process.
Stopping a Resource
Stop a service
Delete a stop resource
service stop
delete kernel module
Delete a delete utility
RHEL
| Info |
|---|
rpm -e kmod-bsr rpm -e bsr-utils |
Ubuntu
| Info |
|---|
bsradm down all systemctl stop bsr dpkg -r bsr-dkms dpkg -r bsr-utils |
Update
Updating is the act of involves deleting the version already installed version and reinstalling the it with a new version.
First, Uninstall the product is uninstalled, followed by and then perform the following update processprocesses in order.
Utility
...
| Info |
|---|
[root@bsr-01 bsr]# rpm -Uvh bsr-utils-root@ubuntu:/home/mantech# dpkg -i bsr-utils_1.6-A4.el7.x86_64amd64.rpmdeb |
...
Kernel module
| Info |
|---|
root@ubuntu:/home/mantech# dpkg -i bsr-utilsdkms_1.6-A4_amd64.deb |
Kernel Module Update
...
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]# rpm -Uvh kmod-bsr-1.6_modinfo bsr [root@bsr-01 x86_64]# bsradm -V |
| 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 |
Ubuntu
| Info |
|---|
root@ubuntu:/home/mantech# dpkg -i bsr-dkms_1.6-A4_all.deb |
Secure Boot
...
-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.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 |
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 code signing has Secure Boot have been updated, you will need to must perform the Secure Boot setup process described above again.