Loading...
Loading...
I would like to request the following modifications enhancing the functionality of the current DHCP Event trace implementation - Change the format of the timestamp to add msec granularity ?07:54:32.947? (instead of 07:54:32) - Add info about buffer capacity (for example last 200 messages or last 2 days) so the user could understand what is the recorded time span - Add the ability to clear the buffer content - Add the ability to filter by date - Add column presenting also Source MAC and Source IP - Add column presenting Flow ID to be able to distinguish different DHCP events - Add info regarding the involved inter-process communication to be able to distinguish if the packet is sent from FED to IOS or from IOS to DHCP Snooping or vice versa - Add the option to present the detail information of the recorded packets ? brief output vs detail output. In the detail option, we should be able to see the structure of the given DHCP packet - for example should be able to observe the option82 used in SDA environment - Add option to display DHCP events for given mac address in given VLAN/VRF (very important in SDA environment) - Unify the CLI to create a consistent way of verification of all feature related event traces for example: show monitor event-trace ? dhcp stp show monitor event-trace dhcp ? mac show monitor event-trace dhcp mac XX:XX:XX:XX:XX:XX:XX <-- xxxx.xxxx.xxxx vlan
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.