3.7. VPLS Service Configuration Command Reference

This section describes the VPLS service configuration command reference.

3.7.1. Command Hierarchies

3.7.1.1. Global Commands

config
— service
— system
fdb-table-size table-size
vpls service-id [customer customer-id] [vpn vpn-id] [m-vpls] [b-vpls | i-vpls] [etree] [name name] [create]
— no vpls service-id
[no] mrouter-port
[no] mrouter-port
backbone-vpls service-id[:isid]
[no] stp
bgp
pw-template-binding policy-id [split-horizon-group group-name] [import-rt ext-community [ext-community ... (up to 5 max)]]
— no pw-template-binding policy-id
[no] bfd-enable
bfd-template [name]
monitor-oper-group group-name
oper-group group-name
— no oper-group
route-target {ext-community | export ext-community [import ext-community] | import ext-community}
vsi-export policy-name [policy-name...(up to 5 max)]
— no vsi-export
vsi-import policy-name [policy-name...(up to 5 max)]
— no vsi-import
[no] bgp-ad
vpls-id vpls-id
vsi-id
prefix low-order-vsi-id
— no prefix
max-ve-id value
— no max-ve-id
ve-name name
— no ve-name
ve-id ve-id-value
— no ve-id
[no] shutdown
ip ip-address
— no ip
mac ieee-address
— no mac
description description-string
[no] disable-aging
[no] discard-unknown
endpoint endpoint-name [create]
— no endpoint
description description-string
[no] mac-pinning
max-nbr-mac-addr table-size
[no] mc-endpoint
mc-ep-peer name
mc-ep-peer ip-address
— no mc-ep-peer
restrict-protected-src alarm-only
restrict-protected-src [discard-frame]
revert-time revert-time | infinite
static-mac ieee-address [create]
— no static-mac
[no] mep mep-id domain md-index association ma-index
[no] ccm-enable
ccm-ltm-priority priority
description description-string
[no] test-pattern {all-zeros | all-ones} [crc-enable]
grace
eth-ed
priority priority
— no priority
[no] rx-eth-ed
[no] tx-eth-ed
low-priority-defect {allDef | macRemErrXcon | remErrXcon | errXcon | xcon | noXcon}
mac-address mac-address
[no] shutdown
tunnel-fault [accept | ignore]
[no] fdb-table-high-wmark high-water-mark
[no] fdb-table-low-wmark low-water-mark
fdb-table-size table-size
— no fdb-table-size [table-size]
gsmp
[no] group name [create]
ancp
[no] oam
description description-string
hold-multiplier multiplier
keepalive seconds
— no keepalive
[no] neighbor ip-address
description description-string
local-address ip-address
priority-marking dscp dscp-name
priority-marking prec ip-prec-value
[no] shutdown
[no] shutdown
[no] idle-filter
[no] shutdown
host-connectivity-verify source-ip ip-address [source-mac ieee-address] [interval interval] [action {remove | alarm}]
expiry-time expiry-time
[no] shutdown
mvr
description description-string
group-policy policy-name
[no] shutdown
query-interval seconds
query-src-ip ip-address
report-src-ip ip-address
robust-count robust-count
[no] shutdown
[no] interface ip-int-name
address ip-address[/mask] [netmask]
— no address
arp-timeout seconds
description long-description-string
up ip seconds
— no up ip
up ipv6 seconds
— no up ipv6
down ip seconds [init-only]
— no down ip
down ipv6 seconds [init-only]
— no down ipv6
mac ieee-address
— no mac
[no] shutdown
static-arp ieee-mac-addr unnumbered
— no static-arp unnumbered]
unnumbered [ip-int-name | ip-address]
— no unnumbered
entry range-entry-id [create]
— no entry range-entry-id
range isid [to isid]
— no range
[no] use-def-mcast
local-age aging-timer
— no local-age [aging-time]
[no] mac-move
move-frequency frequency
number-retries number-retries
cumulative-factor cumulative-factor
[no] sap sap-id
[no] spoke-sdp spoke-id
[no] cumulative-factor factor
retry-timeout timeout
cumulative-factor cumulative-factor
[no] sap sap-id
[no] spoke-sdp spoke-id
[no] cumulative-factor factor
[no] shutdown
count value
— no count
interval deci-seconds
— no interval
renotify seconds
— no renotify
[no] shutdown
[no] mac ieee-address
mac-subnet-length subnet-length
mcast-ipv6-snooping-scope {mac-based | sg-based}
mfib-table-high-wmark high-water-mark
mfib-table-low-wmark low-water-mark
mfib-table-size table-size
mvr
description description-string
group-policy policy-name
[no] shutdown
query-interval seconds
query-src-ip ipv6-address
report-src-ip ipv6-address
robust-count robust-count
[no] shutdown
mrp
flood-time flood-time
— no flood-time
[no] shutdown
mvrp
flood-time flood-time
— no flood-time
[no] hold-time value
[no] shutdown
multicast-info-policy policy-name
[no] pim-snooping
group-policy grp-policy-name [.. grp-policy-name]
hold-time seconds
— no hold-time
mode mode
remote-age aging-timer
— no remote-age
send-bvpls-flush {[all-but-mine] | [all-from-me]}
service-mtu octets
[no] shutdown
site name [create]
— no site name
boot-timer seconds
— no boot-timer
failed-threshold [1 to 1000]
sap sap-id
— no sap
[no] shutdown
site-min-down-timer min-down-time
site-id value
— no site-id
split-horizon-group group-name
spoke-sdp sdp-id:vc-id
— no spoke-sdp
spb [isis-instance] [fid fid] [create]
no spb
level [1..1]
bridge-priority bridge-priority
ect-algorithm fid-range fid-range {low-path-id|high-path-id}
— no ect-algorithm fid-range fid-range
forwarding-tree-topology unicast {spf | st}
hello-interval seconds
hello-multiplier multiplier
metric ipv4-metric
no metric
lsp-lifetime seconds
— no lsp-lifetime
lsp-refresh-interval [seconds] [half-lifetime {enable | disable}]
[no] split-horizon-group group-name [residential-group]
description description-string
restrict-protected-src alarm-only
restrict-protected-src [discard-frame]
mac ieee-address [create] black-hole
mac ieee-address [create] sap sap-id monitor {fwd-status}
mac ieee-address [create] spoke-sdp sdp-id:vc-id monitor {fwd-status}
— no mac ieee-address
stp
forward-delay forward-delay
hello-time hello-time
— no hello-time
hold-count BDPU tx hold count
— no hold-count
max-age max-info-age
— no max-age
mode {rstp | comp-dot1w | dot1w | mstp | pmstp}
— no mode
[no] mst-instance mst-inst-number
mst-priority bridge-priority
[no] vlan-range vlan-range
mst-max-hops hops-count
mst-name region-name
— no mst-name
mst-revision revision-number
priority bridge-priority
— no priority
[no] shutdown
timers
lsp-wait lsp-wait [lsp-initial-wait initial-wait] [lsp-second-wait second-wait]
no lsp-wait
spf-wait spf-wait [spf-initial-wait initial-wait] [spf-second-wait second-wait]
no spf-wait
vpls-group id
service-range startid-endid [vlan-id startvid]
[no] mvrp-control
vxlan vni vni-id create
— no vxlan vni vni-id
qos network-policy-id fp-redirect-group queue-group-name instance instance-id
— no qos
restrict-protected-src discard-frame

3.7.1.2. Oper Group Commands

config
— service
— vpls service-id
[no] interface ip-int-name

3.7.1.3. SAP Commands

