Guest

Preview Tool

Cisco Bug: CSCte71703 - There is no detail logging of WAN side DHCP and PPPoE transaction

Last Modified

Mar 12, 2010

Products (1)

Known Affected Releases

1.0.0

Description (partial)

Symptom:
There is no detail logging of WAN side DHCP and PPPoE transaction

Actual Result:
Only simple display 1 row PPPoE & IPoE connection log.

Expected Result:
VZ Technical Requirment 1.14.11
The router MUST log the latest events in RAM and non-volatile memory (and only the latest) for WAN side DHCP transactions, discovery, offer, request, acknowledgement, and release, and use separate entries for the 5 individual events. That is, the router always holds no more than 5 timestamped entries for WAN DHCP transaction. Successful transaction MUST indicate in the ACK log entry at least WAN interface, WAN IP address, DNS addresses, default gateway IP. Such logging MUST be implemented without interference to DHCP transaction speed, e.g hold in RAM before flush all events within one transactions to flash.

VZ Technical Requirment 1.14.12
The router MUST log the latest events (and only the latest) for WAN side PPPoE transactions, PADI, PADO, PADR, PADS, PADT, and use separate entries for the 5 individual events. That is, the router always holds no more than 5 timestamped entries for WAN PPPoE transaction. Successful transaction MUST indicate in the ACK log entry at least WAN interface, WAN IP address, DNS addresses, default gateway IP. Such logging MUST be implemented without interference to PPPoE transaction speed, e.g hold in RAM before flush all events within one transactions to flash.

VZ Technical Requirment 1.14.13
The router MUST log the latest (and only the latest) successful LAN DHCP transactions per MAC address.
Conditions:
There is no detail logging of WAN side DHCP and PPPoE transaction

Actual Result:
Only simple display 1 row PPPoE & IPoE connection log.

Expected Result:
VZ Technical Requirment 1.14.11
The router MUST log the latest events in RAM and non-volatile memory (and only the latest) for WAN side DHCP transactions, discovery, offer, request, acknowledgement, and release, and use separate entries for the 5 individual events. That is, the router always holds no more than 5 timestamped entries for WAN DHCP transaction. Successful transaction MUST indicate in the ACK log entry at least WAN interface, WAN IP address, DNS addresses, default gateway IP. Such logging MUST be implemented without interference to DHCP transaction speed, e.g hold in RAM before flush all events within one transactions to flash.

VZ Technical Requirment 1.14.12
The router MUST log the latest events (and only the latest) for WAN side PPPoE transactions, PADI, PADO, PADR, PADS, PADT, and use separate entries for the 5 individual events. That is, the router always holds no more than 5 timestamped entries for WAN PPPoE transaction. Successful transaction MUST indicate in the ACK log entry at least WAN interface, WAN IP address, DNS addresses, default gateway IP. Such logging MUST be implemented without interference to PPPoE transaction speed, e.g hold in RAM before flush all events within one transactions to flash.

VZ Technical Requirment 1.14.13
The router MUST log the latest (and only the latest) successful LAN DHCP transactions per MAC address.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.