cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2311
Views
5
Helpful
2
Replies

Catalyst Option 82 hostname (remote-id) and interface (circuit-id) sent in hex

smailmilak
Level 4
Level 4

Hello,

 

I have configured IP DHCP SNOPPING with DHCP Option 82.

On BNG/BRAS I see the circuit and remote ID in hex format which is annoying.

 

Is this normal behavior and is there a way to get the Option 82 info in text format or it depends on the BNG/BRAS?

I am on ASR9K with 5.3.2

2 Replies 2

Peter Paluch
Cisco Employee
Cisco Employee

Hello,

The DHCP Relay Agent Information Option 82 is very generic in the sense that the format of the Remote ID and Circuit ID are largely arbitrary. See RFC 3046 Section 2.0 for details. Thus, there is no fixed representation or meaning to the contents of these suboptions, and according to the same RFC, there is no indication of what type of information has been inserted into them. Every vendor can put different values in there, and there is no unambiguous way of knowing what do those values represent.

Cisco Catalyst switches use the following format for Option 82 when doing DHCP Snooping:

(Retaken from Catalyst 3560 Configuration Guide.)

You can optionally force your Catalysts to use either a hostname or a user-defined string in the Remote ID suboption by means of ip dhcp snooping information option format remote-id { hostname | string ... } command.

In addition, you can redefine the Circuit ID using the per-interface ip dhcp snooping vlan information option format-type circuit-id string ... command.

So, specifically on Catalyst switches, you can redefine the Remote ID and Circuit ID to any unique values you would like to have. However, other devices and/or vendors may use their own values and their meaning. Once again, because there is nothing in the Option 82 alone that would indicate the type or format of these values, you cannot expect that your BNG/BRAS will know how to interpret them and show them nicely.

Best regards,
Peter

Hi,

 

many thanks for the reply. I did configure custom remote and circuit-id and with Wireshark I see it in hex format. 

Problem is that the BNG is just taking the string in hex and puting it under subscriber session.

DSLAM's are working different, I have circuit and remote-id in clear text.

Review Cisco Networking for a $25 gift card