If you’re on the buying side of the IT industry, you’ll love the “42 is the answer” post by Storagebod. The really fun part describes vendors trying to properly position themselves ... and failing in the process:
When all you have is a hammer, every problem looks a nail but even if your hammer is the best hammer in all the world and sure you could bang in a screw, at the end of the day, there will be dissatisfaction with results.
BTW, his question that gives the answer 42 is way too narrow (although personally relevant; just read his post); Douglas Adams took a much wider perspective.
In a comment to my “Did you notice 15.1T is released?” post kcuorbax shared exciting news about the new CCIE track launched yesterday:
CCIE Numbering experts will have the outstanding ability to find if a bug fixed in release A is fixed in release B. They will understand why new features are inadvertently introduced in mainline trains and why developers forget to commit fixes in the branches where the bugs were discovered. They will master the double numbering of IOS-XE and the sudden change from 12.2XN to 15.0S.
Anyone brave enough to try to take this exam?
One of the exciting new features of the recently launched CRS-3 router enables Service Providers to implement first-ever all-optical end-to-end traffic grooming. One of the new linecards (unfortunately not compatible with CRS-1 due to increased hardware complexity) supports the SFSS protocol (defined in RFC 4824).
Using a high-quality video link and all-optical spatial separators you can easily transport more than one SFSS instance on the same wavelength, allowing you to implement a true sub-lambda traffic grooming in the optical domain. There’s just one gotcha: due to the encoding requirements of SFSS, you cannot carry it in the dense channel spacing of DWDM; you have to use CWDM or even wider optical bands depending on the receiver’s capabilities.