Yes

kindly email [email protected]

Thanks all videos already uploaded.

Core exam first

Agreed Worst trinner.

Thanks for the feedback!

Worst Trainer Indeed, check other trainings

Worst Trainer Indeed

No live sessions

Thanks

don't have these version

You're welcome

Glad you found it helpful!

1. Understand the Basics of IPS Bandwidth: The IPS bandwidth requirement refers to the amount of traffic that the IPS device can process without causing latency or packet drops. It needs to be sufficient to handle the site's maximum traffic volume while performing deep packet inspection and other security tasks. 2. Assess the Site's Network Traffic: A. Calculate Peak Bandwidth Usage: Measure the peak bandwidth usage at the site using network monitoring tools. You can use tools like NetFlow, SNMP, or other traffic analyzers. Look at the busiest times (e.g., working hours) to estimate the highest bandwidth utilization. B. Estimate the Average Bandwidth Per User: Determine how much bandwidth an average user consumes during normal operations. Different applications have varying bandwidth requirements. For instance: Browsing and emails: Low (100-500 Kbps per user) Streaming and video conferencing: High (1-5 Mbps per user) Cloud applications or backups: High (5-10 Mbps per user) C. Multiply by the Number of Users: Multiply the average bandwidth per user by the total number of users at the site. Add a buffer (20-30%) for unexpected spikes in usage. 3. Account for Traffic Types and Inspection Complexity: A. Traffic Types: Identify the types of traffic your IPS will inspect. Encrypted traffic (HTTPS), for example, requires more processing power than unencrypted traffic. B. Inspection Depth: The level of inspection affects performance. Deep packet inspection, SSL decryption, or advanced threat analysis consume more IPS resources and may reduce throughput. 4. Evaluate IPS Performance Specifications: Check the IPS device specifications from the vendor: Maximum Throughput: The total bandwidth the IPS can handle under optimal conditions. Real-World Throughput: Throughput when all security features are enabled (e.g., SSL decryption, threat detection, etc.). This is usually much lower than the maximum throughput. Ensure the IPS can handle the calculated peak bandwidth with all security features enabled. 5. Plan for Growth: Consider future scalability. If the number of users or traffic volume is likely to increase, choose an IPS with higher capacity than your current requirement. Allow for at least 25-50% headroom to accommodate growth. 6. Example Calculation: Scenario: Site has 500 users. Average bandwidth per user is 2 Mbps (mix of browsing, emails, and light streaming). Peak utilization is 70% of total capacity. IPS will perform deep inspection and SSL decryption. Steps: Total Estimated Bandwidth: Bandwidth = Users × Average Bandwidth per User Bandwidth=Users×Average Bandwidth per User Bandwidth = 500 × 2 Mbps = 1000 Mbps Bandwidth=500×2 Mbps=1000 Mbps Peak Bandwidth Utilization: Peak Bandwidth = 1000 Mbps × 0.7 = 700 Mbps Peak Bandwidth=1000 Mbps×0.7=700 Mbps Add Buffer: Required Bandwidth = 700 Mbps + 30 % = 910 Mbps Required Bandwidth=700 Mbps+30%=910 Mbps Check IPS Specification: Ensure the IPS supports at least 910 Mbps throughput with all features enabled. 7. Other Considerations: A. Redundancy: Deploy redundant IPS devices if the site cannot tolerate downtime during maintenance or failure. B. Cloud-Based IPS: For sites with highly variable traffic, consider a cloud-based IPS solution to scale bandwidth dynamically. C. Subscription Licensing: Ensure the IPS licensing supports the required bandwidth. Some vendors limit throughput based on the license tier. Conclusion: To determine the IPS bandwidth, calculate the site's peak traffic, adjust for inspection requirements and growth, and compare with the IPS device's real-world performance. Always consider future scalability and redundancy for optimal results.

Thanks

You're welcome!

Glad you liked it!

Part 2 is not released yet. giganetworkers.in/document-center/f/cisco-ise-training

please email [email protected]

@@CCIE_with_Ratnesh I already sent the email request. Thank you Sir

thanks

Yes

@CCIE_with_Ratnesh where can I find or buy it ?

Udemy

Thanks

Maybe some recording issue

Thanks

I am providing lab setup for 99 USD

@@CCIE_with_Ratnesh I'm ok with that. Do you have a full workbook for this? How can we connect?

@@ahmedsalman3294 email [email protected]

cisco sd-wan

viptela

​@@CCIE_with_Ratneshthank you How can I join your training sessions?

anyone please suggest

