The description command associates a text string with a configuration context to help identify the context in the configuration file.
The no form of this command removes any description string from the context.
config>subscr-mgmt>sub-ident-policy>primary
config>subscr-mgmt>sub-ident-policy>secondary
config>subscr-mgmt>sub-ident-policy>tertiary
config>subscr-mgmt>diameter-policy>diameter-base>peer
The shutdown command administratively disables the entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics. Many entities must be explicitly enabled using the
no shutdown command.
The shutdown command administratively disables an entity. 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 can be deleted.
Shutting down a subscriber interface will operationally shut down all child group interfaces and SAPs. Shutting down a group interface will operationally shut down all SAPs that are part of that group-interface.
The no form of the command puts an entity into the administratively enabled state.
All subscriber hosts belonging to the same subscriber are subject to the same hierarchical QoS (HQoS) processing. The HQoS processing is defined in the sub-profile (the subscriber profile). A sub-profile refers to an existing scheduler policy (configured in
the configure>qos>scheduler-policy context) and offers the possibility to overrule the rate of individual schedulers within this policy.
ANCP polices control rates and subscribers based on port-up/port-down messages from the access node. When configured, the 7750 SR should stop SHCV to a host that is part of a port defined to be down (by port-down message). When the node receives a port-up message for a port that was in port-down, state the node will initiate the SHCV process immediately to verify connectivity.
This command configures a rate adjustment for the scheduler. The rate-adjustment command should be used when the rate returned by the DSLAM is calculated with different encapsulation than the 7750 SR. The node will adjust the rate by the percent specified as:
The no form of the command returns the default value.
This command defines a constant rate reduction to the rate specified by the DSLAM. The rate-reduction command should be used if the node should adjust the rate to a value that is offset (for example by a fixed multicast dedicated bandwidth) compared to the total available on the DSLAM.
rate-modify {scheduler
scheduler-name | arbiter
arbiter-name}
rate-modify {scheduler
scheduler-name | arbiter
arbiter-name}
[no
] disable-shcv
[alarm
] [hold-time
seconds]
entry key ancp-string customer
customer-id multi-service-site
customer-site-name ancp-policy
policy-name
entry key ancp-string sap
sap-id ancp-policy
policy-name
no entry key ancp-string customer
customer-id multi-service-site
customer-site-name
Specify the ASCII representation of the DSLAM circuit-id name.
Specify the associated customer’s configured MSS name.
[no
] dynamic-topology-discover
The no form of this command disables the feature.
The no form of this command disables the feature.
|
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, ef, cp47, nc1, cp49, cp50, cp51, cp52, cp53, cp54, cp55, nc2, cp57, cp58, cp59, cp60, cp61, cp62, cp63
|
[no
] persistency-database
The no form of the command resets the default UDP port to 3799.
The no form of the command removes the RADIUS server configuration for session authentication.
[no
] accept-authorization-change
[no
] host-accounting
[interim-update
]
[no
] include-radius-attribute
[no
] use-std-acct-attributes
[no] all-authorized-session-addresses
The no form of the command excludes called station id attributes.
This command enables the inclusion of the calling-station-id attribute in RADIUS authentication requests and RADIUS accounting messages. The value inserted is 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.
The acct-session-id attribute for each subscriber host will be generated at the very beginning of the session initiation. This command will enable or disable sending this attribute to the RADIUS server in the Access-Request messages regardless of whether the accounting is enabled or not. The
acct-session-id attribute can be used to address the subscriber hosts from the RADIUS server in the CoA Request.
The acct-session-id attribute will be unique per subscriber host network wide. It is a 22bytes long field comprised of the system MAC address along with the creation time and a sequence number in a hex format.
[no
] dhcp-vendor-class-id
[no
] nas-port
bit-specification binary-spec
The no form of this command disables your nas-port configuration.
*12o*12i00*2s*2m*2p => oooo oooo oooo iiii iiii iiii 00ss mmpp
If outer vlan = 0 & inner vlan = 1 & slot = 3 & mda = 1 & port = 1
=> 0000 0000 0000 0000 0000 0001 0011 0101 => nas-port = 309
[no
] nas-port-id
[prefix-string
string] [suffix
suffix-option]
The no form of the command reverts to the default.
The no form of the command disables the inclusion of the user-name attribute.
This command sets a password that is sent with user-name in every RADIUS authentication request sent to the RADIUS server upon receipt of DHCP discover or request messages.
If no password is provided, an empty password will be sent.
The no form of the command reverts to the default value.
Specifies the key is entered in a more complex encrypted form. If the
hash2 parameter is
not used, the less encrypted hash form is assumed.
This command determines the interval during which no new communication attempts will be made to a RADIUS server that is marked down to prevent immediately overloading the server when it is starting up. The only exception is when all servers in the authentication policy are marked
down; in that case they will all be used again to prevent failures on new client connections.
The no form of the command reverts to the default value.
The no form of the command removes the radius-server-policy reference from the configuration
server server-index address
ip-address secret
key [hash
| hash2
] [port
port-num] [coa-only] [pending-requests-limit
limit]
The no form of the command removes the server from the configuration.
Specifies the key is entered in a more complex encrypted form. If the
hash2 parameter is
not used, the less encrypted hash form is assumed.
The system IP address must be configured in order for the RADIUS client to work. See Configuring a System Interface in the 7750 SR OS Router Configuration Guide. Note that the system IP address must only be configured if the source-address is not specified. When the
no source-address command is executed, the source address is determined at the moment the request is sent. This address is also used in the nas-ip-address attribute: over there it is set to the system IP address if
no source-address was given.
The no form of the command reverts to the default value.
The no form of the command reverts to the default value.
The no form of the command sets the default to 10% of the configured update-interval.
[no
] use-std-acct-attributes
The no form of the command disables the use of standard accounting attributes.
The no form of the command reverts to the default value.
|
•
|
on-request-failure: All failure conditions between the sending of an Access-Request and the reception of an Access-Accept or Access-Reject.
|
|
•
|
on-accept-failure: All failure conditions that appear after receiving an Access-Accept and before successful instantiation of the host or session.
|
The no form of the command switches to the default format,
mac.
ascii-converted-circuit-id — Identical to circuit-id, but the user name will be sent to the RADIUS server as a string of hex digits, for use if there is binary data in the circuit-id.
ascii-converted-tuple — Identical to tuple, but the circuit-id part of the user name will be sent to the RADIUS server as a string of hex digits, for use if there is binary data in the circuit-id.
circuit-id — If the system serves as a DHCP relay server which inserts option 82 info, the user name will be formatted as defined under DHCP information option.
If the system is not a DHCP relay server, the circuit-id will be taken from option 82 in the received DHCP message. If no circuit-id can be found, the DHCP-msg is rejected.
dhcp-client-vendor-opts — Creates a concatenation of the DHCP client-identifier option (option 60), a “@” delimiter and the DHCP vendor-class identifier options. The two option strings are parsed for any characters which are non-printing are considered invalid and must be converted to underscore “_” characters. In addition, any space character (hex 20) and @ character (hex 40) are also converted to underscore. The character set considered valid is ASCII hex 21 through hex 3F, and hex 41 through hex 7E. Any character outside this set will be converted into an underscore (hex 5F) character.
mac — The MAC source address of the DHCP DISCOVER message is used in the user-name field. The format of the MAC address string used as the user name in the RADIUS authentication requests uses lowercase hex digits, and “:” as the inter-digit separator, for example, 00:11:22:aa:bb:cc is valid but 00-11-22-AA-BB-CC will return an error. The RADIUS server must be configured accordingly, otherwise the authentication request will fail.
mac-giaddr — Specifies that MAC giaddr indicates the format used to identify the user towards the RADIUS server.
tuple — The concatenation of MAC source address and circuit-ID are used in the user-name field.
[no] diameter-policy diameter-policy-name
[no] watchdog-timer seconds
[no] connection-timer seconds
The no form of the command reverts to the default value.
[no] transaction-timer seconds
The no form of the command reverts to the default value.
|
Values
|
router-instance: router-name| service-id
router-name: Base, management service-id: 1 — 2147483647
|
subscription-id {circuit-id
|subscriber-id
|imsi
|msisdn
|imei
} [type
{e164
|private
|imsi
}]
The no form of the command reverts to the default value.
The no form of the command reverts to the default value.
The no form of the command reverts to the default value.
copy {ip-filter | mac-filter | ipv6-filter
} src-filter-id [src-entry
src-entry-id] to
dst-filter-id [dst-entry
dst-entry-id] [overwrite
]
entry entry-id [time-range
time-range-name] [create
]
match [next-header
next-header]
renum old-entry-id new-entry-id
scope exclusive | template
The no version of the command disables the insertion, which means that information from auth-response messages cannot be stored in the filter, and the corresponding host will not be created in the system.
The no version of the command disables the insertion, which means that entries will not be installed even though the credit for the given category and subscriber-host has been exhausted.
The no version of the command sets the default values for the respective thresholds.
The no form of the command reverts the configured values to the defaults.
[no
] override-counter
override-counter-id
The no form of the command removes the ID from the configuration.
The no form of the command
The no form of the command
The no form of the command reverts to the default value
Specifies the queue-id for which counters will be collected in this custom record.
[no
] in-profile-octets-discarded-count
The no form of the command excludes the in-profile octets discarded count.
[no
] in-profile-octets-forwarded-count
The no form of the command excludes the in-profile octets forwarded count.
[no
] in-profile-packets-discarded-count
The no form of the command excludes the in-profile packets discarded count.
[no
] in-profile-packets-forwarded-count
The no form of the command excludes the in-profile packets forwarded count.
[no
] out-profile-octets-discarded-count
The no form of the command excludes the out of profile packets discarded count.
[no
] out-profile-octets-forwarded-count
The no form of the command excludes the out of profile octets forwarded count.
[no
] out-profile-packets-discarded-count
The no form of the command excludes the out of profile packets discarded count.
[no
] out-profile-packets-forwarded-count
The no form of the command excludes the out of profile packets forwarded count.
The no form of the command
[no
] all-octets-offered-count
The no form of the command excludes the octets offered in the count.
[no
] all-packets-offered-count
The no form of the command excludes the packets offered in the count.
[no
] high-octets-discarded-count
The no form of the command excludes the high octets discarded count.
[no
] high-octets-offered-count
The no form of the command excludes the high octets offered count.
[no
] high-packets-discarded-count
The no form of the command excludes the high packets discarded count.
[no
] high-packets-offered-count
The no form of the command excludes the high packets offered count.
[no
] in-profile-octets-forwarded-count
The no form of the command excludes the in profile octets forwarded count.
[no
] in-profile-packets-forwarded-count
The no form of the command excludes the in profile packets forwarded count.
[no
] low-octets-discarded-count
The no form of the command excludes the low octets discarded count.
[no
] low-packets-discarded-count
The no form of the command excludes the low packets discarded count.
[no
] low-octets-offered-count
The no form of the command excludes the low octets discarded count.
[no
] low-packets-offered-count
The no form of the command excludes the low packets discarded count.
[no
] out-profile-octets-forwarded-count
The no form of the command excludes the out of profile octets forwarded count.
[no
] out-profile-packets-forwarded-count
The no form of the command excludes the out of profile packets forwarded count.
[no
] uncoloured-packets-offered-count
The no form of the command excludes the uncoloured octets offered in the count.
[no
] uncoloured-packets-offered-count
The no form of the command excludes the uncoloured packets offered count.
The no form of the command
The no form of the command reverts to the default value.
The no form of the command reverts to the default value.
When this command is enabled, BGP adds the router ID to the aggregator path attribute. The no form of the command used at the global level reverts to default where BGP adds the AS number and router ID to the aggregator path attribute.
Authentication is performed between neighboring routers before setting up the BGP session by verifying the password. Authentication is performed using the MD-5 message-based digest. The authentication key can be any combination of letters or numbers from 1 to 16.
Specifies the key is entered in a more complex encrypted form. If the
hash2 parameter is
not used, the less encrypted hash form is assumed.
The no form of the command deletes the cluster ID and effectively disables the Route Reflection for the given group.
The no form of the command used at the global level reverts to the default value.
The no form of the command used at the global level disables route damping.
Half-life: 15 minutes
Max-suppress: 60 minutes
Suppress-threshold: 3000
Reuse-threshold 750
The no form of the command resets the behavior to the default which is to enable the use of 4-byte ASN.
[no
] disable-client-reflect
The no form re-enables client reflection of routes.
[no]
disable-fast-external-failover
The no form of this command removes all route policy names from the export list.
no export — BGP advertises routes from other BGP routes but does not advertise any routes from other protocols unless directed by an export policy.
The no form of the command used at the global level reverts to the default value.
This command specifies the import policies to be used to control routes advertised to BGP neighbors. Route policies are configured in the config>router>policy-options context. When multiple policy names are specified, the policies are evaluated in the order they are specified. A maximum of five (5) policy names can be specified. The first policy that matches is applied.
The no form of this command removes all route policy names from the import list.
no import — BGP accepts all routes from configured BGP neighbors. Import policies can be used to limit or modify the routes accepted and their corresponding parameters and metrics.
If the hold-time interval is set to zero, then the configured value of the keepalive value is ignored. This means that the connection with the peer is up permanently and no keepalive packets are sent to the peer.
The no form of the command used at the global level reverts to the default value..
When a local address is not specified, the 7750 SR OS uses the system IP address when communicating with IBGP peers and uses the interface address for directly connected EBGP peers. This command is used at the neighbor level to revert to the value defined under the group level.
The no form of the command removes the configured local-address for BGP.
The
no form of the command used at the group level reverts to the value defined at the global level.
The
no form of the command used at the neighbor level reverts to the value defined at the group level.
In addition to the AS number configured for BGP in the config>router>autonomous-system context, a virtual (local) AS number is configured.The virtual AS number is added to the as-path message before the router’s AS number makes the virtual AS the second AS in the as-path.
The no form of the command used at the global level will remove any virtual AS number configured.
The
no form of the command used at the group level reverts to the value defined at the global level.
The
no form of the command used at the neighbor level reverts to the value defined at the group level.
The no form of the command at the global level specifies that incoming routes with local-preference set are not overridden and routes arriving without local-preference set are interpreted as if the route had local-preference value of 100.
loop-detect {drop-peer
| discard-route
| ignore-loop| off
}
The no form of the command used at the global level reverts to default, which is
loop-detect ignore-loop.
The no form of the command used at the global level reverts to default where the MED is not advertised.
The no form of the command used at the global level reverts to default.
The no form of the command reverts to default values.
The no form of the command is used to convey to the BGP instance that the EBGP peers are directly connected.
The
no form of the command reverts to default values.
1 — EBGP peers are directly connected.
The no form of the command disables the passive mode.
[no
] preference
preference
The no form of the command used at the global level reverts to default value.
The no form of the command removes the
prefix-limit.
The no form of the command used at the global level reverts to default value.
[no
] type
{internal
| external
}
The type of internal indicates the peer is an IBGP peer while the type of external indicates that the peer is an EBGP peer.
The no form of the command used at the group level reverts to the default value.
The no form of the command removes the name from the configuration. The object must be shutdown prior to deletion. No prefix is needed to delete an existing route-download object.
The no form of the command removes the user-name from the configuration.
The no form of the command reverts to the default.
The no form of the command resets the password to its default of
ALU and will be stored using hash/hash2 encryption.
Specifies the key is entered in a more complex encrypted form. If the
hash2 parameter is not used, the less encrypted
hash form is assumed.
This command references an existing radius-server-policy (available under the config>aaa context). The server (or servers) referenced by the policy will be used as the targets for the access-request message.
The no form of the command removes the policy name from the route-downloader configuration.
The no form of the command reverts to the default values.
|
Values
|
now keyword - switch to standby CPM)
|
NOTE: Switching to the standby displays the following message.
WARNING: Configuration and/or Boot options may have changed since the last save.
Are you sure you want to switchover (y/n)?
|
Values
|
boot-env|config : keywords
|
This command performs a synchronization of the standby CPM’s images and/or config files to the active CPM. Either the
boot-env or
config parameter must be specified.
In the config>redundancy context, this command performs an automatically triggered standby CPM synchronization.
When the standby CPM takes over operation following a failure or reset of the active CPM, it is important to ensure that the active and standby CPMs have identical operational parameters. This includes the saved configuration, CPM and IOM images.
The active CPM ensures that the active configuration is maintained on the standby CPM. However, to ensure smooth operation under all circumstances, runtime images and system initialization configurations must also be automatically synchronized between the active and standby CPM.
The no form of this command administratively disables multi-chassis LAG. MC-LAG can only be issued only when mc-lag is shutdown.
The no form of this command sets this parameter to default value.
lag lag-id lacp-key
admin-key system-id
system-id [remote-lag
lag-id] system-priority
system-priority
The same lacp-key,
system-id, and
system-priority must be configured on both nodes of the redundant pair in order to MC-LAG to become operational. In order MC-LAG to become operational, all parameters (
lacp-key,
system-id,
system-priority) must be configured the same on both nodes of the same redundant pair.
The partner system (the system connected to all links forming MC-LAG) will consider all ports using the same lacp-key,
system-id,
system-priority as the part of the same LAG. In order to achieve this in MC operation, both redundant-pair nodes have to be configured with the same values. In case of the mismatch, MC-LAG is kept in oper-down status.
The LAG identifier, expressed as a decimal integer. Specifying the lag-id allows the mismatch between lag-id on redundant-pair. If no
lag-id is specified it is assumed that neighbor system uses the same
lag-id as a part of the given MC-LAG. If no matching MC-LAG group can be found between neighbor systems, the individual LAGs will operate as usual (no MC-LAG operation is established.).
port [port-id | lag-id] [sync-tag
sync-tag] [create
]
range encap-range sync-tag
sync-tag
|
Values
|
Dot1Q start-vlan- end-vlan
QinQ Q1. start-vlan-Q1. end-vlan
|
The keywords (ipoe,
pppoe) must match on both nodes. If not, subscriber synchronization will fail.
[no
] ring
sync-tag [create
]
The no form of the command removes the sync-tag from the configuration.
[no
] l3-ring name
[create
]
This command enables the inband control path debouncing. The no form of the command disables inband control path debouncing.
[no
] ring-node
ring-node-name
[no] srrp-instance
srrp-id
[no
] accounting-policy
acct-policy-id
event-control application-id [event-name | event-number] [generate
[severity-level] [throttle]
event-control application-id [event-name | event-number] suppress
The no form of the command reverts the parameters to the default setting for events for the application or a specific event within the application. The severity, generate, and suppress options will also be reset to the initial values.
aps, atm, bgp, cflowd, chassis, debug, dhcp, efm_oam, filter, gsmp, igmp, igmp_snooping, ip, isis, lag, ldp, logger, mc_redundancy, mirror, mpls, ntp, oam, ospf, pim, port, ppp, rip, route_policy, rsvp, security, snmp, stp, svcmgr, system, user, vrrp, vrtr
[no
] sub-ident-policy
sub-ident-policy-name
entry key app-profile-string app-profile
app-profile-name
The no form of the command removes the values from the configuration.
[no
] use-direct-map-as-default
The no form of the command disables the direct mapping.
entry key sla-profile-string sla-profile
sla-profile-name
entry key sub-profile-string sub-profile
sub-profile-name
|
Values
|
mac — The MAC address can be combined with other subscriber host identification fields (circuit-id, remote-id, session-id or sap-id) to form a sub-id name in a user readable format or as a random 10 character encoded value.
|
circuit-id — The circuit-id can be combined with other subscriber host identification fields (mac, remote-id, session-id or sap-id) to form a sub-id name in a user readable format or as a random 10 character encoded value.
remote-id — The remote-id can be combined with other subscriber host identification fields (mac, circuit-id, session-id or sap-id) to form a sub-id name in a user readable format or as a random 10 character encoded value.
sap-id — The sap-id can be combined with other subscriber host identification fields (mac, circuit-id, remote-id, or session-id) to form a sub-id name in a user readable format or as a random 10 character encoded value.
In case that a more specific sub-id name generation method is not available and the auto-id keyword is defined under the def-sub-id hierarchy, the sub-id name will be generated by concatenating fields defined in this command separated by a “|” character.
In case that a more specific sub-id name generation method is not available and the auto-id keyword is not defined under the def-sub-id hierarchy, the sub-id name will be a random 10 character encoded string based on the fields defined under this command.
|
Values
|
mac — The MAC address can be combined with other subscriber host identification fields (circuit-id, remote-id, session-id or sap-id) to form a sub-id name in a user readable format or as a random 10 character encoded value.
|
circuit-id — The circuit-id can be combined with other subscriber host identification fields (mac, remote-id, session-id or sap-id) to form a sub-id name in a user readable format or as a random 10 character encoded value.
remote-id — The remote-id can be combined with other subscriber host identification fields (mac, circuit-id, session-id or sap-id) to form a sub-id name in a user readable format or as a random 10 character encoded value.
sap-id — The sap-id can be combined with other subscriber host identification fields (mac, circuit-id, remote-id, or session-id) to form a sub-id name in a user readable format or as a random 10 character encoded value.
session-id — The session-id can be combined with other subscriber host identification fields (mac, circuit-id, remote-id, or sap-id) to form a sub-id name in a user readable format or as a random 10 character encoded value.
[no
] sub-profile subscriber-profile-name
When a subscriber profile is created with the subscriber-profile-name default, it will be used when no other subscriber profile is associated with the subscriber host by the system. Creating a subscriber profile with the
subscriber-profile-name default is optional. If a default subscriber profile is not created, all subscriber hosts subscriber identification strings must match either a non-provisioned default or be provisioned as an explicit match to a subscriber profile.
The no form of this command removes the accounting policy association.
When the no collect-stats command is issued the statistics are still accumulated by the IOM 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.
agg-rate-limit {max
| kilobits-per-second} [queue-frame-based-accounting
]
The no form of the command removes both an egress aggregate rate limit and egress frame based accounting for all subscribers associated with the sub-profile. If a subscriber’s accounting mode is changed, the subscriber’s queue statistics are cleared.
{max |
kilobits-per-second}
The max keyword and
kilobits-per-second parameter are mutually exclusive. Either max or a value for kilobits-per-second must follow the egress-agg-rate-limit command.
The no form of the command removes the avg-frame-size parameter from the subscriber profile.
When the encap-offset option is configured in the subscriber profile, the subscriber host queue rates, that is, CLI and operational PIR and CIR as well as queue bucket updates, the queue statistics, that is, forwarded, dropped, and HQoS offered counters use the last-mile frame-over-the-wire format. The scheduler policy CLI and operational rates also use LM-FoW format. The port scheduler max-rate and the priority level rates and weights, if a Weighted Scheduler Group is used, are always entered in CLI and interpreted as local port frame-over-the-wire rates. The same is true for an agg-rate-limit applied to a vport. Finally the subscriber agg-rate-limit is entered in CLI as last-mile frame-over-the-wire rate. The system maintains a running average frame expansion ratio for each queue to convert queue rates between these two formats.
scheduler scheduler-name rate
pir-rate [cir
cir-rate]
This command provides a way to override parameters of the existing scheduler associated with the egress or ingress scheduler policy. A scheduler defines bandwidth controls that limit each child (other schedulers 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 queues or other schedulers defined as child associations. The scheduler can be a child (take bandwidth from a scheduler in a higher tier, except for schedulers created in tier 1).
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 no form of the command removes the policy name from the configuration. The policy must not be associated with any entity.
This command selects an existing host lockout policy. The host-lockout-policy policy-name is created in the
config>subscriber-mgmt context.
The no form of the command removes the policy name from the SAP configuration.
The no form of the command reverts to the default value
The no form of the command reverts to the default value.
This command specifies a scheduler policy to associate to the subscriber profile. Scheduler policies are configured in the configure>qos>scheduler>policy context. Each scheduler policy is divided up into groups of schedulers based on the tier each scheduler is created under. A tier is used to give structure to the schedulers within a policy and define rules for parent scheduler associations. The policy defines the hierarchy and operating parameters for virtual schedulers.
This command is used to create, delete, or modify policer control policies. 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 can also be applied to the ingress or egress context of a sub-profile.
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.
The create keyword is required when a new policy is being created and the system is configured for explicit object creation mode.
The max-rate command defines the parent policer’s PIR leaky bucket’s decrement rate. A parent policer is created for each time the policer-control-policy is applied to either a SAP or subscriber instance. Packets that are not discarded by the child policers associated with the SAP or subscriber instance are evaluated against the parent policer’s PIR leaky bucket.
The policer-control-policy root max-rate setting may be overridden on each SAP or sub-profile where the policy is applied.
The max parameter is mutually exclusive with defining a
kilobits-per-second value. When max is specified, the parent policer does not enforce a maximum rate on the aggregate throughput of the child policers. This is the default setting when the
policer-control-policy is first created and is the value that the parent policer returns to when no max-rate is executed. In order for the parent policer to be effective, a kilobits-per-second value should be specified.
The no max-rate command returns the policer-control-policy’s parent policer maximum rate to max.
The priority-mbs-thresholds command contains the root arbiter parent policer’s
min-thresh-separation command and each priority level’s
mbs-contribution command that is used to internally derive each priority level’s shared-portion and fair-portion values. The system uses each priority level’s shared-portion and fair-portion value to calculate each priority level’s discard-unfair and discard-all MBS thresholds that enforce priority sensitive rate-based discards within the root arbiter’s parent policer.
The priority-mbs-thresholds CLI node always exists and does not need to be created.
The min-thresh-separation command defines the minimum required separation between each in-use discard threshold maintained for each parent policer context associated with the policer-control-policy. The min-thresh-separation value may be overridden on each SAP or sub-profile to which the policy is applied.
The second function the system uses the min-thresh-separation value for is determining the value per priority level for the fair-portion:
When the mbs-contribution command’s optional fixed keyword is defined for a priority level within the policy, the system will treat the defined
mbs-contribution value as an explicit definition of the priority level’s MBS. While the system will continue to track child policer associations with the parent policer priority levels, the association counters will have no effect. Instead the following rules will be used to determine a fixed priority level’s shared-portion and fair-portion:
|
•
|
If the mbs-contribution value is not set to zero:
|
mbs-contribution value less
min-thresh-separation value
Each time the min-thresh-separation value is modified, the thresholds for all instances of the parent policer created through association with this
policer-control-policy are reevaluated.
The minimum value for min-thresh-separation should be set equal to the maximum size packet that will be handled by the parent policer. This ensures that when a lower priority packet is incrementing the bucket, the size of the increment will not cause the bucket's depth to equal or exceed a higher priority threshold. It also ensures that an unfair packet within a priority level cannot cause the PIR bucket to increment to the discard-all threshold within the priority.
In most circumstances, a value larger than the maximum packet size is not necessary. Management of priority level aggregate burst tolerance is intended to be implemented using the priority level mbs-contribution command. Setting a value larger than the maximum packet size will not adversely affect the policer performance, but it may increase the aggregate burst tolerance for each priority level.
The no form of this command returns the policy’s
min-thresh-separation value to the default value.
The size parameter is required when executing the min-thresh-separation command. It is expressed as an integer and specifies the shared portion in bytes or kilobytes that is selected by the trailing bytes or kilobytes keywords. If both bytes and kilobytes are missing, kilobytes is the assumed value. Setting this value has no effect on parent policer instances where the
min-thresh-separation value has been overridden.
The bytes keyword is optional and is mutually exclusive with the
kilobytes keyword. When specified, size is interpreted as specifying the size of
min-thresh-separation in bytes.
The kilobytes keyword is optional and is mutually exclusive with the
bytes keyword. When specified, size is interpreted as specifying the size of
min-thresh-separation in kilobytes.
The priority level command contains the
mbs-contribution configuration command for a given strict priority level. Eight levels are supported numbered 1 through 8 with 8 being the highest strict priority.
The mbs-contribution command is used to configure the policy-based burst tolerance for a parent policer instance created when the policy is applied to a SAP or subscriber context. The system uses the parent policer’s
min-thresh-separation value, the priority level’s
mbs-contribution value and the number of child policers currently attached to the priority level to derive the priority level’s shared-portion and fair-portion of burst tolerance within the local priority level. The shared-portion and fair-portions for each priority level are then used by the system to calculate each priority level’s discard-unfair threshold and discard-all threshold.
The value for a priority level’s mbs-contribution within the policer-control-policy may be overridden on the SAP or subscriber sub-profile where the policy is applied in order to allow fine tuning of the discard-unfair and discard-all thresholds relevant to the needs of the local child policers on the object.
When defining mbs-contribution, the specified size may only be a portion of the burst tolerance associated with the priority level. The packets associated with the priority level share the burst tolerance of lower within the parent policer. As the parent policer PIR bucket depth increases during congestion, the lower priority packets eventually experience discard based on each priority’s discard-unfair and discard-all thresholds. Assuming congestion continues once all the lower priority packets have been prevented from consuming bucket depth, the burst tolerance for the priority level will be consumed by its own packets and any packets associated with higher priorities.
In the most conservative case, a priority level’s mbs-contribution value may be set to be greater than the sum of child policer’s mbs and one max-size-frame per child policer. This ensures that even in the absolute worst case where all the lower priority levels are simultaneously bursting to the maximum capacity of each child, enough burst tolerance for the priority’s children will exist if they also burst to their maximum capacity.
In the default behavior, the system ignores the mbs-contribution values for a priority level on a subscriber or SAP parent policer when a child policer is not currently associated with the level. This prevents additional burst tolerance from being added to higher priority traffic within the parent policer.
This does cause fluctuations in the defined threshold values when child policers are added or removed from a parent policer instance. If this behavior is undesirable, the fixed keyword may be used which causes the mbs-contribution value to always be included in the calculation of parent policer’s discard thresholds. The defined
mbs-contribution value may be overridden on a subscriber sla-profile or on a SAP instance, but the fixed nature of the contribution cannot be overridden.
If the defined mbs-contribution value for the priority level is zero, the priority level will have no effect on the parent policer’s defined discard thresholds. A packet associated with the priority level will use the next lower priority level’s discard-unfair and discard-all thresholds.
The size parameter is required when executing the mbs-contribution command. It is expressed as an integer and specifies the priority’s specific portion amount of accumulative MBS for the priority level in bytes or kilobytes which is selected by the trailing
bytes or
kilobytes keywords. If both
bytes and
kilobytes are missing,
kilobytes is assumed. Setting this value has no effect on parent policer instances where the priority level’s
mbs-contribution value has been overridden.
The bytes keyword is optional and is mutually exclusive with the
kilobytes keyword. When specified, size is interpreted as specifying the size of
min-thresh-separation in bytes.
The kilobytes keyword is optional and is mutually exclusive with the
bytes keyword. When specified, size is interpreted as specifying the size of min-thresh-separation in kilobytes.
The optional fixed keyword is used to force the inclusion of the defined mbs-contribution value in the parent policer’s discard threshold calculations. If the
mbs-contribution command is executed without the
fixed keyword, the fixed calculation behavior for the priority level is removed.
The no mbs-contribution command returns the policy’s priority level’s MBS contribution to the default value. When changed, the thresholds for the priority level and all higher priority levels for all instances of the parent policer will be recalculated.
This command enables the context to configure SLA profile mapping.
entry key sub-profile-string sub-profile
sub-profile-name
[no
] use-direct-map-as-default
The no form of the command disables direct mapping,
The no form of the command removes the aggregate rate limit from the sub-profile.
The no form of the command returns the HSMDA queue mapping for queue to the default mapping for the forwarding class.
rate pir-rate [cir
cir-rate]
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).
The max default specifies the amount of bandwidth in kilobits per second (thousand bits per second). The
max value is mutually exclusive to the
pir-rate value.
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 or queues.
An hsmda-slope-policy named default always exists on the system and does not need to be created. The default policy is automatically applied to all HSMDA queues unless another HSMDA slope policy is specified for the queue. The default policy cannot be modified or deleted. Attempting to execute no hsmda-slope-policy default will result in an error.
The no form of the command returns the weight value for the queue to the default value.
This command configures an SLA profile mapping. Hosts associated with a subscriber are subdivided into Service Level Agreement (SLA) profiles. For each subscriber host an SLA profile can be specified. For a subscriber host, the SLA profile determines:
When the keywords remove-oldest are specified, the oldest subscriber host will be removed when the host limit is reached.
qos sap-egress-policy-id [vport-scheduler|port-scheduler] [force
]
qos policy-id [shared-queuing
| multipoint-shared
| service-queuing
] [force
]
This keyword is mutually exclusive with the multipoint-shared and
service-queuing keywords to specify the policy used by this SAP. When the value of this object is null it means that the SAP will use individual ingress QoS queues, instead of the shared ones.
This keyword is mutually exclusive with the shared-queuing and
service-queuing keywords. When multipoint-shared is specified, the ingress forwarding plane will conserve hardware queues by performing two tier queuing on ingress unicast and multipoint packets through the SAP. Unicast service queues defined in the SAP ingress QoS policy are created for the SAP on the ingress forwarding plane without regard for the switch fabric destinations to which the SAP may need to forward (other destinations in the VPLS context). The multipoint queues defined in the SAP ingress QoS policy are not created for the SAP. Instead, all multipoint traffic is mapped to the unicast queues based on forwarding class in the first pass. In the second pass the unicast packets will be mapped to the unicast shared queues while the multipoint traffic will be mapped to the multipoint shared queues.
This command configures the context to configure egress or ingress queue parameters. Parameters defined in the config>qos>sap-egress policy-id or the
config>qos>sap-ingress policy-id context are overridden by parameters specified in the subscriber management SLA profile context.
The no form of the command removes the
queue-id from the SLA profile.
Specifies the queue-id for the SAP egress or ingress queue, expressed as a decimal integer. The
queue-id uniquely identifies the queue within the profile.
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.
The queue burst-limit command is used to define 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 burst-limit command is supported under the sap-ingress and sap-egress QoS policy queues. The command is also supported under the ingress and egress queue-group-templates queues.
The no form of this command
is used to restore the default burst limit to the specified queue. This is equivalent to specifying burst-limit default within the QoS policies or queue group templates. When specified within a queue-override queue context, any current burst limit override for the queue will be removed and the queue’s burst limit will be controlled by its defining policy or template.
The bytes qualifier is used to specify that the value given for size must be interpreted as the burst limit in bytes. The byte qualifier is optional and mutually exclusive with the kilobytes qualifier.
The kilobyte qualifier is used to specify that the value given for size must be interpreted as the burst limit in Kilobytes. The kilobyte qualifier is optional and mutually exclusive with the bytes qualifier. If neither bytes nor kilobytes is specified, the default qualifier is kilobytes.
The no form of this command returns the CBS size to the size as configured in the QoS policy.
The defined high-prio-only value cannot be greater than the MBS size of the queue. Attempting to change the MBS to a value smaller than the high priority reserve will generate an error and fail execution. Attempting to set the
high-prio-only value larger than the current MBS size will also result in an error and fail execution.
The no form of this command returns high-prio-only to the size as configured in the QoS policy.
The percent parameter is the percentage reserved for high priority traffic on the queue. If a value of 10KBytes is desired, enter the value 10. A value of 0 specifies that none of the MBS of the queue will be reserved for high priority traffic. This does not affect RED slope operation for packets attempting to be queued.
The no form of this command returns the MBS size to the size as configured in the QoS policy.
mbs size [bytes | kilobytes]
The no form of this command returns the MBS size to the size as configured in the QoS policy.
rate pir-rate [cir
cir-rate]
The CIR can be used by the queue’s parent command’s 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 anytime, 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).
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.
[no
] qos-marking-from-sap
The no form of the command reverts to the egress QoS marking defined in SAP-egress policy defined at sla-profile level.
Specifies the rate taken from the scheduler scheduler-name. If the
scheduler scheduler-name is not present in the scheduler-policy configured in the
config>subscr-mgmt>sub-prof>egr context, fall back to the default (no report-rate)
[no
] use-ingress-l2tp-dscp
Note: system does not check if the configured filter include http-redirection entry. If the filter does not include the http-redirection then it will not be replaced in future.
rate pir-rate [cir
cir-rate]
This command defines the administrative Peak Information Rate (PIR) and the administrative Committed Information Rate (CIR) parameters for the queue. The PIR defines the maximum rate that the queue can transmit packets through the switch fabric (for SAP ingress 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 oversubscription factors or available egress bandwidth.
The CIR can be used by the queue’s parent command’s 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 anytime, altering the PIR and CIR rates for all queues created through the association of the SAP ingress or 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).
Specifies the cir parameter 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 no form of this command is used to delete a policer from a sap-ingress or sap-egress QoS policy. The specified policer cannot currently have any forwarding class mappings for the removal of the policer to succeed. It is not necessary to actually delete the policer ID for the policer instances to be removed from SAPs or subscribers associated with the QoS policy once all forwarding classes have been moved away from the policer. It is automatically deleted from each policing instance although it still appears in the QoS policy.
The policer-id must be specified when executing the policer command. If the specified ID already exists, the system enters that policer's context to allow the policer’s parameters to be modified. If the ID does not exist and is within the allowed range for the QoS policy type, a context for the policer ID will be created (depending on the system's current create keyword requirements which may require the create keyword to actually add the new policer ID to the QoS policy) and the system will enter that new policer’s context for possible parameter modification.
cbs {size [bytes
| kilobytes
] | default
}
The policer’s cbs size defined in the QoS policy may be overridden on an
sla-profile or SAP where the policy is applied.
The size parameter is required when specifying
cbs 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.
When byte is defined, the value given for size is interpreted as the queue’s MBS value given in bytes.
When kilobytes is defined, the value is interpreted as the queue’s MBS value given in kilobytes.
mbs {size [bytes
| kilobytes
] | default
}
This command is used to configure the policer’s PIR leaky bucket’s high priority violate threshold. The high-prio-only command is applied to the MBS value to derive the bucket’s low priority violate threshold. For ingress, trusted in-profile packets and un-trusted high priority packets use the policer’s high priority violate threshold while trusted out-of-profile and un-trusted low priority packets use the policer's low priority violate threshold. At egress, in-profile packets use the policer’s high priority violate threshold and out-of-profile packets use the policer's low priority violate threshold.
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
byte and
kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
When byte is defined, the value given for size is interpreted as the queue’s MBS value given in bytes.
When kilobytes is defined, the value is interpreted as the queue’s MBS value given in kilobytes.
This command is used to modify the size of each packet handled by the policer by adding or subtracting a number of bytes. The actual packet size is not modified; only the size used to determine the bucket depth impact is changed. The packet-byte-offset command is meant to be an arbitrary mechanism the can be used to either add downstream frame encapsulation or remove portions of packet headers. Both the policing metering and profiling throughput is affected by the offset as well as the stats associated with the policer.
The policer’s packet-byte-offset defined in the QoS policy may be overridden on an
sla-profile or SAP where the policy is applied.
The no version of this command is used to remove per packet size modifications from the policer.
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.
The subtract keyword is mutually exclusive to the
add keyword. Either
add or
subtract must be specified. When b 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.
rate {max
| kilobits-per-second
} [cir
{max
| kilobits-per-second
}]
The policer’s adaptation-rule command settings are used by the system to convert the specified rates into hardware timers and decrement values for the policer’s buckets.
By default, the policer’s metering rate is max and the profiling rate is 0 Kbps (all packets out-of-profile).
The rate settings defined for the policer in the QoS policy may be overridden on an
sla-profile or SAP where the policy is applied.
The no form of this command is used to restore the default metering and profiling rate to a policer.
{max |
kilobits-per-second}
Specifying the keyword max or an explicit
kilobits-per-second parameter directly following the rate command is required and identifies the policer’s metering rate for the PIR leaky bucket. When the policer is first created, the metering rate defaults to max. 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.
cir {max | kilobits-per-second
}
The optional cir keyword is used to override the default CIR rate of the policer. Specifying the keyword max or an explicit
kilobits-per-second parameter directly following the cir keyword is required and identifies the policer’s profiling rate for the CIR leaky bucket. When the policer is first created, the profiling rate defaults to 0 Kbps. 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.
stat-mode {no-stats
| minimal
| offered-profile-no-cir
| offered-priority-no-cir
| offered-limited-profile-cir
| offered-profile-cir
| offered-priority-cir
| offered-total-cir
}
While a no-stats mode is supported which prevents any packet accounting, the use of the policer’s
parent command requires at 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. Once a policer has been made a child to a parent policer, the
stat-mode cannot be changed to
no-stats unless the policer parenting is first removed.
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 an
sla-profile or 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 this command attempts to return the policer’s stat-mode setting to minimal. The command will fail if insufficient policer counter resources exist to implement minimal where the QoS policer is currently applied and has a forwarding class mapping.
When collect-stats is enabled, the lack of counters causes the system to generate the following statistics:
The default stat-mode for a policer is
minimal. The
minimal mode allocates 1 forwarding plane offered counter and one traffic manager discard counter. The forwarding counter is derived by subtracting the discard counter from the offered counter. The counters do not differentiate possible offered types (profile or priority) and do not count green or yellow output. This does not prevent the policer from supporting different offered packet types and does not prevent the policer from supporting a CIR rate.
When collect-stats is enabled, the counters are used by the system to generate the following statistics:
With minimal enabled as the policer
stat-mode, the SAP offered stats for the policer returned via MIB query and CLI show commands will return the following values:
The offered-profile-no-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters.
The offered-profile-no-cir mode is most useful when the policer is receiving only in-profile and out-of-profile pre-marked (and trusted) packets. It is expected that in this instance a CIR rate will not be defined since all packet are already pre-marked. This mode does not prevent the policer from receiving un-trusted (color undefined) nor does it prevent the policer from being configured with a CIR rate.
When collect-stats is enabled, the counters are used by the system to generate the following statistics:
With offered-profile-no-cir enabled as the policer
stat-mode, the SAP offered stats for the policer returned via MIB query and CLI show commands will return the following values:
The offered-priority-no-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters.
The offered-priority-no-cir mode is most useful when the policer is receiving only un-trusted packets and the ingress priority high and priority low classification options are being used without a CIR profiling rate defined. This mode does not prevent the policer from receiving trusted packets that are pre-marked in-profile or out-of-profile nor does it prevent the policer from being configured with a CIR rate.
When collect-stats is enabled, the counters are used by the system to generate the following statistics:
With offered-priority-no-cir enabled as the policer
stat-mode, the SAP offered stats for the policer returned via MIB query and CLI show commands will return the following values:
The offered-limitied-profile-cir mode allocates three forwarding plane offered counters and three traffic manager discard counters.
The offered-limited-profile-cir mode is most useful when the policer is receiving trusted out-of-profile (profile out but no profile in) traffic and un-trusted packets are being applied to a defined CIR profiling rate. This mode does not prevent the policer from receiving trusted in-profile packets.
When collect-stats is enabled, the counters are used by the system to generate the following statistics:
With offered-limited-profile-cir enabled as the policer
stat-mode, the SAP offered stats for the policer returned via MIB query and CLI show commands will return the following values:
The offered-profile-cir mode allocates four forwarding plane offered counters and four traffic manager discard counters.
The offered-profile-cir mode is most useful when the policer is receiving trusted out-of-profile and in-profile traffic and is also receiving un-trusted packets that are being applied to a defined CIR profiling rate. This mode differs from
offered-limited-profile-cir mode in that it expects both trusted in-profile and out-of-profile packets while still performing CIR profiling on packets with un-trusted markings. It is expected that in most cases where both trusted and un-trusted packets are received, the predominate case will not include trusted in-profile packets making the offered-limited-profile-cir accounting mode acceptable.
When collect-stats is enabled, the counters are used by the system to generate the following statistics:
With offered-profile-cir enabled as the policer
stat-mode, the SAP offered stats for the policer returned via MIB query and CLI show commands will return the following values:
The offered-priority-cir mode allocates four forwarding plane offered counters and four traffic manager discard counters.
The offered-priority-cir mode is most useful when the policer is receiving only un-trusted packets that are being classified as high priority or low priority and are being applied to a defined CIR profiling rate. This mode differs from
offered-profile-cir mode in that it does not expect trusted in-profile and out-of-profile packets but does not exclude the ability of the policer to receive them.
When collect-stats is enabled, the counters are used by the system to generate the following statistics:
With offered-priority-cir enabled as the policer
stat-mode, the SAP offered stats for the policer returned via MIB query and CLI show commands will return the following values:
The offered-total-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters.
The offered-total-cir mode is most useful when the policer is not receiving trusted in-profile or out-of-profile traffic and both high and low priority classifications are not being used on the un-trusted packets and the offered packets are being applied to a defined CIR profiling rate. This mode does not prevent the policer from receiving trusted in-profile or out-of-profile packets and does not prevent the use of priority high or low classifications on the un-trusted packets.
When collect-stats is enabled, the counters are used by the system to generate the following statistics:
With offered-total-cir enabled as the policer
stat-mode, the SAP offered stats for the policer returned via MIB query and CLI show commands will return the following values:
entry key sub-ident-string [sub-profile
sub-profile-name] [alias
sub-alias-string] [sla-profile
sla-profile-name]
The no form of the command disables the command.
The no form of the command removes the value from the configuration.
configure
system
security
source-address
application <app> <ip-int-name | ip-address>
<app> : cflowd|dns|ftp|ntp|ping|radius|snmptrap|sntp|ssh|
syslog|tacplus|telnet|traceroute|mcreporter
<ip-int-name|ip-ad*> : ip-int-name - 32 chars max
ip-address - a.b.c.d
[no
] per-host-replication
The no form of the command removes the default SLA profile from the SAP configuration.
The no form of the command removes the default SLA profile from the SAP configuration.
The no form of the command removes the default subscriber identification policy from the SAP configuration.
The no form of the command reverts back to the default setting.
The no form of the command removes any configured profile.
[no
] profiled-traffic-only
The no form of the command reverts to the default setting.
The no form of the command removes an SRRP instance from a group IP interface. Once removed, the group interface ignores ARP requests for the SRRP gateway IP addresses that may exist on subscriber subnets associated with the group IP interface. Then the group interface stops routing using the redundant IP interface associated with the group IP interface and will stop routing with the SRRP gateway MAC address. Ingress packets destined to the SRRP gateway MAC will also be silently discarded. This is the same behavior as a group IP interface that is disabled (shutdown).
The no form of the command removes the explicit SRRP gateway MAC address from the SRRP instance. The SRRP gateway MAC address can only be changed or removed when the SRRP instance is shutdown.
The no form of the command restores the default interval.
The no form of the command can only be executed when the SRRP instance is shutdown. Executing no message-path allows the existing SAP to be used for subscriber management functions. A new message-path SAP must be defined prior to activating the SRRP instance.
[no
] policy
vrrp-policy-id
The no form of the command removes the association with vrrp-policy-id from the SRRP instance.
The no form of the command restores the default base priority to the SRRP instance. If a VRRP policy is associated with the SRRP instance, it will use the default base priority as the basis for any modifications to the SRRP instances in-use priority.
The no tos-marking-state command is used to restore the trusted state to a network IP interface. This is equivalent to executing the tos-marking-state trusted command.
Specifies that all egress network IP interfaces will remark IP packets received on the network interface according to the egress marking definitions on each network interface.
The no form of the command reverts to the default setting.
host {[ip
ip-address [mac
mac-address]} [subscriber-sap-id
| subscriber
sub-ident-string [sub-profile
sub-profile-name [sla-profile
sla-profile-name [ancp-string
ancp-string] [app-profile
app-profile-name] [inter-dest-id
intermediate-destination-id]
no host {[ip
ip-address] [mac
ieee-address]}
Use the no form of the command to remove a static entry from the system. The specified
ip-address and
mac-address must match the host’s exact IP and MAC addresses as defined when it was created. When a static host is removed from the SAP, the corresponding anti-spoof filter entry and/or FDB entry is also removed.
|
•
|
For VPLS SAPs with arp-reply-agent enabled with the optional sub-ident parameter, the static subscriber hosts sub-ident-string is used to determine whether an ARP request received on the SAP is sourced from a host belonging to the same subscriber as the destination host. When both the destination and source hosts from the ARP request are known on the SAP and the subscriber identifications do not match, the ARP request may be forwarded to the rest of the VPLS destinations.
|
If the static subscriber hosts sub-ident string is not defined, the host is not considered to belong to the same subscriber as another host on the SAP.
If sub-ident is not enabled on the SAP arp-reply-agent, subscriber identification matching is not performed on ARP requests received on the SAP.
Note that if Enhanced Subscriber Management is enabled on a SAP using the sub-sla-mgmt command, the
sub-ident,
sub-profile, and
sla-profile must be configured for all static hosts defined on this SAP.
The no form of the command removes the policy ID from the SAP or interface configuration.
The no form of the command removes the policy ID from the SAP or interface configuration.
The no form of the command removes the values from the configuration.
The no form of the command removes the values from the configuration.
The no form of the command removes the policy association from the SAP or SDP.
The no form of the command removes the values from the configuration.
The no form of the command removes the value from the 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.
The no form of the command removes the application profile name from the configuration.
This command specifies a default destination string for all subscribers associated with the SAP. The command also accepts the use-top-q flag that automatically derives the string based on the top most delineating Dot1Q tag from the SAP’s encapsulation.
The no form of the command removes the default subscriber identification string from the configuration.
The no form of the command removes the default SLA profile from the MSAP configuration.
The no form of the command removes the default SLA profile from the SAP configuration.
The no form of the command reverts back to the default setting.
The no form of the command removes any configured profile.
[no
] profiled-traffic-only
The no form of the command reverts to the default setting.
[no
] sub-ident-policy
sub-ident-policy-name
ARP replies and requests received on an MSAP with arp-reply-agent enabled will be evaluated by the system against the anti-spoof filter entries associated with the ingress SAP (if the SAP has anti-spoof filtering enabled). ARPs from unknown hosts on the SAP will be discarded when anti-spoof filtering is enabled.
Static hosts can be defined using the host command. Dynamic hosts are enabled on the system by enabling the
lease-populate command in the
dhcp context. In the event that both a static host and a dynamic host share the same IP and MAC address, the VPLS ARP reply agent will retain the host information until both the static and dynamic information are removed. In the event that both a static and dynamic host share the same IP address, but different MAC addresses, the VPLS ARP reply agent is populated with the static host information.
The arp-reply-agent command will fail if an existing static host does not have both MAC and IP addresses specified. Once the ARP reply agent is enabled, creating a static host on the MSAP without both an IP address and MAC address will fail.
The no form of the command disables ARP-reply-agent functions for static and dynamic hosts on the MSAP.
|
•
|
When sub-ident is not configured, the arp-reply-agent does not attempt to identify the subscriber information for the destination or originating host and will not discard an ARP request based on subscriber information.
|
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 MSAP.
|
•
|
Populate an MSAP 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 new lease state entry or updating an existing lease state entry.
|
The no form of the command disables dynamic host lease state management for the MSAP.
The no form of this command returns the system to the default.
action {replace
| drop
| keep
}
The no form of this command returns the system to the default value.
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 disabled, the circuit-id sub-option of the DHCP packet will be left empty.
The no form of this command returns the system to the default.
[no
] vendor-specific-option
The no form of the command disables the sending of the MAC address in the Alcatel-Lucent vendor specific sub-option of the DHCP relay packet.
The no form of the command disables the sending of the SAP ID in the Alcatel-Lucent vendor specific sub-option of the DHCP relay packet.
The no form of the command disables the sending of the service ID in the Alcatel-Lucent vendor specific sub-option of the DHCP relay packet.
The no form of the command returns the default value.
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.
lease-time [days
days] [hrs
hours] [min
minutes] [sec
seconds] [override
]
Further subcategories are created for an IGMP (s,g) flooding list. A Layer 2 (s,g) record is created in a specific VPLS instance (the instance the (s,g) flow ingresses). SAPs within that VPLS context that join the (s,g) record are considered native SAPs within the flooding list. SAPs that join the (s,g) flooding list through the multicast VPLS registration process (MVR) from another VPLS context using the from-vpls command are considered alien SAPs. The distinction between native and alien in the list is maintained to allow the forwarding plane to enforce or suspend split-horizon-group (SHG) squelching. When the source of the (s,g) matching packet is in the same SHG as a native SAP, the packet must not be replicated to that SAP. For a SAP in another VPLS context, the source SHG of the packet has no meaning and the forwarding plane must disregard SHG matching between the native source of the packet and the alien destination. Because the SHG squelch decision is done for the whole chain based on the first SAP in the chain, all SAPs in the chain must be all native or all alien SAPs. Chains for IGMP (s,g) flooding lists are created using the following rules:
The no form of the command removes a specific egress multicast group. Deleting an egress multicast group will only succeed when the group has no SAP members. To remove SAP members, use the
no multicast-group group-name command under each SAP’s egress context.
Note: Efficient multicast replication will only be performed on IOMs that support chassis mode b If an IOM does not support mode b operation, egress-multicast-group membership is ignored on that IOM’s egress forwarding planes. The chassis need not be placed into mode b for efficient multicast replication to be performed on the capable IOMs.
When IGMP fast leave processing is enabled, the SR-Series will immediately remove a SAP or SDP from the IP multicast group when it detects an IGMP 'leave' on that SAP or SDP. Fast leave processing allows the switch to remove a SAP or SDP that sends a 'leave' from the forwarding table without first sending out group-specific queries to the SAP or SDP, and thus speeds up the process of changing channels ('zapping').
The no form of the command removes the policy association from the SAP or SDP.
level level-id bw
bandwidth
This command configures the bandwidth for the interface's multicast CAC policy traffic. When disabled (no unconstrained-bw) there will be no checking of bandwidth constraints on the interface level. When enabled and a policy is defined, enforcement is performed. The allocated bandwidth for optional channels should not exceed the
unconstrained-bw minus the
mandatory-bw and the mandatory channels have to stay below the specified value for the
mandatory-bw. After this interface check, the bundle checks are performed.
If the bandwidth value is 0, no mandatory channels are allowed. If the value of
bandwidth is '-1', then all mandatory and optional channels are allowed.
If the value of mandatory-bw is equal to the value of
bandwidth, then all the unconstrained bandwidth on a given interface is allocated to mandatory channels configured through multicast CAC policy on that interface and no optional groups (channels) are allowed.
The value of mandatory-bw should always be less than or equal to that of
bandwidth, An attempt to set the value of
mandatory-bw greater than that of
bandwidth, will result in inconsistent value error.
|
Values
|
service-id: 1 — 2147483647 svc-name: 64 characters maximum
|
This command configures the IGMP query interval. If the send-queries command is enabled, this parameter specifies the interval between two consecutive general queries sent by the system on an MSAP or SDP.
This command configures the IGMP query response interval. If the send-queries command is enabled, this parameter specifies the maximum response time advertised in IGMPv2/v3 queries.
This command configures the IGMP robustness variable. If the send-queries command is enabled, this parameter allows tuning for the expected packet loss on a SAP or SDP. The robust-count variable allows tuning for the expected packet loss on a subnet and is comparable to a retry count. If an MSAP or SDP is expected to be “lossy”, this parameter may be increased. IGMP snooping on an MSAP or SDP is robust to (robust-count-1) packet losses.
When the send-query command is configured, all type of queries generate ourselves are of the configured
version. If a report of a version higher than the configured version is received, the report gets dropped and a new “wrong version” counter is incremented.
If the send-query command is not configured, the
version command has no effect. The version used on that SAP or SDP will be the version of the querier. This implies that, for example, when there is a v2 querier, a v3 group or group-source specific query when a host wants to leave a certain group will never be sent.
The policy-name parameter is only valid for a SAP with the keywords
capture-sap specified in the SAP’s configuration. The
capture-sap keyword in the SAP configuration captures the SAP where triggering packets will be sent to the CPM. Non-triggering packets captured by the capture SAP will be dropped.
The no form of the command removes the policy-name from the configuration.
eval-msap {policy
msap-policy-name | msap
sap-id}
|
Values
|
[port-id|lag- id]: qtag1
[ port-id|lag- id]: qtag1.qtag2
|
subscriber-interface ip-int-name [fwd-service
service-id fwd-subscriber-interface
ip-int-name] [create
]
Use the no form of the command to remove the subscriber interface.
[no
] address
{ip-address/mask | ip-address netmask} [gw-ip-address
ip-address] [populate-host-routes
]
Use the no form of this command to remove the IP address assignment from the IP interface.
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.
[no
] allow-unmatching-subnets
[no
] allow-unmatching-subnets
The no form of this command removes the policy name from the group interface configuration.
This command enables populating static and dynamic hosts into the system ARP cache. When enabled, the host’s IP address and MAC address are placed in the system ARP cache as a managed entry. Static hosts must be defined on the interface using the host command. Dynamic hosts are enabled on the system through enabling lease-populate in the IP interface DHCP context. In the event that both a static host and a dynamic host share the same IP and MAC address, the system’s ARP cache retains the host information until both the static and dynamic information are removed. Both static and dynamic hosts override static ARP entries. Static ARP entries are marked as inactive when they conflict with static or dynamic hosts and will be repopulated once all static and dynamic host information for the IP address are removed. Since static ARP entries are not possible when static subscriber hosts are defined or when DHCP lease state table population is enabled, conflict between static ARP entries and the arp-populate function is not an issue.
The arp-populate command will fail if an existing static subscriber host on the SAP does not have both MAC and IP addresses specified.
Once arp-populate is enabled, creating a static subscriber host on the SAP without both an IP address and MAC address will fail.
arp-populate can only be enabled on VPRN interfaces supporting Ethernet encapsulation.
Use the no form of the command to disable ARP cache population functions for static and dynamic hosts on the interface. All static and dynamic host information in the systems ARP cache will be removed. Any existing static ARP entries previously inactive due to static or dynamic hosts will be populated in the system ARP cache.
When arp-populate is enabled, the system will not send out ARP Requests for hosts that are not in the ARP cache. Only statically configured and DHCP learned hosts are reachable through an IP interface with arp-populate enabled.
The no form of this command restores
arp-timeout to the default value.
The no form of the command removes the server client type from the configuration.
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 MSAP.
|
•
|
Populate an MSAP 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 new lease state entry or updating an existing lease state entry.
|
The no form of the command disables dynamic host lease state management for the MSAP.
group-interface ip-int-name [
create]
lns
group-interface ip-int-name [
create]
softgre
no group-interface ip-int-name [
create]
Use the no form of the command to remove the group interface from the subscriber interface.
The no form of the command disables
gratuitous-rtr-adv
The no form of the command disables the feature.
The no form of the command disables unicast RPF (uRPF) Check on this interface.
mode {strict
| loose
| strict-no-ecmp
}
The no form of the command reverts to the default (strict) mode.
In loose mode, uRPF checks whether incoming packet has source address with a corresponding prefix in the routing table. However, the loose mode does not check whether the interface expects to receive a packet with a specific source address prefix. This object is valid only when
urpf-check is enabled.
When the match-circuit-id command is enabled this as part of the key is used to guarantee correctness in our lookup. This is really only needed when dealing with an IP aware DSLAM that proxies the client hardware MAC address.
The no form of the command returns the MAC address of the group interface to the default value.
This command configures the aggregate rate limit in the vport container. This command is mutually exclusive with the port-scheduler-policy command under the vport. The
agg-rate-limit is only effective when used with the port scheduler that is defined under the
configure>port>sonet-sdh>path>egress-scheduler-policy port-scheduler-policy-name hierarchy. Without the
port-scheduler, the aggregate rate limit will have no effect.
The agg-limit-rate is on-the-wire rate of the directly connected ATM port. The method of calculating on-the-wire rate depends on whether the encap-offset (sub-profile) command is configured or not.
vpi vpi egress-traffic-desc
atm-td-profile-id
encapsulation [aal5auto | aal5nlpid-ppp | aal5mux-ppp | aal5snap-bridged | aal5mux-bridged-eth-nofcs
]
vc-range num vpi-range
vpi-range vci-range
vci-range
The no form of this command removes the accounting policy association.
The no form of the command reverts back to the default.
Note that for IES and VPRN subscriber group interfaces, setting no anti-spoof will set the default anti-spoofing type which is
ip-mac.
When the no collect-stats command is issued the statistics are still accumulated by the IOM 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.
cpu-protection policy-id [mac-monitoring] | [eth-cfm-monitoring [aggregate] [car]]
The no form of the command removes the association of the CPU protection policy from the associated interface and reverts to the default policy values.
The filter command is used to associate a filter policy with a specified
ip-filter-id with an ingress or egress SAP. The
filter policy 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.
The no form of this command removes any configured filter ID association with the SAP. 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 the
scope command within the filter definition to change the scope to
local or
global. The default scope of a filter is
local.
The qos command is used to associate egress QoS policies. The
qos command only allows egress policies on SAP or IP interface egress. Attempts to associate a QoS policy of the wrong type returns an error.
The no form of this command removes the QoS policy association from the SAP or IP interface, and the QoS policy reverts to the default.
qos policy-id [shared-queuing]
This qos command is used to associate ingress QoS policies. The
qos command only allows ingress policies to be associated on SAP or IP interface ingress.
The no form of this command removes the QoS policy association from the SAP or IP interface, and the QoS policy reverts to the default.
scheduler-policy scheduler-policy-name
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 ingress SAP queues associated with the customer site. 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 ingress queues reliant on the removed schedulers enter into an operational state depicting the orphaned status of one or more queues. When the
no scheduler-policy command is executed, the customer site ingress or egress node will not contain an applied scheduler policy.
The scheduler-policy-name parameter 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.
[no
] host
ip
ip-address [mac
ieee-address]] [subscriber
sub-ident-string] [sub-profile
sub-profile-name] [sla-profile
sla-profile-name]
no host {[ip
ip-address] [mac
ieee-address]}
Use the no form of the command to remove a static entry from the system. The specified
ip-address and
mac-address must match the host’s exact IP and MAC addresses as defined when it was created. When a static host is removed from the SAP, the corresponding anti-spoof entry and/or ARP cache entry is also removed.
|
•
|
For VPRN SAPs with arp-reply-agent enabled with the optional sub-ident parameter, the static subscriber hosts sub-ident-string is used to determine whether an ARP request received on the SAP is sourced from a host belonging to the same subscriber as the destination host. When both the destination and source hosts from the ARP request are known on the SAP and the subscriber identifications do not match, the ARP request may be forwarded to the rest of the VPRN destinations.
|
If the static subscriber hosts sub-ident string is not defined, the host is not considered to belong to the same subscriber as another host on the SAP.
If sub-ident is not enabled on the SAP arp-reply-agent, subscriber identification matching is not performed on ARP requests received on the SAP.
This command creates a new customer site or edits an existing customer site with the customer-site-name parameter. A customer site is an anchor point to create an ingress and egress virtual scheduler hierarchy. When a site is created, it must be assigned to a chassis slot or port with the exception of the
7750 SR-1 in which the slot is set to 1. When scheduler policies are defined for ingress and egress, the scheduler names contained in each policy are created according to the parameters defined in the policy. Multi-service customer sites exist for the sole purpose of creating a virtual scheduler hierarchy and making it available to queues on multiple Service Access Points (SAPs).
Each customer site must have a unique name within the context of the customer. If customer-site-name already exists for the customer ID, the CLI context changes to that site name for the purpose of editing the site scheduler policies or assignment. Any modifications made to an existing site will affect all SAPs associated with the site. Changing a scheduler policy association may cause new schedulers to be created and existing queues on the SAPs to no longer be orphaned. Existing schedulers on the site may cease to exist, causing queues relying on that scheduler to be orphaned.
If the customer-site-name does not exist, it is assumed that an attempt is being made to create a site of that name in the customer ID context. The success of the command execution depends on the following:
|
•
|
The customer-site-name is valid.
|
|
•
|
The create keyword is included in the command line syntax (if the system requires it).
|
If the customer-site-name is invalid, a syntax error occurs, the command will not execute and the CLI context will not change.
This command configures RFC 2684, Multiprotocol Encapsulation over ATM Adaptation Layer 5, encapsulation for an ATM PVCC delimited SAP.
|
Values
|
aal5snap-routed — Routed encapsulation for LLC encapsulated circuit (LLC/SNAP precedes protocol datagram) as defined in RFC 2684. aal5mux-ip — Routed IP encapsulation for VC multiplexed circuit as defined in RFC 2684
|
The no form of the command reverts the traffic descriptor to the default traffic descriptor profile.
The no form of the command sets the value back to the default.
[no
] redundant-interface
ip-int-name
address {ip-address/mask | ip-address netmask} [remote-ip
ip-address]
The SDP must already be defined in the config>service>sdp context in order to associate an SDP with a VPRN service. If the
sdp sdp-id is not already configured, an error message is generated. If the
sdp-id does exist, a binding between that
sdp-id and the service is created.
The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. Once removed, no packets are forwarded to the far-end router.
No sdp-id is bound to a service.
The no form of the command removes the value from the configuration.
pw-port pw-port-id [vc-id
vc-id] [create
]
The no form of the command removes the PW-port ID from the configuration.
The no form of the command removes the configured intermediate destination string.
[no
] pw-sap-secondary-shaper
secondary-shaper-name
The no form of the command removes the configured shaper.
The no form of the command removes the configured vport name.
The no form of the command reverts to the default value.
Specifies ether as the virtual circuit (VC) associated with the SDP binding.
Specifies vlan as the virtual circuit (VC) associated with the SDP binding.
The no form of the command reverts to the default value.
This command specifies the category map name.
{continue |
disconnect-host |
block-category |
change-service-level}
Specifies the activity threshold value in kilobits per second.
This command overrides the credit-type configured in the
config>subscr-mgmt>cat-map context for the given category.
volume credits bytes|kilobytes|megabytes|gigabytes
[no
] exhausted-credit-service-level
[no
] egress-ip-filter-entries
[no
] egress-ipv6-filter-entries
[no
] ingress-ip-filter-entries
[no
] ingress-ipv6-filter-entries
Specifies the HTTP web address that will be sent to the user’s browser. Note that http-redirect is not supported on 7750 SR-1 or 7450 ESS-1 models.
match [protocol
protocol-id]
dst-ip {ip-address/mask | ip-address netmask}
src-ip {ip-address/mask | ip-address netmask}
This command configures the TCP ACK match condition. The no tcp-ack command disables the checking on the presence or absence of the tcp-ack flag.
This command configures the TCP SYN match condition. The no tcp-syn command disables the checking on the presence or absence of the tcp-syn flag.
queue queue-id {ingress-only
| egress-only
| ingress-egress
}
This command configures the rating group applicable for this category.
The no form of the command reverts the configured value to the default.
[no
] egress-scheduler-override
|
•
|
The max-rate allowed for the scheduler.
|
The no form of this command removes all override parameters from the egress port or channel scheduler context. Once removed, the port scheduler reverts all rate parameters back to the parameters defined on the port-scheduler-policy associated with the port.
level priority-level rate
pir-rate [cir
cir-rate]
This command overrides the maximum and CIR rate parameters for a specific priority level on the port or channel’s port scheduler instance. When the level command is executed for a priority level, the corresponding priority level command in the port-scheduler-policy associated with the port is ignored.
The override level command supports the keyword
max for the
rate and
cir parameter.
When executing the level override command, at least the
rate or
cir keywords and associated parameters must be specified for the command to succeed.
The no form of this command removes the local port priority level rate overrides. Once removed, the port priority level will use the port scheduler policies level command for that priority level.
The channel bandwidth definition policy is defined in the mcac policy in the configure>router>mcac>policy context. The policy is applied under the group-interface or in case of redirection under the redirected-interface.
scheduler-policy scheduler-policy-name
The no form of this command removes the configured ingress or egress scheduler policy from the queue-group.
The scheduler-policy-name parameter 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.
# show aaa radius-configuration
===============================================================================
RADIUS configuration
===============================================================================
CoA Port : 3799
===============================================================================
A:cses-E11>config>subscr-mgmt>ancp# show subscriber-mgmt ancp-policy "test"
===============================================================================
ANCP Policy "test"
===============================================================================
I. Rate Reduction : 0 kbps
I. Rate Adjustment : 100 percent
I. Rate Monitor : 63360 kbps
I. Rate Monitor Alarm : Yes
I. Rate Modify : N/A
E. Rate Reduction : 0 kbps
E. Rate Adjustment : 100 percent
E. Rate Monitor : 0 kbps
E. Rate Monitor Alarm : no
E. Rate Modify : N/A
Port Down : N/A
Last Mgmt Change: 02/13/2013 19:15:28
===============================================================================
*A:cses-E11>config>subscr-mgmt>ancp#
show subscriber-mgmt ancp-string "ANCP-0000003-0000001"
========================================================================
ANCP-String "ANCP-0000003-0000001"
========================================================================
Type : SUB - "4AACAHCU74"
State : Up Ancp Policy: N/A
I. Rate : 129 kbps E. Rate : 130 kbps
Adj I. Rate: N/A Adj E. Rate: N/A
Act I. Rate: N/A Act E. Rate: N/A
Service Id : 50 (VPRN)
Group : linux
Neighbor : 10.0.0.2:34885
Persist Key: N/A
------------------------------------------------------------------------
Actual-Net-Data-Rate-Upstream : 129 kbits/s
Actual-Net-Data-Rate-Downstream : 130 kbits/s
Minimum-Net-Data-Rate-Upstream : 131 kbits/s
Minimum-Net-Data-Rate-Downstream : 132 kbits/s
Attainable-Net-Data-Rate-Upstream : 133 kbits/s
Attainable-Net-Data-Rate-Downstream : 134 kbits/s
Maximum-Net-Data-Rate-Upstream : 135 kbits/s
Maximum-Net-Data-Rate-Downstream : 136 kbits/s
Minimum-Net-Low-Power-Data-Rate-Upstream : 137 kbits/s
Minimum-Net-Low-Power-Data-Rate-Downstream : 138 kbits/s
Maximum-Interleaving-Delay-Upstream : 139 ms
Actual-Interleaving-Delay-Upstream : 140 ms
Maximum-Interleaving-Delay-Downstream : 141 ms
Actual-Interleaving-Delay-Downstream : 142 ms
DSL-Line-State : 2 (IDLE)
Access-Loop-Encapsulation : 16909056 (0x01020300)
========================================================================
# show subscriber-mgmt authentication
===============================================================================
Authentication Policies
===============================================================================
Name Description
-------------------------------------------------------------------------------
auth-policy-1 Radius auth policy - servers
auth-policy-2 Radius auth policy - radius-server-policy
-------------------------------------------------------------------------------
Number of Authentication Policies : 2
===============================================================================
# show subscriber-mgmt authentication "auth-policy-2"
===============================================================================
Authentication Policy auth-policy-2
===============================================================================
Description : Radius auth policy - radius-server-policy
Re-authentication : Yes Username Format : MAC Address
PPPoE Access Method : PAP/CHAP Username Mac-Format : "aa:"
PPP-Username Oper : None
PPP-Domain-Name : N/A
Username Oper : None
Domain-Name : N/A
Acct-Stop-On-Fail :
RADIUS Server Policy : "aaa-server-policy-1"
Fallback Action : deny
Last Mgmt Change : 06/24/2013 21:16:50
-------------------------------------------------------------------------------
Include Radius Attributes
-------------------------------------------------------------------------------
Remote Id : Yes Circuit Id : Yes
NAS Port Id : Yes NAS Identifier : Yes
PPPoE Service Name : Yes DHCP Vendor Class Id : Yes
Access Loop Options : Yes MAC Address : Yes
NAS Port Prefix : None NAS Port Suffix : None
NAS-Port-Type : Yes (standard) Acct Session Id : Host
Calling Station Id : Yes (sap-string) Called Station Id : Yes
Tunnel Server Attr : Yes DHCP Options : Yes
NAS Port : Yes
NAS Port Bits Spec : *3s*1m*4p*12o*12i
-------------------------------------------------------------------------------
Radius Servers
-------------------------------------------------------------------------------
Router : management + Base Source Address : N/A
Access Algorithm : Direct Retry : 3
Timeout (s) : 5 Hold down time (s) : 30
-------------------------------------------------------------------------------
Index IP Address Port Pend-Req-Limit Out/Overload time (s) Oper State
-------------------------------------------------------------------------------
No Radius Servers configured.
-------------------------------------------------------------------------------
Accept Radius Attributes
-------------------------------------------------------------------------------
No Matching Entries
-------------------------------------------------------------------------------
Radius Script Policies
-------------------------------------------------------------------------------
Access-Request : "N/A"
Access-Accept : "N/A"
Change-of-Authorization : "N/A"
===============================================================================
# show subscriber-mgmt authentication "auth-policy-2" association
===============================================================================
Authentication Policy auth-policy-2
===============================================================================
-------------------------------------------------------------------------------
SAP Associations
-------------------------------------------------------------------------------
No associations found.
-------------------------------------------------------------------------------
Interface Associations
-------------------------------------------------------------------------------
Service-Id : 3000 (VPRN)
- If Name : group-int-ws-1-1
-------------------------------------------------------------------------------
Local-User-Db PPPoE Host Associations
-------------------------------------------------------------------------------
Local-User-Db : ludb-1
- Host : host-1
-------------------------------------------------------------------------------
Local-User-Db DHCP Host Associations
-------------------------------------------------------------------------------
Local-User-Db : ludb-1
- Host : default
-------------------------------------------------------------------------------
Application Assurance Associations
-------------------------------------------------------------------------------
No associations found.
===============================================================================
No associated L2TP groups found.
No associated L2TP tunnels found.
# show subscriber-mgmt authentication statistics
===============================================================================
Authentication Policy Statistics
===============================================================================
Policy Name Subscr. Pkts Subscr. Pkts Subscr. Pkts
Authenticated Rejected Rejected
Send Failed
-------------------------------------------------------------------------------
auth-policy-1 0 0 0
auth-policy-2 0 0 0
-------------------------------------------------------------------------------
Number of Authentication Policies : 2
===============================================================================
# show subscriber-mgmt authentication "auth-policy-1" statistics
===============================================================================
Authentication Policy Statistics
===============================================================================
-------------------------------------------------------------------------------
Policy name : auth-policy-1
subscriber packets authenticated : 0
subscriber packets rejected : 0
subscriber packets rejected send failed : 0
-------------------------------------------------------------------------------
radius server requests requests requests requests requests requests
idx IP-address accepted rejected no reply md5 failed pending send failed
-------------------------------------------------------------------------------
1 172.16.1.1 0 0 0 0 0 0
-------------------------------------------------------------------------------
===============================================================================
# show subscriber-mgmt authentication coa-statistics
===============================================================================
Radius Notify Statistics Change-Of-Authorization Disconnect-Messages
===============================================================================
Requests Received 7 10
Requests Accepted 5 6
Requests Rejected 2 4
Requests Dropped 0 0
No Auth Policy found 0 0
Invalid message 0 0
Out of resources 0 0
Authentication failure 0 0
===============================================================================
B:Dut-A>show>subscr-mgmt# explicit-subscriber-map
===============================================================================
Explicit Subscriber Map
===============================================================================
Key Sub profile
SLA profile
-------------------------------------------------------------------------------
sub_ident_A_1 sub_prof80
sla_prof80
-------------------------------------------------------------------------------
Number of Explicit Subscriber Mappings : 1
===============================================================================
B:Dut-A>show>subscr-mgmt#
*A:cses-E11# show subscriber-mgmt host-lockout-policy
===============================================================================
Host Lockout Policies
===============================================================================
Lockout Policy Last Mgmt Change
Lockout Time Min Lockout Time Max
Description
Lockout Reset Time Max Lockout Hosts
-------------------------------------------------------------------------------
test 04/20/2012 19:51:02
10 3600
test
60 100
===============================================================================
*A:cses-E11#
*A:cses-E11# show subscriber-mgmt host-lockout-policy "test"
===============================================================================
Host Lockout Policy "test"
===============================================================================
Description : test
Last Mgmt Change : 04/20/2012 19:51:02
Lockout time min : 10
Lockout time max : 3600
Lockout reset time : 60
Max lockout hosts : 100
===============================================================================
*A:cses-E11#
*B:Dut-C# show subscriber-mgmt igmp-policy
===============================================================================
IGMP Policies
===============================================================================
IGMP Policy
Import Policy Admin Version
Description
Num Subscribers Host Max Groups
Fast Leave
-------------------------------------------------------------------------------
pol1
3
2 0
fast-leave
pol2
3
0 0
fast-leave
===============================================================================
*B:Dut-C#
*B:Dut-C# show subscriber-mgmt igmp-policy "pol1"
===============================================================================
IGMP Policy pol1
===============================================================================
Import Policy :
Admin Version : 3
Num Subscribers : 2
Host Max Group : 0
Fast Leave : yes
===============================================================================
*B:Dut-C#
*B:Dut-C# show subscriber-mgmt igmp-policy "pol1" association
===============================================================================
IGMP Policy pol1 Associations
===============================================================================
sub_1
sub_2
-------------------------------------------------------------------------------
No. of subscriber(s): 2
===============================================================================
*B:Dut-C#
*A:ALA-48>show>subscr-mgmt# local-user-db
===============================================================================
Local User Databases
===============================================================================
Name Admin Host Description
State Count
-------------------------------------------------------------------------------
database01 Down 1
database02 Provider001/Class0002 Down 0 This is a long testdescription wi*
test Down 2
-------------------------------------------------------------------------------
Number of Local User Databases : 3 Number of Hosts : 3
===============================================================================
* indicates that the corresponding row element may have been truncated.
*A:ALA-48>show>subscr-mgmt#
*A:ALA-48>show>subscr-mgmt# local-user-db database01
===============================================================================
Local User Database "database01"
===============================================================================
Admin State : Down
Last Mgmt Change : 11/08/2007 12:27:36
Host Count : 1
DHCP Match Types : circ-id
DHCP CircId Mask Pfx : test
DHCP CircId Mask Sfx : N/A
PPPoE Match Types : N/A
PPPoE CircId Mask Pfx: N/A
PPPoE CircId Mask Sfx: N/A
===============================================================================
*A:ALA-48>show>subscr-mgmt#
*A:ALA-48>show>subscr-mgmt# local-user-db database01 dhcp-all-hosts
===============================================================================
Local User Database "database01" DHCP hosts
===============================================================================
Name Admin Matched objects
State
-------------------------------------------------------------------------------
host001 Down -
-------------------------------------------------------------------------------
Number of DHCP Hosts : 1
===============================================================================
*A:ALA-48>show>subscr-mgmt#
*A:ALA-48>show>subscr-mgmt# local-user-db "database01" dhcp-host host001
===============================================================================
DHCP Host "host001"
===============================================================================
Admin State : Down
Last Mgmt Change : 11/08/2007 12:13:42
Host Indentification
Circuit Id : N/A
Mac Address : N/A
Remote Id : N/A
Sap Id : N/A
Service Id : N/A
String : N/A
Option 60 : N/A
System Id : N/A
Matched Objects : N/A
Address : N/A
Identification Strings
Subscriber Id : N/A
SLA Profile String : N/A
Sub Profile String : N/A
App Profile String : N/A
ANCP String : N/A
Inter Destination Id: N/A
===============================================================================
*A:ALA-48>show>subscr-mgmt#
*A:ALA-48>show>subscr-mgmt# local-user-db "database01" dhcp-unmatched-hosts
==============================================================================
Local User Database "database01" DHCP unmatched hosts
==============================================================================
Name Reason Duplicate Host
------------------------------------------------------------------------------
host002 No match N/A
host003 Duplicate host001
host004 No match N/A
host005 Duplicate host001
------------------------------------------------------------------------------
Number of DHCP Unmatched Hosts : 4
==============================================================================
*A:ALA-48>show>subscr-mgmt#
*A:ALA-48>show>subscr-mgmt# local-user-db "database01" association
===============================================================================
DHCP Servers where database01 is used
===============================================================================
Server-Name Router-Name
-------------------------------------------------------------------------------
dhcpS1 vprn1000
-------------------------------------------------------------------------------
No. of Server(s): 1
===============================================================================
Interfaces where database01 is used for authentication
===============================================================================
Interface-Name Service-Id Type
-------------------------------------------------------------------------------
No. of Interface(s): 0
===============================================================================
*A:ALA-48>show>subscr-mgmt#
*A:ALA-48>show>subscr-mgmt# local-user-db "database01" association dhcp
===============================================================================
DHCP Servers where database01 is used
===============================================================================
Server-Name Router-Name
-------------------------------------------------------------------------------
dhcpS1 vprn1000
-------------------------------------------------------------------------------
No. of Server(s): 1
===============================================================================
*A:ALA-48>show>subscr-mgmt#
*A:ALA-48>show>subscr-mgmt# msap-policy
===============================================================================
Managed SAP Policies
===============================================================================
Name Num Description
MSAPs
-------------------------------------------------------------------------------
test 0 (Not Specified)
test 1 0 (Not Specified)
-------------------------------------------------------------------------------
Number of MSAP Policies : 2
Number of MSAPs : 0
===============================================================================
*A:ALA-48>show>subscr-mgmt#
A:Dut-A# show subscriber-mgmt sla-profile
===============================================================================
SLA Profiles
===============================================================================
Name Description
-------------------------------------------------------------------------------
sla_default
sla_prof100_VOIP
sla_prof110_VOIP
sla_prof120_VOIP
sla_prof130_VOIP
sla_prof140_VOIP
sla_prof230_VOIP
sla_prof80
sla_prof80_VOIP
sla_prof81_VOIP
sla_prof90_VOIP
sla_profPC1
sla_profPC2
sla_profPC3
-------------------------------------------------------------------------------
Number of SLA Profiles : 14
===============================================================================
A:Dut-A#
A:Dut-A# show subscriber-mgmt sla-profile sla_prof100_VOIP
===============================================================================
SLA Profile sla_prof100_VOIP
===============================================================================
Host Limit : 3 (Remove Oldest)
Ingress Qos-Policy : 100 Egress Qos-Policy : 100
Ingress Queuing Type : Service-queuing
Ingress Filter-Id : N/A Egress Filter-Id : N/A
Last Mgmt Change : 07/10/2006 12:55:33
-------------------------------------------------------------------------------
Ingress Queue Overrides
-------------------------------------------------------------------------------
Queue Rate CIR HiPrio CBS MBS
-------------------------------------------------------------------------------
2 4000 - - - -
3 2500 - - - -
-------------------------------------------------------------------------------
Egress Queue Overrides
-------------------------------------------------------------------------------
Queue Rate CIR HiPrio CBS MBS
-------------------------------------------------------------------------------
2 4000 - - - -
3 2500 - - - -
===============================================================================
A:Dut-A#
A:Dut-A# show subscriber-mgmt sla-profile sla_prof100_VOIP association
===============================================================================
SLA Profile sla_prof100_VOIP
-------------------------------------------------------------------------------
SAP Default-Profile Associations
-------------------------------------------------------------------------------
No associations found.
-------------------------------------------------------------------------------
SAP Static Host Associations
-------------------------------------------------------------------------------
No associations found.
-------------------------------------------------------------------------------
SAP Non-Sub-Traffic-Profile Associations
-------------------------------------------------------------------------------
No associations found.
-------------------------------------------------------------------------------
Sub-Ident-Policy Profile Map Associations
-------------------------------------------------------------------------------
Policy-name : sub_ident_all
- Key : sla_prof100_VOIP
-------------------------------------------------------------------------------
Sub-Profile Map Associations
-------------------------------------------------------------------------------
No associations found.
-------------------------------------------------------------------------------
Explicit Subscriber Map Associations
-------------------------------------------------------------------------------
No associations found.
===============================================================================
A:Dut-A#
statistics iom (slot | all
) [host
|session
|subscriber
|summary
] [non-zero-value-only
]
statistics mda (mda | all
) [host
|session
|subscriber
|summary
] [non-zero-value-only
]
statistics port (port-id | all
) [host
|session
|subscriber
|summary
] [non-zero-value-only
]
statistics pw-port (pw-port | all
) [host
|session
|subscriber
|summary
] [non-zero-value-only
]
Note that the peak values can be reset via the clear subscriber-mgmt peakvalue-stats command.
show subscriber-mgmt statistics port 1/1/1
===============================================================================
Subscriber Management Statistics for Port 1/1/1
===============================================================================
Type Current Peak Peak Timestamp
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Host Statistics
-------------------------------------------------------------------------------
IPv4 PPP Hosts - IPCP 0 0
PPP Hosts - L2TP 0 0
IPOE Hosts - DHCP 0 0
IPOE Hosts - ARP 0 0
IPOE Hosts - Static 0 0
Non-Sub-Traffic Hosts 0 0
-------------------------------------------------------------------------------
IPv6 PPP Hosts - SLAAC 0 0
PPP Hosts - DHCP6 (PD) 0 0
PPP Hosts - DHCP6 (NA) 0 0
IPOE Hosts - SLAAC 0 0
IPOE Hosts - DHCP6 (PD) 0 0
IPOE Hosts - DHCP6 (NA) 0 0
-------------------------------------------------------------------------------
Total PPP Hosts 0 0
IPOE Hosts 0 0
IPv4 Hosts 0 0
IPv6 Hosts 0 0
IPv4 + IPv6 Hosts 0 0
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Session Statistics
-------------------------------------------------------------------------------
Local PPP Sessions - PPPoE 0 0
PPP Sessions - PPPoEoA 0 0
PPP Sessions - PPPoA 0 0
PPP Sessions - L2TP (LNS) 0 0
-------------------------------------------------------------------------------
LAC PPP Sessions - PPPoE 0 0
PPP Sessions - PPPoEoA 0 0
PPP Sessions - PPPoA 0 0
PPP Sessions - L2TP (LTS) 0 0
-------------------------------------------------------------------------------
Total PPP Sessions - established 0 0
PPP Sessions - in setup 0 0
PPP Sessions - local 0 0
PPP Sessions - LAC 0 0
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Subscriber Statistics
-------------------------------------------------------------------------------
Total Subscribers 0 0
-------------------------------------------------------------------------------
===============================================================================
Peak values last reset at : n/a Default: N/A
script {primary
| secondary
| tertiary
}
B:Dut-A>show>subscr-mgmt# sub-ident-policy
===============================================================================
Subscriber Identification Policies
===============================================================================
Name Description
-------------------------------------------------------------------------------
sub_ident_all
sub_ident_pc
-------------------------------------------------------------------------------
Number of Subscriber Identification Policies : 2
===============================================================================
B:Dut-A>show>subscr-mgmt#
B:Dut-A>show>subscr-mgmt# sub-ident-policy sub_ident_all
===============================================================================
Subscriber Identification Policy sub_ident_all
===============================================================================
Sub Profile Map
-------------------------------------------------------------------------------
Key Sub profile
-------------------------------------------------------------------------------
sub_prof100 sub_prof100
sub_prof110 sub_prof110
sub_prof120 sub_prof120
sub_prof130 sub_prof130
sub_prof140 sub_prof140
sub_prof230 sub_prof230
sub_prof80 sub_prof80
sub_prof81 sub_prof81
sub_prof90 sub_prof90
-------------------------------------------------------------------------------
SLA Profile Map
-------------------------------------------------------------------------------
Key SLA profile
-------------------------------------------------------------------------------
sla_prof100_VOIP sla_prof100_VOIP
sla_prof110_VOIP sla_prof110_VOIP
sla_prof120_VOIP sla_prof120_VOIP
sla_prof130_VOIP sla_prof130_VOIP
sla_prof140_VOIP sla_prof140_VOIP
sla_prof230_VOIP sla_prof230_VOIP
sla_prof80_VOIP sla_prof80_VOIP
sla_prof81_VOIP sla_prof81_VOIP
sla_prof90_VOIP sla_prof90_VOIP
-------------------------------------------------------------------------------
Python Scripts
-------------------------------------------------------------------------------
# Admin Oper Script
State State Name
-------------------------------------------------------------------------------
Primary Down Down pyTom.py
Secondary Up Up pyTomDebug.py
Tertiary Up Up hardcoded.py
===============================================================================
B:Dut-A>show>subscr-mgmt#
B:Dut-A>show>subscr-mgmt# sub-ident-policy sub_ident_all association
===============================================================================
Subscriber Identification Policy sub_ident_all
===============================================================================
SAP Associations
-------------------------------------------------------------------------------
Service-Id : 80 (VPLS)
- SAP : 1/2/1:80
Service-Id : 90 (VPLS)
- SAP : 1/2/1:90
Service-Id : 100 (VPLS)
- SAP : 1/2/1:100
- SAP : 1/2/1:101
- SAP : 1/2/1:102
Service-Id : 110 (VPLS)
- SAP : 1/2/1:110
- SAP : 1/2/1:111
- SAP : 1/2/1:112
Service-Id : 120 (VPLS)
- SAP : 1/2/1:120
- SAP : 1/2/1:121
- SAP : 1/2/1:122
Service-Id : 130 (VPLS)
- SAP : 1/2/1:130
Service-Id : 140 (VPLS)
- SAP : 1/2/1:140
===============================================================================
B:Dut-A>show>subscr-mgmt#
B:Dut-A>show>subscr-mgmt# sub-ident-policy sub_ident_all script primary
===============================================================================
Subscriber Identification Policy sub_ident_all
===============================================================================
Primary Script
-------------------------------------------------------------------------------
URL : ftp://xxx:yyy@a.b.c.d/pyTom.py
Admin State : Down Oper State : Down
-------------------------------------------------------------------------------
Source (dumped from memory)
-------------------------------------------------------------------------------
Script is not active.
-------------------------------------------------------------------------------
===============================================================================
B:Dut-A>show>subscr-mgmt#
B:Dut-A>show>subscr-mgmt# sub-ident-policy sub_ident_all script secondary
===============================================================================
Subscriber Identification Policy sub_ident_all
===============================================================================
Secondary Script
-------------------------------------------------------------------------------
URL : ftp://xxx:yyy@a.b.c.d/pyTomDebug.py
Admin State : Up Oper State : Up
-------------------------------------------------------------------------------
Source (dumped from memory)
-------------------------------------------------------------------------------
1 import alc
2 yiaddr = alc.dhcp.yiaddr
3 # Subscriber ID equals full client IP address.
4 # Note: IP address 10.10.10.10 yields 'sub-168430090'
5 # and not 'sub-10.10.10.10'
6 alc.dhcp.sub_ident = 'sub-' + str(yiaddr)
7 # DHCP server is configured such that the third byte (field) of the IP
8 # address indicates the session Profile ID.
9 alc.dhcp.sla_profile = 'sp-' + str((yiaddr & 0x0000FF00) >> 8)
===============================================================================
B:Dut-A>show>subscr-mgmt#
B:Dut-A>show>subscr-mgmt# sub-ident-policy sub_ident_all script tertiary
===============================================================================
Subscriber Identification Policy sub_ident_all
===============================================================================
Tertiary Script
-------------------------------------------------------------------------------
URL : ftp://xxx:yyy@a.b.c.d/hardcoded.py
Admin State : Up Oper State : Up
-------------------------------------------------------------------------------
Source (dumped from memory)
-------------------------------------------------------------------------------
1 from alc import dhcp
2
3 dhcp.sub_ident = 'sub_ident_A_1'
4 dhcp.sub_profile_string = 'sub_prof_B_2'
5 dhcp.sla_profile_string = 'sla_prof_C_3'
6
===============================================================================
B:Dut-A>show>subscr-mgmt#
A:Dut-A# show subscriber-mgmt sub-profile
===============================================================================
Subscriber Profiles
===============================================================================
Name Description
-------------------------------------------------------------------------------
sub_default
sub_prof100
sub_prof110
sub_prof120
sub_prof130
sub_prof140
sub_prof230
sub_prof80
sub_prof81
sub_prof90
sub_profPC1
sub_profPC2
sub_profPC3
-------------------------------------------------------------------------------
Number of Subscriber Profiles : 13
===============================================================================
A:Dut-A#
A:Dut-A# show subscriber-mgmt sub-profile sub_prof100
===============================================================================
Subscriber Profile sub_prof100
===============================================================================
I. Sched. Policy : service100
E. Sched. Policy : service100
Acct. Policy : 1 Collect Stats : Enabled
Last Mgmt Change : 07/10/2006 12:55:33
-------------------------------------------------------------------------------
Ingress Scheduler Overrides
-------------------------------------------------------------------------------
Scheduler Rate CIR
-------------------------------------------------------------------------------
serv100 8000 sum
-------------------------------------------------------------------------------
Egress Scheduler Overrides
-------------------------------------------------------------------------------
Scheduler Rate CIR
-------------------------------------------------------------------------------
serv100 8000 sum
-------------------------------------------------------------------------------
SLA Profile Map
-------------------------------------------------------------------------------
Key SLA Profile
-------------------------------------------------------------------------------
No mappings configured.
===============================================================================
A:Dut-A#
A:Dut-A# show subscriber-mgmt sub-profile sub_prof100 association
===============================================================================
Subscriber Profile sub_prof100
-------------------------------------------------------------------------------
SAP Default-Profile Associations
-------------------------------------------------------------------------------
No associations found.
-------------------------------------------------------------------------------
SAP Static Host Associations
-------------------------------------------------------------------------------
No associations found.
-------------------------------------------------------------------------------
SAP Non-Sub-Traffic-Profile Associations
-------------------------------------------------------------------------------
No associations found.
-------------------------------------------------------------------------------
Sub-Ident-Policy Profile Map Associations
-------------------------------------------------------------------------------
Policy-name : sub_ident_all
- Key : sub_prof100
-------------------------------------------------------------------------------
Explicit Subscriber Map Associations
-------------------------------------------------------------------------------
No associations found.
===============================================================================
A:Dut-A#
port-scheduler-policy port-scheduler-policy-name scheduler-policy
scheduler-policy-name sap-egress
policy-id
A:NS072860910>config>qos>port-sched-plcy# info
----------------------------------------------
max-rate 10000
group "group1" create
rate 3000 cir 1000
exit
group "group2" create
rate 2000 cir 500
exit
level 7 rate 7000 cir 700 group "group1" weight 3
level 6 rate 6000 cir 600 group "group1" weight 2
level 5 rate 5000 cir 500 group "group1" weight 1
level 2 rate 2000 cir 200 group "group2" weight 2
level 1 rate 1000 cir 100 group "group2" weight 1
----------------------------------------------
A:NS072860910# show qos scheduler-hierarchy port 5/1/2 vport "fred"
========================================================================
Scheduler Hierarchy - Port 5/1/2, Vport "fred"
========================================================================
Port-scheduler-policy psp1
Port Bandwidth : 1000000 Max Rate : 10000
Consumed : 0 Offered : 0
[Within CIR Level 8]
Rate : max
Consumed : 0 Offered : 0
(Q) : 1->5/1/2:1->1
(Q) : 1->5/1/2:2->1
[Within CIR Group "group1"]
Rate : 1000
Consumed : 0 Offered : 0
[Within CIR Level 7]
Weight : 3
Rate : 700
Consumed : 0 Offered : 0
(Q) : 1->5/1/2:1->2
(Q) : 1->5/1/2:2->2
[Within CIR Level 6]
Weight : 2
Rate : 600
Consumed : 0 Offered : 0
(Q) : 1->5/1/2:1->3
(Q) : 1->5/1/2:2->3
[Within CIR Level 5]
Weight : 1
Rate : 500
Consumed : 0 Offered : 0
(Q) : 1->5/1/2:1->4
(Q) : 1->5/1/2:2->4
[Within CIR Level 4]
Rate : max
Consumed : 0 Offered : 0
[Within CIR Level 3]
Rate : max
Consumed : 0 Offered : 0
(Q) : 1->5/1/2:1->5
(Q) : 1->5/1/2:2->5
[Within CIR Group "group2"]
Rate : 500
Consumed : 0 Offered : 0
[Within CIR Level 2]
Weight : 2
Rate : 200
Consumed : 0 Offered : 0
(Q) : 1->5/1/2:1->6
(Q) : 1->5/1/2:2->6
[Within CIR Level 1]
Weight : 1
Rate : 200
Consumed : 0 Offered : 0
(Q) : 1->5/1/2:1->7
(Q) : 1->5/1/2:2->7
[Within CIR Level 0]
Rate : 0
Consumed : 0 Offered : 0
(Q) : 1->5/1/2:1->8
(Q) : 1->5/1/2:2->8
[Above CIR Level 8]
Rate : max
Consumed : 0 Offered : 0
[Above CIR Group "group1"]
Rate : 3000
Consumed : 0 Offered : 0
[Above CIR Level 7]
Weight : 3
Rate : 7000
Consumed : 0 Offered : 0
[Above CIR Level 6]
Weight : 2
Rate : 6000
Consumed : 0 Offered : 0
[Above CIR Level 5]
Weight : 1
Rate : 5000
Consumed : 0 Offered : 0
[Above CIR Level 4]
Rate : max
Consumed : 0 Offered : 0
[Above CIR Level 3]
Rate : max
Consumed : 0 Offered : 0
[Above CIR Group "group2"]
Rate : 2000
Consumed : 0 Offered : 0
[Above CIR Level 2]
Weight : 2
Rate : 2000
Consumed : 0 Offered : 0
[Above CIR Level 1]
Weight : 1
Rate : 1000
Consumed : 0 Offered : 0
(Q) : 1->5/1/2:1->1
(Q) : 1->5/1/2:1->2
(Q) : 1->5/1/2:1->3
(Q) : 1->5/1/2:1->4
(Q) : 1->5/1/2:1->5
(Q) : 1->5/1/2:1->6
(Q) : 1->5/1/2:1->7
(Q) : 1->5/1/2:1->8
(Q) : 1->5/1/2:2->1
(Q) : 1->5/1/2:2->2
(Q) : 1->5/1/2:2->3
(Q) : 1->5/1/2:2->4
(Q) : 1->5/1/2:2->5
(Q) : 1->5/1/2:2->6
(Q) : 1->5/1/2:2->7
(Q) : 1->5/1/2:2->8
========================================================================
A:NS072860910#
*A:Bennet-Dut-A>config>qos>port-sched-plcy# show qos port-scheduler-policy "psp"
========================================================================
QoS Port Scheduler Policy
========================================================================
Policy-Name : psp
Description : (Not Specified)
Max Rate : max Last changed : 04/15/2010 00:37:02
Group : 1
Group PIR : 80000 Group CIR : max
Group : 2
Group PIR : 80000 Group CIR : max
Group : 3
Group PIR : 80000 Group CIR : max
Group : 4
Group PIR : 80000 Group CIR : max
Lvl1 PIR : max Lvl1 CIR : max
Lvl1 Group : 1 Lvl1 Grp Weight : 10
Lvl2 PIR : max Lvl2 CIR : max
Lvl2 Group : 1 Lvl2 Grp Weight : 20
Lvl3 PIR : max Lvl3 CIR : max
Lvl3 Group : 2 Lvl3 Grp Weight : 30
Lvl4 PIR : max Lvl4 CIR : max
Lvl4 Group : 2 Lvl4 Grp Weight : 40
Lvl5 PIR : max Lvl5 CIR : max
Lvl5 Group : 3 Lvl5 Grp Weight : 50
Lvl6 PIR : max Lvl6 CIR : max
Lvl6 Group : 3 Lvl6 Grp Weight : 60
Lvl7 PIR : max Lvl7 CIR : max
Lvl7 Group : 4 Lvl7 Grp Weight : 70
Lvl8 PIR : max Lvl8 CIR : max
Lvl8 Group : 4 Lvl8 Grp Weight : 80
Orphan Lvl : default Orphan Weight : default
Orphan CIR-Lvl : default Orphan CIR-Weight : default
========================================================================
*A:Bennet-Dut-A>config>qos>port-sched-plcy#
*A:Bennet-Dut-A# show qos port-scheduler-policy "psp" association
========================================================================
QoS Port Scheduler Policy
========================================================================
Policy-Name : psp
Description : (Not Specified)
------------------------------------------------------------------------
Associations
------------------------------------------------------------------------
- Port : 1/1/2 VPort : vp1
========================================================================
*A:Bennet-Dut-A#
*A:Bennet-Dut-A# show qos port-scheduler-policy "psp" sap-egress 1000
========================================================================
Compatibility : Port-scheduler Policy psp & Sap Egress Queue 1000
========================================================================
Orphan Queues :
None Found
Hierarchy :
Root
|
|---(Q) : 1
|
|---(Q) : 2
|
|---(Q) : 3
|
|---(Q) : 4
|
|---(Q) : 5
|
|---(Q) : 6
|
|---(Q) : 7
|
|---(Q) : 8
========================================================================
*A:Bennet-Dut-A#
A:Dut-A# show qos sap-egress
===============================================================================
Sap Egress Policies
===============================================================================
Policy-Id Scope Description
-------------------------------------------------------------------------------
1 Template Default SAP egress QoS policy.
30 Template 1 video channel, 1 BE
31 Template 1 video EF, 2xvideo AF, 1 BE
80 Template Limit outgoing 80
100 Template User100
110 Template User110
120 Template User120
130 Template User130
140 Template User140
901 Template User90_1
902 Template User90_2
903 Template User90_3
904 Template User90_4
905 Template User90_5
1000 Template Service all
===============================================================================
A:Dut-A#
A:Dut-A# show qos sap-egress 31 detail
===============================================================================
QoS Sap Egress
===============================================================================
Sap Scheduler Policy (31)
-------------------------------------------------------------------------------
Policy-id : 31 Scope : Template
Description : 1 video EF, 2xvideo AF, 1 BE
-------------------------------------------------------------------------------
Queue CIR Admin PIR Admin CBS HiPrio PIR Lvl/Wt Parent
CIR Rule PIR Rule MBS CIR Lvl/Wt
-------------------------------------------------------------------------------
1 0 max def def 1/1 limit_8000
closest closest def 0/1
2 0 max def def 2/1 limit_8000
closest closest def 0/1
3 0 max def def 3/1 limit_8000
closest closest def 0/1
-------------------------------------------------------------------------------
FC Name Queue-id Explicit/Default
-------------------------------------------------------------------------------
be 1 Explicit (0)
af 2 Explicit (0)
ef 3 Explicit (0)
-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
Service-Id : 23 (VPLS) Customer-Id : 1
- SAP : 1/2/2:4000
Service-Id : 30 (VPLS) Customer-Id : 2
- SAP : lag-1
- SAP : lag-2:5
Service-Id : 31 (VPLS) Customer-Id : 2
- SAP : 1/2/1:31
SLA Profiles :
- sla_profPC1 override
-------------------------------------------------------------------------------
Mirror SAPs
-------------------------------------------------------------------------------
No Mirror SAPs Found.
===============================================================================
A:Dut-A#
sap-ingress [policy-id] [association
| match-criteria
| detail
]
A:Dut-A# show qos sap-ingress
===============================================================================
Sap Ingress Policies
===============================================================================
Policy-Id Scope Description
-------------------------------------------------------------------------------
1 Template Default SAP ingress QoS policy.
80 Template Dot1p mappings/service for service 80
90 Template Dot1p mappings/service for service 90
100 Template Dot1p mappings/service for service 100
110 Template Dot1p mappings/service for service 110
120 Template Dot1p mappings/service for service 120
130 Template Dot1p mappings/service for service 130
140 Template Dot1p mappings/service for service 140
901 Template User90_1
902 Template User90_2
903 Template User90_3
904 Template User90_4
905 Template User90_5
1000 Template Dot1p mappings/service for all services
===============================================================================
A:Dut-A#
A:Dut-A# show qos sap-ingress 80 detail
===============================================================================
QoS Sap Ingress
===============================================================================
Sap Ingress Policy (80)
-------------------------------------------------------------------------------
Policy-id : 80 Scope : Template
Default FC : be Priority : Low
Criteria-type : IP
Description : Dot1p mappings/service for service 80
-------------------------------------------------------------------------------
Queue Mode CIR Admin PIR Admin CBS HiPrio PIR Lvl/Wt Parent
CIR Rule PIR Rule MBS CIR Lvl/Wt
-------------------------------------------------------------------------------
1 Prio 0 7000 def def 1/1 serv80
closest closest def 0/1
2 Prio 0 3500 def def 2/1 serv80
closest closest def 0/1
3 Prio 0 2000 def def 3/1 serv80
closest closest def 0/1
11 Prio 0 max def def 1/1 None
closest closest def 0/1
-------------------------------------------------------------------------------
FC UCastQ MCastQ BCastQ UnknownQ
-------------------------------------------------------------------------------
be 1 def def def
af 2 def def def
ef 3 def def def
-------------------------------------------------------------------------------
SubFC Profile In-Remark Out-Remark
-------------------------------------------------------------------------------
af None None None
be None None None
ef None None None
-------------------------------------------------------------------------------
Dot1p FC Priority
-------------------------------------------------------------------------------
0 be Default
2 af Default
5 ef Default
-------------------------------------------------------------------------------
DSCP FC Priority
-------------------------------------------------------------------------------
No DSCP-Map Entries Found.
-------------------------------------------------------------------------------
Prec Value FC Priority
-------------------------------------------------------------------------------
No Prec-Map Entries Found.
-------------------------------------------------------------------------------
Match Criteria
-------------------------------------------------------------------------------
IP Match Criteria
-------------------------------------------------------------------------------
Entry : 1
Source IP : Undefined Source Port : None
Dest. IP : Undefined Dest. Port : None
Protocol : None DSCP : None
Fragment : Off
FC : Default Priority : Default
-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
Service-Id : 80 (VPLS) Customer-Id : 80
- SAP : 1/2/1:80
SLA Profiles :
- sla_prof80 override
- sla_prof80_VOIP override
- sla_prof81_VOIP override
===============================================================================
A:Dut-A#
customer customer-id site
customer-site-name [scheduler
scheduler-name] [ingress
|egress
] [detail
]
sap sap-id [scheduler
scheduler-name] [ingress
|egress
] [detail
]
subscriber sub-ident-string [scheduler
scheduler-name] [ingress
|egress
][detail
]
B:Dut-A# show qos scheduler-hierarchy subscriber alcatel_100
===============================================================================
Scheduler Hierarchy - Subscriber alcatel_100
===============================================================================
Root (Ing)
| slot(1)
|--(S) : root
| |
| |--(S) : serv_all
| | |
| | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:101->11 MCast
| | |
| | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->11 MCast
| | |
| | |--(S) : AccessIngress:Sub=6:1 100->1/2/1:100->3
| | | |
| | | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->3 1/1
| | | |
| | | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->3 3/2
| | | |
| | | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->3 1/2
| | | |
| | |
| | |--(S) : AccessIngress:Sub=6:1 100->1/2/1:100->2
| | | |
| | | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->2 1/1
| | | |
| | | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->2 3/2
| | | |
| | | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->2 1/2
| | | |
| | |
| | |--(S) : AccessIngress:Sub=6:1 100->1/2/1:100->1
| | | |
| | | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->1 1/1
| | | |
| | | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->1 3/2
| | | |
| | | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->1 1/2
| | | |
| | |
| | |--(S) : AccessIngress:Sub=6:1 100->1/2/1:101->1
| | | |
| | | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:101->1 1/1
| | | |
| | | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:101->1 3/2
| | | |
| | | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:101->1 1/2
| | | |
| | |
| | |--(S) : AccessIngress:Sub=6:1 100->1/2/1:101->2
| | | |
| | | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:101->2 1/1
| | | |
| | | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:101->2 3/2
| | | |
| | | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:101->2 1/2
| | | |
| | |
| | |--(S) : AccessIngress:Sub=6:1 100->1/2/1:101->3
| | | |
| | | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:101->3 1/1
| | | |
| | | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:101->3 3/2
| | | |
| | | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:101->3 1/2
| | | |
Root (Egr)
| slot(1)
|--(S) : root
| |
| |--(S) : serv_all
| | |
| | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:101->1
| | |
| | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:101->2
| | |
| | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:101->3
| | |
| | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->1
| | |
| | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->2
| | |
| | |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->3
| | |
===============================================================================
B:Dut-A#
B:Dut-A# show qos scheduler-hierarchy subscriber alcatel_100 scheduler serv_all
===============================================================================
Scheduler Hierarchy - Subscriber alcatel_100
===============================================================================
serv_all (Ing)
| slot(1)
|--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:101->11 MCast
|
|--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->11 MCast
|
|--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:102->11 MCast
|
|--(S) : AccessIngress:Sub=6:1 100->1/2/1:100->2
| |
| |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->2 1/1
| |
| |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->2 3/2
| |
| |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->2 1/2
| |
|
|--(S) : AccessIngress:Sub=6:1 100->1/2/1:100->1
| |
| |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->1 1/1
| |
| |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->1 3/2
| |
| |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->1 1/2
| |
|
|--(S) : AccessIngress:Sub=6:1 100->1/2/1:100->3
| |
| |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->3 1/1
| |
| |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->3 3/2
| |
| |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:100->3 1/2
| |
|
|--(S) : AccessIngress:Sub=6:1 100->1/2/1:102->1
| |
| |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:102->1 1/1
| |
| |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:102->1 3/2
| |
| |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:102->1 1/2
| |
|
|--(S) : AccessIngress:Sub=6:1 100->1/2/1:102->2
| |
| |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:102->2 1/1
| |
| |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:102->2 3/2
| |
| |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:102->2 1/2
| |
...
===============================================================================
B:Dut-A#
B:Dut-A# show qos scheduler-hierarchy subscriber alcatel_100 scheduler serv_all detail
===============================================================================
Scheduler Hierarchy - Subscriber alcatel_100
===============================================================================
Legend :
(U) - Unrestricted (P) - Provisioned
(A) - Administrative (O) - Operational
MIR - Measured Info Rate
-------------------------------------------------------------------------------
serv_all (Ing)
| slot(1)
|--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:101->11 MCast
| |
| | PIR Lvl:4 PIR Wt :1
| | CIR Lvl:0 CIR Wt :1
| |
| | MIR :0
| | PIR (P):0 PIR (U):7000
| | CIR (P):0 CIR (U):0
| |
| | PIR (A):1000000 PIR (O):7000
| | CIR (A):0 CIR (O):0
| | CBS :0 MBS :1280
| | Depth :0 Hi Prio:256
|
|--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:102->11 MCast
| |
| | PIR Lvl:4 PIR Wt :1
| | CIR Lvl:0 CIR Wt :1
| |
| | MIR :0
| | PIR (P):0 PIR (U):7000
| | CIR (P):0 CIR (U):0
| |
| | PIR (A):1000000 PIR (O):7000
| | CIR (A):0 CIR (O):0
| | CBS :0 MBS :1280
| | Depth :0 Hi Prio:256
|
|--(S) : AccessIngress:Sub=6:1 100->1/2/1:102->1
| |
| | PIR Lvl:1 PIR Wt :1
| | CIR Lvl:0 CIR Wt :1
| |
| | MIR :1687
| | PIR (P):1690 PIR (U):3510
| | CIR (P):0 CIR (U):0
| |
| | PIR (A):7000
| | CIR (A):0
| |
| |--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:102->1 1/1
| | |
| | | PIR Lvl:1 PIR Wt :1
| | | CIR Lvl:1 CIR Wt :1
| | |
| | | MIR :0
| | | PIR (P):0 PIR (U):1830
| | | CIR (P):0 CIR (U):0
| | |
| | | PIR (A):7000 PIR (O):1850
| | | CIR (A):0 CIR (O):0
| | | CBS :0 MBS :64
| | | Depth :0 Hi Prio:8
| |
...
|--(Q) : Sub=alcatel_100:sla_default 100->1/2/1:102->3
| |
| | PIR Lvl:3 PIR Wt :1
| | CIR Lvl:0 CIR Wt :1
| |
| | MIR :0
| | PIR (P):0 PIR (U):2000
| | CIR (P):0 CIR (U):0
| |
| | PIR (A):2000 PIR (O):2000
| | CIR (A):0 CIR (O):0
| | CBS :0 MBS :64
| | Depth :0 Hi Prio:8
===============================================================================
B:Dut-A#
scheduler-policy [scheduler-policy-name] [association
| sap-ingress
policy-id | sap-egress
policy-id]
B:Dut-A# show qos scheduler-policy
===============================================================================
Sap Scheduler Policies
===============================================================================
Policy-Id Description
-------------------------------------------------------------------------------
maximum_4000_1xEF_1xBE
maximum_8000_1xEF_2xAF_1xBE
multiservice-site
root
scheduler-7Mbps
service100
service110
service120
service130
service140
service80
service90
service_all
===============================================================================
B:Dut-A#
B:Dut-A# show qos scheduler-policy root association
===============================================================================
QoS Scheduler Policy
===============================================================================
Policy-Name : root
-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
No Association Found.
===============================================================================
B:Dut-A#
B:Dut-A# show qos scheduler-policy association
===============================================================================
QoS Scheduler Policy
===============================================================================
Policy-Name : maximum_4000_1xEF_1xBE
-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
No Association Found.
Policy-Name : maximum_8000_1xEF_2xAF_1xBE
-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
Service-Id : 23 (VPLS) Customer-Id : 1
- SAP : 1/3/2:4000 (Egr)
Service-Id : 30 (VPLS) Customer-Id : 2
- SAP : lag-1 (Egr)
- SAP : lag-2:5 (Egr)
Policy-Name : multiservice-site
-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
Service-Id : 90 (VPLS) Customer-Id : 90
- SAP : 1/1/12:95 (Ing) (Egr) MSS : site1
- SAP : 1/1/20:94 (Ing) (Egr) MSS : site1
- Customer : 2 MSS : site1 (Ing) (Egr)
- Customer : 90 MSS : site1 (Ing) (Egr)
Policy-Name : root
-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
No Association Found.
Policy-Name : scheduler-7Mbps
-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
No Association Found.
Policy-Name : service100
-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
Service-Id : 100 (VPLS) Customer-Id : 100
- SAP : 1/2/1:100 (Ing) (Egr)
- SAP : 1/2/1:101 (Ing) (Egr)
- SAP : 1/2/1:102 (Ing) (Egr)
- Customer : 100 MSS : site100 (Ing) (Egr)
Sub Profiles :
- sub_prof100 (Ing) (Egr)
Policy-Name : service110
-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
Service-Id : 110 (VPLS) Customer-Id : 110
- SAP : 1/2/1:110 (Ing) (Egr)
- SAP : 1/2/1:111 (Ing) (Egr)
- SAP : 1/2/1:112 (Ing) (Egr)
Sub Profiles :
- sub_prof110 (Ing) (Egr)
Policy-Name : service120
-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
Service-Id : 120 (VPLS) Customer-Id : 120
- SAP : 1/2/1:120 (Ing) (Egr)
- SAP : 1/2/1:121 (Ing) (Egr)
- SAP : 1/2/1:122 (Ing) (Egr)
Sub Profiles :
- sub_prof120 (Ing) (Egr)
Policy-Name : service130
-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
Service-Id : 130 (VPLS) Customer-Id : 130
- SAP : 1/2/1:130 (Ing) (Egr)
Sub Profiles :
- sub_prof130 (Ing) (Egr)
Policy-Name : service140
-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
Service-Id : 140 (VPLS) Customer-Id : 140
- SAP : 1/2/1:140 (Ing) (Egr)
Sub Profiles :
- sub_prof140 (Ing) (Egr)
Policy-Name : service80
-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
Service-Id : 80 (VPLS) Customer-Id : 80
- SAP : 1/2/1:80 (Ing) (Egr)
- Customer : 80 MSS : site80 (Ing) (Egr)
Sub Profiles :
- sub_prof80 (Ing) (Egr)
- sub_prof81 (Ing) (Egr)
Policy-Name : service90
-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
Service-Id : 90 (VPLS) Customer-Id : 90
- SAP : 1/2/1:90 (Ing) (Egr)
Sub Profiles :
- sub_prof90 (Ing) (Egr)
Policy-Name : service_all
-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
Sub Profiles :
- sub_default (Ing) (Egr)
===============================================================================
B:Dut-A#
A:Dut-A# show qos scheduler-stats subscriber alcatel_100
===============================================================================
Scheduler Stats
===============================================================================
Scheduler Forwarded Packets Forwarded Octets
-------------------------------------------------------------------------------
Ingress Schedulers
root 112777 25218126
serv_all 112777 25218126
Egress Schedulers
root 113781 26008462
serv_all 113781 26008462
===============================================================================
A:Dut-A#
A:Dut-A# show qos scheduler-stats subscriber alcatel_100 scheduler root
===============================================================================
Scheduler Stats
===============================================================================
Scheduler Forwarded Packets Forwarded Octets
-------------------------------------------------------------------------------
Ingress Schedulers
root 0 0
Egress Schedulers
root 0 0
===============================================================================
A:Dut-A#
A:Dut-A# show qos shared-queue
===============================================================================
Shared Queue Policies
===============================================================================
Policy-Id Description
-------------------------------------------------------------------------------
default Default Shared Queue Policy
===============================================================================
A:Dut-A#
A:Dut-A# show qos shared-queue detail
===============================================================================
QoS Network Queue Policy
-------------------------------------------------------------------------------
Shared Queue Policy (default)
-------------------------------------------------------------------------------
Policy : default
Description : Default Shared Queue Policy
-------------------------------------------------------------------------------
Queue CIR PIR CBS MBS HiPrio Multipoint
-------------------------------------------------------------------------------
1 0 100 1 50 10 FALSE
2 25 100 3 50 10 FALSE
3 25 100 10 50 10 FALSE
4 25 100 3 25 10 FALSE
5 100 100 10 50 10 FALSE
6 100 100 10 50 10 FALSE
7 10 100 3 25 10 FALSE
8 10 100 3 25 10 FALSE
9 0 100 1 50 10 TRUE
10 25 100 3 50 10 TRUE
11 25 100 10 50 10 TRUE
12 25 100 3 25 10 TRUE
13 100 100 10 50 10 TRUE
14 100 100 10 50 10 TRUE
15 10 100 3 25 10 TRUE
16 10 100 3 25 10 TRUE
17 0 100 1 50 10 TRUE
18 25 100 3 50 10 TRUE
19 25 100 10 50 10 TRUE
20 25 100 3 25 10 TRUE
21 100 100 10 50 10 TRUE
22 100 100 10 50 10 TRUE
23 10 100 3 25 10 TRUE
24 10 100 3 25 10 TRUE
25 0 100 1 50 10 TRUE
26 25 100 3 50 10 TRUE
27 25 100 10 50 10 TRUE
28 25 100 3 25 10 TRUE
29 100 100 10 50 10 TRUE
30 100 100 10 50 10 TRUE
31 10 100 3 25 10 TRUE
32 10 100 3 25 10 TRUE
-------------------------------------------------------------------------------
FC UCastQ MCastQ BCastQ UnknownQ
-------------------------------------------------------------------------------
be 1 9 17 25
l2 2 10 18 26
af 3 11 19 27
l1 4 12 20 28
h2 5 13 21 29
ef 6 14 22 30
h1 7 15 23 31
nc 8 16 24 32
-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
Service : 10 SAP : 1/1/4:101 (shared Q)
Service : 10 SAP : 1/1/4:102 (shared Q)
Service : 10 SAP : 1/1/4:103 (shared Q)
Service : 10 SAP : 1/1/4:104 (shared Q)
Service : 10 SAP : 1/1/4:105 (shared Q)
Service : 10 SAP : 1/1/4:106 (shared Q)
Service : 10 SAP : 1/1/4:107 (shared Q)
Service : 10 SAP : 1/1/4:108 (shared Q)
Service : 10 SAP : 1/1/4:109 (shared Q)
Service : 10 SAP : 1/1/4:110 (shared Q)
Service : 10 SAP : 1/1/4:111 (shared Q)
Service : 10 SAP : 1/1/4:112 (shared Q)
Service : 10 SAP : 1/1/4:113 (shared Q)
Service : 10 SAP : 1/1/4:114 (shared Q)
Service : 10 SAP : 1/1/4:115 (shared Q)
Service : 10 SAP : 1/1/4:116 (shared Q)
Service : 10 SAP : 1/1/4:117 (shared Q)
Service : 10 SAP : 1/1/4:118 (shared Q)
Service : 10 SAP : 1/1/4:119 (shared Q)
Service : 10 SAP : 1/1/4:120 (shared Q)
Service : 10 SAP : 1/1/4:121 (shared Q)
Service : 10 SAP : 1/1/4:122 (shared Q)
Service : 10 SAP : 1/1/4:123 (shared Q)
Service : 10 SAP : 1/1/5:279 (shared Q)
===============================================================================
A:Dut-A#
A:active# show subscriber-mgmt ancp-policy
===============================================================================
ANCP Policies
===============================================================================
adsl-operator1
vdsl-operator1
-------------------------------------------------------------------------------
Number of ANCP policies : 2
===============================================================================
A:active#
A:active# show subscriber-mgmt ancp-policy adsl-operator1
===============================================================================
ANCP Policy "adsl-operator1"
===============================================================================
I. Rate Reduction : 0 kbps
I. Rate Adjustment : 100 percent
I. Rate Monitor : 0 kbps
I. Rate Monitor Alarm : no
I. Rate Modify : scheduler "root"
E. Rate Reduction : 10 kbps
E. Rate Adjustment : 100 percent
E. Rate Monitor : 0 kbps
E. Rate Monitor Alarm : no
E. Rate Modify : scheduler "root"
Port Down : N/A
Last Mgmt Change: 01/26/2007 17:10:51
================================================================================
A:active#
A:active# show subscriber-mgmt ancp-policy adsl-operator1 association
===============================================================================
ANCP Policy "adsl-operator1" associations ===============================================================================
SAP Static Map Associations
-------------------------------------------------------------------------------
- SAP : 1/1/3 Svc-id : 333 (VPLS)
String : "ANCP-String-1"
String : "ANCP-String-2"
------------------------------------------------------------------------------
MSS Static Map Associations
-------------------------------------------------------------------------------
- Cust-id : 1 MSS-name: mss1
String : "ANCP-String-3"
-------------------------------------------------------------------------------
Subscriber Associations
-------------------------------------------------------------------------------
No associations found.
Number of associations : 3
===============================================================================
A:active#
Specify the associated customer’s configured MSS name.
A:active# show subscriber-mgmt ancp-string
===============================================================================
ANCP-Strings
===============================================================================
ANCP-String Assoc State
-------------------------------------------------------------------------------
"ANCP-String-1" SAP Up
"ANCP-String-2" SAP Down
"ANCP-String-3" MSS Up
"ANCP-String-4" MSS Unknown
"ANCP-String-5" ANCP Up
"ANCP-String-6" MSS Unknown
-------------------------------------------------------------------------------
Number of ANCP-Strings : 6
===============================================================================
A:active#
*A:Dut-C# show subscriber-mgmt ancp-string hpolSub43
===============================================================================
ANCP-String "hpolSub43"
===============================================================================
Type : SUB - "hpolSub43"
State : Up Ancp Policy: ancpPol
I. Rate : 100 kbps E. Rate : 200 kbps
Adj I. Rate: N/A Adj E. Rate: 200 kbps
Act I. Rate: N/A Act E. Rate: 182 kbps
Service Id : 1 (VPRN)
Group : Alu
Neighbor : 100.100.100.1:49063
===============================================================================
*A:Dut-C#
A:active# show service id 333 sap 1/1/3 detail
===============================================================================
Service Access Points(SAP)
===============================================================================
Service Id : 333
SAP : 1/1/3 Encap : null
...
-------------------------------------------------------------------------------
ANCP Override
-------------------------------------------------------------------------------
Ing Sched Name: root
- PIR : 100 kbps
- String : "ANCP-String-1"
Egr Sched Name: root
- PIR : 100 kbps
- String : "ANCP-String-1"
-------------------------------------------------------------------------------
...
Dro. InProf : 0 0
Dro. OutProf : 0 0
===============================================================================
A:active#
A:active# show service customer 1 site mss1
===============================================================================
Customer 1
===============================================================================
Customer-ID : 1
Description : Default customer
...
-------------------------------------------------------------------------------
ANCP Override
-------------------------------------------------------------------------------
Egr Sched Name: root
- PIR : 90 kbps
- String : "ANCP-String-3"
-------------------------------------------------------------------------------
Service Association
-------------------------------------------------------------------------------
No Service Association Found.
===============================================================================
A:active#
subscriber sub-ident-string [scheduler
scheduler-name] [ingress
|egress
]
statistics interface
subscriber-interface [id
srrp-id]
edit-lease-state sap
sap-id ip
ip-address [subscriber
sub-ident-string] [sub-profile-string
sub-profile-string] [sla-profile-string
sla-profile-string]
edit-lease-state svc-id
service-id ip ip-address [subscriber
sub-ident-string] [sub-profile-string
sub-profile-string] [sla-profile-string
sla-profile-string]
|
Values
|
service-id: 1 — 2147483647 svc-name: 64 characters maximum
|
|
Values
|
service-id: 1 — 2147483647 svc-name: 64 characters maximum
|
eval-lease-state [svc-id
service-id] [sap
sap-id] [subscriber
sub-ident-string] [ip
ip-address]
|
Values
|
service-id: 1 — 2147483647 svc-name: 64 characters maximum
|
sync-database [peer
ip-address] [port
port-id | lag-id] [sync-tag
sync-tag] [application
application] [detail
] [type
type]
This command causes the download process to start immediately. If an ongoing download is already in progress then no further action is needed, except if the force keyword is added. In case the
force keyword is added, then the current download is aborted and a new one is immediately restarted. If aborting the current download, the internal route table should not be emptied or cleared.
mode {dropped-only
|ingr-and-dropped
|egr-ingr-and-dropped
}
ppp [lcp
] [pap
] [chap
] [ipcp
] [ipv6cp
]
[no
] circuit-id
circuit-id
authentication [policy
policy-name] [mac-addr
ieee-address] [circuit-id
circuit-id]
[no
] sub-ident-policy
policy-name
[no
] script-compile-error
[no
] script-export-variables
[no
] script-output-on-error
[no
] script-runtime-error
The no form of the command disables debugging.
[no
] events
[interface
ip-int-name]
The no form of the command disables debugging.
[no
] packets
[interface
ip-int-name]
The no form of the command disables debugging.
radius-attr type attribute-type [transaction
] {address
|hex
|integer
|string
} value
attribute-value
radius-attr vendor vendor-id type
attribute-type [transaction
] [encoding
encoding-type] {address
|hex
|integer
|string
} value
attribute-value
subscriber sub-ident-string sap
sap-id sla-profile
sla-profile-name [base
| ingress-queue-id
ingress-queue-id | egress-queue-id
egress-queue-id] [interval
seconds] [repeat
repeat] [absolute
| rate
]
When the absolute keyword is specified, the raw statistics are displayed, without processing. No calculations are performed on the delta or rate statistics.
When the rate keyword is specified, the rate-per-second for each statistic is displayed instead of the delta.
A:Dut-A# monitor service subscriber alcatel_100 sap 1/2/1:101 sla-profile sla_default
===============================================================================
Monitor statistics for Subscriber alcatel_100
===============================================================================
At time t = 0 sec (Base Statistics)
-------------------------------------------------------------------------------
SLA Profile Instance statistics
-------------------------------------------------------------------------------
Packets Octets
Off. HiPrio : 0 0
Off. LowPrio : 94531 30704535
Off. Uncolor : 0 0
Queueing Stats (Ingress QoS Policy 1000)
Dro. HiPrio : 0 0
Dro. LowPrio : 7332 2510859
For. InProf : 0 0
For. OutProf : 87067 28152288
Queueing Stats (Egress QoS Policy 1000)
Dro. InProf : 880 127660
Dro. OutProf : 0 0
For. InProf : 90862 12995616
For. OutProf : 0 0
-------------------------------------------------------------------------------
SLA Profile Instance per Queue statistics
-------------------------------------------------------------------------------
Packets Octets
Ingress Queue 1 (Unicast) (Priority)
Off. HiPrio : 0 0
Off. LowPrio : 0 0
Off. Uncolor : 0 0
Dro. HiPrio : 0 0
Dro. LowPrio : 0 0
For. InProf : 0 0
For. OutProf : 0 0
Ingress Queue 2 (Unicast) (Priority)
Off. HiPrio : 0 0
Off. LowPrio : 94531 30704535
Off. Uncolor : 0 0
Dro. HiPrio : 0 0
Dro. LowPrio : 7332 2510859
For. InProf : 0 0
For. OutProf : 87067 28152288
Ingress Queue 3 (Unicast) (Priority)
Off. HiPrio : 0 0
Off. LowPrio : 0 0
Off. Uncolor : 0 0
Dro. HiPrio : 0 0
Dro. LowPrio : 0 0
For. InProf : 0 0
For. OutProf : 0 0
Ingress Queue 11 (Multipoint) (Priority)
Off. HiPrio : 0 0
Off. LowPrio : 0 0
Off. Uncolor : 0 0
Dro. HiPrio : 0 0
Dro. LowPrio : 0 0
For. InProf : 0 0
For. OutProf : 0 0
Egress Queue 1
Dro. InProf : 880 127660
Dro. OutProf : 0 0
For. InProf : 90862 12995616
For. OutProf : 0 0
Egress Queue 2
Dro. InProf : 0 0
Dro. OutProf : 0 0
For. InProf : 0 0
For. OutProf : 0 0
Egress Queue 3
Dro. InProf : 0 0
Dro. OutProf : 0 0
For. InProf : 0 0
For. OutProf : 0 0
===============================================================================
A:Dut-A#
A:Dut-A# monitor service subscriber alcatel_100 sap 1/2/1:101 sla-profile sla_default base rate
===============================================================================
Monitor statistics for Subscriber alcatel_100
===============================================================================
At time t = 0 sec (Base Statistics)
-------------------------------------------------------------------------------
SLA Profile Instance statistics
-------------------------------------------------------------------------------
Packets Octets
Off. HiPrio : 0 0
Off. LowPrio : 109099 35427060
Off. Uncolor : 0 0
Queueing Stats (Ingress QoS Policy 1000)
Dro. HiPrio : 0 0
Dro. LowPrio : 8449 2894798
For. InProf : 0 0
For. OutProf : 100523 32489663
Queueing Stats (Egress QoS Policy 1000)
Dro. InProf : 880 127660
Dro. OutProf : 0 0
For. InProf : 105578 15104553
For. OutProf : 0 0
-------------------------------------------------------------------------------
At time t = 11 sec (Mode: Rate)
-------------------------------------------------------------------------------
SLA Profile Instance statistics
-------------------------------------------------------------------------------
Packets Octets % Port
Util.
Off. HiPrio : 0 0 0.00
Off. LowPrio : 1469 477795 0.38
Off. Uncolor : 0 0 0.00
Queueing Stats (Ingress QoS Policy 1000)
Dro. HiPrio : 0 0 0.00
Dro. LowPrio : 119 40691 0.03
For. InProf : 0 0 0.00
For. OutProf : 1349 437350 0.34
Queueing Stats (Egress QoS Policy 1000)
Dro. InProf : 0 0 0.00
Dro. OutProf : 0 0 0.00
For. InProf : 1469 209129 0.16
For. OutProf : 0 0 0.00
===============================================================================
A:Dut-A#
A:Dut-A# monitor service subscriber alcatel_100 sap 1/2/1:101 sla-profile sla_default ingress-queue-id 1
===============================================================================
Monitor statistics for Subscriber alcatel_100
===============================================================================
At time t = 0 sec (Base Statistics)
-------------------------------------------------------------------------------
Packets Octets
Ingress Queue 1 (Unicast) (Priority)
Off. HiPrio : 0 0
Off. LowPrio : 0 0
Off. Uncolor : 0 0
Dro. HiPrio : 0 0
Dro. LowPrio : 0 0
For. InProf : 0 0
For. OutProf : 0 0
===============================================================================
A:Dut-A#
A:Dut-A# monitor service subscriber alcatel_100 sap 1/2/1:101 sla-profile sla_default egress-queue-id 1
===============================================================================
Monitor statistics for Subscriber alcatel_100
===============================================================================
At time t = 0 sec (Base Statistics)
-------------------------------------------------------------------------------
Packets Octets
Egress Queue 1
Dro. InProf : 880 127660
Dro. OutProf : 0 0
For. InProf : 164366 23506178
For. OutProf : 0 0
==============================================================================
A:Dut-A#
host [sap
sap-id] [wholesaler
service-id] [port
port-id] [inter-dest-id
intermediate-destination-id] [detail
]
host [sap
sap-id] [wholesaler
service-id] [port
port-id] no-inter-dest-id
[detail
]
host [detail
] wholesaler
service-id (VPRN only)
|
Values
|
service-id: 1 — 2147483647 svc-name: 64 characters maximum
|