config
— service
vpls service-id [customer customer-id] [vpn vpn-id] [m-vpls] [b-vpls | i-vpls] [etree] [name name] [create]
— no vpls service-id
sap sap-id [split-horizon-group group-name] [create] [capture-sap] [root-leaf-tag leaf-tag-vid | leaf-ac]
[no] sap eth-tunnel-tunnel-id [:eth-tunnel-sap-id]
— no sap sap-id
accounting-policy acct-policy-id
anti-spoof {ip | mac | ip-mac}
— no anti-spoof
app-profile app-profile-name
host-limit max-num-hosts
— no host-limit
min-auth-interval min-auth-interval
[no] shutdown
arp-reply-agent [sub-ident]
atm
egress
traffic-desc traffic-desc-profile-id
encapsulation atm-encap-type
traffic-desc traffic-desc-profile-id
oam
[no] alarm-cells
bandwidth bandwidth
— no bandwidth
bpdu-translation {auto | auto-rw | pvst | pvst-rw | stp}
calling-station-id {mac | remote-id | sap-id | sap-string}
[no] cflowd
[no] collect-stats
cpu-protection policy-id {[mac-monitoring] | [eth-cfm-monitoring [aggregate] [car]]}
default-msap-policy policy-name
description long-description-string
dhcp
description description-string
lease-populate [nbr-of-entries]
[no] option
action [dhcp-action]
— no action
circuit-id [ascii-tuple | vlan-ascii-tuple]
circuit-id hex [0x0..0xFFFFFFFF...(64 hex nibbles)]
— no circuit-id
remote-id [mac | string string]
remote-id hex [0x0..0xFFFFFFFF...(64 hex nibbles)]
— no remote-id
[no] sap-id
[no] service-id
string text
— no string
[no] system-id
emulated-server ip-address
lease-time [days days] [hrs hours] [min minutes] [sec seconds] [radius-override]
— no lease-time
[no] shutdown
[no] shutdown
[no] snoop
dhcp-python-policy policy-name
dhcp6-user-db local-user-db-name
dhcp6
description description-string
[no] option
interface-id ascii-tuple
interface-id vlan-ascii-tuple
remote-id mac
remote-id string [32 chars max]
— no remote-id
[no] shutdown
[no] snoop
[no] disable-aging
dist-cpu-protection policy-name
egress
[no] agg-rate
rate {max | rate}
— no rate
encap-group group-name [type group-type] [qos-per-member] [create]
— no encap-group group-name
[no] agg-rate
rate {max | rate}
— no rate
[no] member encap-id [to encap-id]
qos policy-id
— no qos
scheduler-policy scheduler-policy-name
filter ip ip-filter-id
filter ipv6 ipv6-filter-id
filter mac mac-filter-id
— no filter
— no filter [ip ip-filter-id] [mac mac-filter-id] [ipv6 ipv6-filter-id]
secondary-shaper secondary-shaper-name
wrr-policy hsmda-wrr-policy-name
— no wrr-policy
packet-byte-offset {add add-bytes | subtract sub-bytes}
queue queue-id
— no queue queue-id
wrr-weight weight
— no wrr-weight
mbs size {[bytes | kilobytes] | default}
— no mbs
rate pir-rate
— no rate
slope-policy hsmda-slope-policy-name allowable
max-rate {rate | max}
min-thresh-separation size [bytes | kilobytes]
[no] priority level
mbs-contribution size [bytes | kilobytes]
policer-control-policy policy-name
policer policer-id [create]
— no policer policer-id
cbs size [bytes | kilobytes]
— no cbs
mbs {size [bytes | kilobytes] | default}
— no mbs
packet-byte-offset {add add-bytes | subtract sub-bytes}
rate {rate | max} [cir {max | rate}]
stat-mode stat-mode
— no stat-mode
qos policy-id [port-redirect-group queue-group-name instance instance-id]]
— no qos
[no] queue queue-id
adaptation-rule [pir adaptation-rule] [cir adaptation-rule]
avg-frame-overhead percentage
burst-limit {default | size [bytes | kilobytes]}
cbs size-in-kbytes
— no cbs
low
mbs {size [bytes | kilobytes] | default}
— no mbs
parent {[weight weight] [cir-weight cir-weight]}
no parent
percent-rate pir-percent [cir cir-percent]
rate pir-rate [cir cir-rate]
— no rate
[no] scheduler scheduler-name
parent [weight weight] [cir-weight cir-weight]
— no parent
rate pir-rate [cir cir-rate]
— no rate
scheduler-policy scheduler-policy-name
fc fc-name [fc-name ... (up to 8 max)]
— no fc
fc-in-profile fc-name [fc-name ... (up to 8 max)]
mep mep-id domain md-index association ma-index [direction {up |down}] primary-vlan-enable [vlan vlan-id]
— no mep mep-id domain md-index association ma-index
[no] ais-enable
ccm-padding-size ccm-padding
— no ccm-padding-size ccm-padding
[no] csf-enable
multiplier multiplier-value
— no multiplier
client-meg-level [level [level...]]
[no] description
interval {1 | 60}
— no interval
priority priority-value
— no priority
[no] ccm-enable
ccm-ltm-priority priority
test-pattern {all-zeros | all-ones} [crc-enable]
fault-propagation-enable {use-if-tlv | suspend-ccm}
grace
eth-ed
priority priority
— no priority
[no] rx-eth-ed
[no] tx-eth-ed
low-priority-defect {allDef | macRemErrXcon | remErrXcon | errXcon | xcon | noXcon}
mac-address mac-address
[no] shutdown
[no] squelch-ingress-levels [md-level [md-level…]]
[no] mip [{mac mac-address | default-mac}]
tunnel-fault [accept | ignore]
[no] vmep-filter
path path-index tag qtag[.qtag]
— no path path-index
[no] mip
fault-propagation-bmac [mac-name | ieee-address] [create]
— no fault-propagation-bmac [mac-name | ieee-address
[no] frf-12
[no] interleave
scheduling-class class-id
host-connectivity-verify source-ip ip-address [source-mac ieee-address] [interval interval] [action {remove | alarm}]
expiry-time expiry-time
import policy-name
— no import
max-num-groups max-num-groups
max-num-sources max-num-sources
max-num-grp-sources [1..32000]
[no] fast-leave
import policy-name
— no import
max-num-groups max-num-groups
max-num-sources max-num-sources
max-num-grp-sources [1 to 32000]
mcac
if-policy mcac-if-policy-name
— no if-policy
level level-id bw bandwidth
— no level level-id
number-down number-lag-port-down level level-id
[no] shutdown
policy policy-name
— no policy
unconstrained-bw bandwidth mandatory-bw mandatory-bw
[no] mrouter-port
mvr
from-vpls vpls-id
— no from-vpls
to-sap sap-id
— no to-sap
query-interval interval
robust-count count
[no] send-queries
static
[no] group group-address
[no] source ip-address
[no] starg
version version
— no version
filter ip ip-filter-id
filter ipv6 ipv6-filter-id
filter mac mac-filter-id
— no filter [ip ip-filter-id] [mac mac-filter-id] [ipv6 ipv6-filter-id]
match-qinq-dot1p {top | bottom}
max-rate {rate | max}
min-thresh-separation size [bytes | kilobytes]
[no] priority level
mbs-contribution size [bytes | kilobytes]
policer-control-policy policy-name
policer policer-id [create]
— no policer policer-id
cbs size [bytes | kilobytes]
— no cbs
mbs {size [bytes | kilobytes] | default}
— no mbs
packet-byte-offset {add add-bytes | subtract sub-bytes}
rate {rate | max} [cir {max | rate}]
stat-mode stat-mode
— no stat-mode
qos policy-id [shared-queuing | multipoint-shared] [fp-redirect-group queue-group-name instance instance-id]
— no qos
[no] queue queue-id
adaptation-rule [pir {max | min | closest}] [cir {max | min | closest}]
cbs size-in-kbytes
— no cbs
low
mbs {size [bytes | kilobytes] | default}
— no mbs
parent {[weight weight] [cir-weight cir-weight]}
no parent
percent-rate pir-percent [cir cir-percent]
rate pir-rate [cir cir-rate]
— no rate
[no] scheduler scheduler-name
parent [weight weight] [cir-weight cir-weight]
— no parent
rate pir-rate [cir cir-rate]
— no rate
scheduler-policy scheduler-policy-name
l2pt-termination [cdp] [dtp] [pagp] [stp] [udld] [vtp]
lag-link-map-profile link-map-profile-id
lag-per-link-hash class {1 | 2 | 3} weight [1 to 1024]
limit-mac-move [blockable | non-blockable]
[no] mac-pinning
[no] default-sap
[no] range vlan-range
max-nbr-mac-addr table-size
[no] fast-leave
import policy-name
— no import
max-num-groups max-num-groups
mcac
if-policy mcac-if-policy-name
— no if-policy
level level-id bw bandwidth
— no level level-id
number-down number-lag-port-down level level-id
[no] shutdown
policy policy-name
— no policy
unconstrained-bw bandwidth mandatory-bw mandatory-bw
mvr
— no fast-leave
to-sap sap-id
— no to-sap
query-interval seconds
robust-count robust-count
[no] send-queries
static
[no] group group-address
[no] source ip-address
[no] starg
version version
— no version
mrp
[no] join-time value
[no] leave-all-time value
[no] leave-time value
[no] mrp-policy policy-name
[no] periodic-time value
[no] periodic-time
mvrp
endstation-vid-group id vlan-id startvid-endvid
[no] shutdown
[no] service service-id
policy msap-policy-name
— no policy
monitor-oper-group group-name
oper-group group-name
— no oper-group
multi-service-sitecustomer-site-name
max-num-groups num-groups
pppoe-policy pppoe-policy-name
restrict-protected-src alarm-only
restrict-protected-src [discard-frame]
shcv-policy-ipv4 policy-name
[no] shutdown
spb [isis-instance] [fid fid] [create]
no spb
level [1 to 1]
hello-interval seconds
hello-multiplier multiplier
metric ipv4-metric
no metric
lsp-pacing-interval milli-seconds
[no] shutdown
static-host ip ip-address [mac ieee-address] [create]
static-host mac ieee-address [create]
— no static-host [ip ip-address] mac ieee-address
— no static-host all [force]
— no static-host ip ip-address
ancp-string ancp-string
app-profile app-profile-name
inter-dest-id intermediate-destination-id
[no] shutdown
sla-profile sla-profile-name
sub-profile sub-profile-name
subscriber sub-ident
— no subscriber
[no] static-isid range entry-id isid [to isid] [create]
[no] static-mac ieee-address
stp
[no] auto-edge
[no] edge-port
link-type {pt-pt | shared}
— no link-type
mst-instance mst-inst-number
mst-path-cost inst-path-cost
mst-port-priority bridge-priority
path-cost sap-path-cost
— no path-cost
[no] port-num virtual-port-number
priority stp-priority
— no priority
[no] vpls-group
[no] shutdown
[no] sub-sla-mgmt
def-sla-profile default-sla-profile-name
def-sub-profile default-subscriber-profile-name
multi-sub-sap [subscriber-limit]
[no] shutdown
non-sub-traffic sub-profile sub-profile-name sla-profile sla-profile-name [subscriber sub-ident-string]
sub-ident-policy sub-ident-policy-name
trigger-packet [dhcp] [pppoe] [arp] [dhcp6] [ppp] [data]

3.7.1.4. Template Commands

config
— service
vpls-template name/id create
[no] temp-flooding flood-time
[no] disable-aging
[no] discard-unknown
[no] fdb-table-high-wmark high-water-mark
[no] fdb-table-low-wmark low-water-mark
fdb-table-size table-size
— no fdb-table-size [table-size]
local-age aging-timer
— no local-age
[no] mac-move
move-frequency frequency
number-retries number-retries
cumulative-factor cumulative-factor
retry-timeout timeout
cumulative-factor cumulative-factor
[no] shutdown
remote-age aging-timer
— no remote-age
service-mtu octets
stp
forward-delay forward-delay
hello-time hello-time
— no hello-time
hold-count BDPU tx hold count
— no hold-count
max-age max-info-age
— no max-age
mode {rstp | comp-dot1w | dot1w | mstp | pmstp}
— no mode
priority bridge-priority
— no priority
[no] shutdown
vpls-sap-template name/id create
l2pt-termination [cdp] [dtp] [pagp] [stp] [udld] [vtp]
bpdu-translation {auto | auto-rw | pvst | pvst-rw | stp}
[no] collect-stats
cpu-protection policy-id [mac-monitoring]
[no] mip primary-vlan-enable [vlan vlan-id]
[no] squelch-ingress-levels [md-level [md-level…]]
[no] disable-aging
egress
[no] agg-rate
rate {max | rate}
— no rate
filter ip ip-filter-id
filter ipv6 ipv6-filter-id
filter mac mac-filter-id
— no filter
— no filter [ip ip-filter-id] [mac mac-filter-id] [ipv6 ipv6-filter-id]
[no] filter-name
ip name
— no ip
ipv6 name
— no ipv6
mac name
— no mac
policer-control-policy policy-name
qos sap-egress-policy-id
qos name sap-egress-policy-name
— no qos
scheduler-policy scheduler-policy-name
filter ip ip-filter-id
filter ipv6 ipv6-filter-id
filter mac mac-filter-id
— no filter [ip ip-filter-id] [mac mac-filter-id] [ipv6 ipv6-filter-id]
[no] filter-name
ip name
— no ip
ipv6 name
— no ipv6
mac name
— no mac
match-qinq-dot1p {top | bottom}
policer-control-policy policy-name
qos policy-id [shared-queuing | multipoint-shared]
qos name sap-ingress-policy-name [shared-queuing | multipoint-shared]
— no qos [policy-id]
scheduler-policy scheduler-policy-name
limit-mac-move [blockable | non-blockable]
max-nbr-mac-addr table-size
stp
[no] auto-edge
[no] edge-port
link-type {pt-pt | shared}
— no link-type [pt-pt | shared]
path-cost sap-path-cost
— no path-cost
priority stp-priority
— no priority
[no] vpls-group
[no] shutdown

3.7.1.5. Mesh SDP Commands

config
— service
[no] vpls service-id [customer customer-id] [vpn vpn-id] [m-vpls] [b-vpls | i-vpls] [etree] [name name] [create]
mesh-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [root-leaf-tag | leaf-ac]
— no mesh-sdp sdp-id[:vc-id]
accounting-policy acct-policy-id
[no] bfd-enable
bfd-template name
[no] collect-stats
[no] control-word
description description-string
dhcp
description description-string
[no] snoop
egress
filter ip ip-filter-id
filter ipv6 ipv6-filter-id
filter mac mac-filter-id
— no filter [ip ip-filter-id] [mac mac-filter-id] [ipv6 ipv6-filter-id]
qos network-policy-id port-redirect-group queue-group-name [instance instance-id]
— no qos
[no] mda mda-id
vc-label egress-vc-label
— no vc-label [egress-vc-label]
[no] entropy-label
fc fc-name [fc-name ... (up to 8 max)]
— no fc
fc-in-profile fc-name [fc-name ... (up to 8 max)]
mep mep-id domain md-index association ma-index [direction {up | down}] [primary-vlan-enable]
— no mep mep-id domain md-index association ma-index primary-vlan-enable [vlan vlan-id]
[no] ais-enable
client-meg-level [level [level...]]
interval {1 | 60}
— no interval
low-priority-defect {allDef | macRemErrXcon}
priority priority-value
— no priority
[no] ccm-enable
ccm-padding-size ccm-padding
ccm-ltm-priority priority
[no] csf-enable
multiplier multiplier-value
— no multiplier
description description-string
test-pattern {all-zeros | all-ones} [crc-enable]
fault-propagation-enable {use-if-tlv | suspend-ccm}
grace
eth-ed
priority priority
— no priority
[no] rx-eth-ed
[no] tx-eth-ed
low-priority-defect {allDef | macRemErrXcon | remErrXcon | errXcon | xcon | noXcon}
mac-address mac-address
[no] shutdown
[no] mip [mac mac-address] [primary-vlan-enable vlan-id]
[no] squelch-ingress-levels [md-level [md-level]]
[no] vmep-filter
fault-propagation-bmac [mac-name | ieee-address] [create]
— no fault-propagation-bmac [mac-name | ieee-address]
[no] hash-label
[no] fast-leave
import policy-name
— no import
max-num-groups max-num-groups
max-num-grp-sources [1 to 32000]
mcac
if-policy mcac-if-policy-name
— no if-policy
policy policy-name
— no policy
unconstrained-bw bandwidth mandatory-bw mandatory-bw
[no] mrouter-port
robust-count count
— no robust-count
[no] send-queries
static
[no] group grp-ip-address
[no] source ip-address
[no] starg
version version
— no version
filter ip ip-filter-id
filter ipv6 ipv6-filter-id
filter mac mac-filter-id
— no filter [ip ip-filter-id] [mac mac-filter-id] [ipv6 ipv6-filter-id]
qos network-policy-id fp-redirect-group queue-group-name instance instance-id
— no qos
[no] mda mda-id
vc-label ingress-vc-label
— no vc-label [ingress-vc-label]
[no] mac-pinning
[no] fast-leave
import policy-name
— no import
max-num-groups max-num-groups
mcac
if-policy mcac-if-policy-name
— no if-policy
policy policy-name
— no policy
unconstrained-bw bandwidth mandatory-bw mandatory-bw
mvr
[no] fast-leave
to-sap sap-id
— no to-sap
query-interval seconds
robust-count robust-count
[no] send-queries
static
[no] group
[no] source src-ipv6-address
[no] starg
[no] group grp-ipv6-address
version version
— no version
mrp
[no] join-time value
[no] leave-all-time value
[no] leave-time value
[no] mrp-policy policy-name
[no] periodic-time value
[no] periodic-time
restrict-protected-src alarm-only
restrict-protected-src [discard-frame]
[no] shutdown
[no]static-mac ieee-address
vlan-vc-tag 0 to 4094
— no vlan-vc-tag [0 to 4094]

3.7.1.6. Spoke SDP Commands

config
— service
[no] vpls service-id [customer customer-id] [vpn vpn-id] [m-vpls] [b-vpls | i-vpls] [etree] [name name] [create]
spoke-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [split-horizon-group group-name] [root-leaf-tag | leaf-ac]
— no spoke-sdp sdp-id[:vc-id]
accounting-policy acct-policy-id
app-profile app-profile-name
[no] bfd-enable
bfd-template name
bpdu-translation {auto | auto-rw | pvst | pvst-rw | stp}
[no] collect-stats
refresh-timer value
request-timer timer1 retry-timer timer2 [timeout-multiplier multiplier]
[no] control-word
description description-string
dhcp
description description-string
[no] snoop
[no] disable-aging
[no] entropy-label
fc fc-name [fc-name ... (up to 8 max)]
— no fc
fc-in-profile fc-name [fc-name ... (up to 8 max)]
mep mep-id domain md-index association ma-index [direction {up | down}] [primary-vlan-enable]
— no mep mep-id domain md-index association ma-index
[no] ais-enable
client-meg-level [level [level...]]
interval {1 | 60}
— no interval
priority priority-value
— no priority
[no] ccm-enable
ccm-ltm-priority priority
ccm-padding-size ccm-padding
— no ccm-padding-size ccm-padding
[no] csf-enable
multiplier multiplier-value
— no multiplier
[no] description
test-pattern {all-zeros | all-ones} [crc-enable]
fault-propagation-enable {use-if-tlv | suspend-ccm}
grace
eth-ed
priority priority
— no priority
[no] rx-eth-ed
[no] tx-eth-ed
low-priority-defect {allDef | macRemErrXcon | remErrXcon | errXcon | xcon | noXcon}
mac-address mac-address
[no] description
[no] shutdown
[no] mip [mac mac-address] [primary-vlan-enable vlan-id]
[no] squelch-ingress-levels [md-level [md-level]]
egress
filter ip ip-filter-id
filter ipv6 ipv6-filter-id
filter mac mac-filter-id
— no filter [ip ip-filter-id] [mac mac-filter-id] [ipv6 ipv6-filter-id]
qos network-policy-id port-redirect-group queue-group-name [instance instance-id]
— no qos
[no] mda mda-id
vc-label egress-vc-label
— no vc-label [egress-vc-label]
fault-propagation-bmac [mac-name | ieee-address] [create]
— no fault-propagation-bmac [mac-name | ieee-address
— no hash-label
[no] fast-leave
import policy-name
— no import
max-num-groups max-num-groups
max-num-grp-sources [1 to 32000]
mcac
if-policy mcac-if-policy-name
— no if-policy
policy policy-name
— no policy
unconstrained-bw bandwidth mandatory-bw mandatory-bw
[no] mrouter-port
query-interval interval
robust-count count
— no robust-count
[no] send-queries
static
[no] group group-address
[no] source ip-address
[no] starg
version version
— no version
filter ip ip-filter-id
filter ipv6 ipv6-filter-id
filter mac mac-filter-id
— no filter [ip ip-filter-id] [mac mac-filter-id] [ipv6 ipv6-filter-id]
qos network-policy-id fp-redirect-group queue-group-name instance instance-id
— no qos
[no] mda mda-id
vc-label egress-vc-label
— no vc-label [egress-vc-label]
limit-mac-move [blockable | non-blockable]
[no] mac-pinning
max-nbr-mac-addr table-size
[no] fast-leave
import policy-name
— no import
max-num-groups max-num-groups
mcac
if-policy mcac-if-policy-name
— no if-policy
policy policy-name
— no policy
unconstrained-bw bandwidth mandatory-bw mandatory-bw
query-interval seconds
robust-count robust-count
[no] send-queries
static
[no] group group-address
[no] source ip-address
[no] starg
version version
— no version
monitor-oper-group group-name
oper-group group-name
— no oper-group
mrp
[no] join-time value
[no] leave-all-time value
[no] leave-time value
[no] mrp-policy policy-name
[no] periodic-time value
oper-group group-name
— no oper-group
max-num-groups num-groups
precedence precedence-value | primary
— no precedence
[no] pw-path-id
agi agi
— no agi
saii-type2 global-id:node-id:ac-id
— no saii-type2
taii-type2 global-id:node-id:ac-id
— no taii-type2
propagate-mac-flush [precedence-value | primary]
[no] shutdown
spb [isis-instance] [fid fid] [create]
no spb
level [1 to 1]
hello-interval seconds
hello-multiplier multiplier
metric ipv4-metric
no metric
lsp-pacing-interval milli-seconds
[no] shutdown
[no] static-isid range entry-id isid [to isid] [create]
[no] static-mac ieee-address
stp
[no] auto-edge
[no] edge-port
link-type {pt-pt | shared}
— no link-type
path-cost sap-path-cost
— no path-cost
[no] port-num virtual-port-number
priority stp-priority
— no priority
[no] vpls-group
[no] shutdown
transit-policy prefix prefix-aasub-policy-id
vlan-vc-tag 0 to 4094
— no vlan-vc-tag [0 to 4094]

3.7.1.7. Provider Tunnel Commands

config
— service
[no] vpls service-id [customer customer-id] [vpn vpn-id] [m-vpls] [b-vpls | i-vpls] [name name] [create]
mldp
[no] mldp
[no] root-and-leaf
[no] rsvp
lsp-template p2mp-lsp-template-name
[no] shutdown

3.7.1.8. Routed VPLS Commands

config
— service
vpls service-id [customer customer-id] [vpn vpn-id] [m-vpls] [b-vpls | i-vpls] [etree] [name name] [create]
[no] igmp-snooping
[no] mrouter-port
[no] mld-snooping
[no] mrouter-port

3.7.1.9. Multi-Chassis Redundancy Commands

— config
[no] peer ip-address
[no] sync
[no] igmp-snooping
[no] mld-snooping
pim-snooping [saps] [spoke-sdps]
port [port-id | lag-id] [sync-tag sync-tag] [create]
— no port [port-id | lag-id]
range encap-range [sync-tag sync-tag]
— no range encap-range
sdp sdp-id [sync-tag sync-tag] [create]
— no sdp sdp-id
range vc-id-range [sync-tag sync-tag]
— no range vc-id-range
[no] shutdown

3.7.2. Command Descriptions

3.7.2.1. Generic Commands

shutdown

Syntax 
[no] shutdown
Context 
config>redundancy>multi-chassis>peer>sync
config>service>vpls
config>service>vpls>bgp-ad
config>service>vpls>eth-cfm>mep
config>service>vpls>gsmp
config>service>vpls>gsmp>group
config>service>vpls>gsmp>group>neighbor
config>service>vpls>igmp-snooping
config>service>vpls>igmp-snooping>mvr
config>service>vpls>interface
config>service>vpls>mac-move
config>service>vpls>mesh-sdp
config>service>vpls>mesh-sdp>eth-cfm>mep
config>service>vpls>mld-snooping
config>service>vpls>mld-snooping>mvr
config>service>vpls>mrp
config>service>vpls>sap
config>service>vpls>sap>arp-host
config>service>vpls>sap>dhcp>proxy
config>service>vpls>sap>eth-cfm>mep
config>service>vpls>sap>igmp-snooping>mcac>mc-constraints
config>service>vpls>sap>mld-snooping>mcac>mc-constraints
config>service>vpls>sap>spb
config>service>vpls>sap>stp
config>service>vpls>sap>sub-sla-mgmt
config>service>vpls>spb>level
config>service>vpls>split-horizon-group
config>service>vpls>spoke-sdp
config>service>vpls>spoke-sdp>eth-cfm>mep
config>service>vpls>spoke-sdp>spb
config>service>vpls>spoke-sdp>stp
config>service>vpls>stp
config>redundancy>multi-chassis>peer>sync
Description 

This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics.

The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they may be deleted.

Services are created in the administratively down (shutdown) state. When a no shutdown command is entered, the service becomes administratively up and then tries to enter the operationally up state. Default administrative states for services and service entities is described below in Special Cases.

The no form of this command places the entity into an administratively enabled state.

Special Cases 
Service Admin State—
Bindings to an SDP within the service will be put into the out-of-service state when the service is shut down. While the service is shut down, all customer packets are dropped and counted as discards for billing and debugging purposes.
Service Operational State—
A service is regarded as operational providing that two SAPs or one SDP is operational.
SDP (global)—
When an SDP is shut down at the global service level, all bindings to that SDP are put into the out-of-service state and the SDP itself is put into the administratively and operationally down states. Packets that would normally be transmitted using this SDP binding will be discarded and counted as dropped packets.
SDP (service level)—
Shutting down an SDP within a service only affects traffic on that service from entering or being received from the SDP. The SDP itself may still be operationally up for other services.
SDP Keepalives—
Enables SDP connectivity monitoring keepalive messages for the SDP ID. Default state is disabled (shutdown), in which case the operational state of the SDP ID is not affected by the keepalive message state.
VPLS SAPs and SDPs—
SAPs are created in a VPLS and SDPs are bound to a VPLS in the administratively up default state. The created SAP will attempt to enter the operationally up state. An SDP will attempt to go into the in-service state when bound to the VPLS.
Routed VPLS with forward-ipv4-multicast-to-ip-int and IGMP Snooping—
To enable IGMP snooping (configured using igmp-snooping no shutdown) in a routed VPLS supporting the forwarding of multicast traffic from the VPLS to the IP interface (configured using forward-ipv4-multicast-to-ip-int), it is necessary to enable IGMP on the routed VPLS IP interface.
Routed VPLS with forward-ipv6-multicast-to-ip-int and MLD Snooping—
To enable MLD snooping (configured using mld-snooping no shutdown) in a routed VPLS supporting the forwarding of multicast traffic from the VPLS to the IP interface (configured using forward-ipv6-multicast-to-ip-int) it is necessary to enable MLD on the routed VPLS IP interface.

description

Syntax 
description description-string
no description
Context 
config>service>vpls
config>service>vpls>sap>dhcp6
config>service>vpls>gsmp>group
config>service>vpls>gsmp>group>neighbor
config>service>vpls>igmp-snooping>mvr
config>service>vpls>split-horizon-group
config>service>vpls>mesh-sdp
config>service>vpls>spoke-sdp
config>service>vpls>sap>dhcp
config>service>vpls>mld-snooping>mvr
Description 

This command creates a text description stored in the configuration file for a configuration context.

The description command associates a text string with a configuration context to help identify the content in the configuration file.

The no form of this command removes the string from the configuration.

Parameters 
description-string—
The description character string. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

description

Syntax 
description long-description-string
no description
Context 
config>service>vpls>interface
config>service>vpls>sap
Description 

This command creates a text description stored in the configuration file for a configuration context.

The description command associates a text string with a configuration context to help identify the content in the configuration file.

The no form of this command removes the string from the configuration.

Parameters 
long-description-string—
The description character string. Allowed values are any string up to 160 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

3.7.2.2. VPLS Service Commands

fdb-table-size

Syntax 
fdb-table-size table-size
no fdb-table-size
Context 
config>service>system
Description 

This command configures the maximum system FDB table size, which is dependent on the chassis type. CPMs with at least 16 GB of memory are required when exceeding 500k MAC addresses in a system. The table size cannot be reduced below its default value, which is also chassis-dependent.

The maximum system FDB table size also limits the maximum FDB table size of any card within the system.

The no version of this command sets the table size to its default.

The command default depends on the chassis type and available memory.

Parameters 
table-size —
Specifies the maximum system FDB table size.
Values—
255999 to 2047999

 

vpls

Syntax 
vpls service-id [customer customer-id] [vpn vpn-id] [m-vpls] [b-vpls | i-vpls] [etree] [name name] [create]
no vpls service-id
Context 
config>service
Description 

This command creates or edits a Virtual Private LAN Services (VPLS) instance. The vpls command is used to create or maintain a VPLS service. If the service-id does not exist, a context for the service is created. If the service-id exists, the context for editing the service is entered.

A VPLS service connects multiple customer sites together acting like a zero-hop, Layer 2 switched domain. A VPLS is always a logical full mesh.

When creating a service, you must enter the customer keyword and specify a customer-id to associate the service with a customer. The customer-id must already exist, having been created using the customer command in the service context. The customer-id must already exist having been created using the customer command in the service context. Once a service has been created with a customer association, it is not possible to edit the customer association. The service must be deleted and re-created with a new customer association.

To create a management VPLS on the 7450 ESS, the m-vpls keyword must be specified. See section Hierarchical VPLS Redundancy for an introduction to the concept of management VPLS.

Once a service is created, the use of the customer customer-id is optional for navigating into the service configuration context. Attempting to edit a service with the incorrect customer-id specified will result in an error.

More than one VPLS service may be created for a single customer ID.

By default, no VPLS instances exist until they are explicitly created.

The no form of this command deletes the VPLS service instance with the specified service-id. The service cannot be deleted until all SAPs and SDPs defined within the service ID have been shutdown and deleted, and the service has been shutdown.

Parameters 
service-id—
Specifies unique service identification number identifying the service in the service domain. This ID must be unique to this service and may not be used for any other service of any type. The service-id must be the same number used for every router on which this service is defined.
Values—
service-id: 1 to 2147483647 svc-name: 64 characters maximum

 

customer customer-id
Specifies the customer ID number to be associated with the service. This parameter is required on service creation and optional for service editing or deleting.
Values—
1 to 2147483647

 

vpn vpn-id—
Specifies the VPN ID number which allows you to identify virtual private networks (VPNs) by a VPN identification number
Values—
1 to 2147483647

 

Default—
null (0)
m-vpls—
Specifies a management VPLS
e-tree—
Specifies a VPLS service as an E-Tree VPLS. E-Tree VPLS services have root and leaf-ac SAPs/SDP bindings and root-leaf-tag SAPs/SDP bindings for E-Tree interconnection. The access (AC) root SAP behaves as a normal VPLS SAP. The AC leaf SAP is restricted to communication only with root-connected services. AC leaf and root SAPs are externally normal SAPs. The AC root SDP bind behaves as a normal VPLS SDP bind. The AC leaf SDP bind is restricted to communication only with root-connected services. AC leaf and root SDP bindings are externally normal SDPs bindings.

In the E-Tree VPLS, the root-ac SAP/SDP bindings can communicate with other root-ac and leaf-ac SAP/SDP bind services locally and remotely. Root originated traffic is marked internally with a root indication and root tagged externally on tag SAP/SDP binds. The leaf-ac SAP/SDP bindings can communicate with other root SAP/SDP bindings locally and remotely. Leaf originated traffic is marked internally with a leaf indication and tagged externally on leaf tag SAP/SDP bindings.

There may be any number of AC SAPs of root or leaf up to typical SAP limits. Network Side tag SAPs for root-leaf use additional resources. These tag SAPs used two tags one for Root and one for Leaf. Network side tag SDPs use a hard coded tag of 1 for root and 2 for leaf. AC SDP bindings are designated as root or leaf SDP bindings but carry no tags marking traffic on the egress frames.

An E-Tree SAP types are specified at creation time. To change the type of a E-Tree SAP the SAP must be removed and re-created.

b-vpls | i-vpls—
Creates a backbone-vpls or ISID-vpls
name name—
Configures an optional service name identifier, up to 64 characters, to a given service. This service name can then be used in configuration references, display, and show commands throughout the system. A defined service name can help the service provider or administrator to identify and manage services within the SR OS platforms.

To create a service, you must assign a service ID; however, after it is created, either the service ID or the service name can be used to identify and reference a service.

If a name is not specified at creation time, then SR OS assigns a string version of the service-id as the name.

Values—
name: 64 characters maximum

 

backbone-vpls

Syntax 
backbone-vpls vpls-id[:isid]
no backbone-vpls
Context 
config>service>vpls>pbb
Description 

This command associated the I-VPLS with the B-VPLS service. The ISID value is used to mux/demux packets for the VPLS flowing through the B-VPLS.

Parameters 
vpls-id—
This value represents the VPLS ID value associated with the B-VPLS
isid—
Defines ISID associated with the I-VPLS
Default—
The default is the service-id
Values—
0 to 16777215

 

stp

Syntax 
[no] stp
Context 
config>service>vpls>pbb>backbone-vpls
Description 

This command enables STP on the backbone VPLS service.

The no form of the command disables STP on the backbone VPLS service.

block-on-mesh-failure

Syntax 
[no] block-on-mesh-failure
Context 
config>service>vpls>spoke-sdp
config>service>vpls>endpoint
Description 

This command enables blocking (brings the entity to an operationally down state) after all configured SDPs or endpoints are in operationally down state. This event is signaled to corresponding T-LDP peer by withdrawing service label (status-bit-signaling non-capable peer) or by setting “PW not forwarding” status bit in T-LDP message (status-bit-signaling capable peer).

Default 

no block-on-mesh-failure

bpdu-translation

Syntax 
bpdu-translation {auto | auto-rw | pvst | pvst-rw | stp}
no bpdu-translation
Context 
config>service>vpls>spoke-sdp
config>service>vpls>sap
Description 

This command enables the translation of BPDUs to a specified format, meaning that all BPDUs transmitted on a specified SAP or spoke-SDP will have a specified format.

The no form of this command reverts to the default.

Default 

no bpdu-translation

Parameters 
auto—
Specifies that appropriate format will be detected automatically, based on type of BPDUs received on such port.
auto-rw—
Specifies that appropriate format will be detected automatically and the VLAN ID will be rewritten as follows:
  1. BPDU sent on egress of dot1q SAP will contain the VLAN ID of the SAP in BDPU-PVID TLV
  2. BPDU sent on egress of default QinQ SAP will contain the outer VLAN ID of the SAP in BDPU-PVID TLV
  3. BPDU sent on egress of QinQ SAP will contain the inner VLAN ID of the SAP in BDPU-PVID TLV
pvst—
Specifies the BPDU-format as PVST. Note: the correct VLAN tag is included in the payload (depending on encapsulation value of outgoing SAP).
pvst-rw—
Specifies the BPDU-format as PVST. The VLAN ID will be rewritten as follows:
  1. BPDU sent on egress of dot1q SAP will contain the VLAN ID of the SAP in BDPU-PVID TLV
  2. BPDU sent on egress of default QinQ SAP will contain the outer VLAN ID of the SAP in BDPU-PVID TLV
  3. BPDU sent on egress of QinQ SAP will contain the inner VLAN ID of the SAP in BDPU-PVID TLV
stp—
Specifies the BPDU-format as STP.

calling-station-id

Syntax 
calling-station-id {mac | remote-id | sap-id | sap-string}
no calling-station-id
Context 
config>service>vpls>sap
Description 

This command enables the inclusion of the calling-station-id attribute in RADIUS authentication requests and RADIUS accounting messages.

The no form of the command reverts to the default.

Default 

no calling-station-id

Parameters 
mac—
Specifies that the mac-address will be sent.
remote-id—
Specifies that the remote-id will be sent.
sap-id—
Specifies that the sap-id will be sent.
sap-string—
Specifies that the value is the inserted value set at the SAP level. If no calling-station-id value is set at the SAP level, the calling-station-id attribute will not be sent.

lag-link-map-profile

Syntax 
lag-link-map-profile link-map-profile-id
no lag-link-map-profile
Context 
config>service>vpls>sap
Description 

This command assigns a pre-configured lag link map profile to a SAP/network interface configured on a LAG or a PW port that exists on a LAG. Once assigned/unassigned, the SAP/network interface egress traffic will be re-hashed over LAG as required by the new configuration.

The no form of this command reverts the SAP/network interface to use per-flow, service or link hash as configured for the service/LAG.

Default 

no lag-link-map-profile

Parameters 
link-map-profile-id—
An integer from 1 to 64 that defines a unique lag link map profile on which the LAG the SAP/network interface exist.

l2pt-termination

Syntax 
l2pt-termination [cdp] [dtp] [pagp] [stp] [udld] [vtp]
no l2pt-termination
Context 
config>service>vpls>spoke-sdp
config>service>vpls>sap
Description 

This command enables Layer 2 Protocol Tunneling (L2PT) termination on a specified SAP or spoke-SDP.

This feature can be enabled only if STP is disabled in the context of the specified VPLS service.

The no form of the command reverts to the default.

Default 

no l2pt-termination

Parameters 
cdp—
Specifies the Cisco discovery protocol
dtp—
Specifies the dynamic trunking protocol
pagp—
Specifies the port aggregation protocol
stp—
Specifies all spanning tree protocols: stp, rstp, mstp, pvst (default)
udld—
Specifies unidirectional link detection
vtp—
Specifies the virtual trunk protocol

mcr-default-gtw

Syntax 
mcr-default-gtw
Context 
config>service>vpls
Description 

This command enters the context to configure the default gateway information when using Dual Homing in L2-TPSDA. The IP and MAC address of the default gateway used for subscribers on an L2 MC-Ring are configured in this context. After a ring heals or fails, the system will send out a gratuitous ARP on an active ring SAP in order to attract traffic from subscribers on the ring with connectivity to that SAP.

ip

Syntax 
ip address
no ip
Context 
config>service>vpls>mcr-default-gtw
Description 

This command relates to a system configured for Dual Homing in L2-TPSDA. It defines the IP address used when the system sends out a gratuitous ARP on an active SAP after a ring heals or fails in order to attract traffic from subscribers on the ring with connectivity to that SAP.

The no form of the command reverts to the default.

Default 

no ip

Parameters 
address—
Specifies the IP address in a.b.c.d. format.

mac

Syntax 
mac ieee-address
no mac
Context 
config>service>vpls>mcr-default-gtw
Description 

This command relates to a system configured for Dual Homing in L2-TPSDA. It defines the MAC address used when the system sends out a gratuitous ARP on an active SAP after a ring heals or fails in order to attract traffic from subscribers on the ring with connectivity to that SAP.

The no form of the command reverts to the default.

Default 

no mac

Parameters 
ieee-address—
Specifies the address in xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx format (cannot be all zeros)

dhcp-python-policy

Syntax 
dhcp-python-policy policy-name
no dhcp-python-policy
Context 
config>service>vpls>sap
Description 

This command specifies the name of the Python policy. The Python policy is created in the config>python>python-policy policy-name context.

The no form of the command reverts to the default.

Default 

none

Parameters 
policy-name—
Specifies a Python policy name up to 32 characters in length

dhcp6-user-db

Syntax 
dhcp6-user-db local-user-db-name
no dhcp6-user-db
Context 
config>service>vpls>sap
Description 

This command assigns a local user database for DHCP6 clients (capture SAP only).

The no form of the command removes the name from the configuration.

Default 

none

Parameters 
local-user-db-name—
Specifies a local user database name up to 32 characters in length

dhcp6

Syntax 
dhcp6
Context 
config>service>vpls>sap
Description 

This command enters the context to configure DHCP6 parameters for this SAP.

interface-id

Syntax 
interface-id [ascii-tuple]
interface-id ifindex
interface-id sap-id
interface-id string string
no interface-id
Context 
config>service>ies>if>ipv6>dhcp6>option
Description 

This command configure the interface-id sub-option of the DHCP6 Relay packet.

The no form of the command disables the sending of interface ID options in the DHCPv6 relay packet

Parameters 
ascii-tuple—
Specifies that the ASCII-encoded concatenated tuple will be used which consists of the access-node-identifier, service-id, and interface-name, separated by “|”
vlan-ascii-tuple—
Specifies that the format will include VLAN ID and dot1p bits as well as what is included in ascii-tuple already. The format is supported on dot1q-encapsulated ports only. Therefore, when the option 82 bits are stripped, dot1p bits will be copied to the Ethernet header of an outgoing packet.
mac—
This keyword specifies the MAC address of the remote end is encoded in the sub-option

disable-aging

Syntax 
[no] disable-aging
Context 
config>service>vpls
config>service>vpls>spoke-sdp
config>service>vpls>sap
config>service>template>vpls-template
Description 

This command disables MAC address aging across a VPLS service or on a VPLS service SAP or spoke-SDP.

Like in a Layer 2 switch, learned MACs can be aged out if no packets are sourced from the MAC address for a period of time (the aging time). In each VPLS service instance, there are independent aging timers for local learned MAC and remote learned MAC entries in the VPLS forwarding database (FDB). The disable-aging command turns off aging for local and remote learned MAC addresses.

When no disable-aging is specified for a VPLS, it is possible to disable aging for specific SAPs and/or spoke-SDPs by entering the disable-aging command at the appropriate level.

When the disable-aging command is entered at the VPLS level, the disable-aging state of individual SAPs or SDPs will be ignored.

The no form of this command enables aging on the VPLS service.

Default 

no disable-aging

disable-learning

Syntax 
[no] disable-learning
Context 
config>service>vpls
config>service>vpls>sap
config>service>vpls>spoke-sdp
config>service>template>vpls-template
Description 

This command disables learning of new MAC addresses in the VPLS forwarding database (FDB) for the service instance, SAP instance or spoke-SDP instance.

When disable-learning is enabled, new source MAC addresses will not be entered in the VPLS service forwarding database. This is true for both local and remote MAC addresses.

When disable-learning is disabled, new source MAC addresses will be learned and entered into the VPLS forwarding database.

This parameter is mainly used in conjunction with the discard-unknown command.

The no form of this command enables learning of MAC addresses.

Default 

no disable-learning (Normal MAC learning is enabled)

discard-unknown

Syntax 
[no] discard-unknown
Context 
config>service>vpls
config>service>template>vpls-template
Description 

By default, packets with unknown destination MAC addresses are flooded. If discard-unknown is enabled at the VPLS level, packets with unknown destination MAC address will be dropped instead (even when configured FDB size limits for VPLS or SAP are not yet reached).

The no form of this command allows flooding of packets with unknown destination MAC addresses in the VPLS.

Default 

no discard-unknown — Packets with unknown destination MAC addresses are flooded.

dist-cpu-protection

Syntax 
dist-cpu-protection policy-name
no dist-cpu-protection
Context 
config>service>vpls>sap
Description 

This command assigns a Distributed CPU Protection (DCP) policy to the SAP. Only a valid existing DCP policy can be assigned to a SAP or a network interface (this rule does not apply to templates, such as an msap-policy template).

Default 

If no dist-cpu-protection policy is assigned to a SAP, then the default access DCP policy (_default-access-policy) is used. If no DCP functionality is required on the SAP, then an empty DCP policy can be created and explicitly assigned to the SAP.

Parameters 
policy-name—
Specifies the name of the DCP policy up to 32 characters in length

endpoint

Syntax 
endpoint endpoint-name [create]
no endpoint
Context 
config>service>vpls
Description 

This command configures a service endpoint.

Parameters 
endpoint-name—
Specifies an endpoint name up to 32 characters in length
create—
This keyword is mandatory while creating a service endpoint

description

Syntax 
description description-string
no description
Context 
config>service>vpls>endpoint
Description 

This command creates a text description stored in the configuration file for a configuration context.

The description command associates a text string with a configuration context to help identify the content in the configuration file.

The no form of this command removes the string from the configuration.

Default 

No description associated with the configuration context.

Parameters 
description-string—
The description character string. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

auto-learn-mac-protect

Syntax 
[no] auto-learn-mac-protect
Context 
config>service>vpls>endpoint
config>service>vpls>mesh-sdp
config>service>vpls>sap
config>service>vpls>split-horizon-group
config>service>vpls>spoke-sdp
Description 

This command specifies whether to enable automatic population of the MAC protect list with source MAC addresses learned on the associated with this SHG. For more information, see Auto-Learn MAC Protect.

The no form of the command disables the automatic population of the MAC protect list.

Default 

auto-learn-mac-protect

ignore-standby-signaling

Syntax 
[no] ignore-standby-signaling
Context 
config>service>vpls>endpoint
config>service>vpls>spoke-sdp
Description 

When this command is enabled, the node ignores the standby-bit received from the TLDP peers for the specific spoke-SDP and performs internal tasks without taking it into account.

This command is present at the endpoint level and the spoke-SDP level. If the spoke-SDP is part of the explicit-endpoint, this setting cannot be changed at the spoke-SDP level. The existing spoke-SDP will become part of the explicit-endpoint only if the setting is not conflicting. The newly created spoke-SDP, which is a part of the specified explicit-endpoint, will inherit this setting from the endpoint configuration.

Default 

disabled

revert-time

Syntax 
revert-time revert-time | infinite
no revert-time
Context 
config>service>vpls>endpoint
Description 

This command configures the time to wait before reverting to primary spoke-SDP.

In a regular endpoint the revert-time setting affects just the pseudowire defined as primary (precedence 0). For a failure of the primary pseudowire followed by restoration the revert-timer is started. After it expires the primary pseudowire takes the active role in the endpoint. This behavior does not apply for the case when both pseudowires are defined as secondary. For example, if the active secondary pseudowire fails and is restored it will stay in standby until a configuration change or a force command occurs.

Parameters 
revert-time—
Specifies the time to wait, in seconds, before reverting back to the primary spoke-SDP defined on this service endpoint, after having failed over to a backup spoke-SDP
Values—
0 to 600

 

infinite —
Specifying this keyword makes endpoint non-revertive

static-mac

Syntax 
static-mac ieee-address [create]
no static-mac
Context 
config>service>vpls>endpoint
Description 

This command assigns a static MAC address to the endpoint. In the FDB, the static MAC is then associated with the active spoke-SDP.

Default 

none

Parameters 
ieee-address—
Specifies the static MAC address to the endpoint
Values—
6-byte mac-address (xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx) Cannot be all zeros

 

create—
This keyword is mandatory while creating a static MAC

suppress-standby-signaling

Syntax 
[no] suppress-standby-signaling
Context 
config>service>vpls>endpoint
Description 

When this command is enabled, the pseudowire standby bit (value 0x00000020) will not be sent to T-LDP peer when the specified spoke is selected as a standby. This allows faster switchover as the traffic will be sent over this SDP and discarded at the blocking side of the connection. This is particularly applicable to multicast traffic.

Default 

enabled

propagate-mac-flush

Syntax 
[no] propagate-mac-flush
Context 
config>service>vpls
Description 

This command enabled propagation of mac-flush messages received from the specified T-LDP on all spoke and mesh-SDPs within the context of the VPLS service. The propagation will follow split-horizon principles and any data-path blocking in order to avoid looping of these messages.

Default 

disabled

fdb-table-high-wmark

Syntax 
[no] fdb-table-high-wmark high-water-mark
Context 
config>service>vpls
config>service>template>vpls-template
Description 

This command specifies the value to send logs and traps when the threshold is reached.

Parameters 
high-water-mark—
Specifies the value to send logs and traps when the threshold is reached
Values—
0 to 100

 

Default—
95%

fdb-table-low-wmark

Syntax 
[no] fdb-table-low-wmark low-water-mark
Context 
config>service>vpls
config>service>template>vpls-template
Description 

This command specifies the value to send logs and traps when the threshold is reached.

Parameters 
low-water-mark—
Specifies the value to send logs and traps when the threshold is reached
Values—
0 to 100

 

Default—
90%

fdb-table-size

Syntax 
fdb-table-size table-size
no fdb-table-size [table-size]
Context 
config>service>vpls
config>service>template>vpls-template
Description 

This command specifies the maximum number of MAC entries in the forwarding database (FDB) for the VPLS instance on this node.

The fdb-table-size specifies the maximum number of forwarding database entries for both learned and static MAC addresses for the VPLS instance.

The no form of this command returns the maximum FDB table size to default.

Default 

fdb-table-size 250

Parameters 
table-size—
Specifies the number of entries permitted in the forwarding database for this VPLS instance
Values—
7450 ESS, 7950 XRS, or 7750 SR-7, SR-12, SR-12e: 1 to 511999
7750 SR-e, SR-a: 1 to 250000

 

interface

Syntax 
[no] interface ip-int-name
Context 
config>service>vpls
Description 

This command creates an IP interface.

address

Syntax 
address ip-address[/mask] [netmask]
no address
Context 
config>service>vpls>interface
Description 

This command assigns an IP address, IP subnet, and broadcast address format to an IES IP router interface. Only one IP address can be associated with an IP interface.

An IP address must be assigned to each IES IP interface. An IP address and a mask are used together to create a local IP prefix. The defined IP prefix must be unique within the context of the routing instance. It cannot overlap with other existing IP prefixes defined as local subnets on other IP interfaces in the same routing context within the router.

The local subnet that the address command defines must be part of the services address space within the routing context using the config router service-prefix command. The default is to disallow the complete address space to services. Once a portion of the address space is allocated as a service prefix, that portion can be made unavailable for IP interfaces defined within the config router interface CLI context for network core connectivity with the exclude option in the config router service-prefix command.

The IP address for the interface can be entered in either CIDR (Classless Inter-Domain Routing) or traditional dotted decimal notation. The show commands display CIDR notation and is stored in configuration files.

By default, no IP address or subnet association exists on an IP interface until it is explicitly created.

Use the no form of this command to remove the IP address assignment from the IP interface. When the no address command is entered, the interface becomes operationally down.

Address

Admin State

Oper State

No address

up

down

No address

down

down

1.1.1.1

up

up

1.1.1.1

down

down

The operational state is a read-only variable and the only controlling variables are the address and admin states. The address and admin states are independent and can be set independently. If an interface is in an administratively up state and an address is assigned, it becomes operationally up and the protocol interfaces and the MPLS LSPs associated with that IP interface will be reinitialized.

Parameters 
ip-address—
The IP address of the IP interface. The ip-address portion of the address command specifies the IP host address that will be used by the IP interface within the subnet. This address must be unique within the subnet and specified in dotted decimal notation. Allowed values are IP netmask

The subnet mask in dotted decimal notation. When the IP prefix is not specified in CIDR notation, a space separates the ip-address from a traditional dotted decimal mask. The mask parameter indicates the complete mask that will be used in a logical ‘AND’ function to derive the local subnet of the IP address. Allowed values are dotted decimal addresses in the range 128.0.0.0 to 255.255.255.252. A mask of 255.255.255.255 is reserved for system IP addresses.

arp-timeout

Syntax 
arp-timeout seconds
no arp-timeout
Context 
config>service>vpls>interface
Description 

This command configures the minimum time in seconds an ARP entry learned on the IP interface will be stored in the ARP table. ARP entries are automatically refreshed when an ARP request or gratuitous ARP is seen from an IP host, otherwise, the ARP entry is aged from the ARP table. If arp-timeout is set to a value of zero seconds, ARP aging is disabled.

For the 7450 ESS or 7750 SR, when the arp-populate and lease-populate commands are enabled on an interface, the ARP table entries will no longer be dynamically learned, but instead by snooping DHCP ACK message from a DHCP server. In this case the configured arp-timeout value has no effect.

The default value for arp-timeout is 14400 seconds (4 hours).

The no form of this command restores arp-timeout to the default value.

Default 

14400 seconds

Parameters 
seconds—
The minimum number of seconds a learned ARP entry will be stored in the ARP table, expressed as a decimal integer. A value of zero specifies that the timer is inoperative and learned ARP entries will not be aged.
Values—
0 to 65535

 

hold-time

Syntax 
hold-time
Context 
config>service>vpls>interface
Description 

This command creates the CLI context to configure interface level hold-up and hold-down timers for the associated IP interface.

The up timer controls a delay for the associated IPv4 or IPv6 interface so that the system will delay the deactivation of the associated interface for the specified amount of time.

The down timer controls a delay for the associated IPv4 or IPv6 interface so that the system will delay the activation of the associated interface for the specified amount of time

up

Syntax 
up ip seconds
no up ip
up ipv6 seconds
no up ipv6
Context 
config>service>vpls>interface>hold-time
Description 

This command will cause a delay in the deactivation of the associated IP interface by the specified number of seconds. The delay is invoked whenever the system attempts to bring the associated IP interface down.

The no form of the command removes the command from the active configuration and removes the delay in deactivating the associated IP interface. If the configuration is removed during a delay period, the currently running delay will continue until it expires.

Parameters 
seconds—
The time delay, in seconds, to make the interface operational.
Values—
1 to 1200

 

down

Syntax 
down ip seconds [init-only]
no up ip
up ipv6 seconds [init-only]
no up ipv6
Context 
config>service>vpls>interface>hold-time
Description 

This command will cause a delay in the activation of the associated IP interface by the specified number of seconds. The delay is invoked whenever the system attempts to bring the associated IP interface up, unless the init-only option is configured. If the init-only option is configured, the delay is only applied when the IP interface is first configured or after a system reboot.

The no form of the command removes the command from the active configuration and removes the delay in activating the associated IP interface. If the configuration is removed during a delay period, the currently running delay will continue until it completes.

Parameters 
seconds—
The time delay, in seconds, to make the interface operational
Values—
1 to 1200

 

init-only—
Specifies that the down delay is only applied when the interface is configured or after a reboot
Values—
1 to 1200

 

mac

Syntax 
mac ieee-address
no mac
Context 
config>service>vpls>interface
Description 

This command assigns a specific MAC address to a VPLS IP interface.

For Routed Central Office (CO), a group interface has no IP address explicitly configured but inherits an address from the parent subscriber interface when needed. For example, a MAC will respond to an ARP request when an ARP is requested for one of the IPs associated with the subscriber interface through the group interface.

The no form of the command returns the MAC address of the IP interface to the default value.

Default 

The system chassis MAC address.

Parameters 
ieee-address —
Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee, and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.

static-arp

Syntax 
static-arp ieee-mac-addr unnumbered
no static-arp unnumbered
Context 
config>service>vpls>interface
Description 

This command configures a static address resolution protocol (ARP) entry associating a subscriber IP address with a MAC address for the core router instance. A static ARP can only be configured if it exists on the network attached to the IP interface.

If an entry for a particular IP address already exists and a new MAC address is configured for the IP address, the existing MAC address will be replaced with the new MAC address.

The no form of the command removes a static ARP entry.

Default 

None

Parameters 
ip-address—
Specifies the IP address for the static ARP in dotted decimal notation
ieee-mac-address —
Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.
unnumbered—
Specifies the static ARP MAC for an unnumbered interface. Unnumbered interfaces support dynamic ARP. Once this command is configured, it overrides any dynamic ARP.

static-mac

Syntax 
static-mac
Context 
config>service>vpls
Description 

A set of conditional static MAC addresses can be created within a VPLS supporting bgp-evpn. Conditional static macs are also supported in B-VPLS with SPBM. Conditional Static MACs are dependent on the SAP/SDP state.

This command allows assignment of a set of conditional static MAC addresses to a SAP/ spoke-SDP. In the FDB, the static MAC is then associated with the active SAP or spoke-SDP.

Static MACs are used for PBB Epipe and I-VPLS services that may terminate external to SPBM. If this is configured under a Control B-VPLS the interface referenced will not use IS-IS for this neighbor. This may also be configured under a User B-VPLS where the corresponding interface is not supported under the Control B-VPLS.

Static MACs configured in a bgp-evpn service are advertised as protected (EVPN will signal the mac as protected).

mac

Syntax 
mac ieee-address [create] black-holemac ieee-address [create] sap sap-id monitor {fwd-status}
mac ieee-address [create] spoke-sdp sdp-id:vc-id monitor {fwd-status}
no mac ieee-address
Context 
config>service>vpls>static-mac
Description 

This command assigns a conditional static MAC address entry to an SPBM B-VPLS SAP/spoke-SDP allowing external MACs for single and multi-homed operation.

For the 7450 ESS or 7750 SR, this command also assigns a conditional static MAC address entry to an EVPN VPLS SAP/spoke-SDP.

Static MACs are used for PBB Epipe and I-VPLS services that may terminate external to SPBM. If this is configured under a Control B-VPLS the interface referenced will not use IS-IS for this neighbor. This may also be configured under a User B-VPLS where the corresponding interface is not supported under the Control B-VPLS.

Default 

none

Parameters 
ieee-address —
Specifies the static MAC address to an SPBM/sdp-binding interface
Values—
6-byte mac-address (xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx) Cannot be all zeros.

 

sap-id—
Specifies the SAP identifier
sdp-id—
Specifies the SDP identifier
Values—
1 to 17407

 

vc-id—
Specifies the virtual circuit identifier
Values—
1 to 4294967295

 

create—
This keyword is mandatory while creating a static MAC
fwd-status —
Specifies that this static mac is based on the forwarding status of the SAP or spoke-SDP for multi-homed operation.
black-hole—
Specifies for TLS FDB entries defined on a local SAP the value 'sap', remote entries defined on an SDP have the value 'sdp'.

unnumbered

Syntax 
unnumbered [ip-int-name | ip-address]
no unnumbered
Context 
config>service>vpls>if
Description 

This command configures the interface as an unnumbered interface.

Parameters 
ip-int-name—
Specifies the name of the IP interface. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes
ip-address—
Specifies an IP address which must be a valid address of another interface

isid-policy

Syntax 
isid-policy
no isid-policy
Context 
config>service>vpls
Description 

This command configures ISID policies for individual ISIDs or ISID ranges in a B-VPLS using SPBM. The ISIDs may belong to I-VPLS services or may be static-isids defined on this node. Multiple entry statements are allowed under a isid-policy. ISIDs that are declared as static do not require and isid-policy unless the ISIDs are not to be advertised.

isid-policy allows finer control of ISID multicast but is not typically required for SPBM operation. Use of ISID policies can cause additional flooding of multicast traffic.

Default 

no default

entry

Syntax 
entry range-entry-id [create]
no entry range-entry-id
Context 
config>service>vpls>isid-policy
Description 

This command creates or edits an ISID policy entry. Multiple entries can be created using unique entry-id numbers within the ISID policy.

entry-id — Specifies an entry-id uniquely identifies a ISID range and the corresponding actions. This allows users to insert a new entry in an existing policy without requiring renumbering of all the existing entries.

The following rules govern the usage of multiple entry statements:

  1. overlapping values are allowed:
    1. isid from 301 to 310
    2. isid from 305 to 315
    3. isid 316
  2. the minimum and maximum values from overlapping ranges are considered and displayed. The above entries will be equivalent with “isid from 301 to 316” statement.
  3. there is no consistency check with the content of ISID statements from other entries. The entries will be evaluated in the order of their IDs and the first match will cause the implementation t o execute the associated action for that entry.

no isid - removes all the previous statements under one entry.

no isid value | from value to higher-value - removes a specific ISID value or range. Must match a previously used positive statement: for example, if the command “isid 16 to 100” was used using “no isid 16 to 50”, it will not work but “no isid 16 to 100 will be successful.

Values 1 to 65535

Default 

No entry

Parameters 
range-entry-id—
Specifies the ID of the ISID policy to be created or edited
Values—
1 to 8191

 

create—
Required when first creating the configuration context. Once the context is created, one can navigate into the context without the create keyword.

advertise-local

Syntax 
[no] advertise-local
Context 
config>service>vpls>isid-policy>entry
Description 

The no advertise-local option prevents the advertisement of any locally defined I-VPLS ISIDs or static-isids in the range in a B-VPLS. For I-VPLS services or static-isids that are primarily unicast traffic, the use-def-mcast and no advertise-local options allows the forwarding of ISID based multicast frames locally using the default multicast. The no advertise-local option also suppresses this range of ISIDs from being advertised in ISIS. When using the use-def-mcast and no advertise-local policies, the ISIDs configured under this static-isid declarations SPBM treats the ISIDs as belonging to the default tree.

Default 

advertise-local

range

Syntax 
range isid [to isid]
Context 
config>service>vpls>isid-policy>entry
Description 

This command specifies an ISID or a Range of ISIDs in a B-VPLS. One range is allowed per entry.

Default 

no range

Parameters 
isid—
Specifies the ISID value in 24 bits. When singular, ISID identifies a particular ISID to be used for matching
Values—
0 to 16777215

 

to isid
Identifies upper value in a range of ISIDs to be used as matching criteria

use-def-mcast

Syntax 
[no] use-def-mcast
Context 
config>service>vpls>isid-policy>entry
Description 

The use-def-mcast option prevents local installation of the ISIDs in the range in the MFIB and uses the default multicast tree instead for a B-VPLS. In a node that does not have I-VPLS or static-isids, this command prevents the building of an MFIB entry for this ISID when received in a SPBM TLV and allows the broadcast of ISID based traffic on the default multicast tree. If an isid-policy exists, the core nodes can have this policy to prevent connectivity problems when some nodes are advertising an ISID and others are not. In a I-VPLS service if the customer MAC (C-MAC) is unknown, a frame will have the Multicast DA for an ISID (PBB-OUI + ISID) flooded on the default multicast tree and not pruned.

Default 

no use-def-mcast

load-balancing

Syntax 
load-balancing
Context 
config>service>vpls config>service>template>vpls-template
Description 

This command enables the load-balancing context to configure interface per-flow load balancing options that will apply to traffic entering this interface and egressing over a LAG/ECMP on system-egress. This is a per interface setting. For load-balancing options that can also be enabled on the system level, the options enabled on the interface level overwrite system level configurations.

Default 

not applicable

per-service-hashing

Syntax 
[no] per-service-hashing
Context 
config>service>vpls>load-balancing
config>service>template>vpls-template>load-balancing
Description 

This command enables on a per service basis, consistent per-service hashing for Ethernet services over LAG, over Ethernet tunnel (eth-tunnel) using loadsharing protection-type or over CCAG. Specifically, it enables the new hashing procedures for Epipe, VPLS, regular or PBB services.

The following algorithm describes the hash-key used for hashing when the new option is enabled:

  1. If the packet is PBB encapsulated (contains an I-TAG ethertype) at the ingress side, use the ISID value from the I-TAG
  2. If the packet is not PBB encapsulated at the ingress side
    1. For regular (non-PBB) VPLS and Epipe services, use the related service ID
    2. If the packet is originated from an ingress IVPLS or PBB Epipe SAP
  3. If there is an ISID configured use the related ISID value
  4. If there is no ISID yet configured use the related service ID
    1. For BVPLS transit traffic use the related flood list id
  5. Transit traffic is the traffic going between BVPLS endpoints
  6. An example of non-PBB transit traffic in BVPLS is the OAM traffic
  7. The above rules apply regardless of traffic type
    1. Unicast, BUM flooded without MMRP or with MMRP, IGMP snooped

The no form of this command implies the use of existing hashing options.

Default 

no per-service-hashing

spi-load-balancing

Syntax 
[no] spi-load-balancing
Context 
config>service>vpls>load-balancing config>service>template>vpls-template>load-balancing
Description 

This command enables use of the SPI in hashing for ESP/AH encrypted IPv4/v6 traffic. This is a per interface setting.

The no form disables the SPI function.

Default 

no spi-load-balancing

teid-load-balancing

Syntax 
[no] teid-load-balancing
Context 
config>service>vpls>load-balancing
config>service>template>vpls-template>load-balancing
Description 

This command enables inclusion of TEID in hashing for GTP-U/C encapsulates traffic for GTPv1/GTPv2. The no form of this command ignores TEID in hashing.

Default 

no teid-load-balancing

local-age

Syntax 
local-age aging-timer
no local-age
Context 
config>service>vpls
config>service>template>vpls-template
Description 

Specifies the aging time for locally learned MAC addresses in the forwarding database (FDB) for the Virtual Private LAN Service (VPLS) instance. In a VPLS service, MAC addresses are associated with a Service Access Point (SAP) or with a Service Distribution Point (SDP). MACs associated with a SAP are classified as local MACs, and MACs associated with an SDP are remote MACs.

Like in a Layer 2 switch, learned MACs can be aged out if no packets are sourced from the MAC address for a period of time (the aging time). In each VPLS service instance, there are independent aging timers for local learned MAC and remote learned MAC entries in the FDB. The local-age timer specifies the aging time for local learned MAC addresses.

The no form of this command returns the local aging timer to the default value.

Default 

local age 300 — Local MACs aged after 300 seconds.

Parameters 
aging-timer—
Specifies the aging time for local MACs expressed in seconds
Values—
60 to 86400

 

mac-move

Syntax 
[no] mac-move
Context 
config>service>vpls
config>service>template>vpls-template
Description 

This command enters the context to configure MAC move attributes. A sustained high re-learn rate can be a sign of a loop somewhere in the VPLS topology. Typically, STP detects loops in the topology, but for those networks that do not run STP, the mac-move feature is an alternative way to protect your network against loops.

When enabled in a VPLS, mac-move monitors the re-learn rate of each MAC. If the rate exceeds the configured maximum allowed limit, it disables the SAP where the source MAC was last seen. The SAP can be disabled permanently (until a shutdown/no shutdown command is executed) or for a length of time that grows linearly with the number of times the specified SAP was disabled. You have the option of marking a SAP as non-blockable in the config>service>vpls>sap>limit-mac-move or config>service>vpls>spoke-sdp>limit-mac-move contexts. This means that when the re-learn rate has exceeded the limit, another (blockable) SAP will be disabled instead.

The mac-move command enables the feature at the service level for SAPs and spoke-SDPs, as only those objects can be blocked by this feature. Mesh SDPs are never blocked, but their re-learn rates (sap-to-mesh/spoke-to-mesh or vice versa) are still measured.

The operation of this feature is the same on the SAP and spoke-SDP. For example, if a MAC address moves from SAP to SAP, from SAP to spoke-SDP, or between spoke-SDPs, one will be blocked to prevent thrashing. If the MAC address moves between a SAP and mesh SDP or spoke-SDP and mesh SDP combinations, the respective SAP or spoke-SDP will be blocked.

mac-move will disable a VPLS port when the number of relearns detected has reached the number of relearns needed to reach the move-frequency in the 5-second interval. For example, when the move-frequency is configured to 1 (relearn per second) mac-move will disable one of the VPLS ports when 5 relearns were detected during the 5-second interval because then the average move-frequency of 1 relearn per second has been reached. This can already occur in the first second if the real relearn rate is 5 relearns per second or higher.

The no form of this command disables MAC move.

mac-protect

Syntax 
mac-protect
Context 
config>service>vpls
Description 

This command indicates whether or not this MAC is protected on the MAC protect list. When enabled, the agent will protect the MAC from being learned or re-learned on a SAP, spoke-SDP or mesh-SDP that has restricted learning enabled. The MAC protect list is used in conjunction with restrict-protected-src, restrict-unprotected-dst and auto-learn-mac-protect.

Default 

disabled

mac

Syntax 
[no] mac ieee-address
Context 
config>service>vpls>mac-protect
Description 

This command adds a protected MAC address entry.

Parameters 
ieee-address—
Specifies the 48-bit MAC address in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee, and ff are hexadecimal numbers

mac-subnet-length

Syntax 
mac-subnet-length subnet-length
no mac-subnet-length
Context 
config>service>vpls
Description 

This command specifies the number of bits to be considered when performing MAC learning (MAC source) and MAC switching (MAC destination). Specifically, this value identifies how many bits, starting from the beginning of the MAC address are used. For example, if the mask-value of 28 is used, MAC learning will only do a lookup for the first 28 bits of the source MAC address when comparing with existing FDB entries. Then, it will install the first 28 bits in the FDB while zeroing out the last 20 bits of the MAC address. When performing switching in the reverse direction, only the first 28 bits of the destination MAC address will be used to perform a FDB lookup to determine the next hop.

The no form of this command switches back to full MAC lookup.

Parameters 
subnet-length—
Specifies the number of bits to be considered when performing MAC learning or MAC switching
Values—
24 to 48

 

mac-notification

Syntax 
mac-notification
Context 
config>service>vpls
Description 

This command controls the settings for the MAC notification message.

The mac-notification message must be generated under the following events:

  1. When enabled in the BVPLS using no shutdown, a MAC notification will be sent for every active MC-LAG link. The following 3 cases assume no shutdown in the BVPLS.
  2. Whenever a related MC-LAG link becomes active (the related MC-LAG link has at least 1 SAP associated with the BVPLS) if the MC-LAG peering is initialized and the PE peers are synchronized.
  3. First SAP on an active MC-LAG is associated (via IVPLS/Epipe) with the BVPLS
  4. The link between IVPLS/Epipe and BVPLS is configured and there are I-SAPs configured on an active MC-LAG link.

The MAC notification is not sent for the following events:

  1. Change of source-bmac or source-bmac-lsb
  2. On changes of use-sap-bmac parameter
  3. If MC-LAG peering is not (initialized and in sync).

count

Syntax 
[no] count value
Context 
config>service>vpls>mac-notification
Description 

This command configures how often MAC notification messages are sent.

Parameters 
value—
Specifies, in seconds, how often MAC notification messages are sent
Values—
1 to 10

 

Default—
Inherits the chassis level configuration from config>service>mac-notification

interval

Syntax 
[no] interval deci-seconds
Context 
config>service>vpls>mac-notification
Description 

This command controls the frequency of subsequent MAC notification messages.

Default 

Inherits the chassis level configuration from config>service>mac-notification

Parameters 
deci-seconds—
Specifies the frequency of subsequent MAC notification messages, in deciseconds
Values—
1 to 100

 

renotify

Syntax 
renotify value
no renotify
Context 
config>service>vpls>mac-notification
Description 

This command controls the periodic interval at which sets of MAC notification messages are sent. At each expiration of the renotify timer, a new burst of notification messages is sent, specifically <count> frames at <interval> deci-seconds.

Default 

no renotify

Parameters 
value—
Specifies the time interval between re-notification, in seconds
Values—
240 to 840

 

move-frequency

Syntax 
move-frequency frequency
no move-frequency
Context 
config>service>vpls>mac-move
config>service>template>vpls-template>mac-move
Description 

This command indicates the maximum rate at which MACs can be re-learned in the VPLS service, before the SAP where the moving MAC was last seen is automatically disabled in order to protect the system against undetected loops or duplicate MACs.

The no form of the command reverts to the default value.

Default 

move-frequency 2 (when mac-move is enabled). For example, 10 relearns in a 5 second period.

Parameters 
frequency—
Specifies the rate, in 5-second intervals for the maximum number of relearns
Values—
1 to 10

 

number-retries

Syntax 
number-retries number-retries
no number-retries
Context 
config>service>vpls>mac-move
config>service>template>vpls-template>mac-move
Description 

This command configures the number of times retries are performed for re-enabling the SAP/SDP.

Default 

number-retries 3

Parameters 
number-retries—
Specifies number of retries for re-enabling the SAP/SDP. A zero (0) value indicates unlimited number of retries.
Values—
0 to 255

 

primary-ports

Syntax 
primary-ports
Context 
config>service>vpls>mac-move
config>service>template>vpls-template>mac-move
Description 

This command enters the context to define primary VPLS ports. VPLS ports that were declared as secondary prior to the execution of this command will be moved from secondary port-level to primary port-level. Changing a port to the tertiary level can only be done by first removing it from the secondary port-level.

sap

Syntax 
sap [split-horizon-group group-name] [create] [capture-sap]
no sap sap-id
Context 
config>service>vpls>mac-move>primary-ports
config>service>vpls>mac-move>secondary-ports
Description 

This command declares a specified SAP as a primary (or secondary) VPLS port.

Parameters 
sap-id—
Specifies the physical port identifier portion of the SAP definition

spoke-sdp

Syntax 
[no] spoke-sdp spoke-id
Context 
config>service>vpls>mac-move>primary-ports
config>service>vpls>mac-move>secondary-ports
Description 

This command declares a specified spoke-SDP as a primary (or secondary) VPLS port.

Parameters 
spoke-id—
Specifies the SDP ID to configure as the primary VPLS port
Values—
1 to 17407

 

vc-id—
Specifies the virtual circuit identifier
Values—
1 to 4294967295

 

cumulative-factor

Syntax 
[no] cumulative-factor factor
Context 
config>service>vpls>mac-move>primary-ports
config>service>vpls>mac-move>secondary-ports
config>service>template>vpls-template>mac-move>primary-ports
config>service>template>vpls-template>mac-move>secondary-ports
Description 

This command defines a factor defining how many mac-relearn measurement periods can be used to measure mac-relearn rate. The rate must be exceeded during the defined number of consecutive periods before the corresponding port is blocked by the mac-move feature. The cumulative-factor of primary ports must be higher than cumulative-factor of secondary ports.

Default 

cumulative-factor 2 — secondary ports

cumulative-factor 3 — primary ports

Parameters 
factor—
Specifies the factor defining the number of mac-relearn measurement periods can be used to measure mac-relearn rate
Values—
2 to 10

 

secondary-ports

Syntax 
secondary-ports
Context 
config>service>vpls>mac-move
config>service>template>vpls-template>mac-move
Description 

This command opens configuration context for defining secondary vpls-ports. VPLS ports that were declared as primary prior to the execution of this command will be moved from primary port-level to secondary port-level. Changing a port to the tertiary level can only be done by first removing it from the primary port-level.

retry-timeout

Syntax 
retry-timeout timeout
no retry-timeout
Context 
config>service>vpls>mac-move
config>service>template>vpls-template>mac-move
Description 

This indicates the time in seconds to wait before a SAP that has been disabled after exceeding the maximum relearn rate is re-enabled.

It is recommended that the retry-timeout value is larger or equal to 5s * cumulative factor of the highest priority port so that the sequential order of port blocking will not be disturbed by re-initializing lower priority ports.

A zero value indicates that the SAP will not be automatically re-enabled after being disabled. If, after the SAP is reenabled it is disabled again, the retry timeout is increased with the provisioned retry timeout in order to avoid thrashing. For example, when retry-timeout is set to 15, it increments (15,30,45,60...).

The no form of the command reverts to the default value.

Default 

retry-timeout 10 (when mac-move is enabled)

Parameters 
timeout—
Specifies the time, in seconds, to wait before a SAP that has been disabled after exceeding the maximum relearn rate is reenabled
Values—
0 to 120

 

mcast-ipv6-snooping-scope

Syntax 
mcast-ipv6-snooping-scope {mac-based | sg-based}
Context 
config>service>vpls
Description 

This command specifies the forwarding scope used for IPv6 multicast traffic when PIM snooping for IPv6 is enabled.

By default, the scope is mac-based; IPv6 snooped multicast traffic is forwarded is based on the low-order 32 bits of the destination IPv6 address.

When the scope is configured as sg-based, the IPv6 snooped multicast traffic is forwarded based on both its full source (if specified in the join) and destination IPv6 address. SG-based forwarding is only supported on FP3- (or higher) based line cards.

PIM snooping for IPv6 must be disabled to change the forwarding mode within a VPLS service between mac-based and sg-based.

Default 

mcast-ipv6-snooping-scope mac-based

Parameters 
mac-based—
Enables forwarding for PIM-snooped IPv6 multicast traffic based on the low-order 32 bits of its destination IPv6 address.
sg-based—
Enables forwarding for PIM-snooped IPv6 multicast traffic based on its full source (if specified in the join) and destination IPv6 address.

mfib-table-high-wmark

Syntax 
[no] mfib-table-high-wmark high-water-mark
Context 
config>service>vpls
Description 

This command specifies the multicast FIB high watermark. When the percentage filling level of the multicast FIB exceeds the configured value, a trap is generated and/or a log entry is added.

Parameters 
high-water-mark—
Specifies the multicast FIB high watermark as a percentage
Values—
1 to 100

 

Default—
95

mfib-table-low-wmark

Syntax 
[no] mfib-table-low-wmark low-water-mark
Context 
config>service>vpls
Description 

This command specifies the multicast FIB low watermark. When the percentage filling level of the Multicast FIB drops below the configured value, the corresponding trap is cleared and/or a log entry is added.

Parameters 
low-water-mark —
Specifies the multicast FIB low watermark as a percentage
Values—
1 to 100

 

Default—
90

mfib-table-size

Syntax 
mfib-table-size size
no mfib-table-size
Context 
config>service>vpls
Description 

This command specifies the maximum number of (s,g) entries in the multicast forwarding database (MFIB) for this VPLS instance.

The mfib-table-size parameter specifies the maximum number of multicast database entries for both learned and static multicast addresses for the VPLS instance. When a table-size limit is set on the mfib of a service which is lower than the current number of dynamic entries present in the mfib then the number of entries remains above the limit.

The no form of this command removes the configured maximum MFIB table size.

Default 

no mfib-table-size

Parameters 
size —
Specifies the maximum number of (s,g) entries allowed in the Multicast FIB
Values—
1 to 16383

 

mld-snooping

Syntax 
mld-snooping
Context 
config>service>vpls
config>service>vpls>sap
config>service>vpls>spoke-sdp
config>service>vpls>mesh-sdp
config>service>vpls>bind
Description 

This command configures MLD snooping parameters.

remote-age

Syntax 
remote-age seconds
no remote-age
Context 
config>service>vpls
config>service>template>vpls-template
Description 

Specifies the aging time for remotely learned MAC addresses in the forwarding database (FDB) for the Virtual Private LAN Service (VPLS) instance. In a VPLS service, MAC addresses are associated with a Service Access Point (SAP) or with a Service Distribution Point (SDP). MACs associated with a SAP are classified as local MACs, and MACs associated with an SDP are remote MACs.

Like in a Layer 2 switch, learned MACs can be aged out if no packets are sourced from the MAC address for a period of time (the aging time). In each VPLS service instance, there are independent aging timers for local learned MAC and remote learned MAC entries in the FDB. The remote-age timer specifies the aging time for remote learned MAC addresses. To reduce the amount of signaling required between switches configure this timer larger than the local-age timer.

The no form of this command returns the remote aging timer to the default value.

Default 

remote age 900 — Remote MACs aged after 900 seconds

Parameters 
seconds—
Specifies the aging time for remote MACs expressed in seconds
Values—
60 to 86400

 

selective-learned-fdb

Syntax 
[no] selective-learned-fdb
Context 
config>service>vpls
Description 

This command determines which line cards FDB entries are allocated on for MAC addresses in the VPLS service in which the command is configured.

By default, FDB entries for MAC addresses in VPLS services are allocated on all line cards in the system. Enabling selective-learned-fdb causes FDB entries to be allocated only on the line cards on which the service has a configured object, which includes all line cards:

  1. on which a SAP is configured
  2. which have ports configured in a LAG SAP
  3. which have ports configured in an Ethernet tunnel SAP
  4. which have ports configured on a network interface (which also may be on a LAG) when the service has a mesh or spoke-SDP, VXLAN or EVPN-MPLS configured

Only MAC addresses with a type “L” or “Evpn” in the show output displaying the FDB can be allocated selectively, unless a MAC address configured as a conditional static MAC address is learned dynamically on an object other than its monitored object; this can be displayed with type “L” or “Evpn” but is allocated as global because of the conditional static MAC configuration.

The no form of this command returns the FDB MAC address entry allocation mode to its default where FDB entries for MAC addresses are allocated on all line cards in the system.

Default 

no selective-learned-fdb

send-bvpls-flush

Syntax 
send-bvpls-flush {[all-but-mine] [all-from-me]}
no send-bvpls-flush
Context 
config>service>vpls
Description 

This command enables generation of LDP MAC withdrawal “flush-all-from-me” in the B-VPLS domain when the following triggers occur in the related IVPLS:

  1. MC-LAG failure
  2. Failure of a local SAP
  3. Failure of a local pseudowire/SDP binding

A failure means transition of link SAP/pseudowire to either down or standby status.

This command does not require send-flush-on-failure in B-VPLS to be enabled on an IVPLS trigger to send an MAC flush into the BVPLS.

Default 

no send-bvpls-flush

Parameters 
all-but-mine—
Specifies to send an LDP flush all-but-mine and also sent into the B-VPLS. Both parameters can be set together.
all-from-me—
Specifies to send an LDP flush-all-from and when STP initiates a flush, it is sent into the B-VPLS using LDP MAC flush all-from-me. Both parameters can be set together.

send-flush-on-failure

Syntax 
[no] send-flush-on-failure
Context 
config>service>vpls
Description 

This command enables sending out flush-all-from-me messages to all LDP peers included in affected VPLS, in the event of physical port failures or “operationally down” events of individual SAPs. This feature provides an LDP-based mechanism for recovering a physical link failure in a dual-homed connection to a VPLS service. This method provides an alternative to RSTP solutions where dual homing redundancy and recovery, in the case of link failure, is resolved by RSTP running between a PE router and CE devices. If the endpoint is configured within the VPLS and send-flush-on-failure is enabled, flush-all-from-me messages will be sent out only when all spoke-SDPs associated with the endpoint go down.

This feature cannot be enabled on management VPLS.

Default 

no send-flush-on-failure

service-mtu

Syntax 
service-mtu octets
no service-mtu
Context 
config>service>vpls
config>service>template>vpls-template
Description 

This command configures the service payload (Maximum Transmission Unit – MTU), in bytes, for the service. This MTU value overrides the service-type default MTU. The service-mtu defines the payload capabilities of the service. It is used by the system to validate the SAP and SDP binding’s operational state within the service.

The service MTU and a SAP’s service delineation encapsulation overhead (4 bytes for a dot1q tag) is used to derive the required MTU of the physical port or channel on which the SAP was created. If the required payload is larger than the port or channel MTU, then the SAP will be placed in an inoperative state. If the required MTU is equal to or less than the port or channel MTU, the SAP will be able to transition to the operative state.

When binding an SDP to a service, the service MTU is compared to the path MTU associated with the SDP. The path MTU can be administratively defined in the context of the SDP. The default or administrative path MTU can be dynamically reduced due to the MTU capabilities discovered by the tunneling mechanism of the SDP or the egress interface MTU capabilities based on the next hop in the tunnel path. If the service MTU is larger than the path MTU, the SDP binding for the service will be placed in an inoperative state. If the service MTU is equal to or less than the path MTU, then the SDP binding will be placed in an operational state.

If a service MTU, port or channel MTU, or path MTU is dynamically or administratively modified, then all associated SAP and SDP binding operational states are automatically re-evaluated.

For i-VPLS and Epipes bound to a b-VPLS, the service-mtu must be at least 18 bytes smaller than the b-VPLS service MTU to accommodate the PBB header.

The no form of this command returns the default service-mtu for the indicated service type to the default value.

Default 

service-mtu 1514

Parameters 
octets—
The following table displays MTU values for specific VC types

VC-Type

Example Service MTU

Advertised MTU

Ethernet

1514

1500

Ethernet (with preserved dot1q)

1518

1504

VPLS

1514

1500

VPLS (with preserved dot1q)

1518

1504

VLAN (dot1p transparent to MTU value)

1514

1500

VLAN (QinQ with preserved bottom Qtag)

1518

1504

The size of the MTU in octets, expressed as a decimal integer

Values—
1 to 9194

 

allow-ip-int-bind

Syntax 
[no] allow-ip-int-bind
Context 
config>service>vpls
Description 

The allow-ip-int-bind command that sets a flag on the VPLS or I-VPLS service that enables the ability to attach an IES or VPRN IP interface to the VPLS service in order to make the VPLS service routable. When the allow-ip-int-bind command is not enabled, the VPLS service cannot be attached to an IP interface.

VPLS Configuration Constraints for Enabling allow-ip-int-bind

When attempting to set the allow-ip-int-bind VPLS flag, the system first checks to see if the correct configuration constraints exist for the VPLS service and the network ports. The following VPLS features must be disabled or not configured for the allow-ip-int-bind flag to set:

  1. SAP ingress QoS policies applied to the VPLS SAPs cannot have MAC match criteria defined
  2. The VPLS service type cannot be B-VPLS or M-VPLS
  3. MVR from Routed VPLS and to another SAP is not supported
  4. Enhanced and Basic Subscriber Management (ESM and BSM) features
  5. Network domain on SDP bindings

Once the VPLS allow-ip-int-bind flag is set on a VPLS service, the above features cannot be enabled on the VPLS service.

Network Port Hardware Constraints

The system also checks to ensure that all ports configured in network mode are associated with FlexPath2 forwarding planes. If a port is currently in network mode and the port is associated with a FlexPath1 forwarding plane, the allow-ip-int-bind command will fail. Once the allow-ip-int-bind flag is set on any VPLS service, attempting to enable network mode on a port associated with a FlexPath1 forwarding plane will fail.

VPLS SAP Hardware Constraints

Besides VPLS configuration and network port hardware association, the system also checks to that all SAPs within the VPLS are created on Ethernet ports and the ports are associated with FlexPath2 forwarding planes. Certain Ethernet ports and virtual Ethernet ports are not supported which include HSMDA ports and CCAG virtual ports (VSM based). If a SAP in the VPLS exists on an unsupported port type or is associated with a FlexPath1 forwarding plane, the allow-ip-int-bind command will fail. Once the allow-ip-int-bind flag is set on the VPLS service, attempting to create a VPLS SAP on the wrong port type or associated with a FlexPath1 forwarding plane will fail.

VPLS Service Name Bound to IP Interface without allow-ip-int-bind flag Set

If a service name is applied to a VPLS service and that service name is also bound to an IP interface but the allow-ip-int-bind flag has not been set on the VPLS service context, the system attempt to resolve the service name between the VPLS service and the IP interface will fail. After the allow-ip-int-bind flag is successfully set on the VPLS service, either the service name on the VPLS service must be removed and reapplied or the IP interface must be re-initialized using the shutdown / no shutdown commands. This will cause the system to reattempt the name resolution process between the IP interface and the VPLS service.

The no form of the command resets the allow-ip-int-bind flag on the VPLS service. If the VPLS service currently has an IP interface from an IES or VPRN service attached, the no allow-ip-int-bind command will fail. Once the allow-ip-int-bind flag is reset on the VPLS service, the configuration and hardware restrictions associated with setting the flag are removed. The port network mode hardware restrictions are also removed.

forward-ipv4-multicast-to-ip-int

Syntax 
[no] forward-ipv4-multicast-to-ip-int
Context 
config>service>vpls>allow-ip-int-bind
Description 

This command enables support for forwarding IPv4 multicast traffic from sources connected to the VPLS service of a routed VPLS to the IP interface of the routed VPLS service. It can only be enabled after the routed VPLS service has been bound to an IP interface.

Default 

no forward-ipv4-multicast-to-ip-int

forward-ipv6-multicast-to-ip-int

Syntax 
[no] forward-ipv6-multicast-to-ip-int
Context 
config>service>vpls>allow-ip-int-bind
Description 

This command enables support for forwarding IPv6 multicast traffic from sources connected to the VPLS service of a routed VPLS to the IP interface of the routed VPLS service. It can only be enabled after the routed VPLS service has been bound to an IP interface.

Default 

no forward-ipv6-multicast-to-ip-int

vxlan-ipv4-tep-ecmp

Syntax 
[no] vxlan-ipv4-tep-ecmp
Context 
config>service>vpls>allow-ip-int-bind
Description 

This command enables and disables ECMP on VXLAN IPv4 destinations for R-VPLS services. When this command is enabled, packets entering a VPRN connected to an R-VPLS that is terminating on a VXLAN IPv4 destination are looked up in the routing table. If the next hop is a VXLAN IPv4 TEP, the packets are distributed based on per-flow load-balancing.

This command can only be used in FP3- (or higher) routers. R-VPLS per-flow load-balancing for VXLAN IPv6 destinations works by default without this command.

The no version of this command reverts the process to the default behavior of per-remote VTEP load-balancing.

Default 

no vxlan-ipv4-tep-ecmp

site

Syntax 
site name [create]
no site name
Context 
config>service>vpls
Description 

This command configures a VPLS site.

The no form of the command removes the name from the configuration.

Parameters 
name—
Specifies a site name up to 32 characters in length
create—
This keyword is mandatory while creating a VPLS service

boot-timer

Syntax 
boot-timer seconds
no boot-timer
Context 
config>service>vpls>site
Description 

This command configures for how long the service manger waits after a node reboot before running the DF election algorithm. The boot-timer value should be configured to allow for the BGP sessions to come up and for the NLRI information to be refreshed/exchanged.

The no form of the command reverts the default.

Default 

10

Parameters 
seconds—
Specifies the site boot-timer in seconds
Values—
0 to 100

 

failed-threshold

Syntax 
failed-threshold [1 to 1000]
failed-threshold all
Context 
config>service>vpls>site
Description 

This command defines the number of objects should be down for the site to be declared down. Both administrative and operational status must be evaluated and if at least one is down, the related object is declared down.

Default 

failed-threshold all

Parameters 
1 to 1000—
Specifies the threshold for the site to be declared down

mesh-sdp-binding

Syntax 
[no] mesh-sdp-binding
Context 
config>service>vpls>site
Description 

This command enables applications to all mesh SDPs.

The no form of reverts the default.

Default 

no mesh-sdp-binding

monitor-oper-group

Syntax 
monitor-oper-group group-name
no monitor-oper-group
Context 
config>service>vpls>site
config>service>vpls>spoke-sdp
config>service>vpls>sap
config>service>vpls>bgp>pw-template-binding
Description 

This command specifies the operational group to be monitored by the object under which it is configured. The oper-group name must be already configured under the config>service context before its name is referenced in this command.

The no form of the command removes the association.

Parameters 
group-name—
Specifies the name of the operational group. 32 characters maximum

sap

Syntax 
sap sap-id
no sap
Context 
config>service>vpls>site
Description 

This command configures a SAP for the site.

The no form of the command removes the SAP ID from the configuration.

Parameters 
sap-id—
Specifies the physical port identifier portion of the SAP definition

site-activation-timer

Syntax 
site-activation-timer seconds
no site-activation-timer
Context 
config>service>vpls>site
Description 

This command configures the time-period the system keeps the local sites in standby status, waiting for BGP updates from remote PEs before running the DF (designated-forwarder) election algorithm to decide whether the site should be unblocked. This timer if terminated if an update is received for which the remote PE has transitioned from DF to non-DF.

The no form of the command removes the value from the configuration.

Default 

2

Parameters 
seconds—
Specifies the site activation timer in seconds
Values—
0 to 100

 

site-min-down-timer

Syntax 
site-min-down-timer min-down-time
no site-min-down-timer
Context 
config>service>vpls>site
Description 

This command configures the BGP multi-homing site minimum down time. When set to a non-zero value, if the site goes operationally down it will remain operationally down for at least the length of time configured for the site-min-down-timer, regardless of whether other state changes would have caused it to go operationally up. This timer is restarted every time that the site transitions from up to down. Setting this parameter to zero allows the minimum down timer to be disabled for this service.

The above operation is optimized in the following circumstances:

  1. If the site goes down on the designated forwarder but there are no BGP multi-homing peers with the same site in an UP state, then the site-min-down-timer is not started and is not used.
  2. If the site goes down on the designated forwarder but there are no active BGP multi-homing peers, then the site-min-down-timer is not started and is not used.
  3. If the site-min-down-timer is active and a BGP multi-homing update is received from the designated forwarder indicating its site has gone down, the site-min-down-timer is immediately terminated and this PE becomes the designated forwarder if the BGP multi-homing algorithm determines it should be the designated forwarder.

The no form of this command reverts to the default value.

Default 

Taken from the value of site-min-down-timer configured for Multi-Chassis BGP multi-homing under the config>redundancy>bgp-multi-homing context.

Parameters 
min-down-time—
Specifies the time, in seconds, that a BGP multi-homing site remains operationally down after a transition from up to down
Values—
0 to 100 seconds

 

site-id

Syntax 
site-id value
no site-id
Context 
config>service>vpls>site
Description 

This command configures the identifier for the site in this service.

Parameters 
value—
Specifies the site identifier
Values—
1 to 65535

 

split-horizon-group

Syntax 
split-horizon-group group-name
no split-horizon-group
Context 
config>service>vpls>site
Description 

This command configures the value of split-horizon group associated with this site.

The no form of the command reverts the default.

Default 

no split-horizon-group

Parameters 
group-name—
Specifies a split-horizon group name

spoke-sdp

Syntax 
spoke-sdp sdp-id:vc-id
no spoke-sdp
Context 
config>service>vpls>site
Description 

This command binds a service to an existing Service Distribution Point (SDP).

The no form of the command removes the parameter from the configuration.

Parameters 
sdp-id—
Specifies the SDP identifier
Values—
1 to 17407

 

vc-id—
Specifies the virtual circuit identifier.
Values—
1 to 429496729

 

spb

Syntax 
spb [isis-instance] [fid fid] [create]
no spb
Context 
config>service>vpls
config>service>vpls>sap
config>service>vpls>spoke-sdp
Description 

This command configures Shortest Path Bridging.

Parameters 
isis-instance—
Specifies the ISIS instance
Values—
1024 to 2047

 

fid—
Specifies the FID
Values—
1 to 4095

 

create—
This keyword is mandatory when creating an SPB instance

level

Syntax 
level [1 to 1]
Context 
config>service>vpls>spb
config>service>vpls>sap>spb
config>service>vpls>spoke-sdp>spb
Description 

This command enters the context to configure SPB level information.

bridge-priority

Syntax 
bridge-priority bridge-priority
no bridge-priority
Context 
config>service>vpls>spb>level
Description 

This command configures the level 1 four bit bridge priority associated with this Shortest Path Bridging context in this VPLS service.

Default 

bridge-priority 8

Parameters 
bridge-priority—
Specifies the bridge priority
Values—
0 to 15

 

ect-algorithm

Syntax 
ect-algorithm fid-range fid-range {low-path-id | high-path-id}
no ect-algorithm fid-range fid-range
Context 
config>service>vpls>spb>level
Description 

This command configures the ECT algorithm of forwarding range.

Parameters 
fid-range—
Specifies the FID range in the form start-end; for example, 50-120
Values—
start — 1 to 4095
end — 1 to 4095

 

low-path-id—
Keyword specifies the low path ID
high-path-id—
Keyword specifies the high path ID

forwarding-tree-topology

Syntax 
forwarding-tree-topology unicast {spf | st}
Context 
config>service>vpls>spb>level
Description 

This command specifies level 1 unicast forwarding to follow the shortest path tree or to follow a single tree for this Shortest Path Bridging context in this VPLS service.

Default 

forwarding-tree-topology unicast spf

Parameters 
spf—
Follows the shortest path tree.
st—
Follows a single tree.

hello-interval

Syntax 
hello-interval seconds
no hello-interval
Context 
config>service>vpls>spb>level
config>service>vpls>sap>spb>level
config>service>vpls>spoke-sdp>spb>level
Description 

This command configures the interval in seconds between hello messages issued on this interface at this level. This command is valid only for interfaces on control B-VPLS.

The no form of the command to reverts to the default value.

Default 

hello-interval 3 (for the designated intersystem)

hello-interval 9 (for non-designated intersystems)

Parameters 
seconds —
Specifies the hello interval, in seconds, expressed as a decimal integer
Values—
1 to 20000

 

hello-multiplier

Syntax 
hello-multiplier multiplier
no hello-multiplier
Context 
config>service>vpls>spb>level
config>service>vpls>sap>spb>level
config>service>vpls>spoke-sdp>spb>level
Description 

This command configures the number of missing hello PDUs from a neighbor SPB declares the adjacency down. This command is valid only for interfaces on control B-VPLS.

The no form of the command reverts to the default value.

Default 

hello-multiplier 3

Parameters 
multiplier —
Specifies the multiplier for the hello interval expressed as a decimal integer
Values—
2 to 100

 

lsp-lifetime

Syntax 
lsp-lifetime seconds
no lsp-lifetime
Context 
config>service>vpls>spb
Description 

This command sets the time, in seconds, the router wants the LSPs it originates to be considered valid by other routers in the domain.

Each LSP received is maintained in an LSP database until the lsp-lifetime expires unless the originating router refreshes the LSP. By default, each router refreshes its LSPs every 20 minutes (1200 seconds) so other routers will not age out the LSP.

The LSP refresh timer is derived from this formula: lsp-lifetime/2.

The no form of the command reverts to the default value.

Default 

lsp-lifetime 1200

Parameters 
seconds—
Specifies the time, in seconds, that the router wants the LSPs it originates to be considered valid by other routers in the domain
Values—
350 to 65535

 

lsp-refresh-interval

Syntax 
lsp-refresh-interval [seconds] [half-lifetime [enable | disable]
no lsp-refresh-interval
Context 
config>service>vpls>spb
Description 

This command configures the LSP refresh timer interval. When configuring the LSP refresh interval, the value that is specified for lsp-lifetime must also be considered. The LSP refresh interval cannot be greater than 90% of the LSP lifetime.

The no form of the command reverts to the default (600 seconds), unless this value is greater than 90% of the LSP lifetime. For example, if the LSP lifetime is 400, then the no lsp-refresh-interval command will be rejected.

Default 

lsp-refresh-interval 600 half-lifetime enable

Parameters 
seconds—
Specifies the refresh interval.
Values—
150 to 65535

 

half-lifetime—
Sets the refresh interval to always be half the lsp-lifetime value. When this parameter is set to enable, the configured refresh interval is ignored.
Values—
enable, disable

 

timers

Syntax 
[no] timers
Context 
config>service>vpls>spb
Description 

This command configures the IS-IS timer values.

Default 

disabled

lsp-wait

Syntax 
lsp-wait lsp-wait [lsp-initial-wait initial-wait] [lsp-second-wait second-wait]]
Context 
config>service>vpls>spb>timers
Description 

This command is used to customize LSP generation throttling. Timers that determine when to generate the first, second and subsequent LSPs can be controlled with this command. Subsequent LSPs are generated at increasing intervals of the second lsp-wait timer until a maximum value is reached.

Note:

The IS-IS timer granularity is 100 ms. Timer values are rounded down to the nearest granularity, for example a configured value of 550 ms is internally rounded down to 500 ms.

Parameters 
lsp-wait —
Specifies the maximum interval in milliseconds between two consecutive occurrences of an LSP being generated.
Values—
10 to 120000

 

Default—
5000
initial-wait —
Specifies the initial LSP generation delay in milliseconds. Values < 100 ms are internally rounded down to 0, so that there is no added initial LSP generation delay.
Values—
10 to 100000

 

Default—
10
second-wait —
Specifies the hold time in milliseconds between the first and second LSP generation.
Values—
10 to 100000

 

Default—
1000

spf-wait

Syntax 
[no] spf-wait spf-wait [spf-initial-wait initial-wait] [spf-second-wait second-wait]]
Context 
config>service>vpls>spb>timers
Description 

This command defines the maximum interval between two consecutive SPF calculations in milliseconds. Timers that determine when to initiate the first, second and subsequent SPF calculations after a topology change occurs can be controlled with this command.

Subsequent SPF runs (if required) will occur at exponentially increasing intervals of the spf-second-wait interval. For example, if the spf-second-wait interval is 1000, then the next SPF will run after 2000 milliseconds, and then next SPF will run after 4000 milliseconds, and so on, until it reaches the spf-wait value. The SPF interval will stay at spf-wait value until there are no more SPF runs scheduled in that interval. After a full interval without any SPF runs, the SPF interval will drop back to spf-initial-wait.

Note:

The IS-IS timer granularity is 100 ms. Timer values are rounded down to the nearest granularity, for example a configured value of 550 ms is internally rounded down to 500 ms.

Default 

spf-wait 10000 spf-initial-wait 1000 spf-second-wait 1000

Parameters 
spf-wait —
Specifies the maximum interval in milliseconds between two consecutive SPF calculations.
Values—
10 to 120000

 

Default—
10000
initial-wait —
Specifies the initial SPF calculation delay in milliseconds after a topology change
Values—
10 to 100000

 

Default—
1000
second-wait —
Specifies the hold time in milliseconds between the first and second SPF calculation
Values—
10 to 100000

 

Default—
1000

overload-on-boot

Syntax 
overload-on-boot [timeout seconds]
no overload-on-boot
Context 
config>service>vpls>spb
Description 

When the router is in an overload state, the router is used only if there is no other router to reach the destination. This command configures the IGP upon bootup in the overload state until one of the following events occur:

  1. The timeout timer expires.
  2. A manual override of the current overload state is entered with the config>router>isis>no overload command.

The no overload command does not affect the overload-on-boot function.

If no timeout is specified, IS-IS will go into overload indefinitely after a reboot. After the reboot, the IS-IS status will display a permanent overload state:

  1. L1 LSDB Overload : Manual on boot (Indefinitely in overload)
  2. L2 LSDB Overload : Manual on boot (Indefinitely in overload)

This state can be cleared with the config>router>isis>no overload command.

When specifying a timeout value, IS-IS will go into overload for the configured timeout after a reboot. After the reboot, the IS-IS status will display the remaining time the system stays in overload:

  1. L1 LSDB Overload : Manual on boot (Overload Time Left : 17)
  2. L2 LSDB Overload : Manual on boot (Overload Time Left : 17)

The overload state can be cleared before the timeout expires with the config>router>isis>no overload command.

The no form of the command removes the overload-on-boot functionality from the configuration.

Default 

no overload-on-boot

Use show router ospf status or show router isis status commands to display the administrative and operational state as well as all timers.

Parameters 
seconds—
Specifies the timeout timer for overload-on-boot, in seconds
Values—
60 to 1800

 

overload

Syntax 
overload [timeout seconds]
no overload
Context 
config>service>vpls>spb
Description 

This command administratively sets the router to operate in the overload state for a specific time period, in seconds, or indefinitely.

During normal operation, the router may be forced to enter an overload state due to a lack of resources. When in the overload state, the router is only used if the destination is reachable by the router and will not used for other transit traffic.

If a time period is specified, the overload state persists for the configured length of time. If no time is specified, the overload state operation is maintained indefinitely.

The overload command can be useful in circumstances where the router is overloaded or used prior to executing a shutdown command to divert traffic around the router.

The no form of the command causes the router to exit the overload state.

Default 

no overload

Parameters 
seconds—
Specifies the time, in seconds, that the router must operate in an overload state
Default—
infinity (overload state maintained indefinitely)
Values—
60 to 1800

 

metric

Syntax 
metric ipv4-metric
no metric
Context 
config>service>vpls>spb>level
config>service>vpls>sap>spb>level
config>service>vpls>spoke-sdp>spb>level
Description 

This command configures the IS-IS interface metric for IPv4 unicast.

Parameters 
ipv4-metric—
Specifies the IS-IS interface metric for IPv4 unicast
Values—
1 to 16777215

 

lsp-pacing-interval

Syntax 
lsp-pacing-interval milli-seconds
no lsp-pacing-interval
Context 
config>service>vpls>sap>spb
config>service>vpls>spoke-sdp>spb
Description 

This command configures the interval during which LSPs are sent from the interface.To avoid overwhelming neighbors that have less CPU processing power with LSPs, the pacing interval can be configured to limit how many LSPs are sent during an interval. LSPs may be sent in bursts during the interval up to the configured limit. If a value of 0 is configured, no LSPs are sent from the interface.

The no form of the command reverts to the default value.

Note:

The IS-IS timer granularity is 100 ms. Timer values are rounded down to the nearest granularity, for example a configured value of 550 ms is internally rounded down to 500 ms.

Default 

lsp-pacing-interval 100

Parameters 
milli-seconds—
Specifies the interval, in milliseconds, during which IS-IS LSPs are sent from the interface expressed as a decimal integer
Values—
0 to 65535

 

retransmit-interval

Syntax 
retransmit-interval seconds
no retransmit-interval
Context 
config>service>vpls>sap>spb
config>service>vpls>spoke-sdp>spb
Description 

This command configures the minimum time between LSP PDU retransmissions on a point-to-point interface.

The no form of the command reverts to the default value.

Default 

retransmit-interval 100

Parameters 
seconds—
Specifies the interval in seconds that IS-IS LSPs can be sent on the interface
Values—
1 to 65535

 

split-horizon-group

Syntax 
[no] split-horizon-group [group-name] [residential-group]
Context 
config>service>vpls
Description 

This command creates a new split horizon group for the VPLS instance. Traffic arriving on a SAP or spoke-SDP within this split horizon group will not be copied to other SAPs or spoke-SDPs in the same split horizon group.

A split horizon group must be created before SAPs and spoke-SDPs can be assigned to the group.

The split horizon group is defined within the context of a single VPLS. The same group-name can be re-used in different VPLS instances.

Up to 30 split horizon groups can be defined per VPLS instance. Half are supported in i-VPLS.

The no form of the command removes the group name from the configuration.

Default 

A split horizon group is by default not created as a residential-group.

Parameters 
group-name —
Specifies the name of the split horizon group to which the SDP belongs
residential-group—
Defines a split horizon group as a residential split horizon group (RSHG). Doing so entails that:

a) SAPs which are members of this Residential Split Horizon Group will have:

  1. Double-pass queuing at ingress as default setting (can be disabled)
  2. STP disabled (cannot be enabled)
  3. ARP reply agent enabled per default (can be disabled)
  4. MAC pinning enabled per default (can be disabled)
  5. Downstream broadcast packets are discarded thus also blocking the unknown, flooded traffic
  6. Downstream multicast packets are allowed when IGMP snooping is enabled

