cancel
Showing results for 
Search instead for 
Did you mean: 

Big-IP not recognized by Big-IQ

Dexter
Altostratus
Altostratus

Dear Techs,

 

I'm in a strange situation where I'm supposed to add both F5 Big-IP with Big-IQ. Both Big-IP and Big-IQ are in same subnet, so firewall isn't a question.

 

The Big-IP are in HA. I've successfully added the Standby unit with Big-IQ without any issues while adding the Active unit I'm getting below error message :

 

The device <Big-IP-Management-IP> (null) is not a Big-IP device.

 

I've added a total of 7 devices successfully, using the same procedure, same authentication. Any help with be greatly appreciated.

 

Big IQ version : 8.0.0

Big-IP version : 14.1.4

 

thank you

16 REPLIES 16

Dexter
Altostratus
Altostratus

Any idea guys?​

Lidev
MVP
MVP

Hi Dexter,

 

This K article below helped me a lot to solve this kind of discovery problem.

K16307: Troubleshooting BIG-IQ device discovery failures

 

Hope it's help

Regards

 

Dexter
Altostratus
Altostratus

Thank you dear. I did read the document before but sadly couldn't find my answer there. At first, i thought to update the REST API but since the document says its not applicable if version is 12.x and above, i believe i still have to hunt for the solution.

Connectivty test are ok between BIG-IP and BIG-IQ ? what does the restjavad says on the BIG-IQ ?

haven't check that yet, but i do remember if I goto monitoring tab and under events (i believe) where it says start/fail :

 

start : nothing is visible there

fail : the other product is not big-ip

OK, the first step to debug this problem is to verify TCP communication between BIG-IQ and BIG-IP systems.

The communication are open as they are in same subnet and the secondary appliance is easily added under big-iq.

Can you tell me how to get the debug logs from cli while adding the primary box. May be there's something I'm missing that can be revealed via debug.​

sure, connect to the BIG-IQ in SSH and check theses logs when you try to discover BIG-IP :

/var/log/icrd

/var/log/restjavad.0.log

/var/log/restjavad-audit.0.log

 

K articles will be also help :

K15436: Configuring the verbosity for restjavad logs on the BIG-IP system

K22244445: Enabling debug logging for restjavad in BIG-IQ

 

regards

Thank you so much bro. Let me run these and get back to you with an update since the site is remote.​

The onl​y log that posted something while big-iq was trying to connect with big IP was restjavad.0.log :

[/Shared/framework-info-tasks FrameworkInfoTaskCollectionWorker] FrameworkInfo device <big-ip address> started.

The device <big-ip address> (null) is not a big-ip device

Dexter
Altostratus
Altostratus

One thing more, the big ip we want to add have it's device certificate expire. Is this can be the reason? Also what are the impacts of renewing the device liecense, I believe the HA will break right?​

Didn't know but in all cases it's necessary to renew this device certificate to restore iQuery communication and Trusted Device Certificate between the cluster. Maybe it will allow the BIG-IQ to discover it.

 

K16951115: Changing the BIG-IP system device certificate using the Configuration utility

 

why do you want to renew the licence ?

Sorry not license, I meant device certificate. Does renewing device certificate breaks/interrupts HA or production traffic?​

I don't think so but I've never tested it, so to be safe, plan the change during maintenance window.

 

Regards

JamesCrk
Nimbostratus
Nimbostratus

did you get this resolved? exact same issue here

So I also just had the same issue. On a whim I restarted restjavad on the the BigIP (not the BigIQ) with # tmsh restart sys service restjavad

After doing this the BigIQ was able to add the device. Hopefully this works for others as well.