Follow

How to check BIG-IP access to Silverline for Hybrid Signaling

Description

  • How to check Outbound access to Silverline from the on-prem BIG-IP
    • destined for port 443 (HTTPS) to api.f5silverline.com.  
    • API calls (aka Signaling), are sent to: https://api.f5silverline.com/api/
  • This is a requirement for Hybrid Signaling as explained on Article 1 - How to Configure Hybrid Connector iApp

 

Environment

  • Silverline DDoS
  • Hybrid Signaling
    • Hybrid Connector
  • F5 BIG-IP
  • API

 

Procedure

Step 1: Determine TMOS Version

  • Use this command to determine TMOS version:
    • tmsh show /sys version
    • Output Example: Troubleshooting_-_TMOS_version.jpg

Why TMOS Version Matters

  • There are different commands depending on whether or not the Management Interface has been selected for Signals.  
  • In different BIG-IP versions, the Management Interface has a different name.  
    • Starting in TMOS v13.0.0 the interface is called: 'mgmt'.  
    • For previous versions, it is called 'eth0'.  

 

Step 2: Check BIG-IP Access

TMOS v 13.0.0 and newer with Management Interface

  1. From the on-prem BIG-IP CLI, to ensure connectivity to the F5 Silverline Cloud Platform, execute the following command:
    • curl -s -o /dev/null --interface mgmt -w "\n%{http_code}\n\n" https://api.f5silverline.com
    • Example output

  2. Ensure a response of "302" is received.
  3. For a full curl response, the following command can be utilized:

 

TMOS Pre v 13.0.0 With Management Interface

  1. From the on-prem BIG-IP CLI, to ensure connectivity to the F5 Silverline Cloud Platform, execute the following command:
    • curl -s -o /dev/null --interface eth0 -w "\n%{http_code}\n\n" https://api.f5silverline.com
    • Example output

  2. Ensure a response of "302" is received.
  3. For a full curl response, the following command can be utilized:

 

Without Management Interface

  1. From the on-prem BIG-IP CLI, to ensure connectivity to the F5 Silverline Cloud Platform, execute the following command:
    • curl -s -o /dev/null -w "\n%{http_code}\n\n" https://api.f5silverline.com
    • Example output

  2. Ensure a response of "302" is received.
  3. For a full curl response, the following command can be utilized:

 

Related Content

Other Common Issues with Hybrid Signaling iApp

More on Hybrid Connector iApp

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request