cancel
Showing results for 
Search instead for 
Did you mean: 

SAN Client: Support for different kernel versions on Linux Fibre Transport Media servers

karentv11
Level 3

Hi all,

I am currently going through the Veritas procedure to configuring SAN client and Fibre Transport mode. I need to start nbhba mode on Linux and use the command:

/usr/openv/netbackup/bin/admincmd/nbftsrv_config -nbhba
 

When I use this command, I get the error: "kernel is unknown or not supported, exiting."

From this article, I saw that there were other supported kernel versions: https://www.veritas.com/support/en_US/article.100021571

The problem is that there doesn't seem to be any support for Red Hat Enterprise Linux 8 kernels, which is the kernel that my RHEL 8 backup host is using:

karentv11_0-1624656372690.png

I tried to create a symbolic link for the "closest version" kernel, but it says in the guide: "It should be noted that the first three dot separated numbers, such as 2.6.9 or 2.6.16, must match. ", so this will not work.  

Does anyone have a workaround for this issue?

 

1 ACCEPTED SOLUTION

Accepted Solutions

davidmoline
Level 6
Employee

Hi @karentv11 

Yes - use a backup host with a supported operating system as per the HCL (i.e. use RHEL 7).

I can say that support for RHEL 8 (and SUSE 15) is in the works, but I am unable to say when this support might be available. 

David

View solution in original post

2 REPLIES 2

davidmoline
Level 6
Employee

Hi @karentv11 

Yes - use a backup host with a supported operating system as per the HCL (i.e. use RHEL 7).

I can say that support for RHEL 8 (and SUSE 15) is in the works, but I am unable to say when this support might be available. 

David

rasulk
Level 1

I have same problem

Netbackup version: 9.0.0.1

 

[root@computer admincmd]# ./nbftsrv_config -nbhba
Unsupported kernel revision: 4.18.0-305.3.1.el8_4.x86_64

[root@computer driver]# ls -l
total 12060
-rw-r--r--. 1 root root 3372616 Mar 30 14:01 lancerg6_A12.8.340.8.grp
-r-xr--r--. 1 root bin 396016 Mar 30 14:01 ql2300_stub.ko.2.6.18-128.el5
-r-xr--r--. 1 root bin 396016 Mar 30 14:01 ql2300_stub.ko.2.6.18-164.el5
-r-xr--r--. 1 root bin 396016 Mar 30 14:01 ql2300_stub.ko.2.6.18-194.el5
-r-xr--r--. 1 root bin 396392 Mar 30 14:01 ql2300_stub.ko.2.6.18-8.el5
-r-xr--r--. 1 root bin 396248 Mar 30 14:01 ql2300_stub.ko.2.6.18-92.el5
-r-xr--r--. 1 root bin 487608 Mar 30 14:01 ql2300_stub.ko.2.6.32-71.el6.x86_64
-r-xr--r--. 1 root bin 345259 Mar 30 14:01 ql2300_stub.ko.2.6.9-55.ELsmp
-r-xr--r--. 1 root bin 547281 Mar 30 14:01 ql2300_stub.ko.3.10.0-123.el7.x86_64
lrwxrwxrwx. 1 root root 36 Mar 29 12:13 ql2300_stub.ko.4.18.0-305.3.1.el8_4.x86_64 -> ql2300_stub.ko.3.10.0-123.el7.x86_64
-r-xr--r--. 1 root bin 212744 Mar 30 14:01 ql2500-firmware-8.04.00.bin
-r-xr--r--. 1 root bin 1837 Mar 30 14:01 ql2500-firmware-8.04.00-LICENSE
-r-xr--r--. 1 root bin 404692 Mar 30 14:01 ql2700-firmware-8.07.10.bin
drwxr-xr-x. 2 root bin 4096 Mar 30 14:01 scst
-r-xr--r--. 1 root bin 349860 Mar 30 14:01 windrvr6.ko.2.6.18-128.el5
-r-xr--r--. 1 root bin 349860 Mar 30 14:01 windrvr6.ko.2.6.18-164.el5
-r-xr--r--. 1 root bin 349860 Mar 30 14:01 windrvr6.ko.2.6.18-194.el5
-r-xr--r--. 1 root bin 349860 Mar 30 14:01 windrvr6.ko.2.6.18-8.el5
-r-xr--r--. 1 root bin 349860 Mar 30 14:01 windrvr6.ko.2.6.18-92.el5
-r-xr--r--. 1 root bin 849514 Mar 30 14:01 windrvr6.ko.2.6.32-71.el6.x86_64
-r-xr--r--. 1 root bin 317798 Mar 30 14:01 windrvr6.ko.2.6.9-34.ELsmp
-r-xr--r--. 1 root bin 319674 Mar 30 14:01 windrvr6.ko.2.6.9-55.ELsmp
-r-xr--r--. 1 root bin 887051 Mar 30 14:01 windrvr6.ko.3.10.0-123.el7.x86_64
-r-xr--r--. 1 root bin 824352 Mar 30 14:01 windrvr6.ko.3.10.0-862.el7.x86_64
lrwxrwxrwx. 1 root root 33 Mar 29 12:14 windrvr6.ko.4.18.0-305.3.1.el8_4.x86_64 -> windrvr6.ko.3.10.0-862.el7.x86_64