Which OSI layers are network managers responsible for?

Which OSI layers are network managers responsible for?

We know that some technology and software can perform automated network operation tasks, for example, DHCP in the Network layer and error coding (FEC) in the Link layer. I'm sure there are many more examples.

Based on the complexity of tasks, my question, is which OSI layers, i.e., Physical, Link, Network, Transport or Application (see the OSI Reference Model illustrated for more information) are network managers more inclined to focus their manual operations? Or are we as NMs concerned with all layers equally?

I'm only after a general idea of which layers NMs tend to be involved in, such as VLANs in a MAC address configuration. I'm not looking for detail on each individual OSI layer.

    Requires Free Membership to View

    By submitting your registration information to SearchNetworking.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchNetworking.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

The answer to this question is about as varied as the grains of sand on the beach. However, that being said, there are a lot of core competencies of a network management toolset.

To answer your question succinctly, most network management tasks focus on the network and to a smaller degree the Link and Physical layers. The aim of most network management tasks is to consistently apply a single policy or configuration across multiple devices in the network.

For example, network management software will provide you the capabilities for setting up rules for VLAN management which target the network layers. Additional capabilities include establishing QoS policies, routing protocols, and other network layer configuration tasks. But you would also be able to provision all Ethernet interfaces as 100 Mbps full duplex circuits instead of relying on auto negotiation. This capability targets the data link layers and is highly recommended over relying on auto negotiation. So while the network management pieces tend to lean toward network layer configuration, you may use them for lower layer management. There's a few pieces that they will do with upper layer configuration but that tends to vary more.

This was first published in January 2009