Dell Networking OS provides two predefined buffer profiles, one for single-queue (for example, non-quality-of-service [QoS]) applications,
and one for four-queue (for example, QoS) applications.
You must reload the system for the global buffer profile to take effect, a message similar to the following displays: % Info: For the
global pre-defined buffer profile to take effect, please save the config and reload the system..
Dell Networking OS Behavior: After you configure buffer-profile global 1Q, the message displays during every bootup. Only one reboot is
required for the configuration to take effect; afterward you may ignore this bootup message.
Dell Networking OS Behavior: If you configure 1Q, save the running-config to the startup-config, and then delete the startup-
config and reload the chassis. The only way to return to the default buffer profile is to remove the 1Q profile configured and then reload
the chassis.
If you have already applied a custom buffer profile on an interface, the buffer-profile global command fails and a message similar
to the following displays: % Error: User-defined buffer profile already applied. Failed to apply global
pre-defined buffer profile. Please remove all user-defined buffer profiles.
Similarly, when you configure buffer-profile global, you cannot not apply a buffer profile on any single interface. A message similar
to the following displays: % Error: Global pre-defined buffer profile already applied. Failed to apply
user-defined buffer profile on interface Te 1/1. Please remove global pre-defined buffer
profile.
To apply a predefined buffer profile, use the following command:
•
Apply one of the predefined buffer profiles for all port pipes in the system.
CONFIGURATION mode
buffer-profile global [1Q|4Q]
If the default buffer profile dynamic is active, Dell Networking OS displays an error message instructing you to remove the default
configuration using the no buffer-profile global command.
Troubleshooting Packet Loss
The show hardware stack-unit command is intended primarily to troubleshoot packet loss.
To troubleshoot packet loss, use the following commands.
•
show hardware stack-unit stack-unit-number cpu data-plane statistics
•
show hardware stack-unit stack-unit-number cpu party-bus statistics
•
show hardware stack-unit stack-unit-number drops unit unit-number
•
show hardware stack-unit stack-unit-number unit unit-number {counters | details | port-stats
[detail] | register | ipmc-replication | table-dump}
•
show hardware {ip | ipv6 | mac} {eg-acl | in-acl} stack-unit stack-unit-number port-set 0
pipeline 0-3
•
show hardware ip qos stack-unit stack-unit-number port-set 0
•
show hardware system-flow layer2 stack-unit stack-unit-number port-set 0 {counters | pipeline
0-3}
•
show hardware drops interface interface
•
show hardware buffer-stats-snapshot resource interface interface
•
show hardware buffer inteface interface{priority-group { id | all } | queue { id| all} |
detail} buffer-info
•
show hardware buffer-stats-snapshot resource interface interface{priority-group { id | all } |
queue { ucast{id | all}{ mcast {id | all} | all}
•
show hardware drops interface interface
•
clear hardware stack-unit stack-unit-number counters
•
clear hardware stack-unit stack-unit-number unit 0-1 counters
•
clear hardware stack-unit stack-unit-number cpu data-plane statistics
Debugging and Diagnostics
1053