| Table of Contents |
|---|
...
|
The bsr installation package 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.
설치 정보
설치가 성공적으로 완료되면 아래와 같이 디렉토리가 구성됩니다.
bin
BSR 을 구성하는 바이너리 프로그램들이 위치합니다.etc
구성 파일 경로 입니다.jre
설치 패키지를 위한 Java runtime environment 경로입니다.bsrservice
bsr service 바이너리의 경로입니다.
bsr service 는 복제 수행을 위한 초기화 작업을 수행합니다. 서비스가 중단 될 경우 복제가 중단될 수 있기 때문에 서비스 제어에 주의를 요합니다.
업데이트
BSR이 설치된 상태에서 신규 버전의 패키지를 재설치하면 업데이트 설치가 자동으로 수행됩니다.
기존 버전을 제어판의 프로그램 및 기능에서 삭제하여 재설치를 하는 방식은 삭제 후 리부팅이 필수이기 때문에 번거로울 수 있고, 만약 삭제 후 (실수로) 리부팅 없이 재설치를 하면 심각한 문제가 발생할 수 있으므로 주의를 요합니다. 제어판에서 삭제 후 업데이트를 하는 방식은 권장하지 않습니다.
삭제
BSR의 삭제는 제어판의 프로그램 및 기능에서 BSR 패키지를 삭제할 수 있습니다. 삭제 후 머신을 리부팅해야 합니다.
Linux
리눅스는 커널모듈과 유틸리티 패키지를 구분하여 배포하기 때문에 각각 개별적으로 설치해야 하고 BSR 서비스를 별도로 구성해야 합니다.
Installation
커널 모듈 설치
| Info |
|---|
[root@bsr-01 bsr]# rpm -ivh /root/rpmbuild/RPMS/x86_64/kmod-bsr-1.6.0_2.6.32_754.24.3-PREALPHA3.el6.x86_64.rpm |
유틸리티 설치
| Info |
|---|
[root@bsr-01 x86_64]# rpm -ivh /root/rpmbuild/RPMS/x86_64/bsr-utils-1.6.0-PREALPHA3.el6.x86_64.rpm |
적재
bsr 모듈을 적재 합니다.
| Info |
|---|
[root@bsr-01 bsr]# modprobe bsr |
서비스 구성
시스템이 시작될 때 항상 BSR 을 자동으로 기동 시키려면 BSR 서비스를 구성해 두어야 합니다.
...
Install Path
Once installation is completed successfully, the directory 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 TCP loopback ports 5678 and 5679 for netlink and service purposes. To change this port, you 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 the package while bsr is installed, the update will 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
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: |
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
CentOS 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 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 installation fails due to dependency issues, you can resolve the dependency issues using the command below 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 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 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.
| 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 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 |
삭제
다음은 BSR을 삭제하는 명령 예 입니다.
| Info |
|---|
rpm -e kmod-bsr rpm -e bsr-utils-A3 |
| 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.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 Secure Boot have been updated, you must perform the Secure Boot setup process again.