Cisco ISE Software Configuration Guide - Page 30

Committing a VC to a Bundle, Applying Parameters to Individual VCs

Get Cisco ISE - Line Card ISE PDF manuals and user guides
UPC - 746320730097
View all Cisco ISE manuals
Add to My Manuals
Save this manual to your list of manuals

Page 30 highlights

Software Configuration of ATM ISE Line Cards for Cisco 12000 Series Routers How to Configure Layer 3 Terminated VCs on the 4-Port ATM ISE Line Card Committing a VC to a Bundle To add a VC to an existing bundle and enter bundle-vc configuration mode, use the following command in bundle configuration mode: Command Router(config-if-atm-bundle)# pvc-bundle pvc-name [vpi/] [vci] Purpose Adds the specified VC to the bundle and enters bundle-vc configuration mode to configure the specified VC bundle member. For information on how to create a bundle and configure it, see the "Creating a VC Bundle" section on page 28 and the "Applying Bundle-Level Parameters" section on page 28. Applying Parameters to Individual VCs Parameters can be applied to individual VCs either by using VC classes or by directly applying them to the bundle members. Parameters applied to an individual VC supersede bundle-level parameters. Parameters applied directly to a VC take precedence over the same parameters applied within a class to the VC at the bundle-vc configuration level. The following should be noted regarding parameters applied to individual VCs: • Policing in a policy-map is performed on the aggregate traffic of the bundle. In other words, policing is not per VC, but rather for the whole subinterface. • MDRR defined using the bandwidth command is applied to each VC separately. In other words, the weight of the MDRR will be relative to the traffic passing on each VC and not relative to the traffic passing on the bundle. The following sections describe applying parameters to individual VCs: • Configuring a VC Bundle Member Directly, page 30 • Configuring VC Class Parameters to Apply to a VC Bundle Member, page 31 • Applying a VC Class to a Discrete VC Bundle Member, page 32 • Configuring a VC Not to Accept Bumped Traffic, page 32 Configuring a VC Bundle Member Directly Configuring VC bundle members directly is optional if a VC class is attached to the bundle member. To configure an individual VC bundle member directly, use the following commands in bundle-vc configuration mode: Command Router(config-if-atm-member)# bump {implicit | explicit precedence-level | traffic} Router(config-if-atm-member)# mpls experimental [other | range] Router(config-if-atm-member)# precedence [other | range] Purpose Configures the bumping rules for the VC bundle member. Specifies which MPLS experimental bit values can be mapped to a member of a VC bundle. Configures the precedence levels that apply to the VC bundle member. Cisco IOS Release 12.0(27)S 30

  • 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
Software Configuration of ATM ISE Line Cards for Cisco 12000 Series Routers
How to Configure Layer 3 Terminated VCs on the 4-Port ATM ISE Line Card
30
Cisco IOS Release 12.0(27)S
Committing a VC to a Bundle
To add a VC to an existing bundle and enter bundle-vc configuration mode, use the following command
in bundle configuration mode:
For information on how to create a bundle and configure it, see the
“Creating a VC Bundle” section on
page 28
and the
“Applying Bundle-Level Parameters” section on page 28
.
Applying Parameters to Individual VCs
Parameters can be applied to individual VCs either by using VC classes or by directly applying them to
the bundle members.
Parameters applied to an individual VC supersede bundle-level parameters. Parameters applied directly
to a VC take precedence over the same parameters applied within a class to the VC at the bundle-vc
configuration level.
The following should be noted regarding parameters applied to individual VCs:
•
Policing in a policy-map is performed on the aggregate traffic of the bundle. In other words, policing
is not per VC, but rather for the whole subinterface.
•
MDRR defined using the bandwidth command is applied to each VC separately. In other words, the
weight of the MDRR will be relative to the traffic passing on each VC and not relative to the traffic
passing on the bundle.
The following sections describe applying parameters to individual VCs:
•
Configuring a VC Bundle Member Directly, page 30
•
Configuring VC Class Parameters to Apply to a VC Bundle Member, page 31
•
Applying a VC Class to a Discrete VC Bundle Member, page 32
•
Configuring a VC Not to Accept Bumped Traffic, page 32
Configuring a VC Bundle Member Directly
Configuring VC bundle members directly is optional if a VC class is attached to the bundle member.
To configure an individual VC bundle member directly, use the following commands in bundle-vc
configuration mode:
Command
Purpose
Router(config-if-atm-bundle)#
pvc-bundle
pvc-name
[
vpi
/] [
vci
]
Adds the specified VC to the bundle and enters bundle-vc
configuration mode to configure the specified VC bundle
member.
Command
Purpose
Router(config-if-atm-member)#
bump
{
implicit
|
explicit
precedence-level
|
traffic
}
Configures the bumping rules for the VC bundle member.
Router(config-if-atm-member)#
mpls
experimental
[
other
|
range
]
Specifies which MPLS experimental bit values can be mapped to
a member of a VC bundle.
Router(config-if-atm-member)#
precedence
[
other
|
range
]
Configures the precedence levels that apply to the VC bundle
member.