F3215-HP Load Balancing Module Network Management Configuration Guide-6PW101

448
Ste
p
Command
Remarks
5. Set the COMMUNITY attribute
for BGP routes.
apply community { none | additive |
{ community-number&<1-16> |
aa:nn&<1-16> | internet |
no-advertise | no-export |
no-export-subconfed } * [ additive ] }
Optional.
Not set by default.
6. Set a cost for routing
information.
apply cost [ + | - ] value
Optional.
Not set by default.
7. Set a cost type for routing
information.
apply cost-type [ external | internal
| type-1 | type-2 ]
Optional.
Not set by default.
8. Set the extended community
attribute for BGP routes.
apply extcommunity { { rt
route-target }&<1-16> [ additive ] |
soo site-of-origin additive }
Optional.
Not set by default.
9. Set the next hop.
Set the next hop for IPv4 routes:
apply ip-address next-hop
ip-address
Set the next hop for IPv6 routes:
apply ipv6 next-hop
ipv6-address
Optional.
Not set by default.
10. Set the IP precedence.
apply ip-precedence
ip-precedence-value
Optional.
Not set by default.
11. Set the local preference for
BGP routing information.
apply local-preference preference
Optional.
Not set by default.
12. Set the ORIGIN attribute for
BGP routes.
apply origin { egp as-number | igp |
incomplete }
Optional.
Not set by default.
13. Set the preference for the
routing protocol.
apply preference preference
Optional.
Not set by default.
14. Set a preferred value for BGP
routes.
apply preferred-value
preferred-value
Optional.
Not set by default.
15. Set a tag value for RIP or OSPF
route.
apply tag value
Optional.
Not set by default.
Configuring a continue clause
Follow these guidelines when you configure a continue clause:
If you configure the same apply clause that set different values (including the apply community and
apply extcommunity clauses with the additive keyword) on nodes that are combined by the
continue clause, the apply clause configured on the last matching node takes effect.
If you configure the apply community clause for multiple nodes that are combined by the continue
clause, the apply comm-list delete clause configured on the current node cannot delete the
COMMUNITY attributes set by preceding nodes.