Now he has an S&P message once again from the network management station.
In other words NPM to write a to 10 1 100 2.
You can see this as an S&P message and S&P uses UDP or use a data Graham protocol which is a connection
list protocol.
Unlike TTP UDP doesn't provide reliability in the same way that TTP does.
You'll also notice that the port is Pt. 1 6 1 so the network management station is communicating with
the router on Destination Port 1 6 1 and the rudders replying back from Port 1 6 1 to the ephemeral
or random port number that was chosen by the animus for this connection.
It's important to remember that UDP port 161 is the destination port that the in a mess initiates sessions
too.
In other words the animus or NPM in this case is going to be initiating sessions to routers on Port
161.
You need to ensure that your firewalls or access lists or ACLU permit or allow UDP port 161 from the
enemies to the devices that are being monitored and the reverse traffic also needs to be permitted.
You may even want to configure devices to use a non default port for S&P.
So rather than using the default port of 161 you may choose to use a another port number like ten thousand
one hundred sixty one you would configure that on the device and you would also need to configure that
on NPM so it knows which port number to use to connect to that device for monitoring in both the S&P
get or S&P request as well as the response.
You'll see the OED values and move information that NPM is getting from the device.
So in the request we can see that the values on null and in the reply we can see the actual values for
those of I.D..
We'll explore that in more detail in a separate video where we discuss I.D. maps and other options.