I’ve been running IPv6 on my home network for a while. The solution in place has evolved over time, from terminating tunnels to a linux VM using gogo6 all the way to front-ending with a Cisco ISR using Hurricane Electric, the goal has always been the same - to practice what I preach. Running IPv6 at home and REFUSING to turn it off when problems arise is one of the best ways to learn the protocol.
I’ve been running IPv6 on my home network for a while. The solution in place has evolved over time, from terminating tunnels to a linux VM using gogo6 all the way to front-ending with a Cisco ISR using Hurricane Electric, the goal has always been the same - to practice what I preach. Running IPv6 at home and REFUSING to turn it off when problems arise is one of the best ways to learn the protocol.
Ah, the age old question that nearly every CCNA and CCNP candidate asks of themselves and others at some point. We see a minimum of 4 routing protocols in our networking studies, more if you decide to take on the Service Provider track. What makes one routing protocol better than another? I think it’s clear why (at least mostly) these particular two protocols are different, keeping in mind that one is distance vector (yes, distance vector, not hybrid distance vector) and the other is link state.
Ah, the age old question that nearly every CCNA and CCNP candidate asks of themselves and others at some point. We see a minimum of 4 routing protocols in our networking studies, more if you decide to take on the Service Provider track. What makes one routing protocol better than another? I think it’s clear why (at least mostly) these particular two protocols are different, keeping in mind that one is distance vector (yes, distance vector, not hybrid distance vector) and the other is link state.
I’m pleased to revive the KIC LABS series with a video on Cisco MQC-style QoS on the Nexus 5000.
PLEASE read these two articles first, as they do a lot better job at explaining the structure that we’re going to be putting together in the video. Unfortunately I was not able to provide this during the video, as I was pressed for time.
https://keepingitclassless.net/2012/11/cisco-quality-of-service-part-1-types-of-qos-policies/
https://keepingitclassless.net/2012/11/qos-part-2-qos-and-jumbo-frames-on-nexus-ucs-and-vmware/
Download the configuration used in this video here.
I’m pleased to revive the KIC LABS series with a video on Cisco MQC-style QoS on the Nexus 5000.
PLEASE read these two articles first, as they do a lot better job at explaining the structure that we’re going to be putting together in the video. Unfortunately I was not able to provide this during the video, as I was pressed for time.
https://keepingitclassless.net/2012/11/cisco-quality-of-service-part-1-types-of-qos-policies/
https://keepingitclassless.net/2012/11/qos-part-2-qos-and-jumbo-frames-on-nexus-ucs-and-vmware/
Download the configuration used in this video here.
I’m pleased to revive the KIC LABS series with a video on Cisco MQC-style QoS on the Nexus 5000.
PLEASE read these two articles first, as they do a lot better job at explaining the structure that we’re going to be putting together in the video. Unfortunately I was not able to provide this during the video, as I was pressed for time.
https://keepingitclassless.net/2012/11/cisco-quality-of-service-part-1-types-of-qos-policies/
https://keepingitclassless.net/2012/11/qos-part-2-qos-and-jumbo-frames-on-nexus-ucs-and-vmware/
Download the configuration used in this video here.
This started off as a company email but I wanted to share it, since I’ve been asked before. Below is opinion and opinion only. I’m more interested in how this compares with your study methods and Cisco exam experiences, so please let me know your thoughts in the comments.
Cisco exams….let’s face it, they suck. (In a good way though) I’ve taken exams from all kinds of vendors, and Cisco is really good at creating exams that vet you technically, but also require that you understand the practical reasons for the technologies we work with, not just memorizing maximum values, or configuration steps.
This started off as a company email but I wanted to share it, since I’ve been asked before. Below is opinion and opinion only. I’m more interested in how this compares with your study methods and Cisco exam experiences, so please let me know your thoughts in the comments.
Cisco exams….let’s face it, they suck. (In a good way though) I’ve taken exams from all kinds of vendors, and Cisco is really good at creating exams that vet you technically, but also require that you understand the practical reasons for the technologies we work with, not just memorizing maximum values, or configuration steps.
I’ve run into many circumstances where jumbo frames are enabled, most notably in the data center. After all, allowing for a maximum tranmission unit of greater than 1500 bytes allows us to transmit more data per frame
As I explained in Part 2 of my QoS Series, MTU can be a touch subject. Do it wrong, and you encounter one of two big network problems. One potential issue when configuring jumbo frames at L2 is that stuff just doesn’t work.
I’ve run into many circumstances where jumbo frames are enabled, most notably in the data center. After all, allowing for a maximum tranmission unit of greater than 1500 bytes allows us to transmit more data per frame
As I explained in Part 2 of my QoS Series, MTU can be a touch subject. Do it wrong, and you encounter one of two big network problems. One potential issue when configuring jumbo frames at L2 is that stuff just doesn’t work.
Yesterday kicked off the 5th iteration of Network Field Day. For those that haven’t heard of Tech Field Day, you need to check it out - there’s something for everyone, and it’s a great event that gets the technical details from vendors on their solutions. The delegates that are invited are what I consider thought leaders in each field. I’ve had the privileged of blogging, podcasting, and even meeting with them in person over the past few years, and they’re just the right kind of folks to help keep these vendors honest.
Yesterday kicked off the 5th iteration of Network Field Day. For those that haven’t heard of Tech Field Day, you need to check it out - there’s something for everyone, and it’s a great event that gets the technical details from vendors on their solutions. The delegates that are invited are what I consider thought leaders in each field. I’ve had the privileged of blogging, podcasting, and even meeting with them in person over the past few years, and they’re just the right kind of folks to help keep these vendors honest.
I’ve had some great conversations lately with a lot of folks on the topic of IPv6 prefix length in a variety of applications, specifically one very good discussion on just about anything IPv6 between me, the kind folks over at The Class-C Block and Tom Hollingworth (aka The Networking Nerd).
For many folks that are considering the impact of going dual-stack in their environments, the idea of using a /64 on all links is still a point of contention.
Now we arrive at the question of how much address space to allocate for…anyone. You may be a service provider, you may be a business, you may be a home user. Today, this question is quite easy to solve. If you’re a business-class customer, you ask your ISP for a block of addresses, and based off of your need (or ability to justify the need), you’ll be allocated some addresses. For many small-to-medium businesses, this can be as small as 8, or even 4 addresses.
Now we arrive at the question of how much address space to allocate for…anyone. You may be a service provider, you may be a business, you may be a home user. Today, this question is quite easy to solve. If you’re a business-class customer, you ask your ISP for a block of addresses, and based off of your need (or ability to justify the need), you’ll be allocated some addresses. For many small-to-medium businesses, this can be as small as 8, or even 4 addresses.
I’ve had some great conversations lately with a lot of folks on the topic of IPv6 prefix length in a variety of applications, specifically one very good discussion on just about anything IPv6 between me, the kind folks over at The Class-C Block and Tom Hollingworth (aka The Networking Nerd).
For many folks that are considering the impact of going dual-stack in their environments, the idea of using a /64 on all links is still a point of contention.
As a Data Center junkie, I daily bear witness to the glorious transformations that are taking place all around me with respect to the “next-generation” of data center. Everyone who wants to move their DC to the next level are millions of dollars worth of DC networking gear that is EXTREMELY cutting edge, enabling virtualization and cloud to do things we only dreamed of being able to do mere years ago.
As a Data Center junkie, I daily bear witness to the glorious transformations that are taking place all around me with respect to the “next-generation” of data center. Everyone who wants to move their DC to the next level are millions of dollars worth of DC networking gear that is EXTREMELY cutting edge, enabling virtualization and cloud to do things we only dreamed of being able to do mere years ago.
For so long, I’ve heard - as have many of you I’m sure - that GNS3, though a GREAT emulator for Cisco IOS software, is not practical for studying anything related to switching. Routing is handled just fine, but because of the proprietary ASICs in Cisco switches, it is not something that can be easily reverse-engineered, thus GNS3 cannot do it. After all, all routing is essentially done in software in GNS3.