27.10.2013 Views

8.3.3.8 - Force10 Networks

8.3.3.8 - Force10 Networks

8.3.3.8 - Force10 Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Buffer tuning commands<br />

Task Command Command Mode<br />

Define a buffer profile for the FP queues. buffer-profile fp fsqueue CONFIGURATION<br />

Define a buffer profile for the CSF queues. buffer-profile csf csqueue CONFIGURATION<br />

Change the dedicated buffers on a physical 1G<br />

interface.<br />

Change the maximum amount of dynamic buffers<br />

an interface can request.<br />

buffer dedicated BUFFER PROFILE<br />

buffer dynamic BUFFER PROFILE<br />

Change the number of packet-pointers per queue. buffer packet-pointers BUFFER PROFILE<br />

Apply the buffer profile to a line card. buffer fp-uplink linecard CONFIGURATION<br />

Apply the buffer profile to a CSF to FP link. buffer csf linecard CONFIGURATION<br />

FTOS Behavior: If you attempt to apply a buffer profile to a non-existent port-pipe, FTOS displays the<br />

following message. However, the configuration still appears in the running-config.<br />

%DIFFSERV-2-DSA_BUFF_CARVING_INVALID_PORT_SET: Invalid FP port-set 2 for linecard 2. Valid<br />

range of port-set is <br />

Configuration changes take effect immediately and appear in the running configuration. Since under<br />

normal conditions all ports do not require the maximum possible allocation, the configured dynamic<br />

allocations can exceed the actual amount of available memory; this is called oversubscription. If you<br />

choose to oversubscribe the dynamic allocation, a burst of traffic on one interface might prevent other<br />

interfaces from receiving the configured dynamic allocation, which causes packet loss.<br />

You cannot allocate more than the available memory for the dedicated buffers. If the system determines<br />

that the sum of the configured dedicated buffers allocated to the queues is more than the total available<br />

memory, the configuration is rejected, returning a syslog message similar to the following.<br />

Table 46-4. Buffer Allocation Error<br />

00:04:20: %S50N:0 %DIFFSERV-2-DSA_DEVICE_BUFFER_UNAVAILABLE: Unable to allocate dedicated buffers for<br />

stack-unit 0, port pipe 0, egress port 25 due to unavailability of cells<br />

FTOS Behavior: When you remove a buffer-profile using the command no buffer-profile [fp | csf] from<br />

CONFIGURATION mode, the buffer-profile name still appears in the output of show buffer-profile<br />

[detail | summary]. After a line card reset, the buffer profile correctly returns to the default values, but<br />

the profile name remains. Remove it from the show buffer-profile [detail | summary] command output<br />

by entering no buffer [fp-uplink |csf] linecard port-set buffer-policy from CONFIGURATION mode<br />

and no buffer-policy from INTERFACE mode.<br />

Display the allocations for any buffer profile using the show commands in Figure 46-8. Display the default<br />

buffer profile using the command show buffer-profile {summary | detail} from EXEC Privilege mode, as<br />

shown in Figure 46-7.<br />

S-Series Debugging and Diagnostics | 823

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!