R3721-F3210-F3171-HP High-End Firewalls Network Management Command Reference-6PW101

806
Local
p
arameter Peer
p
arameter Ne
g
otiation result
receive
• send
• both
The ORF receiving capability is enabled locally and the
ORF sending capability is enabled on the peer.
both both
Both the ORF sending and receiving capabilities are
enabled locally and on the peer, respectively.
Examples
# Enable the ORF capability for the BGP peer 1:2::3:4. Then, after negotiation, the local router can
exchange ORF information with the peer 1:2::3:4.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp] ipv6-family
[Sysname-bgp-af-ipv6] peer 1:2::3:4 as-number 100
[Sysname-bgp-af-ipv6] peer 1:2::3:4 capability-advertise orf ipv6-prefix both
peer capability-advertise orf non-standard
Syntax
peer { group-name | ipv6-address } capability-advertise orf non-standard
undo peer { group-name | ipv6-address } capability-advertise orf non-standard
View
IPv6 address family view
Default level
2: System level
Parameters
group-name: Name of a peer group, a string of 1 to 47 characters.
ipv6-address: IPv6 address of a peer.
Parameters
Use peer capability-advertise orf non-standard to enable the non-standard ORF capability (the early
implementation of ORF is different from that defined in RFC) for a BGP peer or peer group.
Use undo peer capability-advertise orf non-standard to disable the non-standard ORF capability for the
BGP peer or peer group.
By default, the non-standard ORF capability is not enabled for a BGP peer or peer group.
This command needs to be configured when the peer supports only non-standard ORF.
Related commands: peer capability-advertise orf.
Examples
# Enable the non-standard ORF capability for the BGP peer 1:2::3:4 (suppose the BGP peer 1:2::3:4
can only send non-standard ORF packets).
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp] ipv6-family