We’re excited to announce the full-scale launch of our CCIE Collaboration 8-Hour Mock Lab Workbook (Vol. 2)! Written and tested by the world’s best Collaboration Instructor – Andy Vassar CCIE #22042 (Collaboration, Voice, and R&S), it’s a must have solution for any student that’s preparing for their Cisco Collaboration Certification.
Five Complete 8-hour Mock Lab Scenarios
Detailed Solution Guide (DSG):
Web-based access to our workbooks
Pathway to success:
After you’ve purchased your CCIE Collaboration 8-Hour Mock Lab Workbook (Vol.2), don’t forget to reserve rack time with our CCIE Collaboration Rack Rental Vouchers – time slots book fast. Purchase your vouchers today!
By now, the transition to adopt IPv6 networks is in full swing. Registrars are running out of prefixes and new users overseas are getting v6-only allocations for new circuits. Mobile providers are going v6-only and transition mechanisms are in place to ease the migration. You can hear about some of these topics in this recent roundtable recorded at Interop last week:
One of the converstaions that I had with Ed Horley (@EHorley) during Interop opened my eyes to another problem that we will soon be facing with IPv6 and legacy technology. Only this time, it’s not because of a numbering scheme. It’s because of old hardware.
Technology always marches on. Things that seemed magical to us just five years ago are now antiquated and slow. That’s the problem with the original 802.11 specification. It supported wireless data rates at a paltry 1 Mbps and 2 Mbps. When 802.11b was released, it raised the rates to 5.5 Mbps and 11 Mbps. Those faster data rates, combined with a larger coverage area, helped 802.11b become commercially successful.
Now, we have 802.11n with data rates in the hundreds of Mbps. We also have 802. Continue reading
This vendor-written tech primer has been edited by Network World to eliminate product promotion, but readers should note it will likely favor the submitter’s approach.
Every April millions upon millions of taxpayers rush to file state and federal taxes before the 15th, and as with every other aspect of day-to-day life, filing taxes has become digital. The IRS website alone receives three to four times as much traffic in early spring as it does in the off-season, and this gigantic spike is indicative of what most tax-related websites experience at this time of year.
+ ALSO ON NETWORK WORLD Yikes: 10,000 IRS impersonation scam calls are placed every week +
To read this article in full or to leave a comment, please click here
Carrier-grade NFV right out of the box.
N-Port Virtualization (NPV), and N-port ID Virtualization (NPIV) have been around for quite some time now. Enhancements have been made to the traditional NPV and NPIV implementations, making it more convenient for unified fabric topologies (which is what we will be discussing today). This blog, part 1 in a 2-part series, will be discussing the ‘fcoe-npv’ implementation of NPV/NPIV, while the next blog will be focused on the traditional implementation.
NPV and NPIV were created as a method in which we could add additional switches (i.e. port density), to a given fabric, without consuming additional domain-id’s, or adding to the administrative burden of a growing SAN (managing zoning, domain-id’s, principle switch elections, FSPF routing, etc…). A lot of this concern stemmed from the fact that the Fibre Channel standard limits us to 239 usable domain id’s. Essentially 8-bits, or the most significant byte in the Fibre Channel ID (FCID), is reserved for this domain-id. This byte is what is used within FSPF protocol to route traffic throughout a Fibre Channel fabric. While this gives us 256 addresses, only 239 are usable, as some are reserved. Beyond this, many vendors restrict us too a much smaller number of domain-id’s on Continue reading