Cisco is extending the timeline for the CCIE lab exams and CCIE certification migrations, from February 24th to April 27, 2020. This means that you can take the existing CCIE lab before April 27, or choose to take the new CCIE lab on or after April 27th.
As you may be aware, on January 30, the World Health Organization declared the Coronavirus outbreak a global health emergency. Our thoughts and prayers are with those affected. Cisco has a well-established process to coordinate our efforts during outbreaks like this, and they have been tracking the situation and taking appropriate action during recent days and weeks. The safety of our customers, partners and employees is always our priority.
One of the actions taken as a result of the continued spread of the virus, was to close CCIE labs in Hong Kong and Beijing, from February 1 through February 14, 2020. These closures impact the timeline for the transition of the CCIE lab exams planned on February 24, 2020, not just for those planning to test in Beijing or Hong Kong, but for our customers globally who have been affected by travel restrictions, business closures and other related circumstances.
Cisco made the decision to delay the migration of existing CCIE certifications to new CCIE certifications until April 27, 2020, when it will transition to the new CCIE lab exams. All other elements of the portfolio transition will take effect as planned on February 24.
For more details please read here Current CCIE Lab Exams Extended, Migration to Occur on April 27, 2020
I got involved in a complicated issue with a Cisco ISE implementation, and to understand what the endpoint (windows) was doing had to debug the 802.1x on the ccommand line.
Look to all interfaces in the current OS stack and providers
netsh trace show interfacesnetsh trace show providers
netsh lan set tracing mode=[yes|no|persistent]
Capture all info to the tracefile trace.etl, make sure you have the right providers
netsh trace start capture=yes tracefile=C:\trace.etl provider=[microsoft-windows-wired-autoconfig|microsoft-windows-wlan-autoconfig|microsoft-windows-onex]
Time to stop the capture and and find the root cause :)
No tags for this post.
If you are all about blooging i totally recomend this amazing opportunity to be recognized as a influencer on the community. Share what you have been doing, share your passion about technology or other areas that keep you up.TEST, Do You Know Someone Who Should Apply? Attention tech bloggers (+vloggers, +podcasters) the prize for the 2019 ITBlogAwards is a pass to Cisco Live – apply!
No tags for this post.
Tuesday, September 10th
Hilton London Kensington – 179-199 Holland Park Avenue
London, W11 4UL
In collaboration with VMware, VMUG is bringing back an opportunity for members to participate in a technical roadshow focused on vSphere 6.7. This event is complimentary to all VMUG members, so make sure you register today!
VMware vSphere is the foundation of VMware’s Software Defined Datacenter and Cloud vision. No matter where you are in your digital transformation journey, getting current on VMware vSphere can best position you to gain maximum value from your VMware SDDC solution. Whether you are implementing new technologies or are looking at hybrid cloud or Bi-modal IT, upgrading vSphere can help you get there faster.
Kev Johnson will be the event facilitator
This is a good opportunity to hear back from peers, networking and be more close with the VMware community.
The documentation might get you a bit confused, but after have a chat with Cisco TAC they shed some light…..Unfortunately this design is not supported, so if you are migrating from a Old Cisco ASA platform it’s time to redesign and avoid redundant interfaces. So i had to move those interfaces to port-channel, so the trade-off was the failover if the principal switch died.
And here is the bug reported
Redundant interfaces are not supported on all FXOS platforms
“Firepower Management Center Configuration Guide, Version 6.1”
Chapter: Interfaces for Firepower Threat DefenseInformation related to Redundant interfaces should be changed
Redundant interfaces are not supported on the Firepower 9300
Redundant interfaces are not supported on the Firepower 9300, 4100, 2100Conditions:
Currently Redundant interfaces are not supported on all FXOS Platforms