It seems like the changes you made in the transport VPN template affected the TLOC (Transport Locator) configuration, which caused the DTLS connection between your Cedge and vBond to go down. Here are a few steps you can check: TLOC Configuration: Ensure that the TLOC extension settings and routes in the transport VPN template are correct. This includes verifying the color and encapsulation (IPsec, GRE, etc.) settings. Incorrect TLOC settings could cause the connection to break. Transport VPN Routes: Review the changes you made to the transport VPN routes. If certain routes were deleted or incorrectly modified, this can affect the control connections, leading to TLOC disabled errors. vManage Sync: Sometimes when a device is moved to a vManage mode template, it may lose critical configurations needed for the control connections to function. Ensure the sync between vManage and the device is complete and successful. Interface & IP Connectivity: Check the interface settings and ensure IP connectivity between Cedge and vBond is still valid after the changes. The transport interface may have been impacted by the route changes. You might want to review the show control connections and show sdwan tlocs outputs to see which TLOCs are disabled and investigate further.

batch got cancelled not future videos

Thanks

5-6 Videos only

How to join

​@@CCIE_with_Ratneshhow to join the class

@@CCIE_with_Ratnesh Why not all EI classess

email [email protected]

all these videos are free.

​@@CCIE_with_Ratnesh Thanks 🎉

The error CERTVERFL you're encountering typically indicates a certificate verification failure, which can prevent control connections from being established in various network and application scenarios. Here’s a detailed approach to troubleshoot and potentially resolve this issue: Step 1: Verify Certificate Validity Check Expiration Date: Ensure that the certificate has not expired. You can check the certificate's validity period by examining its details. Check Issuing Authority: Confirm that the certificate was issued by a trusted certificate authority (CA). Step 2: Certificate Chain and Root CA Complete Chain: Verify that the complete certificate chain is present. Sometimes, intermediate certificates may be missing or not correctly installed. Root CA Trust: Ensure that the root CA is trusted by the system or application you are working with. If not, you might need to import the root CA certificate into your system’s trust store. Step 3: Certificate Hostname Hostname Match: Check that the certificate's Common Name (CN) or Subject Alternative Name (SAN) matches the hostname you are connecting to. A mismatch can cause verification failures. Step 4: Revocation Lists Certificate Revocation: Check if the certificate has been revoked. You can use tools like OpenSSL to query the certificate revocation status via CRL (Certificate Revocation List) or OCSP (Online Certificate Status Protocol). Step 5: System Time Correct System Time: Ensure that the system time and date are correct. Incorrect system time can cause issues with certificate validity checks. Step 6: Application-Specific Settings Protocol Versions: Ensure that the TLS/SSL protocol version supported by your application matches that of the server. Sometimes, older protocols like SSL 3.0 or TLS 1.0 are disabled for security reasons. Cipher Suites: Verify that the cipher suites supported by your application or device are also supported on the server. Step 7: Debugging Tools Use OpenSSL: You can use OpenSSL commands to manually verify the certificate and simulate a connection, which might provide more detailed error information. For example: openssl s_client -connect yourserver:yourport -CAfile cacert.pem Logging: Enable detailed logging on your application or network device to capture more information about the error during the connection attempt. Step 8: Consult Documentation and Support Vendor Documentation: Check the vendor’s documentation for specific guidance on certificate handling and error codes. Support Forums: Sometimes, community forums or support channels can provide solutions to similar problems encountered by others. Step 9: Renew or Replace the Certificate If the certificate is problematic (e.g., damaged, improperly formatted), consider requesting a new certificate from your CA. If you provide the specific context or the system you're dealing with, I can offer more targeted advice or steps.

full course for the paid members

How to join ?

You mean it's available to paid customers on Udemy or where else ?

okay

kzbin.info/www/bejne/nqnIkJ1pYryUhbM

Course link you Need to Join my YT channel as Paid Member - kzbin.info/www/bejne/pIjaiId6qMqCmpY

it is not covered.

DevNet Expert Course is already available @Udemy

@@CCIE_with_Ratnesh Can you please share the link.

some YT issue while file upload.

Yes, a non-IP background individual can absolutely build a career in SD-WAN. While a strong foundation in networking, especially IP concepts, is beneficial, many SD-WAN platforms are designed with simplicity and automation in mind, reducing the need for deep networking expertise. Here are a few steps you can take to build a career in SD-WAN: Learn Basic Networking Concepts: Start with foundational knowledge of networking, such as IP addressing, routing, and switching. This will help you understand how SD-WAN operates within a network. Study SD-WAN Technologies: Focus on understanding how SD-WAN works-its architecture, components, and the problems it solves. Many SD-WAN solutions simplify networking operations, which makes them more accessible to non-networking professionals. Vendor Certifications: Obtain certifications from major SD-WAN vendors like Cisco (Viptela/Meraki), VMware (Velocloud), or Palo Alto Networks (CloudGenix). These certifications provide structured learning paths and help you get familiar with the technology. Hands-On Practice: Many SD-WAN vendors offer virtual labs or trials. Practicing in these environments will give you confidence and familiarity with real-world implementations. Leverage Automation and Orchestration: SD-WAN heavily relies on automation, which makes programming and scripting skills valuable. Familiarity with tools like Ansible, REST APIs, and Python can be advantageous, even without deep IP knowledge. With the right approach, SD-WAN can be a promising career path for individuals from non-IP backgrounds. It’s all about continuous learning and adapting to new technologies.

Thanks

Yes this will cost 150USD

Thanks