network
config>port>ethernet
config>port>sonet-sdh>path
config>port>tdm>ds1>channel-group
config>port>tdm>ds3
config>port>tdm>e1>channel-group
config>port>tdm>e3
This command enables access to the context to configure network port parameters.
n/a
accounting-policy policy-id
no accounting-policy
config>port>ethernet>network
config>port>sonet-sdh>path>network
config>port>tdm>ds1>channel-group>network
config>port>tdm>ds3>network
config>port>tdm>e1>channel-group>network
config>port>tdm>e3>network
This command configures an accounting policy that can apply to an interface.
An accounting policy must be configured before it can be associated to an interface. If the accounting policy-id does not exist, an error is returned.
Accounting policies associated with service billing can only be applied to SAPs. Accounting policies associated with network ports can only be associated with interfaces. Only one accounting policy can be associated with an interface at a time.
No accounting policies are specified by default. You must explicitly specify a policy. If configured, the accounting policy configured as the default under the config>log>accounting-policy>default command is used.
The no form of this command removes the accounting policy association from the network interface, and the accounting policy reverts to the default.
n/a
specifies the accounting policy-id of an existing policy. Accounting policies record either service (access) or network information. A network accounting policy can only be associated with the network port configurations. Accounting policies are configured in the config>log>accounting-policy context.
[no] collect-stats
config>port>ethernet>network
config>port>sonet-sdh>path>network
config>port>tdm>ds1>channel-group>network
config>port>tdm>ds3>network
config>port>tdm>e1>channel-group>network
config>port>tdm>e3>network
This command enables the collection of accounting and statistical data for the network interface. When applying accounting policies, the data, by default, is collected in the appropriate records and written to the designated billing file.
When the no collect-stats command is issued, the statistics are still accumulated by the adapter cards. However, the CPU does not obtain the results and write them to the billing file. If the collect-stats command is issued again (enabled), then the counters written to the billing file will include the traffic collected while the no collect-stats command was in effect.
no collect-stats
egress
config>port>ethernet>network
This command enables access to the context to assign network egress parameters.
n/a
shaper-policy name
no shaper-policy
config>port>ethernet>network>egress
This command assigns a shaper policy to the specified port.
The shaper policy defines shaper parameters such as shaper group, and PIR and CIR rates. The shaper policy is defined in the config>qos>shaper-policy context. Refer to the 7705 SAR Quality of Service Guide, ‟QoS for Hybrid Ports”, for more information.
The port shaper rate applies to the bulk of access and network traffic. Thus, once the configured egress shaper rate is reached, both the access and network traffic scheduling pauses.
For hybrid ports, there can be a single shaper policy on access egress and a single shaper policy on network egress. Therefore, all the SAP traffic and all the network traffic is each bound to its own shaper group in the shaper policy (access and network shaper policy, respectively). In other words, shaped SAPs and the bulk/aggregate of unshaped SAPs are shaped together as per the shaper policy assigned to the access egress. A similar behavior applies to network traffic, where the shaped interfaces and the bulk/aggregate of unshaped interfaces are shaped together as per the shaper policy assigned to the network egress.
The no form of this command reverts to the default.
‟default”
specifies an existing shaper policy name
unshaped-if-cir cir-rate
no unshaped-if-cir
config>port>ethernet>network>egress
This command sets the CIR rate for the aggregate of all the unshaped VLANs (that is, network interfaces) on the port. The default cir-rate is 0 kb/s. When the cir-rate is set to max, the CIR rate adopts the maximum rate of the port. The actual rate of the port is dictated by the physical port speed, which can be overwritten by the egress-rate sub-rate command.
If the cir-rate is higher than the sub-rate, the cir-rate is stored in the configuration database but the sub-rate limit is used.
On Gen-3 hardware, the cir-rate for this command can be configured and is applied but has no effect on the network port, except for network traffic in hybrid mode, where the cir-rate value has an effect.
The no form of the command sets the unshaped-if-cir CIR rate to 0 kb/s.
no unshaped-if-cir
the CIR rate for the aggregate of all the unshaped VLANs on the port
queue-policy name
no queue-policy
config>port>ethernet>network
config>port>sonet-sdh>path>network
config>port>tdm>ds1>channel-group>network
config>port>tdm>ds3>network
config>port>tdm>e1>channel-group>network
config>port>tdm>e3>network
This command specifies the network queue policy that defines queue parameters such as CBS-priority-only burst size, MBS, CIR, and PIR rates, as well as FC-to-queue mappings. The network queue policy is defined in the config>qos>network-queue context. Refer to the 7705 SAR Quality of Service Guide, ‟Network Queue QoS Policies”, for more information.
The no form of this command reverts to the default.
‟default”
specifies an existing network queue policy name
scheduler-mode {profile | 4-priority | 16-priority}
config>port>ethernet>network
This command selects the network-side scheduling option for the following:
8-port Gigabit Ethernet Adapter card
Packet Microwave Adapter card
10-port 1GigE/1-port 10GigE X-Adapter card
2-port 10GigE (Ethernet) Adapter card
2-port 10GigE (Ethernet) module
Ethernet ports on the 7705 SAR-A, 7705 SAR-Ax, 7705 SAR-H, 7705 SAR-Hc, 7705 SAR-M, and 7705 SAR-Wx
On the 6-port Ethernet 10Gbps Adapter card and the 7705 SAR-X, scheduler-mode is permanently set to support 4-priority and is not user-configurable.
With profiled (or rate-based) scheduling, both in-profile and out-of-profile scheduling are supported. Packets with a flow rate that is less than or equal to the CIR value of a queue are scheduled as in-profile. Packets with a flow rate that exceeds the CIR value but is less than the PIR value of a queue are scheduled as out-of-profile. In-profile traffic has strict priority over out-of-profile traffic.
Profiled scheduling does not take queue type into consideration. With queue type-based scheduling, queues are divided into two categories – those that are serviced by the Expedited scheduler and those that are serviced by the Best Effort scheduler. The Expedited scheduler has precedence over the Best Effort scheduler.
Four-priority scheduling combines both profiled and queue type-based scheduling. The combination provides four scheduling priorities. Packets are scheduled in the following order, in strict priority fashion:
Expedited in-profile packets
Best-effort in-profile packets
Expedited out-of-profile packets
Best-effort out-of-profile packets
16-priority —8-port Gigabit Ethernet Adapter card, 10-port 1GigE/1-port 10GigE X-Adapter card, 2-port 10GigE (Ethernet) Adapter card, 2-port 10GigE (Ethernet) module, Packet Microwave Adapter card, 7705 SAR-A, 7705 SAR-Ax, 7705 SAR-H, 7705 SAR-Hc, 7705 SAR-M, and 7705 SAR-Wx Ethernet ports (cannot be changed)
not applicable
permanently set on the 6-port Ethernet 10Gbps Adapter card and the 7705 SAR-X and is not user-configurable
sets the 16-priority scheduling option for the 8-port Gigabit Ethernet Adapter card, 10-port 1GigE/1-port 10GigE X-Adapter card, 2-port 10GigE (Ethernet) Adapter card, 2-port 10GigE (Ethernet) module, Packet Microwave Adapter card, 7705 SAR-A, 7705 SAR-Ax, 7705 SAR-H, 7705 SAR-Hc, 7705 SAR-M, and 7705 SAR-Wx Ethernet ports