b) Spoke SDPs which are members of this Residential Split Horizon Group will have:

  1. Downstream multicast traffic supported
  2. Double-pass queuing is not applicable
  3. STP is disabled (can be enabled)
  4. ARP reply agent is not applicable (dhcp-lease-states are not supported on spoke-SDPs)
  5. MAC pinning enabled per default (can be disabled)

process-cpm-traffic-on-sap-down

Syntax 
process-cpm-traffic-on-sap-down
[no] process-cpm-traffic-on-sap-down
Context 
config>service>vpls>sap
Description 

This command is applicable to simple SAPs configured on LAGs that are not part of any “endpoint” configurations or complicated resiliency schemes like MC-LAG with inter-chassis-backup (ICB) configurations. When configured, a simple LAG SAP will not be removed from the forwarding plane and flooded traffic (unknown unicast, broadcast and multicast) will be dropped on egress. This allows applicable control traffic that is extracted at the egress interface to be processed by the CPM. This command will not prevent a VPLS service from entering an Operational Down state if it is the last active connection to enter a non-operational state. By default, without this command, when a SAP on a LAG enters a non-operational state it is removed from the forwarding plane and no forwarding occurs to the egress.

The no form of the command means a SAP over a LAG that is not operational will be removed from the forwarding process.

Default 

no process-cpm-traffic-on-sap-down

pppoe-policy

Syntax 
pppoe-policy pppoe-policy-name
no pppoe-policy
Context 
config>service>vpls>sap
Description 

For the 7450 ESS or 7750 SR, this command specifies an existing PPPoE policy. These policies are referenced from interfaces configured for PPPoE. Multiple PPPoE policies may be configured.

Default 

none

Parameters 
pppoe-policy-name—
Specifies an existing PPPoE policy name up to 32 characters in length

auto-learn-mac-protect

Syntax 
[no] auto-learn-mac-protect
Context 
config>service>vpls>sap
config>service>vpls>spoke-sdp
config>service>vpls >mesh-sdp
config>service>vpls>split-horizon-group
config>service>vpls>endpoint
config>service>pw-template
config>service>pw-template>split-horizon-group
Description 

This command enables the automatic protection of source MAC addresses learned on the associated object. MAC protection is used in conjunction with restrict-protected-src, restrict-unprotected-dst and mac-protect. When this command is applied or removed, the MAC addresses are cleared from the related object.

When the auto-learn-mac-protect is enabled on an SHG the action only applies to the associated SAPs (no action is taken by default for spoke-SDPs in the SHG). To enable this function for spoke-SDPs within a SHG, the auto-learn-mac-protect must be enabled explicitly under the spoke-SDP. If required, auto-learn-mac-protect can also be enabled explicitly under specific SAPs within the SHG.

Default 

no auto-learn-mac-protect

restrict-protected-src

Syntax 
restrict-protected-src [{alarm-only | discard-frame}]
no restrict-protected-src
Context 
config>service>vpls>sap
config>service>vpls>spoke-sdp
config>service>vpls>mesh-sdp
config>service>vpls>split-horizon-group
config>service>vpls>endpoint
config>service>pw-template>
config>service>pw-template>split-horizon-group
Description 

