Cisco DNAC Day01 - Full Course @Graphy

Рет қаралды 10,103

CCIE with Ratnesh

Күн бұрын

Пікірлер: 23

@amirkhurshid5484 Жыл бұрын

Thank you Ratnesh ! Glad to see you progress

@CCIE_with_Ratnesh Жыл бұрын

Thanks a ton

@madoalfarsi2930 4 ай бұрын

Hallo sir I hope you are doing well. I have some questions about Thousandeyes integration with DNA center. How can I contact you? For thousandeye integration it needs VLAN and IP address, which VlAn and IP does it mean? There are a lot of IPs and VLANs in my switch. Thanks for a feedback

@CCIE_with_Ratnesh 4 ай бұрын

ThousandEyes Integration with Cisco DNA Center 1. VLAN and IP Address Requirements: For integrating ThousandEyes with Cisco DNA Center, you'll need to specify a VLAN and IP address. These are required for the ThousandEyes Enterprise Agent to communicate effectively within your network. 2. Choosing VLAN and IP Address: VLAN: Select a VLAN that has access to the necessary network segments. This VLAN should be capable of reaching both internal and external network resources as required by the ThousandEyes monitoring setup. IP Address: Assign an IP address from the chosen VLAN's subnet. This IP address should be static and reserved for the ThousandEyes Enterprise Agent to ensure consistent connectivity. 3. Configuring the VLAN and IP Address on Your Switch: If you have multiple VLANs and IP addresses on your switch, follow these steps to configure the required VLAN and IP address: Identify the VLAN: Ensure the VLAN you choose has sufficient network access for the monitoring tasks. It should not be restricted by ACLs or firewall rules that could block ThousandEyes traffic. Assign IP Address: Assign a static IP address from the selected VLAN's subnet to the ThousandEyes Enterprise Agent. Example Configuration: Let's assume VLAN 200 is chosen for ThousandEyes integration and the subnet for VLAN 200 is 192.168.200.0/24. Switch Configuration Example: plaintext Copy code # Create VLAN 200 if it doesn't exist configure terminal vlan 200 name ThousandEyes_VLAN exit # Assign a static IP address to the VLAN interface interface Vlan200 ip address 192.168.200.10 255.255.255.0 no shutdown exit # Ensure ports are assigned to VLAN 200 if needed interface GigabitEthernet1/0/1 switchport access vlan 200 switchport mode access no shutdown exit 4. Additional Considerations: Ensure the VLAN is properly routed and accessible from the DNA Center. Verify that necessary firewall rules are in place to allow traffic from the ThousandEyes Agent to the Internet and other required network segments. Further Assistance If you need more detailed guidance or have specific questions about the integration process, please feel free to reach out to me directly using the contact information provided above. I'm here to help ensure a smooth integration of ThousandEyes with your Cisco DNA Center.

@madoalfarsi2930 6 ай бұрын

Hi. Sir. I have a question. I have devices in the Inventory DNA Center. For some devices the DNA is not showing Health (It shows No Health), although I configured the devices with same configs. What could be the reason. I checked everything. SNMP, SNMP Polling, Collector, Netconf thanks

@CCIE_with_Ratnesh 6 ай бұрын

If you're experiencing devices in Cisco DNA Center's Inventory not showing health status (displaying "No Health") despite having configured them with the same settings as other devices that do show health status, there are several potential reasons for this issue. Here are some troubleshooting steps and possible reasons: SNMP Configuration: Verify that SNMP configurations are correct and consistent across all devices. Ensure that SNMP polling is enabled and functioning properly. Check if SNMP traps are being received from the devices correctly. Netconf Configuration: Confirm that Netconf is properly configured on all devices and that DNA Center can communicate with them using Netconf. Ensure that Netconf capabilities are consistent across devices and match the requirements of DNA Center. Device Reachability: Check the reachability of the devices from DNA Center. Ensure there are no network issues affecting communication. Confirm that there are no firewall rules or access control lists blocking SNMP or Netconf communication. Device Compatibility: Verify that the devices are fully compatible with DNA Center's health monitoring features. Some older or limited-functionality devices may not provide comprehensive health data. DNA Center Collector: Check the status and functionality of the DNA Center collector. Ensure that it is properly collecting and processing data from all devices. Review any logs or error messages related to the collector to identify any issues. Software Versions: Ensure that all devices and DNA Center are running compatible software versions. Incompatible versions can lead to communication issues and incomplete data retrieval. Configuration Consistency: Double-check that the configurations applied to the devices are identical and that there are no discrepancies that could affect health status reporting. Look for any specific configurations or settings that might be required for health monitoring to function correctly. DNA Center Health Policies: Review the health policies and thresholds configured in DNA Center. Ensure they are appropriate for the devices in question and that they are not causing health status to be reported incorrectly. By systematically checking these areas and troubleshooting any issues that are found, you should be able to identify the reason why some devices are not showing health status in Cisco DNA Center's Inventory.

@madoalfarsi2930 6 ай бұрын

@@CCIE_with_Ratnesh I checked all the things you mentioned here. All the devices have exact same configs, IOS versions, configs, model, and everything is good. But some devices do not show Health Data. SNMP, Netconf etc are running and doing good.

@CCIE_with_Ratnesh 6 ай бұрын

@@madoalfarsi2930 Could you please escalate the TAC case?

@madoalfarsi2930 6 ай бұрын

@@CCIE_with_Ratnesh I don't have TAC support access. It's a LAB

@kabisurya Жыл бұрын

Much awaited, thanks a lot Ratnesh. As always great content. Will it be a 20day session? I wish I can afford the course.

@CCIE_with_Ratnesh Жыл бұрын

Thanks, Kabisurya, this is 10 days x2 hours = 20 hours session, class timing is odd, it's at midnight if I form any batch in the India timezone you can attend.

@kabisurya Жыл бұрын

@@CCIE_with_Ratnesh if you can share the timings, i will attend.

@CCIE_with_Ratnesh Жыл бұрын

@@kabisurya please email ratnesh721kumar721@gmail.com will share you the training & cost details