Security

Hello Team,

We have integrated Aruba-CX switches with Cisco ISE for Endpoint profiling. Cisco ISE is configured to use FQDN and other attributes to identify and profile endpoints such as printers, IP phones, etc.

However, we've observed that the FQDN attribute is not consistently learned or visible on the ISE side. This behavior appears to be random across different endpoints.

Could you please advise on the following:

1. How can we verify whether the Aruba-CX switch is learning the FQDN from the endpoint?
2. Is there a way to confirm if the switch is forwarding the FQDN attribute to Cisco ISE?
3. Are there specific configurations or logs on Aruba-CX or ISE that we should check to troubleshoot this issue?

Any guidance or best practices for ensuring consistent FQDN profiling would be greatly appreciated.

DHCP relay should send this. Why are you using DNS probe? Is DHCP probe enabled on ISE? Are the endpoints actually sending their hostname in the DHCP request?

Hello Team,

We have integrated Aruba-CX switches with Cisco ISE for Endpoint profiling. Cisco ISE is configured to use FQDN and other attributes to identify and profile endpoints such as printers, IP phones, etc.

However, we've observed that the FQDN attribute is not consistently learned or visible on the ISE side. This behavior appears to be random across different endpoints.

Could you please advise on the following:

1. How can we verify whether the Aruba-CX switch is learning the FQDN from the endpoint?
2. Is there a way to confirm if the switch is forwarding the FQDN attribute to Cisco ISE?
3. Are there specific configurations or logs on Aruba-CX or ISE that we should check to troubleshoot this issue?

Any guidance or best practices for ensuring consistent FQDN profiling would be greatly appreciated.

How i can verify if endpoints sending their hostname to switch, Is there any command 

or I Packet capture is the only option

DHCP relay should send this. Why are you using DNS probe? Is DHCP probe enabled on ISE? Are the endpoints actually sending their hostname in the DHCP request?

Hello Team,

We have integrated Aruba-CX switches with Cisco ISE for Endpoint profiling. Cisco ISE is configured to use FQDN and other attributes to identify and profile endpoints such as printers, IP phones, etc.

However, we've observed that the FQDN attribute is not consistently learned or visible on the ISE side. This behavior appears to be random across different endpoints.

Could you please advise on the following:

1. How can we verify whether the Aruba-CX switch is learning the FQDN from the endpoint?
2. Is there a way to confirm if the switch is forwarding the FQDN attribute to Cisco ISE?
3. Are there specific configurations or logs on Aruba-CX or ISE that we should check to troubleshoot this issue?

Any guidance or best practices for ensuring consistent FQDN profiling would be greatly appreciated.

How i can verify if endpoints sending their hostname to switch, Is there any command 

or I Packet capture is the only option

DHCP relay should send this. Why are you using DNS probe? Is DHCP probe enabled on ISE? Are the endpoints actually sending their hostname in the DHCP request?

Hello Team,

We have integrated Aruba-CX switches with Cisco ISE for Endpoint profiling. Cisco ISE is configured to use FQDN and other attributes to identify and profile endpoints such as printers, IP phones, etc.

However, we've observed that the FQDN attribute is not consistently learned or visible on the ISE side. This behavior appears to be random across different endpoints.

Could you please advise on the following:

1. How can we verify whether the Aruba-CX switch is learning the FQDN from the endpoint?
2. Is there a way to confirm if the switch is forwarding the FQDN attribute to Cisco ISE?
3. Are there specific configurations or logs on Aruba-CX or ISE that we should check to troubleshoot this issue?

Any guidance or best practices for ensuring consistent FQDN profiling would be greatly appreciated.

Can we get specific steps to capture DHCP transition, I tried to do through mirroring and exported file, but i unable to see DHCP packet capture

How i can verify if endpoints sending their hostname to switch, Is there any command 

or I Packet capture is the only option

DHCP relay should send this. Why are you using DNS probe? Is DHCP probe enabled on ISE? Are the endpoints actually sending their hostname in the DHCP request?

Hello Team,

We have integrated Aruba-CX switches with Cisco ISE for Endpoint profiling. Cisco ISE is configured to use FQDN and other attributes to identify and profile endpoints such as printers, IP phones, etc.

However, we've observed that the FQDN attribute is not consistently learned or visible on the ISE side. This behavior appears to be random across different endpoints.

Could you please advise on the following:

1. How can we verify whether the Aruba-CX switch is learning the FQDN from the endpoint?
2. Is there a way to confirm if the switch is forwarding the FQDN attribute to Cisco ISE?
3. Are there specific configurations or logs on Aruba-CX or ISE that we should check to troubleshoot this issue?

Any guidance or best practices for ensuring consistent FQDN profiling would be greatly appreciated.