Guest

Preview Tool

Cisco Bug: CSCut63250 - Enable ASA to customise DHCP client option 61 DHCPOPT_CLIENT_IDENTIFIER

Last Modified

May 14, 2018

Products (1)

  • Cisco ASA 5500-X Series Firewalls

Known Affected Releases

9.1(2) 9.9(1) 9.9(2)

Description (partial)

Symptom:
Current ASA software generates the DHCP client ID based by concatenating the 
following elements :

"cisco"-"macaddress"-"relayid+circuitid||sessionid"-"interface"

As opposed to the current functionality where the DHCP client ID cannot be
customised, customers would benefit a lot from getting an ASCII string option (e.g. username)
added to the DHCP Client Identifier.

Conditions:
ASA RA VPN with DHCP

Related Community Discussions

ASA 5505 +MER Connection Type
Hi My UK (SKY) Fibre provider requires MER authentication so I need to have my ASA 5505 to perform that. Even though ASA 5505 supports DHCP with option 61 it appears that you can only use either MAC close or the default settings "Cisco-<MAC address>-<Interface>-Host" http://www.cisco.com/c/en/us/td/docs/security/asa/asa91/configuration/general/asa_91_general_config/basic_dhcp.html However there is no option to parse credentials over DHCP option 61. Anyone aware of any workarounds? Thanks
Latest activity: Feb 22, 2016
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.