This command indicates how the agent will handle relearn requests for protected MAC addresses, either manually added using the mac-protect command or automatically added using the auto-learn-mac-protect command. While enabled all packets entering the configured SAP, spoke-SDP, mesh-SDP, or any SAP that is part of the configured split horizon group (SHG) will be verified not to contain a protected source MAC address. If the packet is found to contain such an address, the action taken depends on the parameter specified on the restrict-protected-src command, namely:

  1. No parameter — The packet will be discarded, an alarm will be generated and the SAP, spoke-SDP or mesh SDP will be set operationally down. The SAP, spoke-SDP or mesh-SDP must be shutdown and enabled (no shutdown) for this state to be cleared.
  2. alarm-only — The packet will be forwarded, an alarm will be generated but the source MAC is not learned on the SAP, spoke-SDP or mesh SDP.
  3. discard-frame — The packet will be discarded and an alarm generated. The frequency of alarm generation is fixed to be at most one alarm per MAC address per FP per 10 minutes in a specified VPLS service. This parameter is only applicable to automatically protected MAC addresses.

When the restrict-protected-src is enabled on an SHG, the action only applies to the associated SAPs (no action is taken by default for spoke-SDPs in the SHG) and is displayed in the SAP show output as the oper state unless it is overridden by the configuration of restrict-protected-src on the SAP itself. To enable this function for spoke-SDPs within a SHG, the restrict-protected-src must be enabled explicitly under the spoke-SDP. If required, restrict-protected-src can also be enabled explicitly under specific SAPs within the SHG.

When this command is applied or removed, with either the alarm-only or discard-frame parameters, the MAC addresses are cleared from the related object.

The use of restrict-protected-src discard-frame is mutually exclusive with the configuration of manually protected MAC addresses within a specified VPLS.

The alarm-only parameter is not supported on the 7750 SR-a, 7750 SR-1e/2e/3e, or 7950 XRS.

Default 

no restrict-protected-src

Parameters 
alarm-only —
Specifies that the packet will be forwarded, an alarm will be generated but the source MAC is not learned on the SAP, spoke-SDP or mesh SDP
discard-frame—
Specifies that the packet will be discarded and an alarm generated. The frequency of alarm generation is fixed to be at most one alarm per MAC address per FP per 10 minutes within a specified VPLS service

restrict-unprotected-dst

Syntax 
restrict-unprotected-dst
no restrict-unprotected-dst
Context 
config>service>pw-template>split-horizon-group
config>service>vpls>split-horizon-group
config>service>vpls>sap
Description 

This command indicates how the system will forward packets destined for an unprotected MAC address, either manually added using the mac-protect command or automatically added using the auto-learn-mac-protect command. While enabled all packets entering the configured SAP or SAPs within a split horizon group (but not spoke or mesh-SDPs) will be verified to contain a protected destination MAC address. If the packet is found to contain a non-protected destination MAC, it will be discarded. Detecting a non-protected destination MAC on the SAP will not cause the SAP to be placed in the operationally down state. No alarms are generated.

If the destination MAC address is unknown, even if the packet is entering a restricted SAP, with restrict-unprotected-dst enabled, it will be flooded.

Default 

no restrict-unprotected-dst

shcv-policy-ipv4

Syntax 
shcv-policy-ipv4 policy-name
no shcv-policy-ipv4
Context 
config>service>vpls>sap
Description 

This command specifies the Subscriber Host Connectivity Verification (SHCV) policy for IPv4 only.

The no form of the command removes the policy name from the SAP configuration.

vpls-group

Syntax 
[no] vpls-group id
Context 
config>service>vpls
Description 

This command defines a vpls-group index. Multiple vpls-group commands can be specified to allow the use of different VPLS and SAP templates for different ranges of service ids. A vpls-group can be deleted only in shutdown state. Multiple commands under different vpls-group ids can be issued and can be in progress at the same time.

Default 

no vpls-group

Parameters 
id—
Specifies the ID associated with the VPLS group
Values—
1 to 4094

 

service-range

Syntax 
service-range startid-endid [start-vlan-id startvid]
no service-range startid-endid
Context 
config>service>vpls>vpls-group
Description 

This command configures the service ID and implicitly the VLAN ID ranges to be used as input variables for related VPLS and SAP templates to pre-provision “data” VPLS instances and related SAPs using the service ID specified in the command. If the start-vlan-id is not specified then the service-range values are used for vlan-ids. The data SAPs will be instantiated on all the ports used to specify SAP instances under the related control VPLS.

Modifications of the service id and vlan ranges are allowed with the following restrictions.

  1. service-range increase can be achieved in two ways:
    1. Allowed when vpls-group is in shutdown state
    2. By creating a new vpls-group
  2. service-range decrease can be achieved in two ways:
    1. Allowed when vpls-group is in shutdown state; when shutdown command is executed the associated service instances are deleted.
    2. Allowed when vpls-group is in no shutdown state and has completed successfully instantiating services.
    3. In both cases, only the services that do not have user configured SAPs will be deleted. Otherwise the above commands are rejected. Existing declarations or registrations do not prevent service deletion.
  3. start-vlan-id change can be achieved in two ways:
    1. Allowed when vpls-group is in shutdown state
    2. At the time of range decrease by increasing the start-vlan-id which can be done when vpls-group is in no shutdown state and has completed successfully instantiating services

The no form of this command removes the specified ranges and deletes the pre-provisioned VPLS instances and related SAPs. The command will fail if any of the VPLS instances in the affected ranges have a provisioned SAP.

Default 

no service-range

Parameters 
startid-endid—
Specifies the range of service IDs
Values—
1 to 2147483647

 

startvid—
Specifies the starting VLAN ID; it provides a way to set aside a service ID range that is not the same as the VLAN range and allows for multiple MVRP control-VPLSs to control same VLAN range on different ports.
Values—
1 to 4094

 

vpls-template-binding

Syntax 
vpls-template-binding name/id
no vpls-template-binding
Context 
config>service>vpls>vpls-group
Description 

This command configures the binding to a VPLS template to be used to instantiate pre-provisioned data VPLS using as input variables the service IDs generated by the vid-range command.

The no form of this command removes the binding and deletes the related VPLS instances. The command will fail if any of the affected VPLS instances have either a provisioned SAP or an active MVRP declaration/registration or if the related vpls-group id is in no shutdown state. Any changes to the vpls-template-binding require the vpls-group to be in shutdown state.

Default 

no vpls-template-binding

Parameters 
name/id—
Specifies the name or the ID of the VPLS template
Values—
1 to 1024

 

sap-template-binding

Syntax 
sap-template-binding name/id
no sap-template-binding
Context 
config>service>vpls>vpls-group
Description 

This command configures the binding to a SAP template to be used to instantiate SAPs in the data VPLS using as input variables the VLAN IDs generated by the vid-range command.

The no form of this command removes the binding and deletes the related SAP instances. The command will fail if any of the affected VPLS instances have either a provisioned SAP or an active MVRP declaration/registration registration or if the related vpls-group is in no shutdown state. Any changes to the sap-template-binding require the vpls-group to be in shutdown state. New control SAP additions to the management VPLS are allowed as long as data VPLS instantiations/removals for vpls-groups are not in progress. Control SAPs can be removed at any time generating the removal of related data SAPs from the data VPLS. The shutdown or no shutdown state for the control SAPs does not have any effect on data SAPs instantiated with this command.

Default 

no sap-template-binding

Parameters 
name—
Specifies the name of the VPLS template
Values—
ASCII character string

 

id—
Specifies the ID of the VPLS template
Values—
1 to 8196

 

mvrp-control

Syntax 
[no] mvrp-control
Context 
config>service>vpls>vpls-group
Description 

This command enables MVRP control in the VPLS instances instantiated using the templates for the specified vpls-group. That means the flooding FDB will be created empty and will be populated with endpoints whenever MVRP receives a declaration and a registration on a specific endpoint. Also the VLAN ID associated by the control VPLS with the instantiated VPLS will be declared on service activation by MVRP on all virtual MVRP ports in the control VPLS. Service activation takes place when at least one other SAP is provisioned and brought up under the data VPLS. This is usually a customer facing SAP or a SAP leading outside of the MVRP controlled domain.

The no form of this command disallows MVRP control over this VPLS. The VPLS will be created with a regular FDB and will become as a result active upon creation time. Command change is allowed only when the related vpls-group is in shutdown state.

Default 

no mvrp-control

mvrp

Syntax 
mvrp
Context 
config>service>vpls>mrp
config>service>vpls>sap>mrp
Description 

This object consolidates the MVRP attributes. MVRP is only supported initially in the management VPLS so the object is not supported under BVPLS, IVPLS or regular VPLS not marked with the m-vpls tag.

hold-time

Syntax 
hold-time value
no hold-time
Context 
config>service>vpls>mrp>mvrp
Description 

This command enables the dampening timer and applies to both types of provisioned SAPs – end-station and UNI. When a value is configured for the timer, it controls the delay between detecting that the last provisioned SAP in VPLS goes down and reporting it to the MVRP module. The CPM will wait for the time specified in the value parameter before reporting it to the MVRP module. If the SAP comes up before the hold-timer expires, the event will not be reported to MVRP module.

The non-zero hold-time does not apply for SAP transition from down to up, This kind of transition is reported immediately to MVRP module without waiting for hold-time expiration. Also this parameter applies only to the provisioned SAPs. It does not apply to the SAPs configured with the vpls-sap-template command. Also when end-station QinQ SAPs are present only the “no hold-time” configuration is allowed.

The no form of this command disables tracking of the operational status for the last active SAP in the VPLS. MVRP will stop declaring the VLAN only when the last provisioned customer (UNI) SAP associated locally with the service is deleted. Also MVRP will declare the associated VLAN attribute as soon as the first provisioned SAP is created in the associated VPLS instance, regardless of the operational state of the SAP.

Default 

no hold-time

Parameters 
value—
Specifies the hold time in minutes
Values—
1 to 30

 

endstation-vid-group

Syntax 
endstation-vid-group id vlan-id startvid-endvid
no endstation-vid-group id
Context 
config>service>vpls>mrp>mvrp
Description 

This command specifies the range of VLAN IDs that are controlled by MVRP on the port associated with the parent SAP. When the command is present under a certain SAP, the MVRP will treat the associated virtual port as an end-station.

MVRP endstation behavior means that configuration of a new data SAP with the outer tag in the configured endstation-vid-group will generate down that virtual port a MVRP declaration for the new [outer] VLAN attribute. Also registration received for the VLAN attribute in the range will be accepted but not propagated in the rest of MVRP context.

VPLS-groups are not allowed under the associated Management VPLS (M-VPLS) when the endstation is configured under one SAP. VPLS-groups can be supported in the chassis using a different M-VPLS.

The no form of the command removes the specified group id.

Default 

no endstation-vid-group

Parameters 
id—
Specifies the range index
Values—
1 to 4094

 

startvid-endvid—
Specifies the range of VLANs to be controlled by MVRP
Values—
1 to 4094

 

root-guard

Syntax 
[no] root-guard
Context 
config>service>vpls>sap>stp
config>service>vpls>spoke-sdp>stp
Description 

This command specifies whether this port is allowed to become an STP root port. It corresponds to the restrictedRole parameter in 802.1Q. If set, it can cause lack of spanning tree connectivity.

Default 

no root-guard

static-host

Syntax 
static-host ip ip-address [mac ieee-address] [create]
static-host mac ieee-address [create]
no static-host [ip ip-address] mac ieee-address
no static-host all [force]
no static-host ip ip-address
Context 
config>service>vpls>sap
Description 

This command configures a static host on this SAP.

Parameters 
ip-address—
Specifies the IPv4 unicast address
ieee-address —
Specify this optional parameter when defining a static host. Every static host definition must have at least one address defined, IP or MAC.
force—
Specifies the forced removal of the static host addresses.
create—
This keyword is mandatory while configuring a static host.

ancp-string

Syntax 
ancp-string ancp-string
no ancp-string
Context 
config>service>vpls>sap>static-host
Description 

This command specifies the ANCP string associated to this SAP host.

Parameters 
ancp-string—
Specifies the ANCP string up to 63 characters in length

app-profile

Syntax 
app-profile app-profile-name
no app-profile
Context 
config>service>vpls>sap>static-host
Description 

This command specifies an application profile name.

Parameters 
app-profile-name—
Specifies the application profile name up to 32 characters in length

inter-dest-id

Syntax 
inter-dest-id intermediate-destination-id
no inter-dest-id
Context 
config>service>vpls>sap>static-host
Description 

Specifies to which intermediate destination (for example a DSLAM) this host belongs.

Parameters 
intermediate-destination-id—
Specifies the intermediate destination ID. 32 characters maximum

sla-profile

Syntax 
sla-profile sla-profile-name
no sla-profile
Context 
config>service>vpls>sap>static-host
Description 

This command specifies an existing SLA profile name to be associated with the static subscriber host. The SLA profile is configured in the config>subscr-mgmt>sla-profile context.

Parameters 
sla-profile-name—
Specifies the SLA profile name

sub-profile

Syntax 
sub-profile sub-profile-name
no sub-profile
Context 
config>service>vpls>sap>static-host
Description 

This command specifies an existing subscriber profile name to be associated with the static subscriber host.

Parameters 
sub-profile-name—
Specifies the sub-profile name

subscriber

Syntax 
subscriber sub-ident
no subscriber
Context 
config>service>vpls>sap>static-host
Description 

This command specifies an existing subscriber identification profile to be associated with the static subscriber host.

Parameters 
sub-ident—
Specifies the subscriber identification

subscriber-sap-id

Syntax 
[no] subscriber-sap-id
Context 
config>service>vpls>sap>static-host
Description 

This command enables the use of the SAP ID as the subscriber ID.

The no form of the command disables the use of SAP ID as the subscriber ID.

trigger-packet

Syntax 
trigger-packet [dhcp] [pppoe] [arp] [dhcp6] [ppp] [data]
no trigger-packet
Context 
config>service>vpls>sap
Description 

This command enables triggering packet to initiate RADIUS authentication that provides a service context. The authentication, together with the service context for this request, creates a managed SAP. The VLAN is the same as the triggering packet. This SAP behaves as a regular SAP but the configuration is not user-editable and not maintained in the configuration file. The managed SAP remains active as long as the session is active.

Default 

none

Parameters 
dhcp—
Specifies whether the receipt of DHCP trigger packets on this VPLS SAP when the keyword capture-sap is specified in the sap command creation string, will result in a RADIUS authentication that will provide a service context and the creation of a SAP with a value of managed
pppoe—
Specifies whether the receipt of PPPoE trigger packets on this VPLS SAP when the keyword capture-sap is specified in the sap command creation string, will result in a RADIUS authentication that will provide a service context and the creation of a SAP with a value of managed
arp—
Indicates that ARP is the type of trigger packets for this entry
dhcp6—
Indicates that DHCP6 is the type of trigger packets for this entry
ppp—
Indicates that PPP is the type of trigger packets for this entry
data—
Indicates that subscriber data packets are the type of trigger packets for this entry

vxlan

Syntax 
vxlan vni vni-id [create]
no vxlan vni vni-id
Context 
config>service>vpls
Description 

This command enables the use of vxlan in the VPLS service.

Default 

none

Parameters 
vni-id—
Specifies the vxlan network identifier (VNI) configured in the VPLS service. All EVPN advertisements (mac routes and inclusive multicast routes) for this services will encode the configured VNI in the Ethernet Tag field of the NLRI.
Values—
1 to 16777215

 

create—
This keyword is mandatory when creating a vxlan instance

network

Syntax 
network
Context 
config>service>vpls>vxlan
Description 

This command enters the context to configure network parameters for the VPLS VXLAN service.

ingress

Syntax 
ingress
Context 
config>service>vpls>vxlan>network
Description 

This command enters the context to configure network ingress parameters for the VPLS VXLAN service.

qos

Syntax 
qos network-policy-id fp-redirect-group queue-group-name instance instance-id
no qos
Context 
config>service>vpls>vxlan>network>ingress
Description 

This command is used to redirect traffic arriving on VXLAN tunnels in an EVPN VXLAN service as a single entity (per forwarding class) to policers in an ingress forwarding plane queue group for the purpose of rate-limiting.

For the policer to be used, the following must be true:

  1. The configured queue group template name must be applied to the forwarding plane on which the ingress traffic arrives using the instance id specified.
  1. The policer referenced in the FC-to-policer mappings in the ingress context of a network QoS policy must be present in the specified queue group template.

The command will fail if the queue group template name does not exist or if the policer specified in the network QoS policy does not exist in the queue group template. If the queue group template name with the specified instance is not applied to the forwarding plane on which the VXLAN traffic arrives, then this traffic will use the ingress network queues related to the network interface; however, the ingress classification is still based on the applied network QoS policy.

The unicast traffic can be redirected to a policer under the forwarding class fp-redirect-group command in the ingress section of a network QoS policy. Similarly, broadcast, unknown and multicast traffic can be redirected to a broadcast-policer, unknown-policer or mcast-policer, respectively, also under the forwarding class fp-redirect-group command in the ingress section of a network QoS policy.

Ingress classification is based on the configuration of the ingress section of the specified network QoS policy, noting that the dot1p and DSCP classification is based on the outer Ethernet header and IP header, and the use of ler-use-dscp, ip-criteria and ipv6-criteria statements are ignored.

When this command is applied, it overrides the QoS applied to the related network interfaces for traffic arriving on VXLAN tunnels in that service but does not affect traffic received on a spoke-SDP in the same service.

The no version of this command removes the redirection of VXLAN tunnel traffic from the queue group policers.

Parameters 
network-policy-id
Specifies the network policy identification. The value uniquely identifies the policy on the system.
Values—
1 to 65535

 

queue-group-name —
Specifies the name of the queue group template up to 32 characters in length
instance-id —
Specifies the identification of a specific instance of the queue-group
Values—
1 to 65535

 

restrict-protected-src

Syntax 
restrict-protected-src discard-frame
no restrict-protected-src
Context 
config>service>vpls>vxlan
Description 

This command enables protected SRS MAC restrictions.

3.7.2.3. VPLS Interface Commands

interface

Syntax 
[no] interface ip-int-name
Context 
config>service>vpls
Description 

This command creates a logical IP routing interface for a VPLS service. Once created, attributes such as IP address and service access points (SAP) can be associated with the IP interface.

The interface command, under the context of services, is used to create and maintain IP routing interfaces within the VPLS service IDs. The IP interface created is associated with the VPLS management routing instance.This instance does not support routing.

Interface names are case-sensitive and must be unique within the group of defined IP interfaces defined for the network core router instance. Interface names in the dotted decimal notation of an IP address are not allowed. For example, the name “1.1.1.1” is not allowed, but “int-1.1.1.1” is allowed. Show commands for router interfaces use either interface names or the IP addresses. Use unique IP address values and IP address names to maintain clarity. Duplicate interface names can exist in different router instances.

Enter a new name to create a logical router interface. When an existing interface name is entered, the user enters the router interface context for editing and configuration.

By default, no default IP interface names are defined within the system. All VPLS IP interfaces must be explicitly defined in an enabled state.

The no form of this command removes the IP interface and the entire associated configuration. The interface must be administratively shutdown before issuing the no interface command.

For VPLS services, the IP interface must be shutdown before the SAP on that interface is removed.

For VPLS service, ping and traceroute are the only applications supported.

Parameters 
ip-int-name —
Specifies the name of the IP interface. Interface names must be unique within the group of defined IP.

