So I write. A\ lot. A crap load. All that for a simple reason; nobody to discuss stuff. So I create ficitious characters in my head with participants that usually vary between, and upto 8 personnas. Sometimes you might be very surprised and wonder wtf which is by consensus, and when I look at it again, I remember, ooh that was the point personna 7 was relaying to personna 2 and who inturn wnats to bring personna 3 upto speed. Eureka! That way only to me. Like you could drive from work home to find that you absolutely don’t remember being on the road, but somehow you are in the familiar parking spot at home nonetheless, having not driven off a ravine or cliff! One might be surprise that I write most of the stuff actually day dreaming…and when I come to we are 5 miles down the article…when I remember its time to duly uphold my traditions and disabuse some drumsticks or thighs; how dare I! Off to the refrigerator I sprint after hitting post. Then go to somewhere else online, daydream some, then its time to sleep and its adios!
8 years ago or so, I picked up out of the habit of compiling a “Technical Encyclopedia” or “Quick Reference Book” using quicck CTRL^Fs. The “Appendix” at the bottom is usually the “main part” for simple reason; disaggregation of the composite abstract from the iterative concrete; the more succinct aspect that states how the various conceptual elements interact with each other; whereas the more turgid aspect that fully explains the constitution of those elements; it becomes easy to visualize the holistic picture, absent of jargon, to then be followed by a line by lie perusal of the appendices to fully comprehend the subject in its entirety. As most of you have probably realized in your own profession, and particularly at expert level of highly technical fields, accuracy is not a matter of convenience, but rather a necessity. You don’t need to pour through the Appendiix often, and as such ur not too burdened when quickly revisiting an item in the body section, and only when needed, to then read the full description in the appendix. The entries further down are appendix level run downs, hence the relatively higher degree of verbosity. If I was shaky with the concept of SDN, I would simply Ctrl_F and reread the appendix entry in full; more often than not you won’t need to once you grasp the subject, where you will read the condensed description at the top… That is the idea…
Look at my behind, I already have another news paper article …lol…
The process has spun up a lot of good engineers, including those who work for Cisco like I do.
#################################
Cisco ISE – Identity Services Engine: This platform serves the Cisco Identity Server functionality , which runs several processes to limit network access only to entities that have been validated at the correct privilege level, as well as a host of other functionalities pertaining to identity and security. Some processes it can run include the “AAA Server Role” , and to this specific role it is, not exactly a feature parity successor to the Cisco ACS, or Access Control Sever, but functionally it is effectively as such, 802.1X Radius Server for NAC (Network Access Control), third-party integration e.g. with security services such as McAfee AV(Anti-Virus) , and the HIPS(Host Intrusion Prevention Systemm), plus quite a number of others.
SDN-Software Defined Networking
With the bleeding age paradigm coined Software Defined Network; tersely, a dynamically programmable network where here has been a decopling of the control plane from the data plane, such that, contrary to legacy systems where each physical device was a fusion of control/data plane, SDN can migrate control plane to a centralized orchestrator, which in turn can be used to programmatically build the entirety of the network infrastructure before the hardware ever arrives, on the orchestrator, and as such when the relevant hardware arrives, you simply set up and power on the hardware device, followed by a “push” from the orchestrator, or maybe “pull” depending on the order of operations, to be followed by basic connectivity tests between the elements as required, after which process the device goes live!
Hardware Abstraction: The hardware is here considered to be “stateless”, and it’s functionality is abstracted, meaning a “software centric” approach is in use; that a software configuration capsule fully defining the functionality of the device is indexed in an orchestrator, whereas the hardware piece is relegated to an interchangeable plug and play component, not much unlike the disk where you keep a burned copy of a pirated song. You carry CD but the “meaningful good” is the “song”.