Updating BGP Parameters

This page explains the procedure for updating BGP Parameters using the OCX Portal.

Preparation

Please confirm the following before updating BGP Parameters:

1. Your User Role is either admin or user.
2. The status of the configured Interface is activated.

Procedure for Updating BGP Parameters

1. Log in to the OCX Portal.

2. Click [OCX-Router(v1)] from the left navigation bar.

3. On the OCX-Router(v1) page, click the specific Interface within the relevant OCX-Router(v1) resource.

4. The details panel will appear at the bottom. Switch to the [BGP Parameters] tab.

5. Once the BGP Parameter list is displayed, click the Edit icon in the Actions column on the right side of the BGP Parameter you wish to modify.

6. The screen will switch to the settings modification step. The following items can be modified. After completing the input for the items you wish to change, click [Update].

   • AS Path Prepend
     • This is an AS Path attribute attached to the connection path of the Remote ASN. Enter a value from 0 to 8 (e.g., 2).
   • Local Preference
     • You can change the Local Preference setting for the Peer.
       Note: This setting is not applied to iBGP Peers. Available values:

       50, 100, 150, 200, 250, 300, 350, 400, 450, 500, 
       550, 600, 650, 700, 750, 800, 850, 900, 950, 1000
   • Redistribution of Connected and Static Routes
     • Allows BGP redistribution of all Static Routes and Connected routes (interface addresses) configured on the router to the specified Peer.
       Select ON if necessary for proper routing in environments where static and BGP dynamic routing coexist.
       Static or Connected routes added or deleted later will also be applied automatically.
   • Aggregate RFC1918 Routes
     • Aggregates and advertises RFC1918 routes as a single block.
       When ON, if any specific route (longer subnet mask) within the aggregate ranges exists in the routing table, the aggregate route is advertised, and detailed routes are suppressed.
       Use this if the cloud provider has limits on the number of received routes.
       Aggregate ranges:

       10.0.0.0/8 longer
       172.16.0.0/12 longer
       192.168.0.0/16 longer
       Examples:
       • For 10.0.0.0/8: Detected when a route within 10.0.0.0/8 with a mask longer than 8 bits is in the table (e.g., 10.10.10.0/24). Filters the specific and advertises 10.0.0.0/8.
       • For 172.16.0.0/12: Detected when a route within 172.16.0.0/12 with a mask longer than 12 bits is in the table. Filters the specific and advertises 172.16.0.0/12.
       • For 192.168.0.0/16: Detected when a route within 192.168.0.0/16 with a mask longer than 16 bits is in the table. Filters the specific and advertises 192.168.0.0/16.
   • Advertise Default Route
     • Advertises a default route (0.0.0.0/0) via BGP without needing a static route. Select ON if required.
       This only operates if the router holds routes other than "Connected" (i.e., Static or BGP routes).
   • Global Route Filter
     • Filters out all routes except RFC1918 ranges, preventing Global IP addresses from being advertised to the Peer.
       Routes that are NOT filtered:

       10.0.0.0/8 orlonger
       172.16.0.0/12 orlonger
       192.168.0.0/16 orlonger
       Note: You can combine BGP Parameter functions. For example, if both "Aggregate RFC1918 Routes" and this filter are ON, only the aggregate routes are advertised. If used with "Advertise Default Route," the default route will not be filtered.

7. A confirmation pop-up will appear. If the details are correct, click [Update].

8. The BGP Parameter list at the bottom will be updated. Confirm that your changes are reflected.

This completes the update of the BGP Parameter.

Remarks

• When updating a BGP Parameter, only AS Path Prepend is directly modifiable in some versions of the UI. If you need to change other core parameters that are greyed out, please delete the BGP Parameter and create a new one.