If the REST information is not shown in the GUI, the reception of REST messages can be checked in the BQN logging as root to the UNIX shell and executing the following command:
In this example, eno1is the management interface.
# tcpdump -i eno1 tcp and port 3443
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eno1, link-type EN10MB (Ethernet), capture size 65535 bytes
Check the one in your server going to Configuration->Interfaces->Management(remove the 0 added by BQN configuration, e.g., en0s1f0in the BQN GUI is ens1f0 in UNIX).
If the BQN firewall is configured (Configuration->Interfaces->Management Firewall), the IPs of all the REST clients must be added (in our example, 10.10.10.10 y10.10.10.11).
And now the messages are received:
# tcpdump -i eno1 'udp and port 1813’
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eno1, link-type EN10MB (Ethernet), capture size 65535 bytes
17:30:30.767149 IP 192.168.88.12.48316 > 192.168.88.13.ov-nnm-websrv: Flags [S], seq 639501187, win 64240, options [mss 1460,sackOK,TS val 3813494325 ecr 0,nop,wscale 7], length 0
17:30:30.767163 IP 192.168.88.13.ov-nnm-websrv > 192.168.88.12.48316: Flags [S.], seq 2135448282, ack 639501188, win 28960, options [mss 1460,sackOK,TS val 607264358 ecr 3813494325,nop,wscale 5], length 0
17:30:30.767260 IP 192.168.88.12.48316 > 192.168.88.13.ov-nnm-websrv: Flags [.], ack 1, win 502, options [nop,nop,TS val 3813494325 ecr 607264358], length 0
. . .
If the REST messages are not yet received, check the rest of traffic steps. In this example, the REST clients are in 10.10.10.0/24 and the BQN in 192.168.0.0/24. Check that there are valid routes between both subnets and that no intermediate firewall is blocking the TCP port 3443.
We are storing cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.
.svg)