An interface name:

  1. Should not be in the form of an IP address.
  2. Can be from 1 to 32 alphanumeric characters.
  3. If the string contains special characters (such as #,$,spaces), the entire string must be enclosed within double quotes.

If ip-int-name already exists within the service ID, the context changes to maintain that IP interface. If ip-int-name already exists within another service ID, an error occurs and the context does not change to that IP interface. If ip-int-name does not exist, the interface is created and the context is changed to that interface for further command processing.

address

Syntax 
address {ip-address/mask | ip-address netmask}
address ip-address mask
Context 
config>service>vpls>interface
Description 

This command assigns an IP address and an IP subnet, to a VPLS IP router interface. Only one IP address can be associated with an IP interface. An IP address must be assigned to each VPLS IP interface. An IP address and a mask are used together to create a local IP prefix. The defined IP prefix must be unique within the context of the routing instance. It cannot overlap with other existing IP prefixes defined as local subnets on other IP interfaces in the same routing context.

The IP address for the interface can be entered in either CIDR (Classless Inter-Domain Routing) or traditional dotted decimal notation. The show commands display CIDR notation and is stored in configuration files.

By default, no IP address or subnet association exists on an IP interface until it is explicitly created. Use the no form of this command to remove the IP address assignment from the IP interface. When the no address command is entered, the interface becomes operationally down.

Address

Admin State

Oper State

No Address

Up

Down

No Address

Down

Down

1.1.1.1

Up

Up

1.1.1.1

Down

Down

The operational state is a read-only variable and the only controlling variables are the address and admin states. The address and admin states are independent and can be set independently. If an interface is in an administratively up state and an address is assigned, it becomes operationally up.

Parameters 
ip-address —
The IP address of the IP interface. The ip-address portion of the address command specifies the IP host address that will be used by the IP interface within the subnet.

This address must be unique within the subnet and specified in dotted decimal notation. Allowed values are IP addresses in the range 1.0.0.0 – 223.255.255.255 (with support of /31 subnets).

/ —
The forward slash is a parameter delimiter and separates the ip-address portion of the IP address from the mask that defines the scope of the local subnet. No spaces are allowed between the ip-address, the “/” and the mask-length parameter. If a forward slash is not immediately following the ip-address, a dotted decimal mask must follow the prefix.
mask-length —
The subnet mask length when the IP prefix is specified in CIDR notation. When the IP prefix is specified in CIDR notation, a forward slash (/) separates the ip-address from the mask-length parameter. The mask length parameter indicates the number of bits used for the network portion of the IP address; the remainder of the IP address is used to determine the host portion of the IP address. The values allowed are integers in the range 0 – 30. A mask length of 32 is reserved for system IP addresses.
mask —
The subnet mask in dotted decimal notation. When the IP prefix is not specified in CIDR notation, a space separates the ip-address from a traditional dotted decimal mask. The mask parameter indicates the complete mask that will be used in a logical ‘AND’ function to derive the local subnet of the IP address. Allowed values are dotted decimal addresses in the range 128.0.0.0 – 255.255.255.252. A mask of 255.255.255.255 is reserved for system IP addresses.

3.7.2.4. General Switch Management Protocol Commands

gsmp

Syntax 
gsmp
Context 
config>service>vpls
Description 

This command enters the context to configure General Switch Management Protocol (GSMP) connections maintained in this service.

Default 

not enabled

group

Syntax 
[no] group name
Context 
config>service>vpls>gsmp
Description 

This command specifies a GSMP name. A GSMP group name is unique only within the scope of the service in which it is defined.

ancp

Syntax 
ancp
Context 
config>service>vpls>gsmp>group
Description 

This command configures Access Node Control Protocol (ANCP) parameters for this GSMP group.

dynamic-topology-discover

Syntax 
[no] dynamic-topology-discover
Context 
config>service>vpls>gsmp>group>ancp
Description 

This command enables the ANCP dynamic topology discovery capability.

The no form of this command disables the feature.

idle-filter

Syntax 
[no] idle-filter
Context 
config>service>vpls>gsmp
Description 

This command when applied will filter out new subscriber’s ANCP messages from subscriber with “DSL-line-state” IDLE.

Default 

no idle-filter

line-configuration

Syntax 
[no] line-configuration
Context 
config>service>vpls>gsmp>group>ancp
Description 

This command enables the ANCP line-configuration capability.

The no form of this command disables the feature.

oam

Syntax 
[no] oam
Context 
config>service>vpls>gsmp>group>ancp
Description 

This command specifies whether or not the GSMP ANCP OAM capability should be negotiated at startup of the GSMP connection.

The no form of this command disables the feature.

hold-multiplier

Syntax 
hold-multiplier multiplier
no hold-multiplier
Context 
config>service>vpls>gsmp>group
Description 

This command configures the hold-multiplier for the GSMP connections in this group.

Parameters 
multiplier—
Specifies the GSMP hold multiplier value
Values—
1 to 100

 

keepalive

Syntax 
keepalive seconds
no keepalive
Context 
config>service>vpls>gsmp>group
Description 

This command configures keepalive values for the GSMP connections in this group.

Parameters 
seconds—
Specifies the GSMP keepalive timer value in seconds
Values—
1 to 25

 

neighbor

Syntax 
[no] neighbor ip-address
Context 
config>service>vpls>gsmp>group
Description 

This command configures a GSMP ANCP neighbor.

Parameters 
ip-address—
Specifies the IP address of the GSMP ANCP neighbor

local-address

Syntax 
local-address ip-address
no local-address
Context 
config>service>vpls>gsmp>group>neighbor
Description 

This command configures the source ip-address used in the connection toward the neighbor. The local address is optional. If specified the node will accept connections only for that address in the service running ANCP. The address may be created after the reference but connections will not be accepted until it is created. If the local address is not used, the system accepts connections on any interface within the routing context.

Parameters 
ip-address—
Specifies the source IP address to be used in the connection toward the neighbor

priority-marking

Syntax 
priority-marking dscp dscp-name
priority-marking prec ip-prec-value
no priority-marking
Context 
config>service>vpls>gsmp>group>neighbor
Description 

This command configures the type of priority marking to be used.

Parameters 
dscp dscp-name
Specifies the DSCP code-point to be used
Values—
be, cp1, cp2, cp3, cp4, cp5, cp6, cp7, cs1, cp9, af11, cp11, af12, cp13, af13, cp15, cs2, cp17, af21, cp19, af22, cp21, af23, cp23, cs3, cp25, af31, cp27, af32, cp29, af33, cp31, cs4, cp33, af41, cp35, af42, cp37, af43, cp39, cs5, cp41, cp42, cp43, cp44, cp45, ed, cp47, nc1, cp49, cp50, cp51, cp52, cp53, cp54, cp55, nc2, cp57, cp58, cp59, cp60, cp61, cp62, cp63

 

prec ip-prec-value—
Specifies the precedence value to be used
Values—
0 to 7

 

persistency-database

Syntax 
persistency-database
no persistency-database
Context 
config>service>vpls>gsmp
Description 

This command enables the system to store DSL line information in memory. If the GSMP connection terminates, the DSL line information will remain in memory and accessible for Radius authentication and accounting.

Default 

no persistency-database

3.7.2.4.1. VPLS DHCP Commands

dhcp

Syntax 
dhcp
Context 
config>service>vpls>sap
config>service>vpls>spoke-sdp
config>service>vpls>mesh-sdp
Description 

This command enters the context to configure DHCP parameters.

lease-populate

Syntax 
lease-populate [nmb-of-entries]
no lease-populate
Context 
config>service>vpls>sap>dhcp
Description 

This command enables and disables dynamic host lease state management for VPLS SAPs. For VPLS, DHCP snooping must be explicitly enabled (using the snoop command) at all points where DHCP messages requiring snooping enter the VPLS instance (both from the DHCP server and from the subscribers). Lease state information is extracted from snooped DHCP ACK messages to populate lease state table entries for the SAP.

The optional number-of-entries parameter is used to define the number of lease state table entries allowed for this SAP or IP interface. If number-of-entries is omitted, only a single entry is allowed. Once the maximum number of entries has been reached, subsequent lease state entries are not allowed and subsequent DHCP ACK messages are discarded.

The retained lease state information representing dynamic hosts may be used to:

  1. populate a SAP based anti-spoof filter table to provide dynamic anti-spoof filtering. If the system is unable to populate the dynamic host information in the anti-spoof filter table on the SAP, the DHCP ACK message must be discarded without adding a new lease state entry or updating an existing lease state entry.
  2. generate dynamic ARP replies if arp-reply-agent is enabled.
Default 

no lease-populate

Parameters 
nbr-of-entries—
Specifies the number of DHCP leases allowed
Values—
1 to 8000

 

option

Syntax 
[no] option
Context 
config>service>vpls>sap>dhcp
config>service>vpls>sap>dhcp6
Description 

This command enables DHCP Option 82 (Relay Agent Information Option) parameters processing and enters the context for configuring Option 82 sub-options.

The no form of this command returns the system to the default.

Default 

no option

action

Syntax 
action [dhcp-action]
no action
Context 
config>service>vpls>sap>dhcp>option
Description 

This command configures the Relay Agent Information Option (Option 82) processing.

The no form of this command returns the system to the default value.

Default 

The default is to keep the existing information intact.

Parameters 
dhcp-action—
Specifies the DHCP option action

replace — In the upstream direction (from the user), the Option 82 field from the router is inserted in the packet (overwriting any existing Option 82 field). In the downstream direction (toward the user) the Option 82 field is stripped (in accordance with RFC 3046).

drop — The DHCP packet is dropped if an Option 82 field is present, and a counter is incremented

keep — The existing information is kept in the packet and the router does not add any additional information. In the downstream direction the Option 82 field is not stripped and is sent on toward the client.

The behavior is slightly different in case of Vendor Specific Options (VSOs). When the keep parameter is specified, the router will insert his own VSO into the Option 82 field. This will only be done when the incoming message has already an Option 82 field.

If no Option 82 field is present, the router will not create the Option 82 field. In this in that case, no VSO will be added to the message.

circuit-id

Syntax 
circuit-id [ascii-tuple | vlan-ascii-tuple]
circuit-id hex [0x0..0xFFFFFFFF...(64 hex nibbles)]
no circuit-id
Context 
config>service>vpls>sap>dhcp>option
Description 

When enabled, the router sends an ASCII-encoded tuple in the circuit-id sub-option of the DHCP packet. This ASCII-tuple consists of the access-node-identifier, service-id, and SAP-ID, separated by “|”. If no keyword is configured, then the circuit-id sub-option will not be part of the information option (Option 82).

When the command is configured without any parameters, it equals to circuit-id ascii-tuple.

If disabled, the circuit-id sub-option of the DHCP packet will be left empty.

Default 

no circuit-id

Parameters 
ascii-tuple—
Specifies that the ASCII-encoded concatenated tuple consisting of the access-node-identifier, service-id, and interface-name is used
hex—
Specifies the circuit-id hex string
vlan-ascii-tuple—
Specifies that the format will include VLAN ID and dot1p bits as well as what is included in ascii-tuple already. The format is supported on dot1q and qinq encapsulated ports only. Therefore, when the Option 82 bits are stripped, dot1p bits will be copied to the Ethernet header of an outgoing packet.

remote-id

Syntax 
remote-id [mac | string string]
remote-id hex [0x0..0xFFFFFFFF...(64 hex nibbles)]
no remote-id
Context 
config>service>vpls>sap>dhcp>option
config>service>vpls>sap>dhcp6>option
Description 

This command specifies what information goes into the remote-id sub-option in the DHCP Relay packet.

If disabled, the remote-id sub-option of the DHCP packet will be left empty.

When the command is configured without any parameters, it equals to the remote-id mac option.

The no form of this command returns the system to the default.

Default 

no remote-id

Parameters 
hex—
Specifies the remote-id hex string
mac—
This keyword specifies the MAC address of the remote end is encoded in the sub-option
string string
Specifies the remote-id.

vendor-specific-option

Syntax 
[no] vendor-specific-option
Context 
config>service>vpls>sap>dhcp>option
Description 

This command configures the vendor specific sub-option of the DHCP relay packet.

client-mac-address

Syntax 
[no] client-mac-address
Context 
config>service>vpls>sap>dhcp>option>vendor
Description 

This command enables the sending of the MAC address in the vendor specific sub-option of the DHCP relay packet.

The no form of the command disables the sending of the MAC address in the vendor specific sub-option of the DHCP relay packet.

sap-id

Syntax 
[no] sap-id
Context 
config>service>vpls>sap>dhcp>option>vendor
Description 

This command enables the sending of the SAP ID in the vendor specific sub-option of the DHCP relay packet.

The no form of the command disables the sending of the SAP ID in the vendor specific sub-option of the DHCP relay packet.

service-id

Syntax 
[no] service-id
Context 
config>service>vpls>sap>dhcp>option>vendor
Description 

This command enables the sending of the service ID in the vendor specific sub-option of the DHCP relay packet.

The no form of the command disables the sending of the service ID in the vendor specific sub-option of the DHCP relay packet.

string

Syntax 
[no] string text
Context 
config>service>vpls>sap>dhcp>option>vendor
Description 

This command specifies the string in the vendor specific sub-option of the DHCP relay packet.

The no form of the command returns the default value.

Parameters 
text—
The string can be any combination of ASCII characters up to 32 characters in length. If spaces are used in the string, enclose the entire string in quotation marks (“ ”).

system-id

Syntax 
[no] system-id
Context 
config>service>vpls>sap>dhcp>option>vendor
Description 

This command specifies whether the system-id is encoded in the vendor specific sub-option of Option 82.

proxy-server

Syntax 
proxy-server
Context 
config>service>vpls>sap>dhcp
Description 

This command configures the DHCP proxy server.

emulated-server

Syntax 
emulated-server ip-address
no emulated-server
Context 
config>service>vpls>sap>dhcp>proxy
Description 

This command configures the IP address which will be used as the DHCP server address in the context of this VPLS SAP. Typically, the configured address should be in the context of the subnet represented by the VPLS.

The no form of this command reverts to the default setting. The local proxy server will not become operational without the emulated-server address being specified.

Parameters 
ip-address—
Specifies the emulated server address

lease-time

Syntax 
lease-time [days days] [hrs hours] [min minutes] [sec seconds] [radius-override]
no lease-time
Context 
config>service>vpls>sap>dhcp>proxy
Description 

This command defines the length of lease time that will be provided to DHCP clients. By default, the local-proxy-server will always make use of the lease-time information provide by either a RADIUS or DHCP server.

The no form of this command disables the use of the lease-time command. The local proxy server will use the lease time offered by either a RADIUS or DHCP server.

Default 

7 days 0 hours 0 seconds

Parameters 
days—
Specifies the number of days that the specified IP address is valid
Values—
0 to 3650

 

hours—
Specifies the number of hours that the specified IP address is valid
Values—
0 to 23

 

minutes—
Specifies the number of minutes that the specified IP address is valid
Values—
0 to 59

 

seconds—
Specifies the number of seconds that the specified IP address is valid.
Values—
0 to 59

 

snoop

Syntax 
[no] snoop
Context 
config>service>vpls>sap>dhcp6
config>service>vpls>sap>dhcp
config>service>vpls>spoke-sdp>dhcp
config>service>vpls>mesh-sdp>dhcp
Description 

This command enables DHCP snooping of DHCP messages on the SAP or SDP. Enabling DHCP snooping on VPLS interfaces (SAPs and SDP bindings) is required where DHCP messages important to lease state table population are received, or where Option 82 information is to be inserted. This includes interfaces that are in the path to receive messages from either DHCP servers or from subscribers.

Use the no form of the command to disable DHCP snooping on the specified VPLS SAP or SDP binding.

Default 

no snoop

3.7.2.4.2. VPLS STP Commands

stp

Syntax 
stp
Context 
config>service>vpls
config>service>vpls>sap
config>service>vpls>spoke-sdp
config>service>template>vpls-template
Description 

This command enters the context to configure the Spanning Tree Protocol (STP) parameters. Nokia’s STP is simply the Spanning Tree Protocol (STP) with a few modifications to better suit the operational characteristics of VPLS services. The most evident change is to the root bridge election. Since the core network operating between Nokia’s service routers should not be blocked, the root path is calculated from the core perspective.

auto-edge

Syntax 
auto-edge
no auto-edge
Context 
config>service>vpls>sap>stp
config>service>vpls>spoke-sdp>stp
Description 

This command configures automatic detection of the edge port characteristics of the SAP or spoke-SDP.

If auto-edge is enabled, and STP concludes there is no bridge behind the spoke-SDP, the OPER_EDGE variable will dynamically be set to true. If auto-edge is enabled, and a BPDU is received, the OPER_EDGE variable will dynamically be set to true (see edge-port).

The no form of this command returns the auto-detection setting to the default value.

Default 

auto-edge

edge-port

Syntax 
[no] edge-port
Context 
config>service>vpls>sap>stp
config>service>vpls>spoke-sdp>stp
Description 

This command configures the SAP or SDP as an edge or non-edge port. If auto-edge is enabled for the SAP, this value will be used only as the initial value.

Note:

The function of the edge-port command is similar to the rapid-start command. It tells RSTP that it is on the edge of the network (for example, there are no other bridges connected to that port) and, as a consequence, it can immediately transition to a forwarding state if the port becomes available.

RSTP, however, can detect that the actual situation is different from what edge-port may indicate.

Initially, the value of the SAP or spoke-SDP parameter is set to edge-port. This value will change if:

  1. A BPDU is received on that port. This means that after all there is another bridge connected to this port. Then the edge-port becomes disabled.
  2. If auto-edge is configured and no BPDU is received within a certain period of time, RSTP concludes that it is on an edge and enables the edge-port.

The no form of this command returns the edge port setting to the default value.

Default 

no edge-port

forward-delay

Syntax 
forward-delay seconds
no forward-delay
Context 
config>service>vpls>stp
config>service>template>vpls-template>stp
Description 

RSTP, as defined in the IEEE 802.1D-2004 standards, will normally transition to the forwarding state via a handshaking mechanism (rapid transition), without any waiting times. If handshaking fails (e.g. on shared links, see below), the system falls back to the timer-based mechanism defined in the original STP (802.1D-1998) standard.

A shared link is a link with more than two nodes (for example, a shared 10/100BaseT segment). The port-type command is used to configure a link as point-to-point or shared.

For timer-based transitions, the 802.1D-2004 standard defines an internal variable forward-delay, which is used in calculating the default number of seconds that a SAP or spoke-SDP spends in the discarding and learning states when transitioning to the forwarding state.

The value of the forward-delay variable depends on the STP operating mode of the VPLS instance:

  1. in rstp or mstp mode, but only when the SAP or spoke-SDP has not fallen back to legacy STP operation, the value configured by the hello-time command is used;
  2. in all other situations, the value configured by the forward-delay command is used.
Default 

forward-delay 15

Parameters 
seconds—
The forward delay timer for the STP instance in seconds
Values—
4 to 30

 

hello-time

Syntax 
hello-time hello-time
no hello-time
Context 
config>service>vpls>stp
config>service>template>vpls-template>stp
Description 

This command configures the Spanning Tree Protocol (STP) hello time for the Virtual Private LAN Service (VPLS) STP instance.

The hello time parameter defines the default timer value that controls the sending interval between BPDU configuration messages by this bridge, on ports where this bridge assumes the designated role.

The active hello time for the spanning tree is determined by the root bridge (except when the STP is running in RSTP mode, then the hello time is always taken from the locally configured parameter).

The configured hello-time can also be used to calculate the forward delay. See auto-edge.

The no form of this command returns the hello time to the default value.

Default 

hello-time 2

Parameters 
hello-time—
The hello time for the STP instance in seconds
Values—
1 to 10

 

hold-count

Syntax 
hold-count BDPU tx hold count
no hold-count
Context 
config>service>vpls>stp
config>service>template>vpls-template>stp
Description 

This command configures the peak number of BPDUs that can be transmitted in a period of one second.

The no form of this command returns the hold count to the default value

Default 

hold-count 6

Parameters 
BDPU tx hold count—
The hold count for the STP instance in seconds
Values—
1 to 10

 

link-type

Syntax 
link-type {pt-pt | shared}
no link-type
Context 
config>service>vpls>sap>stp
config>service>vpls>spoke-sdp>stp
Description 

This command instructs STP on the maximum number of bridges behind this SAP or spoke-SDP. If there is only a single bridge, transitioning to forwarding state will be based on handshaking (fast transitions). If more than two bridges are connected via a shared media, their SAP or spoke-SDPs should all be configured as shared, and timer-based transitions are used.

The no form of this command returns the link type to the default value.

Default 

link-type pt-pt

mst-instance

Syntax 
mst-instance mst-inst-number
Context 
config>service>vpls>sap>stp
Description 

This command enters the context to configure MSTI related parameters at SAP level. This context can be open only for existing mst-instances defined at the service level (see mst-instance).

Default 

none

Parameters 
mst-inst-number—
Specifies an existing Multiple Spanning Tree Instance number
Values—
1 to 4094

 

mst-path-cost

Syntax 
mst-path-cost inst-path-cost
no mst-path-cost
Context 
config>service>vpls>sap>stp>mst-instance
Description 

This commands specifies path-cost within a specified instance, expressing probability that a specified port will be put into the forwarding state in case a loop occurs (the highest value expresses lowest priority).

The no form of this command sets port-priority to its default value.

Default 

The path-cost is proportional to link speed.

Parameters 
inst-path-cost—
Specifies the contribution of this port to the MSTI path cost of paths toward the spanning tree regional root which include this port
Values—
1 to 200000000

 

mst-port-priority

Syntax 
mst-port-priority stp-priority
no mst-port-priority
Context 
config>service>vpls>sap>stp>mst-instance
Description 

This commands specifies the port priority within a specified instance, expressing probability that a specified port will be put into the forwarding state if a loop occurs.

The no form of this command sets port-priority to its default value.

Default 

mst-port-priority 128

Parameters 
stp-priority—
Specifies the value of the port priority field.

max-age

Syntax 
max-age seconds
no max-age
Context 
config>service>vpls>stp
config>service>template>vpls-template>stp
Description 

This command indicates how many hops a BPDU can traverse the network starting from the root bridge. The message age field in a BPDU transmitted by the root bridge is initialized to 0. Each other bridge will take the message_age value from BPDUs received on their root port and increment this value by 1. The message_age therefore reflects the distance from the root bridge. BPDUs with a message age exceeding max-age are ignored.

STP uses the max-age value configured in the root bridge. This value is propagated to the other bridges via the BPDUs.

The no form of this command returns the max age to the default value.

Default 

max-age 20

Parameters 
seconds—
The max info age for the STP instance in seconds. Allowed values are integers in the range 6 to 40.

mode

Syntax 
mode {rstp | comp-dot1w | dot1w | mstp | pmstp}
no mode
Context 
config>service>vpls>stp
config>service>template>vpls-template>stp
Description 

This command specifies the version of Spanning Tree Protocol the bridge is currently running.

See section Spanning Tree Operating Modes for more information about these modes.

The no form of this command returns the STP variant to the default.

Default 

mode rstp

Parameters 
rstp—
Corresponds to the Rapid Spanning Tree Protocol specified in IEEE 802.1D/D4-2003
dot1w—
Corresponds to the mode where the Rapid Spanning Tree is backward compatible with IEEE 802.1w
compdot1w—
Corresponds to the Rapid Spanning Tree Protocol in conformance with IEEE 802.1w
mstp—
Sets MSTP as the STP mode of operation. Corresponds to the Multiple Spanning Tree Protocol specified in 802.1Q REV/D5.0-09/200
pmstp—
The PMSTP mode is only supported in VPLS services where the mVPLS flag is configured

mst-instance

Syntax 
[no] mst-instance mst-inst-number
Context 
config>service>vpls>stp
Description 

This command creates the context to configure MST instance (MSTI) related parameters. Up to 16 instances will be supported by MSTP. The instance 0 is mandatory by protocol and therefore, it cannot be created by the CLI. The software will maintain this instance automatically.

Default 

none

Parameters 
mst-inst-number—
Specifies the Multiple Spanning Tree instance
Values—
1 to 4094

 

mst-priority

Syntax 
mst-priority bridge-priority
no mst-priority
Context 
config>service>vpls>stp>mst-instance
Description 

This command specifies the bridge priority for this specific Multiple Spanning Tree Instance for this service. The bridge-priority value reflects likelihood that the switch will be chosen as the regional root switch (65535 represents the least likely). It is used as the highest 4 bits of the Bridge ID included in the MSTP BPDUs generated by this bridge.

The priority can only take on values that are multiples of 4096 (4k). If a value is specified that is not a multiple of 4K, then the value will be replaced by the closest multiple of 4K, which is lower than the value entered.

The no form of this command sets the bridge-priority to its default value.

Default 

mst-priority 32768 — All instances created by vlan-range command and not having explicit definition of bridge-priority will inherit default value

Parameters 
bridge-priority—
Specifies the priority of this specific Multiple Spanning Tree Instance for this service
Values—
0 to 65535

 

vlan-range

Syntax 
[no] vlan-range [vlan-range]
Context 
config>service>vpls>stp>mst-instance
Description 

This command specifies a range of VLANs associated with a certain mst-instance. This range applies to all SAPs of the mVPLS.

Every VLAN range that is not assigned within any of the created mst-instance is automatically assigned to mst-instance 0. This instance is automatically maintained by the software and cannot be modified. Changing the VLAN range value can be performed only when the specified mst-instance is shutdown.

The no form of this command removes the vlan-range from the specified mst-instance.

Parameters 
vlan-range—
The first VLAN range specifies the left-bound (i.e., minimum value) of a range of VLANs that are associated with the mVPLS SAP. This value must be smaller than (or equal to) the second VLAN range value. The second VLAN range specifies the right-bound (i.e., maximum value) of a range of VLANs that are associated with the mVPLS SAP.
Values—
1 to 4094 to 1 to 4094

 

mst-max-hops

Syntax 
mst-max-hops hops-count
no mst-max-hops
Context 
config>service>vpls>stp
Description 

This command specifies the number of hops in the region before BPDU is discarded and the information held for the port is aged out. The root bridge of the instance sends a BPDU (or M-record) with remaining-hop-count set to configured <max-hops>. When a bridge receives the BPDU (or M-record), it decrements the received remaining-hop-count by 1 and propagates it in BPDU (or M-record) it generates.

The no form of this command sets the hops-count to its default value.

Default 

mst-max-hops 20

Parameters 
hops-count—
Specifies the maximum number of hops
Values—
1 to 40

 

mst-name

Syntax 
mst-name region-name
no mst-name
Context 
config>service>vpls>stp
Description 

This command defines an MST region name. Two bridges are considered as a part of the same MST region as soon as their configuration of the MST region name, the MST-revision and VLAN-to-instance assignment is identical.

The no form of this command removes region-name from the configuration.

Default 

no mst-name

Parameters 
region-name—
Specifies an MST-region name up to 32 characters in length

mst-revision

Syntax 
mst-revision revision-number
Context 
config>service>vpls>stp
Description 

This command defines the MST configuration revision number. Two bridges are considered as a part of the same MST region as soon as their configuration of MST-region name, MST-revision and VLAN-to-instance assignment is identical.

The no form of this command returns MST configuration revision to its default value.

Default 

mst-revision 0

Parameters 
revision-number—
Specifies the MSTP region revision number to define the MSTP region
Values—
0 to 65535

 

path-cost

Syntax 
path-cost sap-path-cost
no path-cost
Context 
config>service>vpls>sap>stp
config>service>vpls>spoke-sdp>stp
Description 

This command configures the Spanning Tree Protocol (STP) path cost for the SAP or spoke-SDP.

The path cost is used by STP to calculate the path cost to the root bridge. The path cost in BPDUs received on the root port is incremented with the configured path cost for that SAP or spoke-SDP. When BPDUs are sent out of other egress SAPs or spoke-SDPs, the newly calculated root path cost is used. These are the values used for CIST when running MSTP.

STP suggests that the path cost is defined as a function of the link bandwidth. Since SAPs and spoke-SDPs are controlled by complex queuing dynamics, in the 7450 ESS, 7750 SR, and 7950 XRS the STP path cost is a purely static configuration.

The no form of this command returns the path cost to the default value.

Parameters 
path-cost—
The path cost for the SAP or spoke-SDP
Values—
1 to 200000000 (1 is the lowest cost)

 

Default—
10

port-num

Syntax 
[no] port-num virtual-port-number
Context 
config>service>vpls>sap>stp
config>service>vpls>spoke-sdp>stp
Description 

This command configures the virtual port number which uniquely identifies a SAP within configuration bridge protocol data units (BPDUs). The internal representation of a SAP is unique to a system and has a reference space much bigger than the 12 bits definable in a configuration BPDU. STP takes the internal representation value of a SAP and identifies it with it’s own virtual port number that is unique to every other SAP defined on the TLS. The virtual port number is assigned at the time that the SAP is added to the TLS. Since the order that the SAP was added to the TLS is not preserved between reboots of the system, the virtual port number may change between restarts of the STP instance.

The virtual port number cannot be administratively modified.

priority

Syntax 
priority bridge-priority
no priority
Context 
config>service>vpls>stp
config>service>template>vpls-template>stp
Description 

The bridge-priority command is used to populate the priority portion of the bridge ID field within outbound BPDUs (the most significant 4 bits of the bridge ID). It is also used as part of the decision process when determining the best BPDU between messages received and sent. All values will be truncated to multiples of 4096, conforming with IEEE 802.1t and 802.1D-2004.

The no form of this command returns the bridge priority to the default value.

Default 

By default, the bridge priority is configured to 4096 which is the highest priority.

Parameters 
bridge-priority—
The bridge priority for the STP instance
Values—
Allowed values are integers in the range of 4096 to 65535 with 4096 being the highest priority. The actual bridge priority value stored/used is the number entered with the lowest 12 bits masked off which means the actual range of values is 4096 to 61440 in increments of 4096.

 

priority

Syntax 
priority stp-priority
no priority
Context 
config>service>vpls>spoke-sdp
config>service>vpls>sap>stp
Description 

This command configures the Nokia Spanning Tree Protocol (STP) priority for the SAP or spoke-SDP.

STP priority is a configurable parameter associated with a SAP or spoke-SDP. When configuration BPDUs are received, the priority is used in some circumstances as a tie breaking mechanism to determine whether the SAP or spoke-SDP will be designated or blocked.

In traditional STP implementations (802.1D-1998), this field is called the port priority and has a value of 0 to 255. This field is coupled with the port number (0 to 255 also) to create a 16 bit value. In the latest STP standard (802.1D-2004) only the upper 4 bits of the port priority field are used to encode the SAP or spoke-SDP priority. The remaining 4 bits are used to extend the port ID field into a 12 bit virtual port number field. The virtual port number uniquely references a SAP or spoke-SDP within the STP instance.

STP computes the actual priority by taking the input value and masking out the lower four bits.The result is the value that is stored in the SDP priority parameter. For instance, if a value of 0 is entered, masking out the lower 4 bits results in a parameter value of 0. If a value of 255 is entered, the result is 240.

The no form of this command returns the STP priority to the default value.

Default 

priority128

Parameters 
stp-priority—
The STP priority value for the SAP or spoke-SDP. Allowed values are integer in the range of 0 to 255, 0 being the highest priority. The actual value used for STP priority (and stored in the configuration) will be the result of masking out the lower 4 bits, therefore the actual value range is 0 to 240 in increments of 16.

3.7.2.4.3. VPLS SAP Commands

sap

Syntax 
sap sap-id [split-horizon-group group-name] [capture-sap] [create] [eth-ring ring-index] [root-leaf-tag | leaf-ac]
no sap sap-id
Context 
config>service>vpls
Description 

This command creates a Service Access Point (SAP) within a service. A SAP is a combination of port and encapsulation parameters which identifies the service access point on the interface and within the 7450 ESS, 7750 SR, and 7950 XRS. Each SAP must be unique.

All SAPs must be explicitly created. If no SAPs are created within a service or on an IP interface, a SAP will not exist on that object.

Enter an existing SAP without the create keyword to edit SAP parameters. The SAP is owned by the service in which it was created.

A SAP can only be associated with a single service. A SAP can only be defined on a port that has been configured as an access port using the config interface port-type port-id mode access command.

If a port is shutdown, all SAPs on that port become operationally down. When a service is shutdown, SAPs for the service are not displayed as operationally down although all traffic traversing the service will be discarded. The operational state of a SAP is relative to the operational state of the port on which the SAP is defined.

The no form of this command deletes the SAP with the specified port. When a SAP is deleted, all configuration parameters for the SAP will also be deleted. For Internet Enhanced Service (IES), the IP interface must be shutdown before the SAP on that interface may be removed.

Default 

No SAPs are defined.

Special Cases 
VPLS service SAP limits—
A VPLS SAP can be defined with Ethernet ports, SONET/SDH or TDM channels. The limits of the number of SAPs and SDPs supported in a VPLS service depends on the hardware used. Each SDP must have a unique destination or an error will be generated. Split horizon groups can only be created in the scope of a VPLS service.

A default SAP has the following format: port-id:*. This type of SAP is supported only on Ethernet MDAs and its creation is allowed only in the scope of Layer 2 services (Epipe and VPLS). This type of SAP is mutually exclusive with a SAP defined by explicit null encapsulation (for example, 1/1/1:0).

Parameters 
sap-id—
Specifies the physical port identifier portion of the SAP definition
create—
Keyword used to create a SAP instance. The create keyword requirement can be enabled/disabled in the environment>create context.
eth-ring—
When used with Ethernet Rings control the split horizon group accepts the major ring instance "value". This parameter applies to the 7450 ESS or 7750 SR only. The split horizon group prevents loops in the cases where a Ethernet Virtual Ring is miss configured on the main ring. Each path a and path b major ring are configured in the group and associated with the sub-ring control instance in the VPLS service.
ring-index
Specifies the ring index of the Ethernet ring
root-leaf-tag—
Specifies a SAP as a root leaf tag SAP. Only SAPs of the form dot1q (for example, 1/1/1:X) or qinq (for example, 1/1/1:X.Y, 1/1/1:X.*) are supported. The default E-Tree SAP type is a root-ac, if root-leaf-tag (or leaf-ac) is not specified at SAP creation. This option is only available when the VPLS is designated as an E-Tree VPLS; it is not available on BGP EVPN-enabled E-Tree VPLS services.
leaf-tag-vid
Specified after root-leaf-tag to replace the outer SAP-ID for leaf traffic. The leaf tag VID is only significant between peering VPLS but the values must be consistent on each end. This option is not available on BGP EVPN-enabled E-Tree VPLS services.
leaf-ac—
Specifies a SAP as a leaf access (AC) SAP. The default E-Tree SAP type is root-ac if leaf-ac (or root-leaf-tag) is not specified at SAP creation. This option is available when the VPLS is designated as an E-Tree VPLS. BGP EVPN-enabled E-Tree VPLS services also support the leaf-ac option.
split-horizon-group group-name
Specifies the name of the split horizon group to which the SAP belongs. This parameter applies to the 7450 ESS or 7750 SR only.
capture-sap—
Specifies a capturing SAP in which triggering packets will be sent to the CPM. Non-triggering packets captured by the capture SAP will be dropped. This parameter applies to the 7450 ESS or 7750 SR only.

cflowd

Syntax 
[no] cflowd
Context 
config>service>vpls>sap
Description 

This command enables cflowd to collect traffic flow samples through a service interface (SAP) for analysis. When cflowd is enabled on an Ethernet service SAP, the Ethernet traffic can be sampled and processed by the system’s cflowd engine and exported to IPFIX collectors with the l2-ip template enabled.

cflowd is used for network planning and traffic engineering, capacity planning, security, application and user profiling, performance monitoring, usage-based billing, and SLA measurement. When cflowd is enabled at the SAP level, all packets forwarded by the interface are subjected to analysis according to the cflowd configuration.

For Layer 2 services, only ingress sampling is supported.

Default 

no cflowd

discard-unknown-source

Syntax 
[no] discard-unknown-source
Context 
config>service>vpls>sap
config>service>vpls>spoke-sdp
config>service>template>vpls-sap-template
Description 

When this command is enabled, packets received on a SAP or a spoke-SDP with an unknown source MAC address will be dropped only if the maximum number of MAC addresses for that SAP or spoke-SDP (see max-nbr-mac-addr) has been reached. If max-nbr-mac-addr has not been set for the SAP or spoke-SDP, enabling discard-unknown-source has no effect.

When disabled, the packets are forwarded based on the destination MAC addresses.

The no form of this command causes packets with an unknown source MAC addresses to be forwarded by destination MAC addresses in VPLS.

Default 

no discard-unknown-source

3.7.2.5. ETH-CFM Service Commands

eth-cfm

Syntax 
eth-cfm
Context 
config>service>vpls
config>service>vpls>mesh-sdp
config>service>vpls>spoke-sdp
config>service>vpls>sap
Description 

This command enters the context to configure ETH-CFM parameters.

eth-tunnel

Syntax 
eth-tunnel
Context 
config>service>vpls>sap
Description 

The command enables the context to configure Ethernet tunnel SAP parameters.

eth-ring

Syntax 
eth-ring ring-id
no eth-ring
Context 
config>service>vpls
Description 

This command configures a VPLS SAP to be associated with an Ethernet ring. The SAP port ID is associated with the corresponding Ethernet ring path configured on the same port ID. The encapsulation type must be compatible with the Ethernet ring path encapsulation.

The no form of this command removes the Ethernet ring association from this SAP.

Default 

no eth-ring

Parameters 
ring-id—
Specifies the ring ID.
Values—
1 to 128

 

path

Syntax 
path path-index tag qtag[.qtag]
no path path-index
Context 
config>service>vpls>sap>eth-tunnel
Description 

This command configures Ethernet tunnel SAP path parameters.

The no form of the command removes the values from the configuration.

Default 

none

Parameters 
path-index—
Specifies the path index value.
Values—
1 to 16

 

tag qtag[.qtag]
Specifies the qtag value.
Values—
0 to 4094, * (wildcard)

 

collect-lmm-fc-stats

Syntax 
collect-lmm-fc-stats
Context 
config>service>vpls>mesh-sdp>eth-cfm
config>service>vpls>sap>eth-cfm
config>service>vpls>spoke-sdp>eth-cfm
Description 

This command enters the context to configure per-forwarding class (FC) LMM information collection.

This command is mutually exclusive with the collect-lmm-stats command when there is entity resource contention.

fc

Syntax 
fc fc-name [fc-name ... (up to 8 max)]
no fc
Context 
config>service>vpls>mesh-sdp>eth-cfm>collect-lmm-fc-stats
config>service>vpls>sap>eth-cfm>collect-lmm-fc-stats
config>service>vpls>spoke-sdp>eth-cfm>collect-lmm-fc-stats
Description 

This command creates individual counters for the specified FCs without regard for profile. All countable packets that match a configured FC, regardless of profile, will be included in this counter.

A differential is performed when this command is re-entered. Omitted FCs will stop counting, newly added FCs will start counting, and unchanged FCs will continue to count.

Up to eight FCs may be specified. An FC that is specified as part of this command for this specific context cannot be specified as a profile-aware FC using the fc-in-profile command under the same context.

The no form of the command removes all previously defined FCs and stops counting for those FCs.

Default 

no fc

Parameters 
fc-name—
Specifies the name of the FC for which to create an individual profile-unaware counter. In order for the counter to be used, the config>oam-pm>session> ethernet>priority command must be configured with a numerical value representing the FC name (7 = NC, 6 = H1, 5 = EF, 4 = H2, 3 = L1, 2 = AF, 1 = L2, 0 = BE), and the config>oam-pm>session>ethernet>lmm>enable-fc-collection command must be enabled.
Values—
nc, h1, ef, h2, l1, af, l2, be

 

fc-in-profile

Syntax 
fc-in-profile fc-name [fc-name ... (up to 8 max)]
no fc-in-profile
Context 
config>service>vpls>mesh-sdp>eth-cfm>collect-lmm-fc-stats
config>service>vpls>sap>eth-cfm>collect-lmm-fc-stats
config>service>vpls>spoke-sdp>eth-cfm>collect-lmm-fc-stats
Description 

This command creates individual counters for the specified FCs with regard for profile. All countable packets that match a configured FC and are deemed to be in-profile will be included in this counter.

A differential is performed when this command is re-entered. Omitted FCs will stop counting, newly added FCs will start counting, and unchanged FCs will continue to count.

Up to eight FCs may be specified. An FC that is specified as part of this command for this specific context cannot be specified as a profile-unaware FC using the fc command under the same context.

The no form of the command removes all previously defined FCs and stops counting for those FCs.

Default 

no fc-in-profile

Parameters 
fc-name—
Specifies the name of the FC for which to create an individual profile-aware counter. In order for the counter to be used, the config>oam-pm>session> ethernet>priority command must be configured with a numerical value representing the FC name (7 = NC, 6 = H1, 5 = EF, 4 = H2, 3 = L1, 2 = AF, 1 = L2, 0 = BE), and the config>oam-pm>session>ethernet>lmm>enable-fc-collection command must be enabled.
Values—
nc, h1, ef, h2, l1, af, l2, be

 

mep

Syntax 
mep mep-id domain md-index association ma-index [direction {up | down}] [primary-vlan-enable]
no mep mep-id domain md-index association ma-index
Context 
config>service>vpls>mesh-sdp>eth-cfm
config>service>vpls>spoke-sdp>eth-cfm
config>service>vpls>eth-cfm
config>service>vpls>sap>eth-cfm
Description 

This command configures the ETH-CFM maintenance endpoint (MEP). A MEP created at the VPLS service level vpls>eth-cfm creates a virtual MEP.

The no version of the command will remove the MEP.

Parameters 
mep-id—
Specifies the MEP identifier.
Values—
1 to 8191

 

md-index—
Specifies the maintenance domain (MD) index value.
Values—
1 to 4294967295

 

ma-index—
Specifies the maintenance association (MA) index value.
Values—
1 to 4294967295

 

direction up | down—
Indicates the direction in which the MEP faces on the bridge port. Direction is not supported when a MEP is created directly under the vpls>eth-cfm construct (vMEP).

down — Sends ETH-CFM messages away from the MAC relay entity

up — Sends ETH-CFM messages toward the MAC relay entity

primary-vlan-enable—
Provides a method for linking the MEP with the primary VLAN configured under the bridge-identifier for the MA. MEPs cannot be changed from or to primary VLAN functions. This must be configured as part of the creation step and can only be changed by deleting the MEP and re-creating it. Primary VLANs are only supported under Layer 2 Epipe and VPLS services.

mip

Syntax 
mip [mac mac-address] [primary-vlan-enable vlan-id]
mip default-mac
no mip
Context 
config>service>vpls>sap>eth-cfm
config>service>vpls>spoke-sdp>eth-cfm
config>service>vpls>mesh-sdp>eth-cfm
Description 

This command allows Maintenance Intermediate Points (MIPs). The creation rules of the MIP are dependent on the mhf-creation configuration for the MA.

The no form of the command removes the MIP creation request.

Default 

no mip

Parameters 
mac-address—
Specifies the MAC address of the MEP.
Values—
6-byte MAC address in the form of xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx of the MIP. The MAC must be unicast. Using the all-zeros address is equivalent to the no form of this command.

 

default-mac—
Using the no command deletes the MIP. If the operator wants to change the MAC back to the default MAC without having to delete the MIP and reconfiguring, this command is useful.
primary-vlan-enable—
Provides a method for linking the MIP with the primary VLAN configured under the bridge-identifier for the MA. This is only allowed if the mhf-creation method is static. MIPs cannot be changed from or to primary VLAN functions without first being deleted. Primary VLANs are only supported under Layer 2 Epipe and VPLS services.
vlan-id
Must match the vlan-id under the bridge-identifier for the MA that is appropriate for this service.
Values—
0 to 4094

 

mip

Syntax 
mip primary-vlan-enable [vlan vlan-id]
no mip
Context 
config>service>template>vpls-sap-template>eth-cfm
Description 

This command allows Maintenance Intermediate Points (MIPs). The creation rules of the MIP are dependent on the mhf-creation configuration for the MA. This MIP option is only available for default and static mhf-creation methods.

Parameters 
primary-vlan-enable—
Provides a method for linking the MIP with the primary VLAN configured under the bridge-identifier for the MA. This is only allowed if the mhf-creation method is static. MIPs cannot be changed from or to primary VLAN functions without first being deleted. This must be configured as part of the creation step and can only be changed by deleting the MEP and re-creating it. Primary VLANs are only supported under Ethernet SAPs.
vlan —
A required parameter when including primary-vlan-enable. Provides a method for associating the VLAN under the bride-identifier under the MA with the MIP.
vlan-id
Must match the vlan-id under the bridge-identifier for the MA that is appropriate for this service.
Values—
0 to 4094

 

ais-enable

Syntax 
[no] ais-enable
Context 
config>service>vpls>mesh-sdp>eth-cfm>mep
config>service>vpls>spoke-sdp>eth-cfm>mep
Description 

This command enables the generation and the reception of AIS messages.

interface-support-enable

Syntax 
[no] interface-support-enable
Context 
config>service>vpls>sap>eth-cfm>mep>ais
config>service>vpls>spoke-sdp>eth-cfm>mep>ais
config>service>vpls>mesh-sdp>eth-cfm>mep>ais
Description 

This command enables the AIS function to consider the operational state of the entity on which it is configured. With this command, ETH-AIS on operationally down MEPs will be triggered and cleared based on the operational status of the entity on which it is configured. If CCM is also enabled then transmission of the AIS PDU will be based on either the non-operational state of the entity or on any CCM defect condition. AIS generation will cease if BOTH operational state is UP and CCM has no defect conditions. If the MEP is not CCM enabled then the operational state of the entity is the only consideration assuming this command is present for the MEP.

Default 

no interface-support-enabled (AIS will not be generated or stopped based on the state of the entity on) which the operationally down MEP is configured.

client-meg-level

Syntax 
client-meg-level [[level [level ...]]
no client-meg-level
Context 
config>service>vpls>mesh-sdp>eth-cfm>mep>ais-enable
config>service>vpls>spoke-sdp>eth-cfm>mep>ais-enable
Description 

This command configures the client maintenance entity group (MEG) level(s) to use for AIS message generation. Up to 7 levels can be provisioned with the restriction that the client MEG level must be higher than the local MEG level.

Parameters 
level—
Specifies the client MEG level
Values—
1 to 7

 

Default—
1

ccm-padding-size

Syntax 
ccm-padding-size ccm-padding
no ccm-padding-size ccm-padding
Context 
config>service>vpls>mesh-sdp>eth-cfm>mep
config>service>vpls>sap>eth-cfm>mep
config>service>vpls>spoke-sdp>eth-cfm>mep
Description 

Set the byte size of the optional Data TLV to be included in the ETH-CC PDU. This will increase the size of the ETH-CC PDU by the configured value. The base size of the ETH-CC PDU, including the Interface Status TLV and Port Status TLV, is 83 bytes not including the Layer Two encapsulation. CCM padding is not supported when the CCM-Interval is less than one second.

Default 

no ccm-padding-size

Parameters 
ccm-padding—
Specifies the byte size of the Optional Data TLV.
Values—
3 to 1500

 

csf-enable

Syntax 
[no] csf-enable
Context 
config>service>vpls>mesh-sdp>eth-cfm>mep
config>service>vpls>sap>eth-cfm>mep
config>service>vpls>spoke-sdp>eth-cfm>mep
Description 

This command enables the reception and local processing of ETH-CSF frames.

multiplier

Syntax 
multiplier multiplier-value
no multiplier
Context 
config>service>vpls>mesh-sdp>eth-cfm>mep>csf-enable
config>service>vpls>sap>eth-cfm>mep>csf-enable
config>service>vpls>spoke-sdp>eth-cfm>mep>csf-enable
Description 

This command enables the multiplication factor applied to the receive time used to clear the CSF condition in increments of .5.

Default 

3.5

Parameters 
multiplier-value—
Specifies the multiplier used for timing out CSF
Values—
0.0, 2.0 to 30.0

 

interval

Syntax 
interval {1 | 60}
no interval
Context 
config>service>vpls>mesh-sdp>eth-cfm>mep>ais-enable
config>service>vpls>spoke-sdp>eth-cfm>mep>ais-enable
Description 

This command specifies the transmission interval of AIS messages in seconds.

Parameters 
1 | 60—
The transmission interval of AIS messages in seconds
Default—
1

priority

Syntax 
priority priority-value
no priority
Context 
config>service>vpls>mesh-sdp>eth-cfm>mep>ais-enable
config>service>vpls>spoke-sdp>eth-cfm>mep>ais-enable
Description 

This command specifies the priority of AIS messages originated by the node.

Parameters 
priority-value—
Specifies the priority value of the AIS messages originated by the node
Values—
0 to 7

 

Default—
1

ccm-enable

Syntax 
[no] ccm-enable
Context 
config>service>vpls>eth-cfm>mep
config>service>vpls>sap>eth-cfm>mep
config>service>vpls>mesh-sdp>mep
config>service>vpls>spoke-sdp>eth-cfm>mep
Description 

This command enables the generation of CCM messages.

The no form of the command disables the generation of CCM messages.

ccm-ltm-priority

Syntax 
ccm-ltm-priority priority
no ccm-ltm-priority
Context 
config>service>vpls>eth-cfm>mep
config>service>vpls>sap>eth-cfm>mep
config>service>vpls>mesh-sdp>mep
config>service>vpls>spoke-sdp>eth-cfm>mep
Description 

This command specifies the priority value for CCMs and LTMs transmitted by the MEP.

The no form of the command removes the priority value from the configuration.

Default 

The highest priority on the bridge-port.

Parameters 
priority—
Specifies the priority of CCM and LTM messages
Values—
0 to 7

 

eth-test-enable

Syntax 
[no] eth-test-enable
Context 
config>service>vpls>sap>eth-cfm>mep
config>service>vpls>spoke-sdp>eth-cfm>mep
config>service>vpls>mesh-sdp>eth-cfm>mep
Description 

For ETH-test to work, operators need to configure ETH-test parameters on both sender and receiver nodes. The ETH-test then can be done using the following OAM commands:

oam eth-cfm eth-test mac-address mep mep-id domain md-index association ma-index [priority priority] [data-length data-length]

A check is done for both the provisioning and test to ensure the MEP is an Y.1731 MEP (MEP provisioned with domain format none, association format icc-based). If not, the operation fails. An error message in the CLI and SNMP will indicate the problem.

test-pattern

Syntax 
test-pattern {all-zeros | all-ones} [crc-enable]
no test-pattern
Context 
config>service>vpls>sap>eth-cfm>mep>eth-test-enable
config>service>vpls>spoke-sdp>eth-cfm>mep>eth-test-enable
config>service>vpls>mesh-sdp>eth-cfm>mep>eth-test-enable
Description 

This command configures the test pattern for eth-test frames.

The no form of the command removes the values from the configuration.

Parameters 
all-zeros —
Specifies to use all zeros in the test pattern
all-ones—
Specifies to use all ones in the test pattern
crc-enable—
Generates a CRC checksum
Default—
all-zeros

bit-error-threshold

Syntax 
bit-error-threshold bit-errors
Context 
config>service>vpls>sap>eth-cfm>mep>eth-test-enable
config>service>vpls>spoke-sdp>eth-cfm>mep>eth-test-enable
config>service>vpls>mesh-sdp>eth-cfm>mep>eth-test-enable
config>service>vpls>eth-cfm>mep>eth-test-enable
Description 

This command specifies the lowest priority defect that is allowed to generate a fault alarm.

Default 

bit-error-threshold 1

Parameters 
bit-errors
Specifies the lowest priority defect.
Values—
0 to 11840

 

fault-propagation-enable

Syntax 
fault-propagation-enable {use-if-tlv | suspend-ccm}
no fault-propagation-enable
Context 
config>service>vpls>mesh-sdp>eth-cfm>mep
config>service>vpls>sap>eth-cfm>mep
config>service>vpls>spoke-sdp>eth-cfm>mep
Description 

This command configures the fault propagation for the MEP.

Parameters 
use-if-tlv—
Specifies to use the interface TLV.
suspend-ccm—
Specifies to suspend the continuity check messages.

grace

Syntax 
grace
Context 
config>service>vpls>eth-cfm>mep
config>service>vpls>mesh-sdp>eth-cfm>mep
config>service>vpls>spoke-sdp>eth-cfm>mep
config>service>vpls>sap>eth-cfm>mep
Description 

This command enters the context to configure Nokia ETH-CFM Grace and ITU-T Y.1731 ETH-ED expected defect functional parameters.

eth-ed

Syntax 
eth-ed
Context 
config>service>vpls>eth-cfm>mep>grace
config>service>vpls>mesh-sdp>eth-cfm>mep>grace
config>service>vpls>spoke-sdp>eth-cfm>mep>grace
config>service>vpls>sap>eth-cfm>mep>grace
Description 

This command enters the context to configure ITU-T Y.1731 ETH-ED expected defect functional parameters.

max-rx-defect-window

Syntax 
max-rx-defect-window seconds
no max-rx-defect-window
Context 
config>service>vpls>eth-cfm>mep>grace>eth-ed
config>service>vpls>mesh-sdp>eth-cfm>mep>grace>eth-ed
config>service>vpls>spoke-sdp>eth-cfm>mep>grace>eth-ed
config>service>vpls>sap>eth-cfm>mep>grace>eth-ed
Description 

This command limits the duration of the received ETH-ED expected defect window to the lower value of either the received value from the peer or this parameter.

The no form of the command removes the limitation, and any valid defect window value received from a peer MEP in the ETH-ED PDU will be used.

Default 

no max-rx-defect-window

Parameters 
seconds—
Specifies the duration, in seconds, of the maximum expected defect window.
Values—
1 to 86400

 

priority

Syntax 
priority priority
no priority
Context 
config>service>vpls>eth-cfm>mep>grace>eth-ed
config>service>vpls>mesh-sdp>eth-cfm>mep>grace>eth-ed
config>service>vpls>spoke-sdp>eth-cfm>mep>grace>eth-ed
config>service>vpls>sap>eth-cfm>mep>grace>eth-ed
Description 

This command sets the priority bits and determines the forwarding class based on the mapping of priority to FC.

The no form of the command disables the local priority configuration and sets the priority to the ccm-ltm-priority associated with this MEP.

Default 

no priority

Parameters 
priority—
Specifies the priority bit.
Values—
0 to 7

 

rx-eth-ed

Syntax 
[no] rx-eth-ed
Context 
config>service>vpls>eth-cfm>mep>grace>eth-ed
config>service>vpls>mesh-sdp>eth-cfm>mep>grace>eth-ed
config>service>vpls>spoke-sdp>eth-cfm>mep>grace>eth-ed
config>service>vpls>sap>eth-cfm>mep>grace>eth-ed
Description 

This command enables the reception and processing of the ITU-T Y.1731 ETH-ED PDU on the MEP.

The no form of the command disables the reception of the ITU-T Y.1731 ETH-ED PDU on the MEP.

Default 

rx-eth-ed

tx-eth-ed

Syntax 
[no] tx-eth-ed
Context 
config>service>vpls>eth-cfm>mep>grace>eth-ed
config>service>vpls>mesh-sdp>eth-cfm>mep>grace>eth-ed
config>service>vpls>spoke-sdp>eth-cfm>mep>grace>eth-ed
config>service>vpls>sap>eth-cfm>mep>grace>eth-ed
Description 

This command enables the transmission of the ITU-T Y.1731 ETH-ED PDU from the MEP when a system soft reset notification is received for one or more cards.

The config>eth-cfm>system>grace-tx-enable command must be configured to instruct the system that the node is capable of transmitting expected defect windows to the peers. Only one form of ETH-CFM grace (Nokia ETH-CFM Grace or ITU-T Y.1731 ETH-ED) may be transmitted.

The no form of the command disables the transmission of the ITU-T Y.1731 ETH-ED PDU from the MEP.

Default 

no tx-eth-ed

eth-vsm-grace

Syntax 
eth-vsm-grace
Context 
config>service>vpls>eth-cfm>mep>grace
config>service>vpls>mesh-sdp>eth-cfm>mep>grace
config>service>vpls>spoke-sdp>eth-cfm>mep>grace
config>service>vpls>sap>eth-cfm>mep>grace
Description 

This command enters the context to configure Nokia ETH-CFM Grace functional parameters.

rx-eth-vsm-grace

Syntax 
[no] rx-eth-vsm-grace
Context 
config>service>vpls>eth-cfm>mep>grace>eth-vsm-grace
config>service>vpls>mesh-sdp>eth-cfm>mep>grace>eth-vsm-grace
config>service>vpls>spoke-sdp>eth-cfm>mep>grace>eth-vsm-grace
config>service>vpls>sap>eth-cfm>mep>grace>eth-vsm-grace
Description 

This command enables the reception and processing of the Nokia ETH-CFM Grace PDU on the MEP.

The Nokia Grace function is a vendor-specific PDU that informs MEP peers that the local node may be entering a period of expected defect.

The no form of the command disables the reception of the Nokia ETH-CFM Grace PDU on the MEP.

Default 

rx-eth-vsm-grace

tx-eth-vsm-grace

Syntax 
[no] tx-eth-vsm-grace
Context 
config>service>vpls>eth-cfm>mep>grace>eth-vsm-grace
config>service>vpls>mesh-sdp>eth-cfm>mep>grace>eth-vsm-grace
config>service>vpls>spoke-sdp>eth-cfm>mep>grace>eth-vsm-grace
config>service>vpls>sap>eth-cfm>mep>grace>eth-vsm-grace
Description 

This command enables the transmission of the Nokia ETH-CFM Grace PDU from the MEP when a system soft reset notification is received for one or more cards.

The Nokia Grace function is a vendor-specific PDU that informs MEP peers that the local node may be entering a period of expected defect.

The config>eth-cfm>system>grace-tx-enable command must be configured to instruct the system that the node is capable of transmitting expected defect windows to the peers. Only one form of ETH-CFM grace (Nokia ETH-CFM Grace or ITU-T Y.1731 ETH-ED) may be transmitted.

The no form of the command disables the transmission of the Nokia ETH-CFM Grace PDU from the MEP.

Default 

tx-eth-vsm-grace

lbm-svc-act-responder

Syntax 
[no] lbm-svc-act-responder
Context 
config>service>vpls>mesh-sdp>eth-cfm>mep
config>service>vpls>sap>eth-cfm>mep
config>service>vpls>spoke-sdp>eth-cfm>mep
Description 

This command enables the MEP to process service activation streams encapsulated in ETH-CFM LBM frames that are directed to the MEP. The MEP will be allocated additional resources to rapidly respond to a high-speed stream of LBM messages. A MEP created with this option will not validate any TLVs, will not validate the ETH-LBM MAC Address, and will not increment or compute any loopback statistics. Statistical computation and reporting is the responsibility of the test head-end. The ETH-CFM level of the high speed ETH-LBM stream must match the level of a MEP configured with this command. It must not target any lower ETH-CFM level the MEP will terminate. When the service activation test is complete, the MEP may be returned to standard processing by removing this command. If there is available bandwidth, the MEP will respond to other ETH-CFM PDUs, such as ETH-DMM marker packets, using standard processing.

The interaction between this command and the tools perform service id service-id loopback eth command must be carefully considered. It is recommended that either the lbm-svc-act-responder or the tools perform service id service-id loopback eth command be used at any given time within a service. If both commands must be configured, and the target reflection point is the MAC Swap Loopback function, the inbound stream of data must not include ETH-CFM traffic that is equal to or lower than the domain level of any configured MEP which would otherwise extract and process the ETH-CFM message. If the reflection target is a MEP configured with the lbm-svc-act-responder option, the mode (ingress or egress) of the SAP or SDP specified with this tools command and the MEP direction (up or down) must match when the functions are enabled on the same reflection point, and the domain level of the inbound ETH-LBM must be the same as that of the MEP configured with the lbm-svc-act-responder option. At no time should the two functions be conflicting with each other along the path of the stream. This conflict would lead to unpredictable and possibly destabilizing situations.

The no form of the command reverts to MEP LBM standard processing.

Default 

no lbm-svc-act-responder

low-priority-defect

Syntax 
low-priority-defect {allDef | macRemErrXcon | remErrXcon | errXcon | xcon | noXcon}
Context 
config>service>vpls>mesh-sdp>eth-cfm>mep
config>service>vpls>spoke-sdp>eth-cfm>mep
Description 

This command specifies the lowest priority defect that is allowed to generate a fault alarm.

Default 

macRemErrXcon

Parameters 
low-priority-defect—
The low priority defect values are defined below.
Values—

allDef

DefRDICCM, DefMACstatus, DefRemoteCCM, DefErrorCCM, and DefXconCCM

macRemErrXcon

Only DefMACstatus, DefRemoteCCM, DefErrorCCM, and DefXconCCM

remErrXcon

Only DefRemoteCCM, DefErrorCCM, and DefXconCCM

errXcon

Only DefErrorCCM and DefXconCCM

xcon

Only DefXconCCM; or

noXcon

No defects DefXcon or lower are to be reported

 

mac-address

Syntax 
mac-address mac-address
no mac-address
Context 
config>service>vpls>eth-cfm>mep
config>service>vpls>sap>eth-cfm>mep
config>service>vpls>spoke-sdp>eth-cfm>mep
config>service>vpls>mesh-sdp>eth-cfm>mep
Description 

This command specifies the MAC address of the MEP.

The no form of this command reverts the MAC address of the MEP back to that of the port (if the MEP is on a SAP) or the bridge (if the MEP is on a spoke).

Parameters 
mac-address—
Specifies the MAC address of the MEP
Values—
6-byte mac-address in the form of xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx of the MEP. Must be unicast. Using the all zeros address is equivalent to the no form of this command.

 

one-way-delay-threshold

Syntax 
one-way-delay-threshold seconds
Context 
config>service>vpls>sap>eth-cfm>mep
Description 

This command enables/disables eth-test functionality on MEP.

Parameters 
seconds—
Specifies the one way delay threshold, in seconds
Values—
0 to 600

 

Default—
3

tunnel-fault

Syntax 
tunnel-fault {accept | ignore}
Context 
config>service>vpls>eth-cfm
config>service>vpls>sap>eth-cfm
Description 

Allows the individual service SAPs to react to changes in the tunnel MEP state. When tunnel-fault accept is configured at the service level, the SAP will react according to the service type, Epipe will set the operational flag and VPLS, IES and VPRN SAP operational state will become down on failure or up on clear. This command triggers the OAM mapping functions to mate SAPs and bindings in an Epipe service as well as setting the operational flag. If AIS generation is the requirement for the Epipe services this command is not required. See the command ais-enable under epipe>sap>eth-cfm>ais-enable for more details. This works in conjunction with the tunnel-fault accept on the individual SAPs. Both must be set to accept to react to the tunnel MEP state. By default the service level command is “ignore” and the sap level command is “accept”. This means simply changing the service level command to “accept” will enable the feature for all SAPs. This is not required for Epipe services that only wish to generate AIS on failure.

Default 

tunnel-fault ignore (Service Level)

tunnel-fault accept (SAP Level for Epipe and VPLS)

Parameters 
accept—
Specifies to share fate with the facility tunnel MEP
ignore—
Does not share fate with the facility tunnel MEP

vmep-filter

Syntax 
[no] vmep-filter
Context 
config>service>vpls>eth-cfm>sap
config>service>vpls>eth-cfm>spoke-sdp
config>service>vpls>eth-cfm>mesh-sdp
Description 

Suppress eth-cfm PDUs based on level lower than or equal to configured Virtual MEP. This command is not supported under a B-VPLS context. This will also delete any MIP configured on the SAP or Spoke-SDP.

The no form of the command reverts to the default values.

Default 

no vmep-filter

limit-mac-move

Syntax 
limit-mac-move [blockable | non-blockable]
no limit-mac-move
Context 
config>service>vpls>spoke-sdp
config>service>vpls>sap
Description 

This command indicates whether or not the mac-move agent, when enabled using config>service>vpls>mac-move or config>service>epipe>mac-move, will limit the MAC re-learn (move) rate on this SAP.

Default 

limit-mac-move blockable

Parameters 
blockable—
Specifies the agent will monitor the MAC re-learn rate on the SAP, and it will block it when the re-learn rate is exceeded
non-blockable—
Specifies the that this SAP will not be blocked, and another blockable SAP will be blocked instead

mac-pinning

Syntax 
[no] mac-pinning
Context 
config>service>vpls>spoke-sdp
config>service>vpls>mesh-sdp
config>service>vpls>sap
config>service>vpls>endpoint
Description 

Enabling this command will disable re-learning of MAC addresses on other SAPs within the VPLS. The MAC address will remain attached to a specified SAP for duration of its age-timer.

The age of the MAC address entry in the FDB is set by the age timer. If mac-aging is disabled on a specified VPLS service, any MAC address learned on a SAP/SDP with mac-pinning enabled will remain in the FDB on this SAP/SDP forever. Every event that would otherwise result in re-learning will be logged (MAC address; original-SAP; new-SAP).

MAC addresses learned during DHCP address assignment (DHCP snooping enabled) are not impacted by this command. MAC-pinning for such addresses is implicit.

Default 

When a SAP or spoke-SDP is part of a Residential Split Horizon Group (RSHG), MAC pinning is activated at creation of the SAP. Otherwise, MAC pinning is not enabled by default.

max-nbr-mac-addr

Syntax 
max-nbr-mac-addr table-size
no max-nbr-mac-addr
Context 
config>service>vpls>sap
config>service>vpls>spoke-sdp
config>service>vpls>endpoint
config>service>template>vpls-sap-template
Description 

This command specifies the maximum number of FDB entries for both learned and static MAC addresses for this SAP, spoke-SDP, or endpoint.

When the configured limit has been reached, and discard-unknown-source has been enabled for this SAP or spoke-SDP (see discard-unknown-source), packets with unknown source MAC addresses will be discarded.

The no form of the command restores the global MAC learning limitations for the SAP or spoke-SDP.

Default 

no max-nbr-mac-addr

Parameters 
table-size—
Specifies the maximum number of learned and static entries allowed in the FDB of this service
Values—
1 to 511999

 

mc-endpoint

Syntax 
mc-endpoint mc-ep-id
mc-endpoint
Context 
config>service>vpls>endpoint
Description 

This command specifies the identifier associated with the multi-chassis endpoint. This value should be the same on both MC-EP peers for the pseudowires that must be part of the same group.

The no form of this command removes the endpoint from the MC-EP. Single chassis behavior applies.

Default 

no mc-endpoint

Parameters 
mc-ep-id—
Specifies a multi-chassis endpoint ID
Values—
1 to 4294967295

 

mc-ep-peer

Syntax 
mc-ep-peer name
mc-ep-peer ip-address
no mc-ep-peer
Context 
config>service>vpls>endpoint>mc-ep
Description 

This command adds multi-chassis endpoint object.

The no form of this command removes the MC-Endpoint object.

Default 

mc-endpoint is not provisioned.

Parameters 
name—
Specifies the name of the multi-chassis endpoint peer
ip-address—
Specifies the IP address of multi-chassis endpoint peer

msap-defaults

Syntax 
msap-defaults
Context 
config>service>vpls>sap
Description 

This command configures the msap-defaults.

service

Syntax 
[no] service service-id
Context 
config>service>vpls>sap>msap-defaults
Description 

This command sets default service for all subscribers created based on trigger packets received on the specified capture SAP in case the corresponding VSA is not included in RADIUS authentication response. This command is applicable to capture SAP only.

Default 

no service

policy

Syntax 
policy msap-policy-name
no policy
Context 
config>service>vpls>sap>msap-defaults
Description 

This command sets default msap-policy for all subscribers created based on trigger packets received on the specified capture-sap in case the corresponding VSA is not included in the RADIUS authentication response. This command is applicable to capture SAP only.

Default 

no policy

multi-service-site

Syntax 
multi-service-site customer-site-name
no multi-service-site
Context 
config>service>vpls>sap
Description 

This command associates the SAP with a customer-site-name. If the specified customer-site-name does not exist in the context of the service customer ID an error occurs and the command will not execute. If customer-site-name exists, the current and future defined queues on the SAP (ingress and egress) will attempt to use the scheduler hierarchies created within customer-site-name as parent schedulers.

This command is mutually exclusive with the SAP ingress and egress scheduler-policy commands. If a scheduler-policy has been applied to either the ingress or egress nodes on the SAP, the multi-service-site command will fail without executing. The locally applied scheduler policies must be removed prior to executing the multi-service-site command.

The no form of the command removes the SAP from any multi-service customer site the SAP belongs to. Removing the site can cause existing or future queues to enter an orphaned state.

Default 

None

Parameters 
customer-site-name—
Specifies the customer name site. The customer-site-name must exist in the context of the customer-id defined as the service owner. If customer-site-name exists and local scheduler policies have not been applied to the SAP, the current and future queues defined on the SAP will look for their parent schedulers within the scheduler hierarchies defined on customer-site-name.
Values—
Any valid customer-site-name created within the context of the customer-id

 

precedence

Syntax 
precedence [precedence-value | primary]
no precedence
Context 
config>service>vpls>spoke-sdp
Description 

This command configures the precedence of this SDP bind when there are multiple SDP binds attached to one service endpoint. When an SDP bind goes down, the next highest precedence SDP bind begins forwarding traffic.

Parameters 
precedence-value—
Specifies the precedence of this SDP bind
Values—
1 to 4

 

primary—
Assigns this as the primary spoke-SDP

static-isid

Syntax 
[no] static-isid range entry-id isid [to isid] [create]
Context 
config>service>vpls>sap
config>service>vpls>vpls>spokesdp
Description 

This command identifies a set of ISIDs for I-VPLS services that are external to SPBM. These ISIDs are advertised as supported locally on this node unless an altered by an isid-policy. This allows communication from I-VPLS services external to SPBM through this node. The SAP may be a regular SAP or MC-LAG SAP. The spoke-SDP may be a active/standby spoke. When used with MC-Lag or active/stand-by PWs the conditional static-mac must be configured. ISIDs declared this way become part of the ISID multicast and consume MFIBs. Multiple SPBM static-isid ranges are allowed under a SAP/spoke-SDP.

The static-isids are associated with a remote BMAC that must be declared as a static-mac for unicast traffic. ISIDs are advertised as if they were attached to the local BMAC. Only remote I-VPLS ISIDs need to be defined. In the MFIB, the group MACs are then associated with the active SAP or spoke-SDP. An ISID policy may be defined to suppress the advertisement of an ISID if the ISID is primary used for unicast services. The following rules govern the usage of multiple ISID statements:

  1. overlapping values are allowed:
    1. isid from 301 to 310
    2. isid from 305 to 315
    3. isid 316
  2. the minimum and maximum values from overlapping ranges are considered and displayed. The above entries will be equivalent with “ISID from 301 to 316” statement.
  3. there is no consistency check with the content of ISID statements from other entries. The entries will be evaluated in the order of their IDs and the first match will cause the implementation t o execute the associated action for that entry.

The no form of the command removes all the previous statements under one interface

no isid value | from value to higher-value - removes a specific ISID value or range. Must match a previously used positive statement: for example if the command “isid 316 to 400” was used using “no isid 316 to 350” will not work but “no isid 316 to 400 will be successful.

Parameters 
entry-id—
Sets context for specified entry ID for the static-isids
Values—
1— 65535

 

isid—
Configures the ISID or the start of an ISID range. Specifies the ISID value in 24 bits. When just one present identifies a particular ISID to be used for matching.
Values—
0 to 16777215

 

to isid—
Identifies upper value in a range of ISIDs to be used as matching criteria
Values—
0 to 16777215

 

static-mac

Syntax 
[no] static-mac ieee-mac-address [create]
Context 
config>service>vpls>sap
config>service>vpls>mesh-sdp
config>service>vpls>spoke-sdp
Description 

This command creates a local static MAC entry in the Virtual Private LAN Service (VPLS) forwarding database (FDB) associated with the Service Access Point (SAP).

In a VPLS service, MAC addresses are associated with a Service Access Point (SAP) or with a Service Distribution Point (SDP). MACs associated with a SAP are classified as local MACs, and MACs associated with an SDP are remote MACs.

Local static MAC entries create a permanent MAC address to SAP association in the forwarding database for the VPLS instance so that MAC address will not be learned on the edge device.

Static MAC definitions on one edge device are not propagated to other edge devices participating in the VPLS instance, that is, each edge device has an independent forwarding database for the VPLS.

Only one static MAC entry (local or remote) can be defined per MAC address per VPLS instance.

By default, no static MAC address entries are defined for the SAP.

The no form of this command deletes the static MAC entry with the specified MAC address associated with the SAP from the VPLS forwarding database.

Parameters 
ieee-mac-address—
Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.
create—
This keyword is mandatory when specifying a static MAC address

managed-vlan-list

Syntax 
managed-vlan-list
Context 
config>service>vpls>sap
Description 

This command enters the context to configure VLAN ranges to be managed by a management VPLS. The list indicates, for each SAP, the ranges of associated VLANs that will be affected when the SAP changes state. This managed-vlan-list is not used when STP mode is MSTP in which case the vlan-range is taken from the config>service>vpls>stp>msti configuration.

This command is only valid when the VPLS in which it is entered was created as a management VPLS.

default-sap

Syntax 
[no] default-sap
Context 
config>service>vpls>sap>managed-vlan-list
Description 

This command adds a default SAP to the managed VLAN list.

The no form of the command removes the default SAP to the managed VLAN list.

range

Syntax 
[no] range vlan-range
Context 
config>service>vpls>sap>managed-vlan-list
Description 

This command configures a range of VLANs on an access port that are to be managed by an existing management VPLS.

This command is only valid when the VPLS in which it is entered was created as a management VPLS, and when the SAP in which it was entered was created on an Ethernet port with encapsulation type of dot1q or qinq, or on a SONET/SDH port with encapsulation type of bcp-dot1q.

To modify the range of VLANs, first the new range should be entered and afterwards the old range removed. See Modifying VPLS Service Parameters.

Default 

None

Parameters 
vlan-range—
Specify the VLAN start value and VLAN end value. The end-vlan must be greater than start-vlan. The format is <start-vlan>-<end-vlan>.
Values—
start-vlan: 0 to 4094 end-vlan: 0 to 4094

 

3.7.2.5.1. VPLS SAP ATM Commands

atm

Syntax 
atm
Context 
config>service>vpls>sap
Description 

This command enables access to the context to configure ATM-related attributes. This command can only be used when a specified context (for example, a channel or SAP) supports ATM functionality such as:

  1. Configuring ATM port or ATM port-related functionality on MDAs supporting ATM functionality
  2. Configuring ATM-related configuration for ATM-based SAPs that exist on MDAs supporting ATM functionality.

If ATM functionality is not supported for a specified context, the command returns an error.

egress

Syntax 
egress
Context 
config>service>vpls>sap>atm
Description 

This command enters the context to configure egress ATM attributes for the SAP.

encapsulation

Syntax 
encapsulation atm-encap-type
Context 
config>service>vpls>sap>atm
Description 

This command specifies the data encapsulation for an ATM PVCC delimited SAP. The definition references RFC 2684, Multiprotocol Encapsulation over ATM AAL5, and to the ATM Forum LAN Emulation specification.

Ingress traffic that does not match the configured encapsulation will be dropped.

Default 

encapsulation aal5snap-bridged

Parameters 
atm-encap-type—
Specifies the encapsulation type
Values—
aal5snap-bridged — Bridged encapsulation for LLC encapsulated circuit (LLC/SNAP precedes protocol datagram) as defined in RFC 2684.
aal5mux-bridged-eth-nofcs — Bridged IP encapsulation for VC multiplexed circuit as defined in RFC 2684.

 

ingress

Syntax 
ingress
Context 
config>service>vpls>sap>atm
Description 

This command enters the context to configure ingress ATM attributes for the SAP.

traffic-desc

Syntax 
traffic-desc traffic-desc-profile-id
no traffic-desc
Context 
config>service>vpls>sap>atm>ingress
config>service>vpls>sap>atm>egress
Description 

This command assigns an ATM traffic descriptor profile to a specified context (for example, a SAP).

When configured under the ingress context, the specified traffic descriptor profile defines the traffic contract in the forward direction.

When configured under the egress context, the specified traffic descriptor profile defines the traffic contract in the backward direction.

The no form of the command reverts the traffic descriptor to the default traffic descriptor profile.

Default 

The default traffic descriptor (trafficDescProfileId.=1) is associated with newly created PVCC-delimited SAPs.

Parameters 
traffic-desc-profile-id—
Specifies a defined traffic descriptor profile (see the QoS atm-td-profile command)

oam

Syntax 
oam
Context 
config>service>vpls>sap>atm
Description 

This command enters the context to configure OAM functionality for a PVCC delimiting a SAP.

The ATM-capable MDAs support F5 end-to-end OAM functionality (AIS, RDI, Loopback):

  1. ITU-T Recommendation I.610 - B-ISDN Operation and Maintenance Principles and Functions version 11/95
  2. GR-1248-CORE - Generic Requirements for Operations of ATM Network Elements (NEs). Issue 3 June 1996
  3. GR-1113-CORE - Bellcore, Asynchronous Transfer Mode (ATM) and ATM Adaptation Layer (AAL) Protocols Generic Requirements, Issue 1, July 1994

alarm-cells

Syntax 
[no] alarm-cells
Context 
config>service>vpls>sap>atm
Description 

This command configures AIS/RDI fault management on a PVCC. Fault management allows PVCC termination to monitor and report the status of their connection by propagating fault information through the network and by driving PVCC’s operational status.

When alarm-cells functionality is enabled, a PVCC’s operational status is affected when a PVCC goes into an AIS or RDI state because of an AIS/RDI processing (assuming nothing else affects PVCC’s operational status, for example, if the PVCC goes operationally down, or enters a fault state and becomes operationally up, or exits that fault state). RDI cells are generated when PVCC is operationally down. No OAM-specific SNMP trap is raised whenever an endpoint enters/exits an AIS or RDI state, however, if as result of an OAM state change, the PVCC changes operational status, then a trap is expected from an entity the PVCC is associated with (for example a SAP).

The no command disables alarm-cells functionality for a PVCC. When alarm-cells functionality is disabled, the PVCC’s operational status is no longer affected by the PVCC’s OAM state changes due to AIS/RDI processing. When alarm-cells is disabled, a PVCC will change operational status to operationally up from operationally down due to alarm-cell processing). RDI cells are not generated as result of PVCC going into an AIS or RDI state, however, the PVCC’s OAM status will record OAM faults as described above.

Default 

Enabled for PVCCs delimiting VPLS SAPs

3.7.2.5.2. VPLS Filter and QoS Policy Commands

egress

Syntax 
egress
Context 
config>service>vpls>sap
Description 

This command enters the context to configure egress filter policies.

If no sap-egress QoS policy is defined, the system default sap-egress QoS policy is used for egress processing. If no egress filter is defined, no filtering is performed.

ingress

Syntax 
ingress
Context 
config>service>vpls>sap
Description 

This command enters the context to configure ingress SAP Quality of Service (QoS) policies and filter policies.

If no sap-ingress QoS policy is defined, the system default sap-ingress QoS policy is used for ingress processing. If no ingress filter is defined, no filtering is performed.

agg-rate

Syntax 
[no] agg-rate
Context 
config>service>vpls>sap>egress>
config>service>template>vpls-sap-template>egress
config>service>vpls>sap>egress>encap-defined-qos>encap-group
Description 

This command is used to control an HQoS aggregate rate limit. It is used in conjunction with the following parameter commands: rate, limit-unused-bandwidth, and queue-frame-based-accounting.

rate

Syntax 
rate {max | rate}
no rate
Context 
config>service>vpls>sap>egress>agg-rate
config>service>template>vpls-sap-template>egress>agg-rate
config>service>vpls>sap>egress>encap-defined-qos>encap-group>agg-rate
Description 

This command defines the enforced aggregate rate for all queues associated with the agg-rate context. A rate must be specified for the agg-rate context to be considered active on the context’s object (SAP, subscriber, Vport, and so on.).

limit-unused-bandwidth

Syntax 
[no] limit-unused-bandwidth
Context 
config>service>vpls>sap>egress>agg-rate
config>service>template>vpls-sap-template>egress>agg-rate
config>service>vpls>sap>egress>encap-defined-qos>encap-group>agg-rate
Description 

This command is used to enable aggregate rate overrun protection on the agg-rate context.

The no form of the command disables the overrun protection.

queue-frame-based-accounting

Syntax 
[no] queue-frame-based-accounting
Context 
config>service>vpls>sap>egress>agg-rate
config>service>template>vpls-sap-template>egress>agg-rate
Description 

This command is used to enabled frame-based accounting on all policers and queues associated with the agg-rate context. Only supported on Ethernet ports. Not supported on HSMDA Ethernet ports. Packet byte offset settings are not included in the applied rate when queue frame based accounting is configured; however the offsets are applied to the statistics.

The no form of the command disables the-frame based accounting.

dest-mac-rewrite

Syntax 
dest-mac-rewrite ieee-address
no dest-mac-rewrite
Context 
config>service>vpls>sap>egress>agg-rate
Description 

This commands enables the overwriting of a destination MAC address to an operator-configured value for all unicast packets egressing the specified SAP. The command is intended to be deployed with L2 PBF SAP redirect when a remote end of the SAP interface is an L3 interface with a MAC address different from the MAC address of the non-PBF-ed L3 interface. See Filter Policy in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Router Configuration Guide for more details.

The no form disables the option.

Default 

no dest-mac-rewrite

Parameters 
ieee-address
Specifies the MAC address
Values—
1xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx
Cannot be all zeros

 

encap-defined-qos

Syntax 
encap-defined-qos
Context 
config>service>vpls>sap>egress
Description 

This command creates a new QoS sub-context in B-VPLS SAP egress context. The user can define encapsulation groups, referred to as encap-group, based on the ISID value in the packet’s encapsulation and assign a QoS policy and a scheduler policy or aggregate rate limit to the group.

encap-group

Syntax 
encap-group group-name [type group-type] [qos-per-member] [create]
no encap-group group-name
Context 
config>service>vpls>sap>egress>encap-defined-qos
Description 

This command defines an encapsulation group which consists of a group of ISID values. All packets forwarded on the egress of a B-VPLS SAP which payload header matches one of the ISID value in the encap-group will use the same QoS policy instance and scheduler policy or aggregate rate limit instance.

The user adds or removes members to the encap-group one at a time or as a range of contiguous values using the member command. However, when the qos-per-member option is enabled, members must be added or removed one at a time. These members are also referred to as ISID contexts.

The user can configure one or more encap-groups in the egress context of the same B-SAP, therefore defining different ISID values and applying each a different SAP egress QoS policy, and optionally a different scheduler policy/agg-rate. ISID values are unique within the context of a B-SAP. The same ISID value cannot be re-used in another encap-group under the same B-SAP but can be re-used in an encap-group under a different B-SAP. Finally, if the user adds to an encap-group an ISID value which is already a member of this encap-group, the command causes no effect. The same if the user attempts to remove an ISID value which is not a member of this encap-group.

Once a group is created, the user will assign a SAP egress QoS policy, and optionally a scheduler policy or aggregate rate limit, using the following commands:

config>service> vpls>sap>egress>encap-defined-qos>encap-group>qos sap-egress-policy-id

config>service> vpls>sap>egress>encap-defined-qos>encap-group>scheduler-policy scheduler-policy-name

config>service> vpls>sap>egress>encap-defined-qos>encap-group>agg-rate kilobits-per-second

A SAP egress QoS policy must first be assigned to the created encap group before the user can add members to this group. Conversely, the user cannot perform the no qos command until all members are deleted from the encap-group.

An explicit or the default SAP egress QoS policy will continue to be applied to the entire B-SAP but this will serve to create the set of egress queues which will be used to store and forward a packet which does not match any of the defined ISID values in any of the encap-groups for this SAP.

Only the queue definition and fc-to-queue mapping from the encap-group SAP egress QoS policy is applied to the ISID members. All other parameters configurable in a SAP egress QoS policy must be inherited from egress QoS policy applied to the B-SAP.

Furthermore, any other CLI option configured in the egress context of the B-SAP will continue to apply to packets matching a member of any encap-group defined in this B-SAP.

The keyword qos-per-member allows the user to specify that a separate queue set instance and scheduler/agg-rate instance will be created for each ISID value in the encap-group. By default, shared instances will be created for the entire encap-group.

When the B-SAP is configured on a LAG port, the ISID queue instances defined by all the encap-groups applied to the egress context of the SAP will be replicated on each member link of the LAG. The set of scheduler/agg-rate instances will be replicated per link or per IOM or XMA depending if the adapt-qos option is set to link/port-fair mode or distribute mode. This is the same behavior as that applied to the entire B-SAP in the current implementation.

The no form of this command deletes the encap-group.

Parameters 
group-name—
Specifies the name of the encap-group and can be up to 32 ASCII characters in length
type—
Specifies the type of the encapsulation ID used by this encap-group
Values—
isid

 

Default—
None
qos-per-member —
Specifies that a separate queue set instance and scheduler/agg-rate instance will be created for each ISID value in the encap-group

member

Syntax 
[no] member encap-id [to encap-id]
Context 
config>service>vpls>sap>egress>encap-defined-qos>encap-group
Description 

This command adds or removes a member ISID or a range of contiguous ISID members to an encap-group. The user can add or remove members to the encap-group one at a time or as a range of contiguous values using the member command. However, when the qos-per-member option is enabled, members must be added or removed one at a time.

The no form of this command removes the single or range of ISID values from the encap-group.

Parameters 
encap-id—
The value of the single encap-id or the start encap-id of the range. ISID is the only encap-id supported.
to encap-id
The value of the end encap-id of the range. ISID is the only encap-id supported.

qos

Syntax 
qos policy-id
no qos
Context 
config>service>vpls>sap>egress>encap-defined-qos>encap-group
Description 

This command configures the QoS ID.

scheduler-policy

Syntax 
scheduler-policy scheduler-policy-name
no scheduler-policy
Context 
config>service>vpls>sap>egress>encap-defined-qos>encap-group
Description 

This command configures the scheduler policy.

filter

Syntax 
filter ip ip-filter-id
filter ipv6 ipv6-filter-id
filter mac mac-filter-id
no filter [ip ip-filter-id] [mac mac-filter-id] [ipv6 ipv6-filter-id]
Context 
config>service>vpls>sap>egress
config>service>vpls>sap>ingress
config>service>vpls>mesh-sdp>egress
config>service>vpls>mesh-sdp>ingress
config>service>vpls>spoke-sdp>egress
config>service>vpls>spoke-sdp>ingress
Description 

This command associates an IP filter policy or MAC filter policy with an ingress or egress Service Access Point (SAP) or IP interface.

Filter policies control the forwarding and dropping of packets based on IP or MAC matching criteria. There are two types of filter policies: IP and MAC. Only one type may be applied to a SAP at a time.

The filter command is used to associate a filter policy with a specified filter ID with an ingress or egress SAP. The filter ID must already be defined before the filter command is executed. If the filter policy does not exist, the operation will fail and an error message returned.

In general, filters applied to SAPs (ingress or egress) apply to all packets on the SAP. One exception is non-IP packets are not applied to IP match criteria, so the default action in the filter policy applies to these packets.

This command is only supported in 'classic' configuration-mode (configure system management-interface configuration-mode classic).

The no form of this command removes any configured filter ID association with the SAP or IP interface. The filter ID itself is not removed from the system unless the scope of the created filter is set to local. To avoid deletion of the filter ID and only break the association with the service object, use scope command within the filter definition to change the scope to local or global. The default scope of a filter is local.

Special Cases 
VPLS—
Both MAC and IP filters are supported on a VPLS service SAP.
Parameters 
ip ip-filter-id
Specifies IP filter policy. The filter ID must already exist within the created IP filters.
Values—
1 to 65535

 

ipv6 ipv6-filter-id
Specifies the IPv6 filter policy. The filter ID must already exist within the created IPv6 filters.
Values—
1 to 65535

 

mac mac-filter-id
Specifies the MAC filter policy. The specified filter ID must already exist within the created MAC filters. The filter policy must already exist within the created MAC filters.
Values—
1 to 65535

 

hsmda-queue-override

Syntax 
[no] hsmda-queue-override
Context 
config>service>vpls>sap>egress
Description 

This command enters the context to configure HSMDA queue overrides.

queue

Syntax 
queue queue-id [create]
no queue queue-id
Context 
config>service>vpls>sap>egress>hsmda-queue-override
Description 

This command configures overrides for a HSMDA queue. The actual valid values are those defined in the specified SAP QoS policy.

Parameters 
queue-id—
Specifies the queue ID to override
Values—
1 to 8

 

create—
This keyword is mandatory while creating a new queue override

packet-byte-offset

Syntax 
packet-byte-offset {add add-bytes | subtract sub-bytes}
no packet-byte-offset
Context 
config>service>vpls>sap>egress>hsmda-queue-over
Description 

This command adds or subtracts the specified number of bytes to the accounting function for each packet handled by the HSMDA queue. Normally, the accounting and leaky bucket functions are based on the Ethernet DLC header, payload and the 4 byte CRC (everything except the preamble and inter-frame gap). As an example, the packet-byte-offset command can be used to add the frame encapsulation overhead (20 bytes) to the queues accounting functions.

The accounting functions affected include:

  1. Offered High Priority / In-Profile Octet Counter
  2. Offered Low Priority / Out-of-Profile Octet Counter
  3. Discarded High Priority / In-Profile Octet Counter
  4. Discarded Low Priority / Out-of-Profile Octet Counter
  5. Forwarded In-Profile Octet Counter
  6. Forwarded Out-of-Profile Octet Counter
  7. Peak Information Rate (PIR) Leaky Bucket Updates
  8. Committed Information Rate (CIR) Leaky Bucket Updates
  9. Queue Group Aggregate Rate Limit Leaky Bucket Updates

The secondary shaper leaky bucket, scheduler priority level leaky bucket and the port maximum rate updates are not affected by the configured packet-byte-offset. Each of these accounting functions are frame based and always include the preamble, DLC header, payload and the CRC regardless of the configured byte offset.

The packet-byte-offset command accepts either add or subtract as valid keywords which define whether bytes are being added or removed from each packet traversing the queue. Up to 31 bytes may be added to the packet and up to 32 bytes may be removed from the packet. An example use case for subtracting bytes from each packet is an IP based accounting function. Given a Dot1Q encapsulation, the command packet-byte-offset subtract 14 would remove the DLC header and the Dot1Q header from the size of each packet for accounting functions only. The 14 bytes are not actually removed from the packet, only the accounting size of the packet is affected.

As inferred above, the variable accounting size offered by the packet-byte-offset command is targeted at the queue and queue group level. The packet-byte-offset, when set, applies to all queues in the queue group. The accounting size of the packet is ignored by the secondary shapers, the scheduling priority level shapers and the scheduler maximum rate. The actual on-the-wire frame size is used for these functions to allow an accurate representation of the behavior of the subscribers packets on an Ethernet aggregation network.

The packet-byte-offset value may be overridden at the queue-group level.

Parameters 
add add-bytes
Indicates that the byte value should be added to the packet for queue and queue group level accounting functions. Either the add or subtract keyword must be specified. The corresponding byte value must be specified when executing the packet-byte-offset command. The add keyword is mutually exclusive with the subtract keyword.
Values—
0 to 31

 

subtract sub-bytes
Indicates that the byte value should be subtracted from the packet for queue and queue group level accounting functions. The subtract keyword is mutually exclusive with the add keyword. Either the add or subtract keyword must be specified. The corresponding byte value must be specified when executing the packet-byte-offset command.
Values—
1 to 64

 

slope-policy

Syntax 
slope-policy hsmda-slope-policy-name
no slope-policy
Context 
config>service>vpls>sap>egress>hsmda-queue-over>queue
Description 

This command specifies an existing slope policy name.

rate

Syntax 
rate pir-rate
no rate
Context 
config>service>vpls>sap>egress>hsmda-queue-over>queue
Description 

This command specifies the administrative PIR by the user.

Parameters 
pir-rate —
Configures the administrative PIR specified by the user.
Values—
1 to 40000000

 

wrr-weight

Syntax 
wrr-weight value
no wrr-weight
Context 
config>service>vpls>sap>egress>hsmda-queue-over>queue
Description 

This command assigns the weight value to the HSMDA queue.

The no form of the command returns the weight value for the queue to the default value.

Parameters 
percentage
Specifies the weight for the HSMDA queue
Values—
1 to 32

 

wrr-policy

Syntax 
wrr-policy hsmda-wrr-policy-name
no wrr-policy
Context 
config>service>vpls>sap>egress>hsmda-queue-over
Description 

This command associates an existing HSMDA weighted-round-robin (WRR) scheduling loop policy to the HSMDA queue.

Parameters 
hsmda-wrr-policy-name
Specifies the existing HSMDA WRR policy name to associate to the queue

secondary-shaper

Syntax 
secondary-shaper secondary-shaper-name
no secondary-shaper
Context 
config>service>vpls>sap>egress>hsmda-queue-over
Description 

This command configures an HSMDA secondary shaper. A shaper override can only be configured on an HSMDA SAP.

Parameters 
secondary-shaper-name—
Specifies a secondary shaper name up to 32 characters in length

qinq-mark-top-only

Syntax 
[no] qinq-mark-top-only
Context 
config>service>vpls>sap>egress
Description 

When enabled (the encapsulation type of the access port where this SAP is defined as qinq), the qinq-mark-top-only command specifies which P-bits/DEI bit to mark during packet egress. When disabled, both set of P-bits/DEI bit are marked. When enabled, only the P-bits/DEI bit in the top Q-tag are marked.

The no form of this command disables the command.

Default 

no qinq-mark-top-only

policer-control-override

Syntax 
policer-control-override [create]
no policer-control-override
Context 
config>service>vpls>sap>egress
config>service>vpls>sap>ingress
Description 

This command, within the SAP ingress or egress contexts, creates a CLI node for specific overrides to the applied policer-control-policy. A policy must be applied for a policer-control-overrides node to be created. If the policer-control-policy is removed or changed, the policer-control-overrides node is automatically deleted from the SAP.

The no form of the command removes any existing policer-control-policy overrides and the policer-control-overrides node from the SAP.

Default 

no policer-control-override

Parameters 
create—
The create keyword is required when the policer-control-overrides node is being created and the system is configured to expect explicit confirmation that a new object is being created. When the system is not configured to expect explicit confirmation, the create keyword is not required.

max-rate

Syntax 
max-rate {rate | max}
Context 
config>service>vpls>sap>egress config>service>vpls>sap>ingress
Description 

This command, within the SAP ingress and egress contexts, overrides the root arbiter parent policer max-rate that is defined within the policer-control-policy applied to the SAP.

When the override is defined, modifications to the policer-control-policy max-rate parameter have no effect on the SAP’s parent policer until the override is removed using the no max-rate command within the SAP.

Parameters 
rate | max—
Specifies the max rate override in kilobits per second or use the maximum
Values—
1 to 20000000 kb/s

 

priority-mbs-thresholds

Syntax 
priority-mbs-thresholds
Context 
config>service>vpls>sap>egress
Description 

This command overrides the CLI node contains the configured min-thresh-separation and the various priority level mbs-contribution override commands.

min-thresh-separation

Syntax 
min-thresh-separation size [bytes | kilobytes]
Context 
config>service>vpls>sap>egress config>service>vpls>sap>ingress
Description 

This command within the SAP ingress and egress contexts is used to override the root arbiter’s parent policer min-thresh-separation parameter that is defined within the policer-control-policy applied to the SAP.

When the override is defined, modifications to the policer-control-policy min-thresh-separation parameter have no effect on the SAP’s parent policer until the override is removed using the no min-thresh-separation command within the SAP.

The no form of the command removes the override and allows the min-thresh-separation setting from the policer-control-policy to control the root arbiter’s parent policer’s minimum discard threshold separation size.

Default 

no min-thresh-separation

Parameters 
bytes—
Signifies that size is expressed in bytes. The bytes and kilobytes keywords are mutually exclusive and are optionally used to qualify whether size is expressed in bytes or kilobytes. The default is kilobytes.
kilobytes—
The size parameter is required when specifying the min-thresh-separation override. It is specified as an integer representing either a number of bytes or kilobytes that are the minimum separation between the parent policer’s priority level discard thresholds.
Values—
0 to 16777216

 

Default—
kilobytes

priority

Syntax 
[no] priority level
Context 
config>service>vpls>sap>egress config>service>vpls>sap>ingress
Description 

The priority-level level override CLI node contains the specified priority level’s mbs-contribution override value.

This node does not need to be created and will not be output in show or save configurations unless an mbs-contribution override exist for level.

Parameters 
level—
Specifies that the level parameter is required when specifying priority-level and identifies which of the parent policer instances priority level’s the mbs-contribution is overriding
Values—
1 to 8

 

mbs-contribution

Syntax 
mbs-contribution size [bytes | kilobytes]
Context 
config>service>vpls>sap>egress config>service>vpls>sap>ingress
Description 

The mbs-contribution override command within the SAP ingress and egress contexts is used to override a parent policer’s priority level’s mbs-contribution parameter that is defined within the policer-control-policy applied to the SAP. This override allow the priority level’s burst tolerance to be tuned based on the needs of the SAP’s child policers attached to the priority level.

When the override is defined, modifications to the policer-control-policy priority level’s mbs-contribution parameter have no effect on the SAP’s parent policer priority level until the override is removed using the no mbs-contribution command within the SAP.

The no form of the command removes the override and allows the mbs-contribution setting from the policer-control-policy to control the parent policer’s priority level’s burst tolerance.

Default 

no mbs-contribution

Parameters 
bytes—
Signifies that size is expressed in bytes
kilobytes—
Signifies that the size is expressed in kilobytes
Values—
0 – 16777216 or default

 

policer-control-policy

Syntax 
policer-control-policy policy-name
no policer-control-policy
Context 
config>service>vpls>sap>egress
config>service>vpls>sap>ingress
config>service>template>vpls-sap-template>egress
config>service>template>vpls-sap-template>ingress
Description 

This command, within the qos CLI node, is used to create, delete or modify policer control policies. A policer control policy is very similar to the scheduler-policy which is used to manage a set of queues by defining a hierarchy of virtual schedulers and specifying how the virtual schedulers interact to provide an aggregate SLA. In a similar fashion, the policer-control-policy controls the aggregate bandwidth available to a set of child policers. Once created, the policy can be applied to ingress or egress SAPs. The policy may also be applied to the ingress or egress context of a sub-profile.

Policer Control Policy Instances

On the SAP side, an instance of a policy is created each time a policy is applied. When applied to a sub-profile, an instance of the policy is created each time a subscriber successfully maps one or more hosts to the profile per ingress SAP.

Each instance of the policer-control-policy manages the policers associated with the object that owns the policy instance (SAP or subscriber). If a policer on the object is parented to an appropriate arbiter name that exists within the policy, the policer will be managed by the instance. If a policer is not parented or is parented to a non-existent arbiter, the policer will be orphaned and will not be subject to bandwidth control by the policy instance.

Maximum Rate and Root Arbiter

The policer-control-policy supports an overall maximum rate (max-rate) that defines the total amount of bandwidth that may be distributed to all associated child policers. By default, that rate is set to max which provides an unlimited amount of bandwidth to the policers. Once the policy is created, an actual rate should be configured in order for the policy instances to be effective. At the SAP level, the maximum rate may be overridden on a per instance basis. For subscribers, the maximum rate may only be overridden on the subscriber profile which will then be applied to all instances associated with the profile.

The maximum rate is defined within the context of the root arbiter which is always present in a policer-control-policy. The system creates a parent policer which polices the output of all child policers attached to the policy instance to the configured rate. Child policers may be parented directly to the root arbiter (parent root) or parented to one of the tiered arbiters (parent arbiter-name). Since each tiered arbiter must be parented to either another tiered arbiter or the root arbiter (default), every parented child policer is associated with the root arbiter and therefore the root arbiter’s parent policer.

Parent Policer PIR Leaky Bucket Operation

The parent policer is a single leaky bucket that monitors the aggregate throughput rate of the associated child policers. Forwarded packets increment the bucket by the size of each packet. The rate of the parent policer is implemented as a bucket decrement function which attempts to drain the bucket. If the rate of the packets flowing through the bucket is less than the decrement rate, the bucket does not accumulate depth. Each packet that flows through the bucket is accompanied by a derived discard threshold. If the current depth of the bucket is less than the discard threshold, the packet is allowed to pass through, retaining the colors derived from the packet’s child policer. If the current depth is equal to or greater than the threshold value, the packet is colored red and the bucket depth is not incremented by the packet size. Also, any increased bucket depths in the child policer are canceled making any discard event an atomic function between the child and the parent.

Due to the fact that multiple thresholds are supported by the parent policer, the policer control policy is able to protect the throughput of higher priority child policers from the throughput of the lower priority child policers within the aggregate rate.

Tier 1 and Tier 2 Arbiters

As stated above, each child is attached either to the always available root arbiter or to an explicitly created tier 1 or tier 2 arbiter. Unlike the hardware parent policer based root arbiter, the arbiters at tier 1 and tier 2 are only represented in software and are meant to provide an arbitrary hierarchical bandwidth distribution capability. An arbiter created on tier 2 must parent to either to an arbiter on tier 1 or to the root arbiter. Arbiters created on tier 1 always parent to the root arbiter. In this manner, every arbiter ultimately is parented or grand-parented by the root arbiter.

Each tiered arbiter supports an optional rate parameter that defines a rate limit for all child arbiters or child policers associated with the arbiter. Child arbiters and policers attached to the arbiter have a level attribute that defines the strict level at which the child is given bandwidth by the arbiter. Level 8 is the highest and 1 is the lowest. Also a weight attribute defines each child’s weight at that strict level in order to determine how bandwidth is distributed to multiple children at that level when insufficient bandwidth is available to meet each child’s required bandwidth.

Fair and Unfair Bandwidth Control

Each child policer supports three leaky buckets. The PIR bucket manages the policer’s peak rate and maximum burst size, the CIR leaky bucket manages the policer’s committed rate and committed burst size. The third leaky bucket is used by the policer control policy instance to manage the child policer’s fair rate (FIR). When multiple child policers are attached to the root arbiter at the same priority level, the policy instance uses each child’s FIR bucket rate to control how much of the traffic forwarded by the policer is fair and how much is unfair.

In the simplest case where all the child policers in the same priority level are directly attached to the root arbiter, each child’s FIR rate is set according to the child’s weight divided by the sum of the active children’s weights multiplied by the available bandwidth at the priority level. The result is that the FIR bucket will mark the appropriate amount of traffic for each child as fair-based on the weighted fair output of the policy instance.

The fair/unfair forwarding control in the root parent policer is accomplished by implementing two different discard thresholds for the priority. The first threshold is discard-unfair and the second is discard-all for packet associated with the priority level. As the parent policer PIR bucket fills (due the aggregate forwarded rate being greater than the parent policers PIR decrement rate) and the bucket depth reaches the first threshold, all unfair packets within the priority are discarded. This leaves room in the bucket for the fair packets to be forwarded.

In the more complex case where one or more tiered arbiters are attached at the priority level, the policer control policy instance must consider more than just the child policer weights associated with the attached arbiter. If the arbiter is configured with an aggregate rate limit that its children cannot exceed, the policer control policy instance will switch to calculating the rate each child serviced by the arbiter should receive and enforces that rate using each child policers PIR leaky bucket.

When the child policer PIR leaky bucket is used to limit the bandwidth for the child policer and the child’s PIR bucket discard threshold is reached, packets associated with the child policer are discarded. The child policer’s discarded packets do not consume depth in the child policer’s CIR or FIR buckets. The child policers discarded packets are also prevented from impacting the parent policer and will not consume the aggregate bandwidth managed by the parent policer.

Parent Policer Priority Level Thresholds

As stated above, each child policer is attached either to the root arbiter or explicitly to one of the tier 1 or tier 2 arbiters. When attached directly to the root arbiter, its priority relative to all other child policers is indicated by the parenting level parameter. When attached through one of the tiered arbiters, the parenting hierarchy of the arbiters must be traced through to the ultimate attachment to the root arbiter. The parenting level parameter of the arbiter parented to the root arbiter defines the child policer’s priority level within the parent policer.

The priority level is important since it defines the parent policer discard thresholds that will be applied at the parent policer. The parent policer has 8 levels of strict priority and each priority level has its own discard-unfair and discard-all thresholds. Each priority’s thresholds are larger than the thresholds of the lower priority levels. This ensures that when the parent policer is discarding, it will be priority sensitive.

To visualize the behavior of the parent policer, picture that when the aggregate forwarding rate of all child policers is currently above the decrement rate of the parent PIR leaky bucket, the bucket depth will increase over time. As the bucket depth increases, it will eventually cross the lowest priority’s discard-unfair threshold. If this amount of discard sufficiently lowers the remaining aggregate child policer rate, the parent PIR bucket will hover around this bucket depth. If however, the remaining aggregate child rate is still greater than the decrement rate, the bucket will continue to rise and eventually reach the lowest priority’s discard-all threshold which will cause all packets associated with the priority level to be discarded (fair and unfair). Again, if the remaining aggregate child rate is less than or equal to the bucket decrement rate, the parent PIR bucket will hover around this higher bucket depth. If the remaining aggregate child rate is still higher than the decrement rate, the bucket will continue to rise through the remaining priority level discards until equilibrium is achieved.

As noted above, each child’s rate feeding into the parent policer is governed by the child policer’s PIR bucket decrement rate. The amount of bandwidth the child policer offers to the parent policer will not exceed the child policer’s configured maximum rate.

Root Arbiter’s Parent Policer’s Priority Aggregate Thresholds

Each policer-control-policy root arbiter supports configurable aggregate priority thresholds which are used to control burst tolerance within each priority level. Two values are maintained per priority level; the shared-portion and the fair-portion. The shared-portion represents the amount of parent PIR bucket depth that is allowed to be consumed by both fair and unfair child packets at the priority level. The fair-portion represents the amount of parent PIR bucket depth that only the fair child policer packets may consume within the priority level. It should be noted that the fair and unfair child packets associated with a higher parent policer priority level may also consume the bucket depth set aside for this priority.

While the policy maintains a parent policer default or explicit configurable values for shared-portion and fair-portion within each priority level, it is possible that some priority levels will not be used within the parent policer. Most parent policer use cases require fewer than eight strict priority levels.

To derive the actual priority level discard-unfair and discard-all thresholds while only accounting for the actual in-use priority levels, the system maintains a child policer to parent policer association counter per priority level for each policer control policy instance. As a child policer is parented to either the root or a tiered arbiter, the system determines the parent policer priority level for the child policer and increments the association counter for that priority level on the parent policer instance.

The shared-portion for each priority level is affected by the parent policer global min-thresh-separation parameter that defines the minimum separation between any in-use discard thresholds. When more than one child policer is associated with a parent policer priority level, the shared-portion for that priority level will be the current value of min-thresh-separation. When only a single child policer is associated, the priority level’s shared-portion is zero since all packets from the child will be marked fair and the discard-unfair threshold is meaningless. When the association counter is zero, both the shared-portion and the fair-portion for that priority level are zero since neither discard thresholds will be used. Whenever the association counter is greater than 0, the fair-portion for that priority level will be derived from the current value of the priority’s mbs-contribution parameter and the global min-thresh-separation parameter.

Each priority level’s discard-unfair and discard-all thresholds are calculated based on an accumulation of lower priorities shared-portions and fair-portions and the priority level’s own shared-portion and fair-portion. The base threshold value for each priority level is equal to the sum of all lower priority level’s shared-portions and fair-portions. The discard-unfair threshold is the priority level’s base threshold plus the priority level’s shared-portion. The discard-all threshold for the priority level is the priority level’s base threshold plus both the shared-portion and fair-portion values of the priority. As can be seen, an in-use priority level’s thresholds are always greater than the thresholds of lower priority levels.

Policer Control Policy Application

A policer-control-policy may be applied on any Ethernet ingress or egress SAP that is associated with a port (or ports in the case of LAG).

The no form of the command removes a non-associated policer control policy from the system. The command will not execute when policer-name is currently associated with any SAP or subscriber management sub-profile context.

Default 

none

Parameters 
policy-name—
Specifies the policy name. Each policer-control-policy must be created with a unique policy name. The name must given as policy-name must adhere to the system policy ASCII naming requirements. If the defined policy-name already exists, the system will enter that policy’s context for editing purposes. If policy-name does not exist, the system will attempt to create a policy with the specified name. Creating a policy may require use of the create parameter when the system is configured for explicit object creation mode.
create—
The keyword is required when a new policy is being created and the system is configured for explicit object creation mode.

qos

Syntax 
qos policy-id [shared-queuing |multipoint-shared]
qos name sap-ingress-policy-name [shared-queuing |multipoint-shared]
no qos [policy-id]
Context 
config>service>template>vpls-sap-template>ingress
Description 

This command associates a Quality of Service (QoS) policy with an ingress Service Access Point (SAP) for the Epipe SAP template.

Default 

none

Parameters 
policy-id—
The ingress policy ID to associate with SAP or IP interface on ingress. The policy ID must already exist.

This variant of the command is only supported in 'classic' configuration-mode (configure system management-interface configuration-mode classic). The qos name sap-ingress-policy-name variant can be used in all configuration modes.

Values—
1 to 65535

 

shared-queuing—
This keyword can only be specified on SAP ingress. Specify the ingress shared queue policy used by this SAP. When the value of this object is null, the SAP will use individual ingress QoS queues, instead of the shared ones.
multipoint-shared—
This keyword can only be specified on SAP ingress. Multipoint shared queuing is a superset of shared queuing. When multipoint shared queuing keyword is set, as well as the unicast packets, multipoint packets also used shared queues.

Ingress unicast service queues are mapped one-for-one with hardware queues and unicast packets traverse the ingress forwarding plane twice, similar to the shared-queuing option. In addition, the multipoint queues defined in the ingress SAP QoS policy are not created. Instead, multipoint packets (broadcast, multicast and unknown unicast destined) are treated to the same dual pass ingress forwarding plane processing as unicast packets.

When the value of this object is null, the SAP will use individual ingress QoS queues, instead of the shared ones.

When the value of this object is null, the SAP will use individual ingress QoS queues, instead of the shared ones.

Values—
Multipoint or not present

 

Default—
Present (the queue is created as non-multipoint)
sap-ingress-policy-name—
The SAP ingress QoS policy name to associate with the SAP on ingress, up to 64 characters.

qos

Syntax 
qos sap-egress-policy-id
qos name sap-egress-policy-name
no qos
Context 
config>service>template>vpls-sap-template>egress
Description 

This command associates an existing QoS policy with the template.

Parameters 
sap-egress-policy-id—
The egress policy ID to associate with SAP or IP interface on egress. The policy ID must already exist.

This variant of the command is only supported in 'classic' configuration-mode (configure system management-interface configuration-mode classic). The qos name sap-egress-policy-name variant can be used in all configuration modes.

Values—
1 to 65535

 

sap-egress-policy-name—
The SAP egress QoS policy name to associate with the SAP on egress, up to 64 characters.

policer-override

Syntax 
[no] policer-override
Context 
config>service>vpls>sap>egress
config>service>vpls>sap>ingress
Description 

This command, within the SAP ingress or egress contexts, is used to create a CLI node for specific overrides to one or more policers created on the SAP through the sap-ingress or sap-egress QoS policies.

The no form of the command is used to remove any existing policer overrides.

Default 

no policer-overrides

policer

Syntax 
policer policer-id [create]
no policer policer-id
Context 
config>service>vpls>sap>egress>policer-override
config>service>vpls>sap>ingress>policer-override
Description 

This command, within the SAP ingress or egress contexts, is used to create a CLI node for specific overrides to a specific policer created on the SAP through a sap-ingress or sap-egress QoS policy.

The no form of the command is used to remove any existing overrides for the specified policer-id.

Parameters 
policer-id—
The policer-id parameter is required when executing the policer command within the policer-overrides context. The specified policer-id must exist within the sap-ingress or sap-egress QoS policy applied to the SAP. If the policer is not currently used by any forwarding class or forwarding type mappings, the policer will not actually exist on the SAP. This does not preclude creating an override context for the policer-id.
create—
The create keyword is required when a policer policer-id override node is being created and the system is configured to expect explicit confirmation that a new object is being created. When the system is not configured to expect explicit confirmation, the create keyword is not required.

cbs

Syntax 
cbs size [bytes | kilobytes]
no cbs
Context 
config>service>vpls>sap>egress>policer-override
config>service>vpls>sap>ingress>policer-override
Description 

This command, within the SAP ingress and egress policer-overrides contexts, is used to override the sap-ingress and sap-egress QoS policy configured CBS parameter for the specified policer-id.

The no form of this command returns the CBS size to the default value.

Default 

no cbs

Parameters 
size-in-kbytes—
This parameter is required when specifying mbs override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
Values—
0 to 16777216 or default

 

mbs

Syntax 
mbs {size [bytes | kilobytes] | default}
no mbs
Context 
config>service>vpls>sap>egress>policer-override>policer config>service>vpls>sap>ingress>policer-override>policer
Description 

This command, within the SAP ingress and egress policer-overrides contexts, is used to override the sap-ingress and sap-egress QoS policy configured mbs parameter for the specified policer-id.

The no form of the command restores the policer’s mbs setting to the policy defined value.

Default 

no mbs

Parameters 
size —
 The size parameter is required when specifying an mbs override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional bytes and kilobytes keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
Values—
0 to 16777216 | default

 

bytes—
When bytes is defined, the value given for size is interpreted as the policer’s MBS value in bytes.
kilobytes—
When kilobytes is defined, the value given for size is interpreted as the policer’s MBS value in kilobytes.

packet-byte-offset

Syntax 
packet-byte-offset {add add-bytes | subtract sub-bytes}
Context 
config>service>vpls>sap>egress>policer-override>policer config>service>vpls>sap>ingress>policer-override>policer
Description 

This command, within the SAP ingress and egress policer-overrides contexts, is used to override the sap-ingress and sap-egress QoS policy configured packet-byte-offset parameter for the specified policer-id. Packet byte offset settings are not included in the applied rate when (queue) frame based accounting is configured, however the offsets are applied to the statistics.

The no form of the command restores the policer’s packet-byte-offset setting to the policy defined value.

Default 

no packet-byte-offset

Parameters 
add add-bytes
The add keyword is mutually exclusive to the subtract keyword. Either add or subtract must be specified. When add is defined the corresponding bytes parameter specifies the number of bytes that is added to the size each packet associated with the policer for rate metering, profiling and accounting purposes. From the policer’s perspective, the maximum packet size is increased by the amount being added to the size of each packet.
Values—
1 to 31

 

subtract sub-bytes
The subtract keyword is mutually exclusive to the add keyword. Either add or subtract must be specified. When subtract is defined the corresponding bytes parameter specifies the number of bytes that is subtracted from the size of each packet associated with the policer for rate metering, profiling and accounting purposes. From the policer’s perspective, the maximum packet size is reduced by the amount being subtracted from the size of each packet.
Values—
1 to 64

 

rate

Syntax 
rate {rate | max} [cir {max | rate}]
Context 
config>service>vpls>sap>egress>policer-override>policer config>service>vpls>sap>ingress>policer-override>policer
Description 

This command within the SAP ingress and egress policer-overrides contexts is used to override the sap-ingress and sap-egress QoS policy configured rate parameters for the specified policer-id.

The no form of the command restores the policy defined metering and profiling rate to a policer.

Parameters 
{rate | max}
Specifying the keyword max or an explicit kilobits per second parameter directly following the rate override command is required and identifies the policer instance’s metering rate for the PIR leaky bucket. The kilobits per second value must be expressed as an integer and defines the rate in kilobits per second. The integer value is multiplied by 1,000 to derive the actual rate in bits per second. When max is specified, the maximum policer rate used will be equal to the maximum capacity of the card on which the policer is configured. If the policer rate is set to a value larger than the maximum rate possible for the card, then the PIR used is equivalent to max.
Values—
1 to 2000000000, max

 

cir {max | rate}
The optional cir keyword is used to override the policy derived profiling rate of the policer. Specifying the keyword max or an explicit kilobits per second parameter directly following the cir keyword is required. The kilobits per second value must be expressed as an integer and defines the rate in kilobits per second. The integer value is multiplied by 1,000 to derive the actual rate in bits per second. When max is specified, the maximum policer rate used will be equal to the maximum capacity of the card on which the policer is configured. If the policer rate is set to a value larger than the maximum rate possible for the card, then the CIR used is equivalent to max.
Values—
0 to 2000000000, max

 

stat-mode

Syntax 
stat-mode stat-mode
no stat-mode
Context 
config>service>vpls>sap>egress>policer-override>policer config>service>vpls>sap>ingress>policer-override>policer
Description 

The SAP-egress QoS policy’s policer stat-mode command is used to configure the forwarding plane counters that allow offered, output and discard accounting to occur for the policer. A policer has multiple types of offered packets (for example, soft in-profile and out-of-profile from ingress and hard in-profile and out-of-profile due to egress profile overrides) and each of these offered types is interacting with the policers metering and profiling functions resulting in colored output packets (green, yellow and red). Due to the potential large number of egress policers, it is not economical to allocate counters in the forwarding plane for all possible offered packet types and output conditions. Many policers will not be configured with a CIR profiling rate and not all policers will receive explicitly re-profiled offered packets. The stat-mode command allows provisioning of the number of counters each policer requires and how the offered packet types and output conditions should be mapped to the counters.

While a no-stats mode is supported which prevents any packet accounting, the use of the policer’s parent command requires that the policer’s stat-mode to be set at least to the minimal setting so that offered stats are available for the policer’s Fair Information Rate (FIR) to be calculated.

Each time the policer’s stat-mode is changed, any previous counter values are lost and any new counters are set to zero.

Each mode uses a certain number of counters per policer instance that are allocated from the forwarding plane’s policer counter resources.You can view the total/allocated/free stats by using the tools dump system-resources command. If insufficient counters exist to implement a mode on any policer instance, the stat-mode change will fail and the previous mode will continue unaffected for all instances of the policer.

The default stat-mode when a policer is created within the policy is minimal.

The stat-mode setting defined for the policer in the QoS policy may be overridden on a SAP where the policy is applied. If insufficient policer counter resources exist to implement the override, the stat-mode override command will fail. The previous stat-mode setting active for the policer will continue to be used by the policer.

The no form of the command returns the policer’s stat-mode setting to minimal.

Refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Quality of Service Guide for detailed information about the policer stat-mode command parameters.

qos

Syntax 
qos policy-id [shared-queuing | multipoint-shared] [fp-redirect-group queue-group-name instance instance-id]
no qos
Context 
config>service>vpls>sap>ingress
Description 

This command associates a Quality of Service (QoS) policy with an ingress Service Access Point (SAP).

QoS ingress and egress policies are important for the enforcement of SLA agreements. The policy ID must be defined prior to associating the policy with a SAP or IP interface. If the policy-id does not exist, an error will be returned.

The qos command is used to associate both ingress and egress QoS policies. The qos command only allows ingress policies to be associated on SAP ingress and egress policies on SAP egress. Attempts to associate a QoS policy of the wrong type returns an error.

Only one ingress and one egress QoS policy can be associated with a SAP at one time. Attempts to associate a second QoS policy of a specified type will return an error.

When an ingress QoS policy is defined on IES ingress IP interface that is bound to a VPLS, the policy becomes associated with every SAP on the VPLS and augments the QoS policy that is defined on each SAP. Packets that are bridged will be processed using the policy defined on the VPLS SAP; packets that are routed will be processed using the policy defined in the IES IP interface-binding context.

By default, if no specific QoS policy is associated with the SAP for ingress or egress, the default QoS policy is used.

The no form of this command removes the QoS policy association from the SAP, and the QoS policy reverts to the default.

Default 

none

Parameters 
policy-id—
The ingress policy ID to associate with SAP or IP interface on ingress. The policy ID must already exist.
Values—
1 to 65535

 

shared-queuing—
This keyword can only be specified on SAP ingress. Specify the ingress shared queue policy used by this SAP. When the value of this object is null, the SAP will use individual ingress QoS queues, instead of the shared ones.
multipoint-shared—
This keyword can only be specified on SAP ingress. Multipoint shared queuing is a superset of shared queuing. When multipoint shared queuing keyword is set, as well as the unicast packets, multipoint packets also used shared queues.

Ingress unicast service queues are mapped one-for-one with hardware queues and unicast packets traverse the ingress forwarding plane twice, similar to the shared-queuing option. In addition, the multipoint queues defined in the ingress SAP QoS policy are not created. Instead, multipoint packets (broadcast, multicast and unknown unicast destined) are treated to the same dual pass ingress forwarding plane processing as unicast packets.

When the value of this object is null, the SAP will use individual ingress QoS queues, instead of the shared ones.

When the value of this object is null, the SAP will use individual ingress QoS queues, instead of the shared ones.

Values—
Multipoint or not present

 

Default—
Present (the queue is created as non-multipoint)
fp-redirect-group—
Creates an instance of a named queue group template on the ingress forwarding plane of a specified IOM/IMM/XMA. The queue-group-name and instance instance-id are mandatory parameters when executing the command. The named queue group template can contain only policers. If it contains queues, then the command will fail.
queue-group-name
Specifies the name of the queue group template to be instantiated on the forwarding plane of the IOM/IMM/XMA, up to 32 characters in length. The queue-group-name must correspond to a valid ingress queue group template name, configured under config>qos>queue- group-templates.
instance-id
Specifies the instance of the named queue group to be created on the IOM/IMMXMA ingress forwarding plane.

qos

Syntax 
qos policy-id [port-redirect-group queue-group-name instance instance-id]
no qos
Context 
config>service>vpls>sap>egress
Description 

This command associates a Quality of Service (QoS) policy with an egress Service Access Point (SAP).

QoS ingress and egress policies are important for the enforcement of SLA agreements. The policy ID must be defined prior to associating the policy with a SAP. If the policy-id does not exist, an error will be returned.

The qos command is used to associate both ingress and egress QoS policies. The qos command only allows ingress policies to be associated on SAP ingress and egress policies on SAP egress. Attempts to associate a QoS policy of the wrong type returns an error.

Only one ingress and one egress QoS policy can be associated with a SAP at one time. Attempts to associate a second QoS policy of a specified type will return an error.

When an egress QoS policy is associated with an IES IP interface that has been bound to a VPLS, the policy becomes associated with every SAP on the VPLS and augments the egress QoS policy that is defined on each SAP. Packets that are bridged will be processed using the policy defined on the VPLS SAP; packets that are routed will be processed using the policy defined in the IES IP interface- binding context.

By default, if no specific QoS policy is associated with the SAP for ingress or egress, so the default QoS policy is used.

The no form of this command removes the QoS policy association from the SAP, and the QoS policy reverts to the default.

Default 

none

Parameters 
port-redirect-group—
Associates a SAP egress with an instance of a named queue group template on the egress port of a specified IOM/IMM/XMA. The queue-group-name and instance instance-id are mandatory parameters when executing the command.
queue-group-name
Specifies the name of the egress port queue group of the IOM/IMM/XMA, up to 32 characters in length. The queue-group-name must correspond to a valid egress queue group, created under config>port>ethernet>access>egress.
instance instance-id
Specifies the instance of the named egress port queue group on the IOM/IMM/XMA
Values—
1 to 40960

 

Default—
1

queue-override

Syntax 
[no] queue-override
Context 
config>service>vpls>sap>egress
config>service>vpls>sap>ingress
config>service>vpls>sap>egress>hsmda-queue-over>queue
config>service>vpls>sap>ingress>hsmda-queue-over>queue
Description 

This command enters the context to configure override values for the specified SAP egress or ingress QoS queue. These values override the corresponding ones specified in the associated SAP egress or ingress QoS policy.

queue

Syntax 
[no] queue queue-id
Context 
config>service>vpls>sap>egress>queue-override
config>service>vpls>sap>ingress>queue-override
Description 

This command specifies the ID of the queue whose parameters are to be overridden.

The no form of the command removes the queue-id from the configuration.

Parameters 
queue-id—
The queue ID whose parameters are to be overridden
Values—
1 to 32

 

adaptation-rule

Syntax 
adaptation-rule [pir {max | min | closest}] [cir {max | min | closest}]
no adaptation-rule
Context 
config>service>vpls>sap>egress>queue-override>queue
config>service>vpls>sap>ingress>queue-override>queue
Description 

This command can be used to override specific attributes of the specified queue’s adaptation rule parameters. The adaptation rule controls the method used by the system to derive the operational CIR and PIR settings when the queue is provisioned in hardware. For the CIR and PIR parameters individually, the system attempts to find the best operational rate depending on the defined constraint.

The no form of the command removes any explicitly defined constraints used to derive the operational CIR and PIR created by the application of the policy. When a specific adaptation-rule is removed, the default constraints for rate and cir apply.

Default 

no adaptation-rule

Parameters 
pir—
The pir parameter defines the constraints enforced when adapting the PIR rate defined within the queue queue-id rate command. The pir parameter requires a qualifier that defines the constraint used when deriving the operational PIR for the queue. When the rate command is not specified, the default applies.
cir—
The cir parameter defines the constraints enforced when adapting the CIR rate defined within the queue queue-id rate command. The cir parameter requires a qualifier that defines the constraint used when deriving the operational CIR for the queue. When the cir parameter is not specified, the default constraint applies.
adaptation-rule—
Specifies the criteria to use to compute the operational CIR and PIR values for this queue, while maintaining a minimum offset
Values—
max — The max (maximum) keyword is mutually exclusive with the min and closest options. When max is defined, the operational PIR for the queue will be equal to or less than the administrative rate specified using the rate command.
min — The min (minimum) keyword is mutually exclusive with the max and closest options. When min is defined, the operational PIR for the queue will be equal to or greater than the administrative rate specified using the rate command.
closest — The closest parameter is mutually exclusive with the min and max parameter. When closest is defined, the operational PIR for the queue will be the rate closest to the rate specified using the rate command.

 

avg-frame-overhead

Syntax 
avg-frame-overhead percent
no avg-frame-overhead
Context 
config>service>vpls>sap>egress>queue-override>queue
Description 

This command configures the average frame overhead to define the average percentage that the offered load to a queue will expand during the frame encapsulation process before sending traffic on-the-wire. While the avg-frame-overhead value may be defined on any queue, it is only used by the system for queues that egress a SONET or SDH port or channel. Queues operating on egress Ethernet ports automatically calculate the frame encapsulation overhead based on a 20 byte per packet rule (8 bytes for preamble and 12 bytes for Inter-Frame Gap).

When calculating the frame encapsulation overhead for port scheduling purposes, the system determines the following values:

  1. Offered-load — The offered-load of a queue is calculated by starting with the queue depth in octets, adding the received octets at the queue and subtracting queue discard octets. The result is the number of octets the queue has available to transmit. This is the packet based offered-load.
  2. Frame encapsulation overhead — Using the avg-frame-overhead parameter, the frame encapsulation overhead is simply the queue’s current offered-load (how much has been received by the queue) multiplied by the avg-frame-overhead. If a queue had an offered load of 10000 octets and the avg-frame-overhead equals 10%, the frame encapsulation overhead would be 10000 x 0.1 or 1000 octets.

For egress Ethernet queues, the frame encapsulation overhead is calculated by multiplying the number of offered-packets for the queue by 20 bytes. If a queue was offered 50 packets then the frame encapsulation overhead would be 50 x 20 or 1000 octets.

  1. Frame based offered-load — The frame based offered-load is calculated by adding the offered-load to the frame encapsulation overhead. If the offered-load is 10000 octets and the encapsulation overhead was 1000 octets, the frame based offered-load would equal 11000 octets.
  2. Packet to frame factor — The packet to frame factor is calculated by dividing the frame encapsulation overhead by the queue’s offered-load (packet based). If the frame encapsulation overhead is 1000 octets and the offered-load is 10000 octets then the packet to frame factor would be 1000 / 10000 or 0.1. When in use, the avg-frame-overhead will be the same as the packet to frame factor making this calculation unnecessary.
  3. Frame based CIR — The frame based CIR is calculated by multiplying the packet to frame factor with the queue’s configured CIR and then adding that result to that CIR. If the queue CIR is set at 500 octets and the packet to frame factor equals 0.1, the frame based CIR would be 500 x 1.1 or 550 octets.
  4. Frame based within-cir offered-load — The frame based within-cir offered-load is the portion of the frame based offered-load considered to be within the frame-based CIR. The frame based within-cir offered-load is the lesser of the frame based offered-load and the frame based CIR. If the frame based offered-load equaled 11000 octets and the frame based CIR equaled 550 octets, the frame based within-cir offered-load would be limited to 550 octets. If the frame based offered-load equaled 450 octets and the frame based CIR equaled 550 octets, the frame based within-cir offered-load would equal 450 octets (or the entire frame based offered-load).

As a special case, when a queue or associated intermediate scheduler is configured with a CIR-weight equal to 0, the system automatically sets the queue’s frame based within-cir offered-load to 0, preventing it from receiving bandwidth during the port scheduler’s within-cir pass.

  1. Frame based PIR — The frame based PIR is calculated by multiplying the packet to frame factor with the queue’s configured PIR and then adding the result to that PIR. If the queue PIR is set to 7500 octets and the packet to frame factor equals 0.1, the frame based PIR would be 7500 x 1.1 or 8250 octets.
  2. Frame based within-pir offered-load — The frame based within-pir offered-load is the portion of the frame based offered-load considered to be within the frame based PIR. The frame based within-pir offered-load is the lesser of the frame based offered-load and the frame based PIR. If the frame based offered-load equaled 11000 octets and the frame based PIR equaled 8250 octets, the frame based within-pir offered-load would be limited to 8250 octets. If the frame based offered-load equaled 7000 octets and the frame based PIR equaled 8250 octets, the frame based within-pir offered load would equal 7000 octets.

Port scheduler operation using frame transformed rates — The port scheduler uses the frame based rates to calculate the maximum rates that each queue may receive during the within-cir and above-cir bandwidth allocation passes. During the within-cir pass, a queue may receive up to its frame based within-cir offered-load. The maximum it may receive during the above-cir pass is the difference between the frame based within-pir offered load and the amount of actual bandwidth allocated during the within-cir pass.

SAP and subscriber SLA-profile average frame overhead override — The average frame overhead parameter on a sap-egress may be overridden at an individual egress queue basis. On each SAP and within the sla-profile policy used by subscribers an avg-frame-overhead command may be defined under the queue-override context for each queue. When overridden, the queue instance will use its local value for the average frame overhead instead of the sap-egress defined overhead.

The no form of this command restores the average frame overhead parameter for the queue to the default value of 0 percent. When set to 0, the system uses the packet based queue statistics for calculating port scheduler priority bandwidth allocation. If the no avg-frame-overhead command is executed in a queue-override queue id context, the avg-frame-overhead setting for the queue within the sap-egress QoS policy takes effect.

Default 

0

Parameters 
percent—
This parameter sets the average amount of packet-to-frame encapsulation overhead expected for the queue. This value is not used by the system for egress Ethernet queues.
Values—
0 to 100

 

burst-limit

Syntax 
burst-limit {default | size [bytes | kilobytes]}
no burst-limit
Context 
config>service>vpls>sap>egress>queue-override>queue
Description 

The queue burst-limit command defines an explicit shaping burst size for a queue. The configured size defines the shaping leaky bucket threshold level that indicates the maximum burst over the queue's shaping rate.The no form of this command restores the default burst limit to the specified queue. This is equivalent to specifying burst-limit default within the QoS policies. When specified within a queue-override queue context, any current burst limit override for the queue is removed and the queue's burst limit is controlled by its defining policy.

Default 

no burst-limit

Parameters 
default—
Reverts the queue's burst limit to the system default value.
size—
When a numeric value is specified (size), the system interprets the value as an explicit burst limit size. The value is expressed as an integer and by default is interpreted as the burst limit in kilobytes. If the value is intended to be interpreted in bytes, the bytes qualifier must be added following size.
Values—
1 to 13671 kilobytes
1 to 14000000 bytes

 

Default—
No default for size; use the default keyword to specify default burst limit.
bytes—
Specifies that the value given for size must be interpreted as the burst limit in bytes.
kilobytes—
Specifies that the value given for size must be interpreted as the burst limit in kilobytes. If neither bytes nor kilobytes is specified, the default qualifier is kilobytes.

cbs

Syntax 
cbs size-in-kbytes
no cbs
Context 
config>service>vpls>sap>egress>queue-override>queue
config>service>vpls>sap>ingress>queue-override>queue
Description 

This command can be used to override specific attributes of the specified queue’s CBS parameters.

It is permissible to oversubscribe the total CBS reserved buffers for a specified access port egress buffer pool. Over-subscription may be desirable due to the potential large number of service queues and the economy of statistical multiplexing the individual queue’s CBS setting into the defined reserved total.

When oversubscribing the reserved total, it is possible for a queue depth to be lower than its CBS setting and still not receive a buffer from the buffer pool for an ingress frame. As more queues are using their CBS buffers and the total in use exceeds the defined reserved total, essentially the buffers are being removed from the shared portion of the pool without the shared in use average and total counts being decremented. This can affect the operation of the high and low priority RED slopes on the pool, causing them to miscalculate when to start randomly drop packets.

The no form of this command returns the CBS to the default value.

Default 

no cbs

Parameters 
size-in-kbytes—
Specifies the number of kilobytes reserved for the queue. For a value of 10 kbytes, enter the value 10. A value of 0 specifies that no reserved buffers are required by the queue (a minimum reserved size can be applied for scheduling purposes).
Values—
0 to 131072 or default

 

drop-tail

Syntax 
drop-tail
Context 
config>service>vpls>sap>egress>queue-override>queue
config>service>vpls>sap>ingress>queue-override>queue
Description 

This command enters the context to configure queue drop tail parameters.

low

Syntax 
low
Context 
config>service>vpls>sap>egress>queue-override>queue>drop-tail
config>service>vpls>sap>ingress>queue-override>queue>drop-tail
Description 

This command enters the context to configure the queue low drop tail parameters. The low drop tail defines the queue depth beyond which out-of-profile packets are not accepted into the queue and will be discarded.

percent-reduction-from-mbs

Syntax 
percent-reduction-from-mbs percent
no percent-reduction-from-mbs
Context 
config>service>vpls>sap>egress>queue-override>queue>drop-tail>low
config>service>vpls>sap>ingress>queue-override>queue>drop-tail>low
Description 

This command overrides the low queue drop tail as a percentage reduction from the MBS of the queue. For example, if a queue has an MBS of 600 kbytes and the percentage reduction is configured to be 30% for the low drop tail, then the low drop tail will be at 420 kbytes and out-of-profile packets are not accepted into the queue if the queue depth is greater than the low drop tail value, and so will be discarded.

Parameters 
percent—
Specifies the percentage reduction from the MBS for a queue drop tail.
Values—
0 to 100, default

 

mbs

Syntax 
mbs {size [bytes | kilobytes] | default}
no mbs
Context 
config>service>vpls>sap>egress>queue-override>queue
config>service>vpls>sap>ingress>queue-override>queue
Description 

This command overrides specific attributes of the specified queue’s MBS parameters. The MBS is a mechanism to override the default maximum size for the queue.

The sum of the MBS for all queues on an egress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope a packet is associated with. A queue that has not exceeded its MBS size is not guaranteed that a buffer will be available when needed or that the packet’s RED slope will not force the discard of the packet. Setting correct CBS parameters and controlling CBS over-subscription is one major safeguard to queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.

The no form of this command returns the MBS assigned to the queue to the default setting.

Default 

default

Parameters 
size—
The size parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional bytes and kilobytes keywords are mutually exclusive and are used to explicitly define whether the size represents bytes or kilobytes.
Values—
0 to 1073741824
default

 

bytes—
When byte is defined, the value given for size is interpreted as the queue'sMBS value given in bytes.
kilobytes—
When kilobytes is defined, the value is interpreted as the queue's MBSvalue given in kilobytes.
default—
Specifying the keyword default sets the MBS to its default value.

mbs

Syntax 
mbs {size [bytes | kilobytes] | default}
no mbs
Context 
config>service>vpls>sap>ingress>queue-override>queue
Description 

This command overrides specific attributes of the specified queue’s MBS parameters. The MBS value is used by a queue to determine whether it has exhausted all of its buffers while enqueuing packets. Once the queue has exceeded the amount of buffers allowed by MBS, all packets are discarded until packets have been drained from the queue.

The sum of the MBS for all queues on an ingress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope a packet is associated with. A queue that has not exceeded its MBS is not guaranteed that a buffer will be available when needed or that the packets RED slope will not force the discard of the packet. Setting correct CBS parameters and controlling CBS over-subscription is one major safeguard to queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.

The no form of this command returns the MBS assigned to the queue to the default value.

Default 

default

Parameters 
size—
The size parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional bytes and kilobytes keywords are mutually exclusive and are used to explicitly define whether the size represents bytes or kilobytes.
Values—
0 to 1073741824
default

 

bytes—
When byte is defined, the value given for size is interpreted as the queue'sMBS value given in bytes.
kilobytes—
When kilobytes is defined, the value is interpreted as the queue's MBSvalue given in kilobytes.
default—
Specifying the keyword default sets the MBS to its default value.

parent

Syntax 
parent {[weight weight] [cir-weight cir-weight]}
no parent
Context 
config>service>vpls>sap>egress>queue-override>queue
config>service>vpls>sap>ingress>queue-override>queue
Description 

This command defines an optional parent scheduler that further governs the available bandwidth given the queue aside from the queue’s PIR setting. When multiple schedulers and/or queues share a child status with the parent scheduler, the weight or level parameters define how this queue contends with the other children for the parent’s bandwidth.

Checks are not performed to see if a scheduler-name exists when the parent command is defined on the queue. Scheduler names are configured in the config>qos>scheduler-policy>tier level context. Multiple schedulers can exist with the scheduler-name and the association pertains to a scheduler that should exist on the egress SAP as the policy is applied and the queue created. When the queue is created on the egress SAP, the existence of the scheduler-name is dependent on a scheduler policy containing the scheduler-name being directly or indirectly applied (through a multi-service customer site) to the egress SAP. If the scheduler-name does not exist, the queue is placed in the orphaned operational state. The queue will accept packets but will not be bandwidth limited by a virtual scheduler or the scheduler hierarchy applied to the SAP. The orphaned state must generate a log entry and a trap message. The SAP which the queue belongs to must also depict an orphan queue status. The orphaned state of the queue is automatically cleared when the scheduler-name becomes available on the egress SAP.

The parent scheduler can be made unavailable due to the removal of a scheduler policy or scheduler. When an existing parent scheduler is removed or inoperative, the queue enters the orphaned state mentioned above and automatically return to normal operation when the parent scheduler is available again.

When a parent scheduler is defined without specifying weight or strict parameters, the default bandwidth access method is weight with a value of 1.

The no form of the command removes a child association with a parent scheduler. If a parent association does not currently exist, the command has no effect and returns without an error. Once a parent association has been removed, the former child queue attempts to operate based on its configured rate parameter. Removing the parent association on the queue within the policy takes effect immediately on all queues using the SAP egress QoS policy.

Parameters 
weight—
These optional keywords are mutually exclusive to the level keyword. The weight defines the relative weight of this queue in comparison to other child schedulers, policers, and queues while vying for bandwidth on the parent scheduler-name. Any policers, queues, or schedulers defined as weighted receive no parental bandwidth until all policers, queues, and schedulers with a higher (numerically larger) priority on the parent have reached their maximum bandwidth or are idle.

All weight values from all weighted active policers, queues, and schedulers with a common parent scheduler are added together. Then, each individual active weight is divided by the total, deriving the percentage of remaining bandwidth provided to the policer, queue, or scheduler. A weight is considered to be active when the pertaining policer, queue, or scheduler has not reached its maximum rate and still has packets to transmit. All child policers, queues, and schedulers with a weight of 0 are considered to have the lowest priority level and are not serviced until all non-zero weighted policers, queues, and schedulers at that level are operating at the maximum bandwidth or are idle.

Values—
0 to 100

 

Default—
1
cir-weight—
Defines the weight the queue or scheduler will use at the within-cir port priority level (defined by the cir-level parameter). The weight is specified as an integer value from 0 to 100 with 100 being the highest weight. When the cir-weight parameter is set to a value of 0 (the default value), the policer, queue, or scheduler does not receive bandwidth during the port schedulers within-cir pass and the cir-level parameter is ignored. If the cir-weight parameter is 1 or greater, the cir-level parameter comes into play.
Values—
0 to 100

 

percent-rate

Syntax 
percent-rate pir-percent [cir cir-percent]
Context 
config>service>vpls>sap>egress>queue-override>queue
config>service>vpls>sap>ingress>queue-override>queue
Description 

The percent-rate command supports a queue’s shaping rate and CIR rate as a percentage of the egress port’s line rate. When the rates are expressed as a percentage within the template, the actual rate used per instance of the queue group queue-id will vary based on the port speed. For example, when the same template is used to create a queue group on a 1-Gb and a 10-Gb Ethernet port, the queue’s rates will be 10 times greater on the 10-Gb port due to the difference in port speeds. This enables the same template to be used on multiple ports without needing to use port based queue overrides to modify a queue’s rate to get the same relative performance from the queue.

If the port’s speed changes after the queue is created, the queue’s shaping and CIR rates will be recalculated based on the defined percentage value.

The rate and percent-rate commands override one another. If the current rate for a queue is defined using the percent-rate command and the rate command is executed, the percent-rate values are deleted. In a similar fashion, the percent-rate command causes any rate command values to be deleted. A queue’s rate may dynamically be changed back and forth from a percentage to an explicit rate at any time.

An egress port queue group queue rate override may be expressed as either a percentage or an explicit rate independent on how the queue's template rate is expressed.

The no form of this command returns the queue to its default shaping rate and cir rate. When no percent-rate is defined within a port egress queue group queue override, the queue reverts to the defined shaping and CIR rates within the egress queue group template associated with the queue.

Parameters 
pir-percent
Specifies the queue’s shaping rate as a percentage of line rate. The line rate associated with the queue’s port may dynamically change due to configuration or auto-negotiation. The line rate may also be affected by an egress port scheduler defined max-rate.
Values—
0.01 to 100.00

 

Default—
100.00
cir-percent—
Specifies the queue’s committed scheduling rate as a percentage of line rate. The line rate associated with the queue’s port may dynamically change due to configuration or auto-negotiation. The line rate may also be affected by an egress port scheduler defined max-rate.
Values—
0.00 to 100.00

 

Default—
100.00

rate

Syntax 
rate pir-rate [cir cir-rate]
no rate
Context 
config>service>vpls>sap>egress>queue-override>queue
config>service>vpls>sap>ingress>queue-override>queue
config>service>vpls>sap>egress>hsmda-queue-over>queue
Description 

This command can be used to override specific attributes of the specified queue’s Peak Information Rate (PIR) and the Committed Information Rate (CIR) parameters.

The PIR defines the maximum rate that the queue can transmit packets out an egress interface (for SAP egress queues). Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the queue can be limited by over-subscription factors or available egress bandwidth.

The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth. In-profile and then out-of-profile packets are preferentially queued by the system at egress and at subsequent next hop nodes where the packet can traverse. To be properly handled throughout the network, the packets must be marked accordingly for profiling at each hop.

The CIR can be used by the queue’s parent commands cir-level and cir-weight parameters to define the amount of bandwidth considered to be committed for the child queue during bandwidth allocation by the parent scheduler.

The rate command can be executed at any time, altering the PIR and CIR rates for all queues created through the association of the SAP egress QoS policy with the queue-id.

The no form of the command returns all queues created with the queue-id by association with the QoS policy to the default PIR and CIR parameters (max, 0).

Default 

rate max cir 0

Parameters 
pir-rate—
Defines the administrative PIR rate, in kilobits, for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed. Fractional values are not allowed and must be given as a positive integer.

The actual PIR rate is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned.

For egress>queue-override>queue and ingress>queue-override>queue:

Values—
1 to 2000000000, max in kb/s

 

Default—
max
For egress>hsmda-queue-over>queue:
Values—
1 to 100000000, max in kb/s

 

Default—
max
cir cir-rate—
The cir parameter overrides the default administrative CIR used by the queue. When the rate command is executed, a CIR setting is optional. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed. Fractional values are not allowed and must be given as a positive integer. The sum keyword specifies that the CIR be used as the summed CIR values of the children schedulers, policers, or queues.

For egress>queue-override>queue and ingress>queue-override>queue:

Values—
0 to 2000000000, max in kb/s

 

Default—
0

queue-override

Syntax 
[no] queue-override
Context 
config>service>vpls>sap>egress
config>service>vpls>sap>ingress
config>service>vpls>sap>egress>hsmda-queue-over>queue
config>service>vpls>sap>ingress>hsmda-queue-over>queue
Description 

This command enters the context to configure override values for the specified SAP egress or ingress QoS queue. These values override the corresponding ones specified in the associated SAP egress or ingress QoS policy.

queue

Syntax 
[no] queue queue-id
Context 
config>service>vpls>sap>egress>queue-override
config>service>vpls>sap>ingress>queue-override
Description 

This command specifies the ID of the queue whose parameters are to be overridden.

Parameters 
queue-id—
Specifies the queue ID whose parameters are to be overridden
Values—
1 to 32

 

adaptation-rule

Syntax 
adaptation-rule [pir {max | min | closest}] [cir {max | min | closest}]
no adaptation-rule
Context 
config>service>vpls>sap>egress>queue-override>queue
config>service>vpls>sap>ingress>queue-override>queue
Description 

This command can be used to override specific attributes of the specified queue’s adaptation rule parameters. The adaptation rule controls the method used by the system to derive the operational CIR and PIR settings when the queue is provisioned in hardware. For the CIR and PIR parameters individually, the system attempts to find the best operational rate depending on the defined constraint.

The no form of the command removes any explicitly defined constraints used to derive the operational CIR and PIR created by the application of the policy. When a specific adaptation-rule is removed, the default constraints for rate and cir apply.

Default 

no adaptation-rule

Parameters 
pir—
Defines the constraints enforced when adapting the PIR rate defined within the queue queue-id rate command. The pir parameter requires a qualifier that defines the constraint used when deriving the operational PIR for the queue. When the rate command is not specified, the default applies.
cir—
The Defines the constraints enforced when adapting the CIR rate defined within the queue queue-id rate command. The cir parameter requires a qualifier that defines the constraint used when deriving the operational CIR for the queue. When the cir parameter is not specified, the default constraint applies.
adaptation-rule—
Specifies the criteria to use to compute the operational CIR and PIR values for this queue, while maintaining a minimum offset.
Values—
max — The max (maximum) keyword is mutually exclusive with the min and closest options. When max is defined, the operational PIR for the queue will be equal to or less than the administrative rate specified using the rate command.
min — The min (minimum) keyword is mutually exclusive with the max and closest options. When min is defined, the operational PIR for the queue will be equal to or greater than the administrative rate specified using the rate command.
closest — The closest parameter is mutually exclusive with the min and max parameter. When closest is defined, the operational PIR for the queue will be the rate closest to the rate specified using the rate command.

 

avg-frame-overhead

Syntax 
avg-frame-overhead percent
no avg-frame-overhead
Context 
config>service>vpls>sap>egress>queue-override>queue
Description 

This command configures the average frame overhead to define the average percentage that the offered load to a queue will expand during the frame encapsulation process before sending traffic on-the-wire. While the avg-frame-overhead value may be defined on any queue, it is only used by the system for queues that egress a SONET or SDH port or channel. Queues operating on egress Ethernet ports automatically calculate the frame encapsulation overhead based on a 20 byte per packet rule (8 bytes for preamble and 12 bytes for Inter-Frame Gap).

When calculating the frame encapsulation overhead for port scheduling purposes, the system determines the following values:

  1. Offered-load — The offered-load of a queue is calculated by starting with the queue depth in octets, adding the received octets at the queue and subtracting queue discard octets. The result is the number of octets the queue has available to transmit. This is the packet based offered-load.
  2. Frame encapsulation overhead — Using the avg-frame-overhead parameter, the frame encapsulation overhead is simply the queue’s current offered-load (how much has been received by the queue) multiplied by the avg-frame-overhead. If a queue had an offered load of 10000 octets and the avg-frame-overhead equals 10%, the frame encapsulation overhead would be 10000 x 0.1 or 1000 octets.

For egress Ethernet queues, the frame encapsulation overhead is calculated by multiplying the number of offered-packets for the queue by 20 bytes. If a queue was offered 50 packets then the frame encapsulation overhead would be 50 x 20 or 1000 octets.

  1. Frame based offered-load — The frame based offered-load is calculated by adding the offered-load to the frame encapsulation overhead. If the offered-load is 10000 octets and the encapsulation overhead was 1000 octets, the frame based offered-load would equal 11000 octets.
  2. Packet to frame factor — The packet to frame factor is calculated by dividing the frame encapsulation overhead by the queue’s offered-load (packet based). If the frame encapsulation overhead is 1000 octets and the offered-load is 10000 octets then the packet to frame factor would be 1000 / 10000 or 0.1. When in use, the avg-frame-overhead will be the same as the packet to frame factor making this calculation unnecessary.
  3. Frame based CIR — The frame based CIR is calculated by multiplying the packet to frame factor with the queue’s configured CIR and then adding that result to that CIR. If the queue CIR is set at 500 octets and the packet to frame factor equals 0.1, the frame based CIR would be 500 x 1.1 or 550 octets.
  4. Frame based within-cir offered-load — The frame based within-cir offered-load is the portion of the frame based offered-load considered to be within the frame-based CIR. The frame based within-cir offered-load is the lesser of the frame based offered-load and the frame based CIR. If the frame based offered-load equaled 11000 octets and the frame based CIR equaled 550 octets, the frame based within-cir offered-load would be limited to 550 octets. If the frame based offered-load equaled 450 octets and the frame based CIR equaled 550 octets, the frame based within-cir offered-load would equal 450 octets (or the entire frame based offered-load).

As a special case, when a queue or associated intermediate scheduler is configured with a CIR-weight equal to 0, the system automatically sets the queue’s frame based within-cir offered-load to 0, preventing it from receiving bandwidth during the port scheduler’s within-cir pass.

  1. Frame based PIR — The frame based PIR is calculated by multiplying the packet to frame factor with the queue’s configured PIR and then adding the result to that PIR. If the queue PIR is set to 7500 octets and the packet to frame factor equals 0.1, the frame based PIR would be 7500 x 1.1 or 8250 octets.
  2. Frame based within-pir offered-load — The frame based within-pir offered-load is the portion of the frame based offered-load considered to be within the frame based PIR. The frame based within-pir offered-load is the lesser of the frame based offered-load and the frame based PIR. If the frame based offered-load equaled 11000 octets and the frame based PIR equaled 8250 octets, the frame based within-pir offered-load would be limited to 8250 octets. If the frame based offered-load equaled 7000 octets and the frame based PIR equaled 8250 octets, the frame based within-pir offered load would equal 7000 octets.

Port scheduler operation using frame transformed rates — The port scheduler uses the frame based rates to calculate the maximum rates that each queue may receive during the within-cir and above-cir bandwidth allocation passes. During the within-cir pass, a queue may receive up to its frame based within-cir offered-load. The maximum it may receive during the above-cir pass is the difference between the frame based within-pir offered load and the amount of actual bandwidth allocated during the within-cir pass.

SAP and subscriber SLA-profile average frame overhead override — The average frame overhead parameter on a sap-egress may be overridden at an individual egress queue basis. On each SAP and within the sla-profile policy used by subscribers an avg-frame-overhead command may be defined under the queue-override context for each queue. When overridden, the queue instance will use its local value for the average frame overhead instead of the sap-egress defined overhead.

The no form of this command restores the average frame overhead parameter for the queue to the default value of 0 percent. When set to 0, the system uses the packet based queue statistics for calculating port scheduler priority bandwidth allocation. If the no avg-frame-overhead command is executed in a queue-override queue id context, the avg-frame-overhead setting for the queue within the sap-egress QoS policy takes effect.

Default 

0

Parameters 
percent—
Sets the average amount of packet-to-frame encapsulation overhead expected for the queue. This value is not used by the system for egress Ethernet queues.
Values—
0 to 100

 

cbs

Syntax 
cbs size-in-kbytes
no cbs
Context 
config>service>vpls>sap>egress>queue-override>queue
config>service>vpls>sap>ingress>queue-override>queue
Description 

This command can be used to override specific attributes of the specified queue’s CBS parameters.

It is permissible, and possibly desirable, to oversubscribe the total CBS reserved buffers for a specified access port egress buffer pool. Over-subscription may be desirable due to the potential large number of service queues and the economy of statistical multiplexing the individual queue’s CBS setting into the defined reserved total.

When oversubscribing the reserved total, it is possible for a queue depth to be lower than its CBS setting and still not receive a buffer from the buffer pool for an ingress frame. As more queues are using their CBS buffers and the total in use exceeds the defined reserved total, essentially the buffers are being removed from the shared portion of the pool without the shared in use average and total counts being decremented. This can affect the operation of the high and low priority RED slopes on the pool, causing them to miscalculate when to start randomly drop packets.

The no form of this command returns the CBS size to the default value.

Default 

no cbs

Parameters 
size-in-kbytes—
Specifies an integer expression of the number of kilobytes reserved for the queue. If a value of 10KBytes is needed, enter the value 10. A value of 0 specifies that no reserved buffers are required by the queue (a minimal reserved size can still be applied for scheduling purposes).
Values—
0 to 131072 or default

 

mbs

Syntax 
mbs {size [bytes | kilobytes] | default}
no mbs
Context 
config>service>vpls>sap>egress>queue-override>queue
Description 

This command can be used to override specific attributes of the specified queue’s MBS parameters. The MBS is a mechanism to override the default maximum size for the queue.

The sum of the MBS for all queues on an egress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope a packet is associated with. A queue that has not exceeded its MBS size is not guaranteed that a buffer will be available when needed or that the packet’s RED slope will not force the discard of the packet. Setting correct CBS parameters and controlling CBS over-subscription is one major safeguard to queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.

The no form of this command returns the MBS size assigned to the queue.

Default 

default

Parameters 
size—
The size parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional bytes and kilobytes keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
Values—
0 to 1073741824
default

 

bytes—
When bytes is defined, the value given for size is interpreted as the queue'sMBS value given in bytes.
kilobytes—
When kilobytes is defined, the value is interpreted as the queue's MBSvalue given in kilobytes.
default—
Specifying the keyword default sets the MBS to its default value.

mbs

Syntax 
mbs {size [bytes | kilobytes] | default}
no mbs
Context 
config>service>vpls>sap>ingress>queue-override>queue
Description 

This command can be used to override specific attributes of the specified queue’s MBS parameters. The MBS value is used by a queue to determine whether it has exhausted all of its buffers while enqueuing packets. Once the queue has exceeded the amount of buffers allowed by MBS, all packets are discarded until packets have been drained from the queue.

The sum of the MBS for all queues on an ingress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope a packet is associated with. A queue that has not exceeded its MBS size is not guaranteed that a buffer will be available when needed or that the packets RED slope will not force the discard of the packet. Setting correct CBS parameters and controlling CBS over-subscription is one major safeguard to queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.

The no form of this command returns the MBS size assigned to the queue to the default value.

Default 

default

Parameters 
size—
The size parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional bytes and kilobytes keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
Values—
0 to 1073741824
default

 

bytes—
When bytes is defined, the value given for size is interpreted as the queue'sMBS value given in bytes.
kilobytes—
When kilobytes is defined, the value is interpreted as the queue's MBSvalue given in kilobytes.
default—
Specifying the keyword default sets the MBS to its default value.

rate

Syntax 
rate pir-rate [cir cir-rate]
no rate
Context 
config>service>vpls>sap>egress>queue-override>queue
config>service>vpls>sap>ingress>queue-override>queue
config>service>vpls>sap>egress>hsmda-queue-over>queue
Description 

This command can be used to override specific attributes of the specified queue’s Peak Information Rate (PIR) and the Committed Information Rate (CIR) parameters.

The PIR defines the maximum rate that the queue can transmit packets out an egress interface (for SAP egress queues). Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the queue can be limited by over-subscription factors or available egress bandwidth.

The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth. In-profile and then out-of-profile packets are preferentially queued by the system at egress and at subsequent next hop nodes where the packet can traverse. To be properly handled throughout the network, the packets must be marked accordingly for profiling at each hop.

The CIR can be used by the queue’s parent commands cir-level and cir-weight parameters to define the amount of bandwidth considered to be committed for the child queue during bandwidth allocation by the parent scheduler.

The rate command can be executed at any time, altering the PIR and CIR rates for all queues created through the association of the SAP egress QoS policy with the queue-id.

The no form of the command returns all queues created with the queue-id by association with the QoS policy to the default PIR and CIR parameters (max, 0).

Default 

rate max cir 0

Parameters 
pir-rate—
Defines the administrative PIR rate, in kilobits, for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed. Fractional values are not allowed and must be given as a positive integer.

The actual PIR rate is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned.

Values—
1 to 100000000

 

Default—
max
cir cir-rate—
Overrides the default administrative CIR used by the queue. When the rate command is executed, a CIR setting is optional. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed. Fractional values are not allowed and must be given as a positive integer. The sum keyword specifies that the CIR be used as the summed CIR values of the children schedulers, policers, or queues.
Values—
0 to 100000000, max, sum

 

Default—
0

scheduler-override

Syntax 
[no] scheduler-override
Context 
config>service>vpls>sap>egress
config>service>vpls>sap>ingress
Description 

This command specifies the set of attributes whose values have been overridden via management on this virtual scheduler. Clearing a given flag will return the corresponding overridden attribute to the value defined on the SAP's scheduler policy.

scheduler

Syntax 
scheduler scheduler-name
no scheduler scheduler-name
Context 
config>service>vpls>sap>egress>sched-override
Description 

This command can be used to override specific attributes of the specified scheduler name. A scheduler defines a bandwidth controls that limit each child (other schedulers, policers, and queues) associated with the scheduler. Scheduler objects are created within the hierarchical tiers of the policy. It is assumed that each scheduler created will have policers, queues or other schedulers defined as child associations. The scheduler can be a child which takes bandwidth from a scheduler in a higher tier. A total of 32 schedulers can be created within a single scheduler policy with no restriction on the distribution between the tiers.

Each scheduler must have a unique name within the context of the scheduler policy; however the same name can be reused in multiple scheduler policies. If scheduler-name already exists within the policy tier level (regardless of the inclusion of the keyword create), the context changes to that scheduler name for the purpose of editing the scheduler parameters. Modifications made to an existing scheduler are executed on all instantiated schedulers created through association with the policy of the edited scheduler. This can cause policers, queues or schedulers to become orphaned (invalid parent association) and adversely affect the ability of the system to enforce service level agreements (SLAs).

If the scheduler-name exists within the policy on a different tier (regardless of the inclusion of the keyword create), an error occurs and the current CLI context will not change.

If the scheduler-name does not exist in this or another tier within the scheduler policy, it is assumed that an attempt is being made to create a scheduler of that name. The success of the command execution is dependent on the following:

  1. The maximum number of schedulers has not been configured.
  2. The provided scheduler-name is valid.
  3. The create keyword is entered with the command if the system is configured to require it (enabled in the environment create command).

When the maximum number of schedulers has been exceeded on the policy, a configuration error occurs and the command will not execute, nor will the CLI context change.

If the provided scheduler-name is invalid according to the criteria below, a name syntax error will occur, the command will not execute, and the CLI context will not change.

Parameters 
scheduler-name—
Specifies the name of the scheduler.
Values—
Valid names consist of any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

 

Default—
None. Each scheduler must be explicitly created.
create
Specifies that it is acceptable to create a scheduler with the given scheduler-name. If the create keyword is omitted, scheduler-name is not created when the system environment variable create is set to true. This safeguard is meant to avoid accidental creation of system objects (such as schedulers) while attempting to edit an object with a mistyped name or ID. The keyword has no effect when the object already exists.

parent

Syntax 
parent [weight weight] [cir-weight cir-weight]
no parent
Context 
config>service>vpls>sap>ingress>sched-override>scheduler
config>service>vpls>sap>egress>sched-override>scheduler
Description 

This command can be used to override the scheduler’s parent weight and cir-weight information. The weights apply to the associated level/cir-level configured in the applied scheduler policy. The scheduler name must exist in the scheduler policy applied to the ingress or egress of the SAP or multi-service site.

The override weights are ignored if the scheduler does not have a parent command configured in the scheduler policy – this allows the parent of the scheduler to be removed from the scheduler policy without having to remove all of the SAP/MSS overrides. If the parent scheduler does not exist causing the configured scheduler to be fostered on an egress port scheduler, the override weights will be ignored and the default values used; this avoids having non-default weightings for fostered schedulers.

The no form of the command returns the scheduler’s parent weight and cir-weight to the value configured in the applied scheduler policy.

Default 

no parent

Parameters 
weight
Defines the relative weight of this scheduler in comparison to other child schedulers and queues at the same strict level defined by the level parameter in the applied scheduler policy. Within the level, all weight values from active children at that level are summed and the ratio of each active child’s weight to the total is used to distribute the available bandwidth at that level. A weight is considered to be active when the policer, queue, or scheduler the weight pertains to has not reached its maximum rate and still has packets to transmit. A 0 (zero) weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict level.
Values—
0 to 100

 

cir-weight
Specifies the relative weight of this scheduler in comparison to other child schedulers and queues at the same cir-level defined by the cir-level parameter in the applied scheduler policy. Within the strict cir-level, all cir-weight values from active children at that level are summed and the ratio of each active child’s cir-weight to the total is used to distribute the available bandwidth at that level. A cir-weight is considered to be active when the policer, queue, or scheduler that the cir-weight pertains to has not reached the CIR and still has packets to transmit. A 0 (zero) cir-weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict cir-level.
Values—
0 to 100

 

rate

Syntax 
rate pir-rate [cir cir-rate]
no rate
Context 
config>service>vpls>sap>egress>sched-override>scheduler
config>service>vpls>sap>ingress>sched-override>scheduler
Description 

This command can be used to override specific attributes of the specified scheduler rate. The rate command defines the maximum bandwidth that the scheduler can offer its child policers, queues, or schedulers. The maximum rate is limited to the amount of bandwidth the scheduler can receive from its parent scheduler. If the scheduler has no parent, the maximum rate is assumed to be the amount available to the scheduler. When a parent is associated with the scheduler, the CIR parameter provides the amount of bandwidth to be considered during the parent scheduler’s ‘within CIR’ distribution phase.

The actual operating rate of the scheduler is limited by bandwidth constraints other then its maximum rate. The scheduler’s parent scheduler may not have the available bandwidth to meet the scheduler’s needs or the bandwidth available to the parent scheduler could be allocated to other child schedulers or child queues on the parent based on higher priority. The children of the scheduler may not need the maximum rate available to the scheduler due to insufficient offered load or limits to their own maximum rates.

When a scheduler is defined without specifying a rate, the default rate is max. If the scheduler is a root scheduler (no parent defined), the default maximum rate must be changed to an explicit value. Without this explicit value, the scheduler will assume that an infinite amount of bandwidth is available and allow all child policers, queues, and schedulers to operate at their maximum rates.

The no form of this command returns the scheduler’s PIR and CIR parameters to the value configured in the applied scheduler policy.

Parameters 
pir-rate—
Specifies a value of 1 to 3200000000, or the keyword max. Any other value will result in an error without modifying the current PIR rate.
Values—
1 to 3200000000, max

 

cir cir-rate—
Specifies a value of 0 to 3200000000, or the keyword max or sum. Any other value will result in an error without modifying the current CIR rate.

If cir is set to max, then the CIR rate is set to infinity, but bounded by the PIR rate.

The sum keyword specifies that the CIR be used as the summed CIR values of the children schedulers, policers or queues.

Values—
0 to 3200000000, max, sum

 

scheduler-policy

Syntax 
scheduler-policy scheduler-policy-name
no scheduler-policy
Context 
config>service>vpls>sap>ingress
config>service>vpls>sap>egress
Description 

This command applies an existing scheduler policy to an ingress or egress scheduler used by SAP queues and, at egress only, policers associated with this multi-service customer site. The schedulers defined in the scheduler policy can only be created after the customer site has been appropriately assigned to a chassis port, channel or slot. Scheduler policies are defined in the config>qos>scheduler-policy scheduler-policy-name context.

The no form of this command removes the configured ingress or egress scheduler policy from the multi-service customer site. When the policy is removed, the schedulers created due to the policy are removed also making them unavailable for the SAP policers and queues associated with the customer site. Policers and queues that lose their parent scheduler association are deemed to be orphaned and are no longer subject to a virtual scheduler. The SAPs that have policers or queues reliant on the removed schedulers enter into an operational state depicting the orphaned status of one or more policers or queues. When the no scheduler-policy command is executed, the customer site ingress or egress node will not contain an applied scheduler policy.

Parameters 
scheduler-policy-name:—
Applies an existing scheduler policy that was created in the config>qos>scheduler-policy scheduler-policy-name context to create the hierarchy of ingress or egress virtual schedulers. The scheduler names defined within the policy are created and made available to any ingress or egress queues created on associated SAPs.
Values—
Any existing valid scheduler policy name.

 

match-qinq-dot1p

Syntax 
match-qinq-dot1p {top | bottom}
no match-qinq-dot1p de
Context 
config>service>vpls>sap>ingress
Description 

This command specifies which Dot1Q tag position Dot1P bits in a QinQ encapsulated packet should be used to evaluate Dot1P QoS classification.

The match-qinq-dot1p command allows the top or bottom PBits to be used when evaluating the applied sap-ingress QoS policy’s Dot1P entries. The top and bottom keywords specify which position should be evaluated for QinQ encapsulated packets.

The setting also applies to classification based on the DE indicator bit.

The no form of this command reverts the dot1p and de bits matching to the default tag.

By default, the bottom most service delineating Dot1Q tags Dot1P bits are used. Table 38 defines the default behavior for Dot1P evaluation.

Table 38:  Default QinQ and TopQ SAP Dot1P Evaluation  

Port / SAP Type

Existing Packet Tags

PBits Used for Match  

Null

None

None

Null

Dot1P (VLAN ID 0)

Dot1P PBits

Null

Dot1Q

Dot1Q PBits

Null

TopQ BottomQ

TopQ PBits

Null

TopQ (No BottomQ)

TopQ PBits

Dot1Q

None (Default SAP)

None

Dot1Q

Dot1P (Default SAP VLAN ID 0)

Dot1P PBits

Dot1Q

Dot1Q

Dot1Q PBits

QinQ / TopQ

TopQ

TopQ PBits

QinQ / TopQ

TopQ BottomQ

TopQ PBits

QinQ / QinQ

TopQ BottomQ

BottomQ PBits

Default 

no match-qinq-dot1p (no filtering based on p-bits) (top or bottom must be specified to override the default QinQ dot1p behavior)

Parameters 
top—
The top parameter is mutually exclusive to the bottom parameter. When the top parameter is specified, the top most PBits are used (if existing) to match any dot1p dot1p-value entries. The following table defines the dot1p evaluation behavior when the top parameter is specified.
Table 39:   

Port / SAP Type

Existing Packet Tags

PBits Used for Match

Null

None

None

Null

Dot1P (VLAN ID 0)

Dot1P PBits

Null

Dot1Q

Dot1Q PBits

Null

TopQ BottomQ

TopQ PBits

Null

TopQ (No BottomQ)

TopQ PBits

Dot1Q

None (Default SAP)

None

Dot1Q

Dot1P (Default SAP VLAN ID 0)

Dot1P PBits

Dot1Q

Dot1Q

Dot1Q PBits

QinQ / TopQ

TopQ

TopQ PBits

QinQ / TopQ

TopQ BottomQ

TopQ PBits

QinQ / QinQ

TopQ BottomQ

TopQ PBits

bottom—
The bottom parameter is mutually exclusive to the top parameter. When the bottom parameter is specified, the bottom most PBits are used (if existing) to match any dot1p dot1p-value entries. The following table defines the dot1p evaluation behavior when the bottom parameter is specified; see Table 40.
Table 40:  Bottom Position QinQ and TopQ SAP Dot1P Evaluation  

Port / SAP Type

Existing Packet Tags

PBits Used for Match  

Null

None

None

Null

Dot1P (VLAN ID 0)

Dot1P PBits

Null

Dot1Q

Dot1Q PBits

Null

TopQ BottomQ

TopQ PBits

Null

TopQ (No BottomQ)

TopQ PBits

Dot1Q

None (Default SAP)

None

Dot1Q

Dot1P (Default SAP VLAN ID 0)

Dot1P PBits

Dot1Q

Dot1Q

Dot1Q PBits

QinQ / TopQ

TopQ

TopQ PBits

QinQ / TopQ

TopQ BottomQ

TopQ PBits

QinQ / QinQ

TopQ BottomQ

BottomQ PBits

Table 41:   

Egress SAP Type

Ingress Packet Preserved Dot1P State

Marked (or Remarked) PBits

Null

No preserved Dot1P bits

None

Null

Preserved Dot1P bits

Preserved tag PBits remarked using dot1p-value

Dot1Q

No preserved Dot1P bits

New PBits marked using dot1p-value

Dot1Q

Preserved Dot1P bits

Preserved tag PBits remarked using dot1p-value

TopQ

No preserved Dot1P bits

TopQ PBits marked using dot1p-value

TopQ

Preserved Dot1P bits (used as TopQ and BottomQ PBits)

TopQ PBits marked using dot1p-value, BottomQ PBits preserved

QinQ

No preserved Dot1P bits

TopQ PBits and BottomQ PBits marked using dot1p-value

QinQ

Preserved Dot1P bits (used as TopQ and BottomQ PBits)

TopQ PBits and BottomQ PBits marked using dot1p-value

The QinQ and TopQ SAP PBit/DEI bit marking follows the default behavior defined in the table above when qinq-mark-top-only is not specified.

The dot1p dot1p-value command must be configured without the qinq-mark-top-only parameter to remove the TopQ PBits only marking restriction.

A QinQ-encapsulated Ethernet port can have two different sap types:

For a TopQ SAP type, only the outer (top) tag is explicitly specified. For example, sap 1/1/1:10.*

For QinQ SAP type, both inner (bottom) and outer (top) tags are explicitly specified. For example, sap 1/1/1:10.100.

authentication-policy

Syntax 
authentication-policy name
no authentication-policy
Context 
config>service>vpls>sap
Description 

This command defines which subscriber authentication policy must be applied when a DHCP message is received on the interface. The authentication policies must already be defined. The policy will only be applied when DHCP snooping is enabled on the SAP.

bandwidth

Syntax 
bandwidth bandwidth
no bandwidth
Context 
config>service>vpls>sap
Description 

This command specifies the admin bandwidth assigned to SAPs, ports and LAGs which is used by SAP bandwidth CAC.

SAP: Attempts to increase the SAP admin bandwidth will fail if there is insufficient available admin bandwidth on its port or LAG, otherwise the port or LAG available admin bandwidth will be reduced by the incremental SAP admin bandwidth. Reducing the SAP admin bandwidth will increase the available admin bandwidth on its port or LAG. This is not supported for PW-SAPs, Ethernet tunnels or subscriber group interface SAPs.

The no version of the command reverts to the default value.

Default 

no bandwidth

Parameters 
bandwidth—
Specifies the admin bandwidth assigned to the SAP, port or LAG, in kb/s.
Values—
1 to 3200000000

 

accounting-policy

Syntax 
accounting-policy acct-policy-id
no accounting-policy
Context 
config>service>vpls>spoke-sdp
config>service>vpls>mesh-sdp
config>service>vpls>sap
Description 

This command creates the accounting policy context that can be applied to a SAP or SDP. An accounting policy must be defined before it can be associated with a SAP or SDP. If the policy-id does not exist, an error message is generated. A maximum of one accounting policy can be associated with a SAP or SDP at one time. Accounting policies are configured in the config>log context.

The no form of this command removes the accounting policy association from the SAP or SDP, and the accounting policy reverts to the default.

Default 

Default accounting policy.

Parameters 
acct-policy-id—
Specifies the accounting policy-id as configured in the config>log>accounting-policy context
Values—
1 to 99

 

app-profile

Syntax 
app-profile app-profile-name
no app-profile
Context 
config>service>vpls>spoke-sdp
Description 

This command configures the application profile name.

Parameters 
app-profile-name—
Specifies an existing application profile name configured in the config>app-assure>group>policy context

collect-stats

Syntax 
[no] collect-stats
Context 
config>service>vpls>spoke-sdp
config>service>vpls>mesh-sdp
config>service>vpls>sap
Description 

This command enables accounting and statistical data collection for either the SAP or SDP, network port, or IP interface. When applying accounting policies the data, by default, is collected in the appropriate records and written to the designated billing file.

When the no collect-stats command is issued the statistics are still accumulated by the IOM or XCM cards. However, the CPU will not obtain the results and write them to the billing file. If a subsequent collect-stats command is issued then the counters written to the billing file include all the traffic while the no collect-stats command was in effect.

Default 

no collect-stats

3.7.2.5.3. VPLS Template Commands

template

Syntax 
template
Context 
config>service
Description 

This is the node for service templates.

vpls-template

Syntax 
vpls-template name/id create
[no] vpls-template name/id
Context 
config>service>template
Description 

This command is used to create a vpls-template to be used to auto-instantiate a range of VPLS services. Only certain existing VPLS attributes specified in the command reference section can be changed in the vpls-template, not in the instantiated VPLS. The following attributes will be automatically set in the instantiated VPLSs (no template configuration necessary) and the operator cannot change these values.

vpn-id: none

description: “Service <svc id> auto-generated by control VPLS <svc-id>”

service-name: “Service <svc id>” (Auto-generated)

shutdown: no shutdown

Following existing attributes can be set by the user in the instantiated VPLSs:

[no] sap

All the other VPLS attributes are not supported.

Parameters 
name/id—
Specifies the name in ASCII or the template ID
Values—
name: ASCII string

 

Values—
ID: [1 to 2147483647]

 

vpls-sap-template

Syntax 
vpls-sap-template name/id create
[no] vpls-sap-template name/id
Context 
config>service>template
Description 

This is the command used to create a SAP template to be used in a vpls-template. Only certain existing VPLS SAP attributes can be changed in the vpls-sap-template, not in the instantiated VPLS SAP

Following SAP attributes will be set in the instantiated saps (no configuration allowed):

description:”Sap <sap-id> controlled by MVRP service <svc id>” – auto generated

shutdown: no shutdown

Parameters 
name/id—
Specifies the name in ASCII or the template ID
Values—
1 to 2147483647

 

filter-name

Syntax 
[no] filter-name
Context 
config>service>template>vpls-sap-template>egress
config>service>template>vpls-sap-template>ingress
Description