As a (very) long time network engineer, I can't accept this at face value. If the only switch they were locked out of was the core switch, then the bulk of the config could be extracted from all of the neighbors. Once you have the information from the neighbors, then some network events debugging enabled on the neighbors would enable the bulk of the remaining missing information to be derived.
16 posts • joined 2 May 2014
Dead LAN's hand: IT staff 'locked out' of data center's core switch after the only bloke who could log into it dies
Re: I think the author is confused
"The services provided by AWS and Azure are very similar. They both offer trial periods; free VMs (teeny tiny) and documentation galore (on how to expand your footprint)."
I have worked with both of them. The similarity between the two is skin deep. One is very pretty, the other is solidly engineered...
Maybe if the system was designed in the early 80's. When we talk active/passive in networking, we refer to the interface being actively forwarding or not. At the most basic level, passive interfaces still monitor the physical link. In the more typical scenario, the end systems still exchange keep-alive messages over passive interfaces to ensure the elements can actually reach each other.
Re: He has a point
You would not require approval in Australia from the local water authority provided you adhere to any local day/time restrictions dealing in areas prone to drought. A typical failsafe is to use two values in series driven by different controller outputs. You could do this with a master value and value on each spur.
Clearly someone that does not know what they are talking about. ROMMONs are not the IOS software on the platform, they are the equivalent of a BIOS. People do not download "ROMMONs" in order to run unlicensed IOS software. Malicious ROMMONs are installed on machines are intercepted in transit and the ROMMONs replaced.
Beauty is in the eye of the beholder. There are somethings that Microchip does that is difficult to comprehend, such as a serial port in an embedded system that will lock up in the event of a comms error. On the other hand Atmel have their own problems, such that a WDT that can be enabled in software but not disabled in software requiring a processor reset. Or how about lacking a processor RESET instruction.
IMHO the PIC24/dsPIC33 is a vast improvement on both their own and Atmel's 8 bit processors.
SDN has lots of promise but I don't think the chosen analogy with the switch network topology recovering on link failure being a real benefit. In this simple example of centralised control plane (brain), if the switches lose connectivity to the central control plane then traffic between switches will never re-converge. Even when the switches maintain connectivity to the centralised the control plane, depending on the physical separation between the switches and the centralised servers, network re-convergence time can be significantly increased.
When each switch runs its own control plane, it is not sharing fate with anyone. Each switch will build its own map. Re-convergence time can take longer than having a centralised control plane in close proximity but at least it will recover.
The centralised control plane looks really great in simple tests but the real world is never so simple. Take for example the case where an A380 engine exploded on a Qantas flight spraying the wing area with shrapnel. The central site in France, monitoring the performance data from the aircraft in real time, was inundated with hundreds of persistent and reoccurring alarms making it extremely difficult to determine the coarse of action required to return the aircraft to safely. A true credit to the skill of the pilots (local brains) working in conjunction with the human operations team in France (centralised brain).
What is really needed is distributed (local) command and control with centralised oversight.
LET X = ??? Where X come from
Lunar Landers on PDP-8, Coding in machine language, loading code via toggle switches, STOP, RESET, PROGRAM LOAD.
Then the migration to high level assembly language. It was all great stuff. Then along came BASIC with LET X = 10;
What do you mean LET?
Where did X come from?
What register is that or what memory location is being used - certainly nothing I declared.
Boy those were troubling issues in the day...