2.1 Network Management

Notes

APIPA - The windows default IP, means that you have a DHCP client that does not have access to a DHCP server

• Ex. 169.254.x.x

Network Management Lab

The prerequisites for this lab included all of the previous setup we have done, as well as setting up web01 without joining it to the domain

Firewall Setup

The first thing we had to do was enable the SNMP services on the pfSense firewall, I used the GUI and accessed the SMNP service page through the "services" drop down menu. From there I was able to set up the SNMP service on the firewall, using:

• Polling port 161
• Set up a community string
• Bind it to the LAN interface

Then I restarted the SNMP service with the restart button at the top

Nmon01

I had to go through the basic setup the same as web01 for nmon, setting the IP address to the one seen in the IP address entry. To install snmp services I used the command:

• sudo yum install net-snmp-utils

Then I queried the firewall with snmpwalk -Os -c [community string] -v2c fw01-elizabeth system

Web01 SNMP server

For this I had to use the command: sudo yum install net-snmp-utils net-snmp

Next, while preserving the original config file, I made a new /etc/snmp/snmpd.conf with the following lines the only thing in it:

• com2sec myNetwork 10.0.5.0/24 [community string]
• group myROGroup v2c myNetwork
• view all included .1 80
• access myROGroup "" any noauth exact all none none

Saved the file, enabled and started the snmpd with systemctl enable snmpd and systemctl start snmpd, also checked the status. Next I needed to let the port through the firewall with

• firewall-cmd --permanent --add-port=161/udp
• firewall-cmd reload
• firewall-cmd --query-port=161/udp - used to check port status, came back "yes"

I then queried web01 from nmon with snmpwalk -Os -c [community string] -v2c web01-elizabeth system

SNMP on AD and MGMT

Next I needed to add snmp tools to AD and MGMT, both were features

• MGMT got SNMP-Tools under remote administration
• AD got SNMP Service Feature

At first I did not have all of the things checked that I needed to, so I had to go back and install more things, but it did eventually work

To enable remote management on AD I had to use powershell (on AD, from MGMT) with the following command:

• Set-NetFirewallRule -DisplayGroup "Remote Event Log Management" -Enabled True - This edits the firewall rules so I can manage AD from MGMT with Computer Manager

SNMP Service Security Properties on AD

Using Computer Management for AD, under services, I had to find the SNMP service and go to the security tab.

• Add [community string] to the accepted community names
• Change the "accept SNMP packets from this host" to only have nmon's hostname listed (nmon01-elizabeth)

Then restart the service

Query AD from NMON to test

[TO BE CONTINUED]

Research

Below is the research I did on 3 topics from todays class

SNMP Expanded

Since I still didn't fully understand SNMP I decided to research it a little more so I could understand it better. I found the Simple Network Management Protocol is an Application Layer protocol in the OSI Model, which is layer 7. It most commonly uses UDP, which is faster but does not provide error-checking when moving data. SNMP can do many things regarding the configuration of networks, and some of the ones I wanted to expand upon are:

• Set Request - can set a specific configuration on the client computer, this includes sending commands to the client as well
• GetNext Requests - sent to agent to find the values of the next record in MIB hierarchy
• GetBulk Request - Sends multiple GetNexts to retrieve tables of data

I found it interesting that SNMP can be used to retrieve more than management data, it can also be used to configure specific things on clients

Source: [thousandeyes.com](https://www.thousandeyes.com/learning/techtorials/snmp-simple-network-management-protocol#:~:text=Simple%20Network%20Management%20Protocol%20(SNMP,devices%20in%20Internet%20Protocol%20networks.)

MIB Expanded

[]

Topic 3

[]