F3726, F3211, F3174, R5135, R3816-HP Firewalls and UTM Devices Network Management Command Reference-6PW100

1059
When used for BGP, the apply cost-type internal command sets the MED of a matching BGP route
learned from an IBGP peer to the IGP metric of the route's next hop before BGP advertises the route to an
EBGP peer.
Examples
# Create node 10 in permit mode of routing policy policy1. If a route has a tag of 8, set the cost type for
the route to IS-IS internal route.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy] if-match tag 8
[Sysname-route-policy] apply cost-type internal
apply extcommunity
Use apply extcommunity to apply the specified RT extended community attribute to BGP routes.
Use undo apply extcommunity to remove the clause configuration.
Syntax
apply extcommunity { { rt route-target }&<1-16> [ additive ] | soo site-of-origin additive }
undo apply extcommunity
Default
No RT extended community attribute is set for BGP routing information.
Views
Routing policy view
Default command level
2: System level
Parameters
rt route-target: Sets the route target (RT) extended community attribute, which is a string of 3 to 21
characters.
soo site-of-origin: Sets the Site of Origin (SoO) extended community attribute, which is a string of 3 to 21
characters.
A route-target or site-of-origin has one of the following forms:
• 16-bit AS number: 32-bit self-defined number, for example, 101:3.
• 32-bit IP address: 16-bit self-defined number, for example, 192.168.122.15:1.
• 32-bit AS number: 16-bit self-defined number, for example, 70000:3. The AS number must be no
less than 65536.
&<1-16>: Indicates that the argument before it can be entered up to 16 times.
additive: Adds the specified attribute to the original RT community attribute.
Usage guidelines
The following matrix shows the apply extcommunity command and firewalls and UTM devices
compatibility: