How Seven Network Layers Explain the World of Computers – and Why IT Administrators Still Despair Regularly
There are problems in IT that can be explained with surprising precision. A cable is defective, a server is unreachable, a DNS entry is set incorrectly, or a router has decided it has worked hard enough for today. For all these cases, there are diagnostic tools, protocols, and experienced administrators who can provide at least a plausible explanation after a brief analysis.
And then there are the other cases.
Cases where technically everything works. The network connection is up, the server responds, the printer is turned on, and even the dreaded firewall shows no signs of a problem. Yet somewhere, a person sits in front of a screen and explains with growing conviction that “the internet is broken.”
Anyone who has worked in first-level support for some time knows these cases. Some are so curious that one hasn’t forgotten them even years later.
During my training as an IT clerk, I occasionally worked in first-level support. This is the area where the first errors related to computers in a company are handled. For example, once an apprentice from accounting contacted us. On his monitor, he explained, there was an error message.
So the very normal first question in support:
“What is on your monitor?”
The answer came without much hesitation:
“My girlfriend’s stuffed animal.”
This was probably one of the longest seconds in the history of first-level support.
Because naturally, “monitor” did indeed mean the screen. The stuffed animal was also there – or rather, on the desk in front of the monitor. The apprentice had simply misunderstood the question.
The error message had not disappeared yet. Instead, another problem had been identified: Support staff and users can speak the same language and still mean completely different things.
And exactly here begins the phenomenon that IT professionals jokingly refer to as a Layer 8 Problem.
But before we deal with this mysterious eighth layer, it is worth taking a quick look at the seven layers that actually exist.
Seven Layers, One Idea
The OSI model – short for “Open Systems Interconnection” – emerged from the attempt to unify communication between different computer systems. The International Organization for Standardization (ISO) developed the reference model and standardized it in the 1980s. The idea behind it is essentially simple: network communication is complicated, so it is divided into seven layers, each of which takes over a specific part of the work. Layer 1 deals with physical transmission via cables, wireless signals, or fiber optics; Layer 2 handles communication within a local network; Layer 3 manages IP addresses and the path of data through various networks; while Layer 4 takes over the transport of data. Above that, Layer 5 handles sessions and connections, Layer 6 deals with the presentation and formatting of data, and Layer 7 finally covers applications and network services with which the user actually works. Put simply: the lower layers ensure that data gets from A to B at all, while the upper layers determine what happens with this data.
With that, the model is complete.
Seven layers.
Layer 1 to Layer 7.
And exactly here the story could have ended.
But it didn’t.
Then Came the Human
Because however elegantly the OSI model describes technical communication between computer systems, it consistently ignores a crucial component of modern IT infrastructure: the human being.
This is initially not an error of the model. The OSI reference model is meant to describe technical communication. The human was therefore simply not part of the original concept.
For administrators, this developed into a certain practical problem.
Because computers are calculable. Humans are less so.
A computer executes a command if it has been programmed to do so. A human, on the other hand, can execute a command even though they didn’t understand it, execute another command even though they actually wanted something completely different, or click a button that explicitly says “Do not save” – and then wonder why the file wasn’t saved.
Eventually, IT had to find a name for this.
And so, with the mixture of gallows humor and despair typical for administrators, Layer 8 was born.
Officially, this layer does not exist.
Unofficially, it is probably the most frequently occurring one.
What Exactly Is Layer 8?
Layer 8 jokingly refers to the human sitting in front of the computer and operating it.
The term plays on the fact that the OSI model ends with seven technical layers. If a problem cannot be sensibly assigned to any of these seven layers, the cause may possibly – according to the joking theory – lie one floor higher.
With the user.
What is remarkable about this is that Layer 8 problems often initially look like technical errors.
For example, a user reports that the internet is not working. The administrator checks the connection. The router is working. The DNS server responds. Other websites are reachable. Even the server the user wants to access is online.
After a few minutes, it turns out that only the single website the user wants to access right now is unreachable.
So the internet is not broken.
It was just that one website.
The administrator has theoretically solved a technical problem. In practice, he has mainly answered a question that was never really asked.
“I haven’t done anything”
A special variant of the Layer 8 problem often begins with a sentence that in IT is now almost considered a diagnostic procedure:
“I haven’t done anything.”
Experienced administrators know that this sentence should be treated with caution.
In many cases, it actually means: The user has done nothing.
In other cases, it means: The user has done something but no longer remembers exactly what.
And in particularly interesting cases, it means: The user has done something, knows very well what they did, but does not consider it relevant.
Then the actual investigation begins.
“What did you do?”
“Nothing.”
“When did it still work?”
“Just now.”
“What did you do after that?”
“Nothing.”
“Did you install anything?”
“No.”
“Did you change a setting?”
“No.”
“Did you click on something?”
“Just this window.”
“Which window?”
“The one that came up.”
The administrator then opens the log files.
And finds exactly what the user just referred to as “nothing.”
Humans as Unpredictable Network Layer
The real problem with Layer 8 does not lie in the fact that humans are fundamentally incapable of using computers. On the contrary: without humans, there would probably be no computers, networks, or administrators at all.
The problem is rather that humans do not possess a standardized interface.
A network device can be addressed with clearly defined commands. A user, however, can react to the same error message with completely different strategies.
One calls the administrator.
The second restarts the computer.
The third Googles the error message.
The fourth clicks away all warnings until they disappear.
And the fifth decides on the king’s discipline:
They reset the router to factory settings.
Even though only the browser had crashed.
Particularly problematic: Layer 8 with Administrator Rights
For IT security, Layer 8 becomes especially interesting when the user has extensive permissions.
Because a user without rights can cause only limited damage.
A user with administrator rights, however, can theoretically ensure that a previously functioning system faces an entirely new technical challenge within minutes.
Especially feared is the combination of administrator rights and partial technical knowledge.
It leads to sentences like:
“I changed a setting once.”
The administrator’s subsequent question inevitably follows:
“Which one?”
“Don’t remember anymore.”
“Why?”
“Because it said it would be better.”
At this point, a normal support case quickly turns into a forensic project.
Restart as the Last Hope
Despite all scientific findings, there is one measure that has stood up against almost all Layer 8 problems over decades: the restart.
“Have you already restarted the computer?”
This question is not asked by experienced IT staff because they assume the user is too stupid to restart a computer.
It is asked because a restart surprisingly often works.
Why?
Because computers are complicated.
And because humans can sometimes be even more complicated.
The restart has another advantage: it gives both sides the opportunity to emotionally reassess the situation.
The user gets a working computer.
The administrator gets five minutes of peace.
Thus, the error is not scientifically explained, but practically resolved.
Conclusion
The OSI model was created to make the complex communication between computer systems more understandable and structured. Seven clearly defined layers help in understanding technical processes and isolating errors.
However, a small gap exists between the perfect technical model and reality.
In this gap sits the human.
They click.
They experiment.
They forget passwords.
They ignore error messages.
They change settings.
And when nothing works afterwards, they call the administrator and say:
“I haven’t done anything.”
Layer 8 does not officially exist.
For most IT administrators, that is probably better too.
Because if ISO had actually standardized an eighth layer, it would presumably have to make a further subdivision:
Layer 8: User.
Layer 8.1: User with mouse.
Layer 8.2: User with administrator rights.
Layer 8.3: User with administrator rights and Google.
And Layer 8.4:
User with administrator rights, Google, and the firm conviction that they know better than the administrator.
For this case, no known protocol exists yet.
Research is ongoing.
