HP 6125G HP 6125G & 6125G/XG Blade Switches ACL and QoS Command Refere - Page 51

redirect, remark dot1p

Get HP 6125G PDF manuals and user guides View all HP 6125G manuals
Add to My Manuals
Save this manual to your list of manuals

Page 51 highlights

system-view [Sysname] traffic behavior database [Sysname-behavior-database] filter deny redirect Syntax redirect { cpu | interface interface-type interface-number | next-hop { ipv4-add1 [ ipv4-add2 ] | ipv6-add1 [ interface-type interface-number ] [ ipv6-add2 [ interface-type interface-number ] ] } } View undo redirect { cpu | interface interface-type interface-number | next-hop } Traffic behavior view Default level 2: System level Parameters cpu: Redirects traffic to the CPU. interface: Redirects traffic to an interface. interface-type interface-number: Specifies an interface by its type and number. next-hop: Redirects traffic to a next hop. ipv4-add1/ipv4-add2: IPv4 address of the next hop. The ipv4-add2 argument backs up ipv4-add1. If redirecting traffic to ipv4-add1 fails, the switch redirects the traffic to ipv4-add2. ipv6-add1/ipv6-add2: IPv6 address of the next hop. The ipv6-add2 argument backs up ipv6-add1. If redirecting traffic to ipv6-add1 fails, the switch redirects the traffic to ipv6-add2. If the specified next hop IPv6 address is a link-local address, you must also specify the outgoing interface. Otherwise, you do not need to specify the outgoing interface. Description Use redirect to configure a traffic redirecting action in the traffic behavior. Use undo redirect to delete the traffic redirecting action. NOTE: Redirecting traffic to CPU, redirecting traffic to an interface and redirecting traffic to the next hop are mutually exclusive with one another in a traffic behavior. Examples # Configure redirecting traffic to GigabitEthernet 1/0/1 in the traffic behavior database. system-view [Sysname] traffic behavior database [Sysname-behavior-database] redirect interface gigabitethernet1/0/1 remark dot1p Syntax remark dot1p { 8021p | customer-dot1p-trust } 46

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
46
<Sysname> system-view
[Sysname] traffic behavior database
[Sysname-behavior-database] filter deny
redirect
Syntax
redirect
{
cpu
|
interface
interface-type interface-number
|
next-hop
{
ipv4-add1
[
ipv4-add2
] |
ipv6-add1
[
interface-type interface-number
] [
ipv6-add2
[
interface-type interface-number
] ] } }
undo redirect
{
cpu
|
interface
interface-type interface-number
|
next-hop
}
View
Traffic behavior view
Default level
2: System level
Parameters
cpu
: Redirects traffic to the CPU.
interface
: Redirects traffic to an interface.
interface-type interface-number
: Specifies an interface by its type and number.
next-hop
: Redirects traffic to a next hop.
ipv4-add1/ipv4-add2
: IPv4 address of the next hop. The
ipv4-add2
argument backs up
ipv4-add1
. If
redirecting traffic to
ipv4-add1
fails, the switch redirects the traffic to
ipv4-add2
.
ipv6-add1/ipv6-add2
: IPv6 address of the next hop. The
ipv6-add2
argument backs up
ipv6-add1
. If
redirecting traffic to
ipv6-add1
fails, the switch redirects the traffic to
ipv6-add2
. If the specified next hop
IPv6 address is a link-local address, you must also specify the outgoing interface. Otherwise, you do not
need to specify the outgoing interface.
Description
Use
redirect
to configure a traffic redirecting action in the traffic behavior.
Use
undo redirect
to delete the traffic redirecting action.
NOTE:
Redirecting traffic to CPU, redirecting traffic to an interface and redirecting traffic to the next hop are
mutually exclusive with one another in a traffic behavior.
Examples
# Configure redirecting traffic to GigabitEthernet 1/0/1 in the traffic behavior
database
.
<Sysname> system-view
[Sysname] traffic behavior database
[Sysname-behavior-database] redirect interface gigabitethernet1/0/1
remark dot1p
Syntax
remark dot1p
{
8021p
|
customer-dot1p-trust
}