Original subtitles

We're gonna display. How we integrate with Prtg on Ot. Networks and display how that integration will benefit all these operational technology firms out there

Thank you very much, so let me go for the Jenna, for today we're going to talk a little bit about it, and ot convergence, basically because we've seen that there is a lot of people from the ot networks ics kinda side of of the networks, right but

there's also a lot of people joining from it, so we're going to go through a tiny presentation about it, not to convergence.

Why, our ot networks different right? We're going to go through what's pure to, and you've explore a couple of Demos, and then we'll have some time for questions and answers.

So before we get started, just make sure to know that within zoom you have a Q.

And a section where you can just type your question at any time where you have it, and we are going to have this. Q. A.

Section at the end of the Webinar. So just make sure you're using the Q.

A section and not the chat, because if you use the chat we will lose track of that when we finish the Webinar. Right.

So if there is any missing question to get an answer we won't be able to know that.

So please help us out and use the Q. And a one, and let's get started with this.

So it not convergence. Right? It's pretty much known as industrial automation for a long time.

But nowadays you can listen to this. It you know t convergence thing, which basically means, how have we, you know, changed the way that we manufacture things from having multiple people, and this is the same factory.

But you know, nearly 80 years later, right where you had a bunch of different people with doing manual work to get something in this case.

Apples to get boxed and and packaged and shipped.

And how is it now? So? Of course we are all very aware about the number of different technologies that nowadays are present in a shop floor and how this makes it more complex right to manage everything.

So we're not talking only about the proper industrial automation machines.

We are also talking, about, you know, connectivity, and maybe we are talking about servers, and maybe we're talking about applications which are not necessarily on the Plc level or the control level.

But they are in a in an it network. And they are interacting with each other in order to make all these processes fully work right.

So understanding this complexity we see that nowadays there are so many different technologies that people need to keep a a hold on right, and these are related to building technologies.

Right this might be temperatures or environmental conditions in a certain factory or a certain building might have to do with physical security and access restrictions to certain places in a facility.

Right. Then we have everything related to the data center and the data center is really related to services both on premise in the cloud right and everything is gathered together into more and more complex data centers.

Were a lot of technologies are interacting in the course we have all the control layer right?

So we have all the sensors. We have, all the actuators.

We have all the control with illcs with Ipcs with a hard to use right, and we have data systems in hmi.

So the ecosystem is very broad, and what we have seen lately coming from a company that has a lot of you know we we have 2 more than 25 years of experience dealing with it is that it operations.

Have been independent for so many years, that nowadays trying to put them work together, it's just not as easy right?

So operations have kept the plant running well. If historically, it had managed business applications, and these 2 are not necessarily working together.

They are not talking to each other. But nowadays what what has brought them together?

Both it and operations is mainly when you have any system, failures right?

If there is downtime. If there is a problem that's when both operations and it people are are meeting together to try to solve the issue.

And of course this is not the ideal. The situation for you to make friends with another department.

Right? So what has happened lately is all these industrial automation going to networks right or or going to the Internet through IoT, for instance, all the trends like, hey?

You have to do decision-making based in data. You need to use big data.

You need to use, you know, machine learning and predictive maintenance. Right?

So all these big words that we hear every day plus the cyber security problems.

They are pushing actually for closer interaction between these 2 departments and joint efforts.

Right. But this is not had. This hasn't been easy, let's say, because there are different backgrounds, and there are different objectives and different perspectives from both departments.

Right there is also the problem of scalability. Because yeah, maybe corporate is pushing for you need to gather more data okay, which data what do you need it for and many people don't really have a a real answer for that right so controls engineers are bombarded every day with you need

to get more data for us to take decisions, but they don't really get a good feeling about what sort of data and this is creating, you know, scalability issues, because now there is data lakes out there which are not right perhaps properly managed then they don't have the right data and they are just taking

Up storage right, and this has a coast. So all the scalability is going to be eventually a problem.

As you know, the number of technology devices out there continues expanding.

Then we have cyber security, as we say it. So there have been several cases in which people went into networks through ot devices, because ot devices are not meant to have a big robust cybersecurity scheme around them right so of course this is a very big challenge and there is a lot of people

Nowadays trying to figure out the best way around it.

We also have the problem having disparate systems right? And there is lack of visibility across it. And Ot.

So people from it don't get to see what's going on.

What are the problems until they they become a problem right? And the same happens with people from operations relying on it devices.

And then, of course, their it devices are probably redundant.

They are probably made to avoid downtime. But, on the other hand, they also have problems with traffic.

They have problems with resources in these devices. Right? And this the the systems they are using are normally blind to all of this.

So for the it. People out there. We just want to make a little recap about what makes ot networks different right?

So ot is not homogeneous. The proprietary communication protocols are very best right.

There are a lot of them. They are several which are not proprietary necessarily, but they are ot protocols, and they are very different from the it protocols that it network manager knows and it's used to there is a big combination of vendors and technology from different generations because

That's another thing different from what happens in it. Ot devices.

They are made to last, and sometimes you can be having something which was built over 30 pipe or 4 years ago, which is perfectly working fine, and it's performing every single day, but of course, 40 years ago, the the notion of technology the notion of security.

Poor technology was very different in communication as well. Right. So in ot networks you can encounter different generations of technology working together.

Ot devices they are not resilient right? So again the same idea per handling in these older devices was not powerful because they were not meant to really support in communicating these kind of errors.

As we know them today. Right? There are also very tight on resources in several cases, especially when we're talking about older gear.

So of course they couldn't devote a lot of the resources forever handling.

It was just okay. Week restart, and the machine is going to be working again nowadays.

Thinking about it or from the it. Perspective this is not very, very common, and that makes it very hard for some it network managers out there to understand what's going on.

With ot networks, and it makes the devices to be highly sensible.

Right. The other things are ot devices are not necessarily secure.

So again, older devices they don't support authentication.

They don't have patching or operating in a easy way.

So this is a bigger challenge for people when it come to trying to create some cyber security preemer, for instance, or or trying to.

Get, you know better understanding on how can all these devices be secured?

And there have been big attacks to manufacturing in in the past right.

So people taking control over water treatment plans, people taking control over electricity distribution systems, and more things which are critical right for for the countries.

The other thing which is normal in ot networks is that they are aircraft the majority of them.

They are right, so they don't have Internet access. So how do you deal with patching and upgrading stuff?

If it doesn't have Internet access right? That's normally one of the main questions that it people has, and not only that, if you want to get access to these kind of networks, you're required to have some sort of a you know safe space to do that right so like jump host for instance, you

Need to deal with fireworks and Ips, so that you can comfortably and securely access these networks without necessarily exposing them right.

The other thing is ot vendors are highly specialized, so different from again.

It where you have a big number of. You know vendors which are pretty much monopolies. Let's put it like that right.

So you have a couple of different versions of operating systems when it comes to Ot, you might be talking to people creating thermostat.

You might be talking to people creating a robotic arms.

You might be talking to people making line counters. You might be having you know all kinds of different technologies, and not all of these are interoperable because the idea is for them to perform a certain function which of course in the bigger process can can operate with each other but when you look at the bigger

picture of everything that you might have in a single shop floor.

Yeah, if they are not part of the same process, they probably won't be able to talk to each other.

The other important thing here is, there are ot vendors specifically designed or typically designing a bunch of different devices which are or ot. Right?

So which is in firewalls. They would need to be able to understand industrial protocols like Ethernet IP.

Or maybe a propheet, or something like this, an it gear probably doesn't understand these things right.

So here you're required to have specific ot vendors in in your network in order to be fully functional.

The other thing which is different is apologies right? So rotten networks they need to you know, have close to real time communication, because in in a matter of milliseconds you probably can spoil a full full process if there is not the right.

Communication. This is not necessarily the case in it network so it, Edwards can deliver messages and you're expecting that those messages are going to arrive at some point, right but if they are not so time critical the other thing.

Which is very different, and that in low it people's minds is the the fact that there are a lot of ring structures within ot networks to support redundancy right duplicated id where you just you know disconnect and connect the certain plc or a certain device and

That's for an it manager or network manager.

That's just that's just wrong. Right. So they don't understand that Ottawa works require this in order to provide 100% of time or all the processes.

Right static Ips are also very common, and you know there are other different topologies which are, you know, vary a lot compared to it.

So the the main thing that we see here is ot networks are great to production because they are an integral part of production.

Right. So you don't expect to find somebody from it saying like, Hey, I'm part of sales, or I'm part of.

I don't know accounting or something like that. They provide a service, but they are not part of the departments themselves.

Ot networks are very different from that perspective, so from that perspective they are part of production and production cannot wrong without them.

Right. It is very important also to get visibility of the status and providing commercial information to other supervision tools, because there are you. Know.

Ot production, only specific supervision tools out there like state of systems or Hmi.

And these guys are blind to whatever is going on in the network. Right?

They are very focused in production. People might take control over devices.

They can, you know, have a lot of visualization. They can keep historical records, etc.

But when it comes to having information, what's the underlying layer of networking?

This systems have no information right? So, being able to provide with visibility is a a good asset.

And of course everything related to asset discovery, because again this networks are very broad.

They are very big, and they have a lot of different devices within them.

So all the acid discovery documentation and monitoring of these networks can support.

As we're saying here, some other stuff. Some of the big words out there right so predictive maintenance, cyber security, centralized data visualization.

For decision-making, plus other stuff which are looking more simple.

But, on the other hand, allows for people to focus on what's really important right?

Like alerting in the background, so that you don't need to be looking all the time at what's the current status of certain machine and having the possibility to keep historical data well, all of this can support in bridging this it o to convergence gaps that we are

Looking at every day right. So this is where our products come together to support you in in having a better visualization and better visibility of what's what's going on in your ot networks?

So these are 2 products we have the UV explorer on the left hand side, and UV.

Explorer, as you will see, is a topology map.

Configuration backup acid discovery in the documentation tool that will be able to check what's going on in your network and start creating the relationship between the different devices that you have you will have different ways to do that as Brian is going to to show and part of how do

We work together is, you can actually import all the information that you've explorer is creating or gathering from the Ot networks into paste.

Their Prtg and Pesler Prtg is a remote, monitoring, historical data, data, visualization tool that had the capability to talk to both Ot and it devices.

In order to provide you with. You know a single PIN of glass where you can see what's the current status of everything that you have connected to your Ot.

And your it networks. So with that being said, I'm going to give the microphone and the screen to Brian

So he can introduce us to what UV explorer is doing.

Okay. Okay. So thank you for having us today and what I've shared here.

Is our you'd be explore client or agent, that is as described as a discovery an asset tool that can automatically discover an IP.

Network, and provide not only asset data, but also toology relationships, and also dive deeper into the configuration management side of any it or Ot. Network.

If some of you may be familiar with the UV explorer functionality and some of you may not be so we're gonna do a brief walk through about how this works.

And then also show demonstrate how that Plugin is connected through to Prtg

If you're looking in directly at any, do discovery, tool everything that we do starts specifically with credentials.

We like Prtg utilize the smp protocol to discover devices on on your it network, and you we could support anything from Snp: v one, b 2 v 3 through other protocols like telnet, Ssh.

And particular Http, or rest Apis for lots of different environments like ubiquity.

Muraki and Ruckus, and so forth. Once you have these protocols to find what you can do is go ahead and set up a discovery setting where you can define what part of the network you want to explore so you start in a particular seed IP range telling us how

You want to discover whether you want to just ping, sweep, or crawl around the network through an arc cash discovery, and you can indicate what protocols you want us to test to see if those devices support those protocols.

And then we will go ahead and try to discover everything that we can about those devices.

You know in the in the UV explorer world we definitely, want to know as much about those devices as we can.

Not just an IP. Address a Mac address or a hosting.

But what type of device it is with serial numbers. What software it's running, and also how it's interconnected.

But with these discovery settings set up, you can go ahead and run what what we we consider, discover, or scan of the network, and one of the things that's unique about the Ui explorer environment is that every scan you do you can actually save it as a document or a a

snapshot of what the discovery was at that time.

So everything that is captured during any scan can be saved in in our repository that runs here on the agent, and you can keep a time capsule.

Of how everything was at a particular time the reason that we do this is so we can do differences between discoveries.

So if you look here, I have a number of discoveries that are saved here in our lab, and what you'll see here is we scheduled these discoveries to run every few hours so that it will capture the changes of the network.

Then we also have what we call a rollup of how all those changes kind of merge together to kind of give you the most comprehensive view of the network.

But with the discovery settings in place, you're ready to start.

Discovering the network, and what we would do is normally just go ahead and pick those settings and discover everything about the network, and we're going to go ahead and skip that for now just so we can kind of preserve our time but i'm gonna go ahead and open up a previous discovery

Of our lab here, and when you look at when you're looking at a discovery result, what you see here is on the left.

We try to break down every device that we found on the network based on its function on the network.

Now, obviously these there's some generic categories like all devices, core devices and snp devices, but things like routers and switches and wireless controllers, wireless aps and printers, all of these devices will ubiquitous will try to

Categorize so that you can view those separately and utilize them in reports and mapping.

But if you drill into specific things about these devices, you can see we have a listing here to the right details.

All the names IP Mac addresses and vendors, and at the bottom we have details about those devices, so particularly in this environment, like these switches.

You have system information. IP. Addresses and interfaces, bridge ports, and what Vlans are configured on and you can see out here that the UV explorers already documenting what devices are connected out each individual port so you can see here what devices are connected to each

Port, along with the asset and inventory for models, serial numbers, hardware versions, and then detailing all the links and credentials.

Now most people look, look! Look! At excuse me.

Sorry getting the frog in my throat. Here most people look use you the explorer, to not only discover the IP devices themselves, but the relationships, of those devices, so you can see here that UV explore through that simple scan can automatically.

Document, how the devices are connected together, and you can.

You can double click on those devices and get all the details about them, or you can just look at them here in the map and mouse over them to show the relationships based on the connectivity.

Of each port. You're on the on the topology map now, along with each these maps that are auto generated, you can do a number of different things.

You can export those to a documentation tool like Luca, Chart or Visio, by simply clicking and generating Vdx document.

We can build you a topology view of those topology document of those devices, so you can share those with your it.

Organization. You can see here that all the features are all the details of the discovery are available in the document.

Not only you know, we don't want to just do graphics.

We want to do links vlans in interfaces, etc.

But but as mentioned earlier, is like, How does this information get directly into Pr.

Tg, so we've discovered this information here, but through the Prtg Api, which you can define here as one of the credentials in the Ev Explorer environment, you can just go ahead and set up your target server for prtg within Username and pass hash and then

You can also using this export tool you can export everything about what we discovered to Prtg: So if I simply click on export to Prtg, currently I have a Prtg instance just running here with really, nothing in it so I just have my local probe but to them folders

For network infrastructure. So I'm gonna go ahead and I want to.

I'm going to find a place to put these new devices, and I'm going to create a new group which is ping sensors on them by simply hitting export.

We can share all the information that we gather about these devices directly with Prtg, as if we were a native Prtg discovery agent so if I jump back over here and refresh my view here just a little bit, you can see that I am now listing all these S. And P.

Devices here inside of Prtg, with their pink sensors, and some of these are already reporting back the period pulling engines, already picking them up and reporting their status.

Now at this point Prtg is, can run, function completely.

On its own. We've configured it as if it's its own product, and you can just ping these devices.

One of the things that we add along with that export is, if you go to the group that we just exported, you can.

You'll see new 2 new tabs here uvx map and the Uvx report.

If you click on the userx map you'll see that the topology map that was here invisible inside the the UV Explorer agent is now shared with that group here in Prtg and not only is the map there but you can double click on the devices and get all the device

details IP. Addresses, interfaces, Bridge Point and their connectivity.

So all of the information that we captured inside the agent is now available for your Prtg administrators to be able to view from a mapping percent perspective.

Also from a reporting side. You can see asset and inventory of the devices their connectivity.

So if I was looking for a particular network device on the in my repository, I could simply come to this report type in an IP address.

Let's see. Let's try here.

Yeah, 35 60, and I can see how all those connections are.

The the cat, 35, 60, or the if I was to export the whole repository, I would get all the end stations also.

So

Sorry, Mike.

But then going back to our device list any device that you click into here.

You can also see the specifics about it, like, for example, if I clicked into this 35 60, I can look at the Uvx details.

There's all my IP addresses, bridge ports, everything, and asset.

And inventory, and along with that comes the ability to not only discover and map everything about these devices, but also we mentioned that one of the protocols that we support.

Is tell that, and Ssh, and also the rest. Apis as part of the discovery process.

UV explore also over to you the opportunity to capture and back up your configurations, so you can simply, in the discovery settings.

You can specify that you'd like to use these additional protocols and click on the capture device configuration side, and those device, those configurations will automatically be captured during the discovery so during the switches discovery here we can see here that there's

a new tab here called configs, where we're capturing the running and startup configuration.

So with this feature, you can actually tell what we do is we actually capture the running config and start a config at that time, and compare it to the previous capture to see if anything is, changed.

If it has changed, then you get multiple rows inside these environments so that you can go back and compare those.

So you can go back to any kind of running config and see the differences between the devices like this one.

You got a banner change, and so you'll be able to recognize the exact changes.

Here, but those same configurations automatically get pushed to the Uvx details here inside of Prtg those same comparisons and views are also available within the prtg console so UV explorer really acts like an enhanced or a

Discovery, agent for Prtg, with some additional features to enhance the experience of both visualization and configuration management.

Now one of the things that we we're trying to identify for this Webinar is is that how the it and Ot environments actually merge together?

For example, in our lab here we have a few Hirschman here that we also can see directly in our topology map, and you can see here them.

Let's see, there are on the edge of this of this network, and we can identify them and show you how they're interconnected.

Being able to provide a full visibility of how the the network is actually put together, and how your Ot environment is built, but also along with that you can get the details of those individual devices along with their serial numbers, model numbers and so forth for reporting and management but along with that you can automatically use the tools to

say I want to capture the config from this device.

So some of these devices support S Ssh. Some of them support things like Http: so you can simply capture those using different protocols, and you can do that for example, directly.

Right there. So by simply doing that we've captured the configuration from that horseman device, and now it's part of our repository.

And when we export those device, that device information is automatically synchronized with the Prtg environment, so that everything is kept up to date.

One of the key aspects of the way our agent interacts with Prtg also is not only just exporting the maps.

In the visualization visualization, but we also provide a number of specialized monitors like, for example, the config monitor.

This this config monitor allows you to come in here and say, Well, I want to set up on a schedule, say every 5 min, or every 10 min or every day.

I want to go through a number of devices, and you can see here that we're not just including the Ot environment, but also the it infrastructure to capture the running config, and then you can by simply doing this one monitor.

Here and then on the event side you can click it so that it will actually send those configs directly to Prtg when you do that, then it'll automatically keep these configs up to date both in this repository.

But also in the Prtg repository.

So it's a very specialized monitor that gives you the fig capture, capability, but also a notification mechanism so that we, can when you save it, notify here we will actually place a sensor on these devices inside of prtg for monitoring the config so if the config

Ever changes. You will actually see an alert directly in Prtg, and it will use all the alert notification mechanisms that are available for Prtg to show you colorization SMS messaging email and so forth to be fully aware of any changes from the configuration side on

Those devices along with that one of the key features I I fail to mention when you're dealing with any kind of it environment is when you're dealing with the mapping when you create these groups dependency mapping is a challenge and also key.

To your awareness, challenge and also key to making sure that you are aware of the the outages and where they're where those breaks are.

So edit when you export these maps, you can actually create what we call dependency mappings, so we can.

I'm gonna go ahead and create a different map this time with just switches to.

But I want this time I'm gonna go ahead and create dependencies, so that I know that if anything was ever go down on a production, line I know where the break is, because I know the dependencies of these devices and how the workflow gets to the end.

Station. So I simply do that with Ping. You'll see here that I can.

I'm just gonna go ahead and create a new group and their sensors.

And then jump back over here to Prtg, and just like that I got another group, and if I look here at the dependencies, you'll see a tree of all the dependencies.

That we've we've

Having a hard time scroll. You can see how we've mapped all the dependencies of those devices.

So, if anything in that production line was to go down, you'll actually get a real time notification of where that break is, and then you can start your troubleshooting from there that that process sometimes can be very tedious and difficult but with the topology information that we provide we can automatically.

Do that and maintain that for the Prtg.

Environment, I think. Lastly, here I wanted to also articulate on the on the configuration side, not only do we provide the configuration backups, but we also provide the ability to create what we call scheduled tasks, UV explorer can be

Scripted in a way that you can identify a large set of devices.

You know any type you know from your mark from your discovered devices you can identify which devices you want to script to run on, and you can go in and define you know what you want to do on that device you can see here that we have a script.

That? Says I. Wanna just log in enable, and and then run a few commands.

These commands can range from anywhere from capturing data, but also changing the configuration of the device or uploading configuration snippets to your particular.

It, or ot devices. So the the agent can both pull and push configurations to your it.

Environment and do it on it a multi device scenario, so that you can schedule.

Maybe maybe at night you want to go ahead and change snmp passwords, or you want to change device passwords.

You can go ahead and schedule us for change on a pick.

Your schedule at certain day and time you can write a script that'll automatically do that, so that you can automate the maintenance of those devices and kind of streamline how you interact with the configurations of your your it infrastructure I know

that's kind of a quick and yeah. High level view of everything that we can do.

Obviously the goal here is to bring everything that you know is critical to an it environment in both device discovery, asset management, and topology, along with configuration and merge that into the monitoring infrastructure so you get one comprehensive view of everything that's

Running on your network as you can see here, these maps are already showing the the monitoring status.

Here that Prtg is providing on the on the UV explorer maps, and once you have that, then you can schedule you can step back to your UV.

Explore and set up your scheduled discoveries so that you can run your discovered discoveries on a particular schedule, and then also export those results directly to Prtg so as to synchronize all the information that you are seeing here with your UV explore

Agent, so I know we wanted to leave some time for question answer.

So I'm gonna go ahead and stop my presentation to this time and hand it back to David.

But we can. If there's questions we can go back to that.

At the end

No

Thanks, Brian, so I am going to elaborate on the pure Tg.

Yeah, there you go.

Site, I believe you can see the screen there right? So as you've seen, we can use UV networks as one of the pulling agents that will provide us with information from the network and also the dependencies and the creation of the maps and getting access to more information from the devices right so what

happens next. What happens when you was? You have all this information already mapped out by UV networks.

Well, Prtg is, as I said before, remote monitoring solution that has the purpose of, or in remotely monitoring the conditions of your devices.

Connect to networks. This could be it. Networks, ot networks can be.

I IoT devices IoT devices connected to you know 0 G.

Or to Bluetooth, sending information to a certain gateway, because in the end our platform is Multi plot of protocol right so we can deal with stuff like Snp or Wmi or Ssh right for the it portion but we can also deal with the other particles like MoD bos or

Opcua, or mqtt. Right? And we can also integrate with a bunch of other gateways that can support in the translation of different protocols into one of the protocols that we can natively support so as you can see here what we have is different you know locations.

We have a local probe. We have couple of remote locations and for the sake of this demo we have a bunch of different groups here that allows us to show what kind of things can be monitored with prtg so we might be looking at medical devices.

We might be looking at servers, both virtual or physical, right.

We might be looking at certain operating system aspects.

This could be Wmi. This could be different distributions of Linux storage is the network part that I'm going to open look into more detail.

Everything related to critical power, as well. So battery banks.

You might be looking at ups, or Pdus, or you know our pps.

All everything which is actually supporting the critical power in your facility.

Then we have environmental conditions as well, so connecting to sensors providing with temperatures, humidities, all this kind of of things, vibrations as well.

The security portion is related more to cameras and access controls right, which are also relevant for factories.

Then we have some cloud services, IoT things, you know, printters as Brian also showed critical applications running.

Corporate websites right? So the idea is to show that there is a lot of things that you can actually monitor with Brdg, and I'm going to go ahead and just click on the ot switches group that I have here because as we mentioned before you have a bunch of different vendors right which

Are not necessarily the Cisco's, or you know, like the HP.

Is that you are finding in in it here. We might be looking at stuff from Rockwell automation.

So here we have a stratics, 5,700 right, and the kind of things that we can see in this, and the switches are not only related to traffic right because, of course, traffic is going to be very important you want to be looking at your up links you want to see whenever you have a

Bottleneck in one of your interfaces, and you will be able to look at all that information.

Historically, because this is something very important. One of them main features that Prg has.

You will be able to export the data or keep the data in our database for a year, as a default.

But you can even extend that right. So you can make it to 3 years, so that you can get long time data in order to you to then analyze it later on.

You are going to see stuff like a traffic. Total traffic in traffic out.

You can see what's the the information looking like for the last 2 days?

30 days. This is a very bad example, because it doesn't have a lot of information, but you can see what I'm saying right so 365 days and from there, you will be able to look at okay, rhetoric data you can go to the detailed view of saying like I

Wanted to start this day at certain time our in minute right to go to another date.

I'm our in minute right? So you can export this information.

Using Xml. Or Csb. In case you want to.

Use this for further reporting or doing something different right? And as you can see here we are compatible with in this case it is mainly snmp which this ot switches are are created are are using right so Irishman is providing with similar visibility we can see you know system

Up time, and you can see traffic, etc. But something I I forgot to mention is, if the device are is compatible with providing with specific aspects on the health of the device like it could be the power, supplies or memory, or CPU usage or fans or temperatures you can also bring

That information into Prtg, and get alerted whenever there is any problem with any of the physical layer of your switch, you can look at other kinds of data like Armon.

If the the switch is compatible with that, so that you can see what kind of packets are going through that traffic.

So it's not only about you know volumes.

It's also. What is it? Right? And if the switches are compatible with other stuff like could be Netflix, for instance, then in the same tool, you can also get access to see what are the connections looking like for for that traffic right so you can check and click click, on top connections and from

Here you will see first IP. Source ports, destination Ips, and destination, ports and protocols.

It's, etc. Right? So how much a traffic is created by each of these connections so that you can keep an eye on who is using the majority of the traffic that you were getting in those switches right good to go back here, and you will see some other.

Very well known brands that we have been able to to be compatible with.

So maybe marks a Siemens phoenix context, which is right.

Cisco switches. In this case industrial ethernet, which is, for instance, and the kind of idea here is, you will be able to get information.

What is the traffic looking like? You can also see something which is interesting, which is the anomaly detection.

So our tool is going to be looking at the baseline of traffic that you're an ot networks using and whenever there is any kind of unusual behavior which could be there is too much traffic or to few traffic right for a certain day in the week we are automatically going to

Notify you about that. So without you needing to set up any thresholds or anything, or even reaching the thresholds that you probably got already there.

You will be able to see any anomalies going on in your traffic, and the same happens for maybe servers, that you have connected running applications critical to your production.

Process so we will be able to tell you hey? The CPU is too unusually low or unusually high for this weekday at this time. Right?

So this is important because it can provide you with this ability of a certain problem that you might be encountering without you even knowing about that right.

Some other stuff which is important is this is not over when you get to the switches right?

There is another, or or multiple different layers below the switches.

Which could be, you know, Ipc: so if you're we were moving into the control layer, you probably will be looking at, you know.

Ipcs, which are controlling certain processes in your production line.

So you also want to make sure that you have available memory available. CPU.

For this for this process is to occur right. You probably would be looking at, maybe gathering information directly from the Plcs.

And for this, if the Poc. Is our compatible with either a MoD bus or opcua we will be able to connect to those specifically in other cases we probably would be able to connect using third-party tools like you know prodigal conversion.

To into opcua or prodigal conversion, need to MoD bus, and from here you will also get access to see what is going on.

In this case with a sematic S 7 Plc. Here, so that you don't only get to the point where you see what's what's going on in the traffic and the switches.

But you can go a layer below that and see or right.

Oh, there's stuff that is very important that you can see.

Here is okay. You have certain temperatures. You probably have a certain, you know, counter in the production line.

You want to know whenever things are not working the way they should. Right.

So as you can see temperature in this case, then have different thresholds, so can be bad that it is too low. It can be bad that it is too high.

So changing this threshold is very simple. You can do that by enabling alerting, based on limits. Right?

You can create your own thresholds, and then leave Prtg working for you in the background.

Once you have that we're working for you. What you can create are the different rules, and these rules will allow you to see, you know.

How do you want to handle those notifications? So if a sensor in this case any metric and a signal that you are gathering from your your devices is in a certain state which could be error?

State, or warning state, or unusual, you can set up, or how long does it need to prevail that situation before you are alerted, using one of the different methods that we have, for that and in this case, It's important as Paul mentioned before or sorry Brian mentioned before we have different ways to

alert for conditions which are out of what's normal. Right?

So you have. Email you have SMS compatibility with different providers for uss.

You have, you can execute actions or execute programs as well.

So this couple of notifications will actually allow you to take control and support remediation of any problem that you probably have.

You can do some other it stuff here, but you can send push notifications to your cell phone or somebody cell phone.

You can also use either teams or slack in order to create groups of people which might be able to support insulting the issue that you are having right, and there are these couple of of notifications here as well in case you are using either Mqtt.

Or Opc. Way. Now the Opcua notification is important, because, as I mentioned in the beginning, there is a lot of nowadays.

At least you can see an increasing number of system which are compatible with Opc Ua.

Because Opc. Always trying to get, you know, recognized as a standard for manufacturing, industrial orange.

So what happens? Is, you can actually support the visibility of possible problems that you're having in the networking layer for your production teams.

By creating opcua notifications that we'll see a notification that can then pop up in this data system, or in an Hmi, which are compatible with opcua telling people people in the shop floor hey?

You probably are running on a failover of the switch which supports this machine.

That you are manipulating at this point right? So you can provide information and anything that you have your say more it kinda in the monitoring into the production, tools for making sure that things are going well, so provision tools like state systems right so this is very important and we are moving a step forward in this case

Because we are creating our own Opc. Way. Server. That will allow you to extract information from Prtg.

Take it to another Opc. Way, server. So again, let's think about a stay the system, and that's K.

The system wants to be, or that the people looking at the data system they want to know what's going on with a certain you know critical application.

That's running in that shop or they don't have access to any of that.

But now they will be able to do that on demand, not only whenever there is a wrong condition, right?

So all these alerts are very important, because they can support in bringing information from it into your Ot tools as well, in case you have them, and if you don't, we do provide with data visualization right so here there is an example of how could it look like to have access to see you know what's the

Current state of an ot switch different database servers, perhaps different workstations which are in the shop floor.

Maybe some hmi as well, and in different Elc.

's connected to it. So in this case we are reporting on status.

We are reporting on traffic. We are reporting on whatever is important for you and for the people looking at the specific dashboard could look like this as well, right.

So different ways of visualization in the end. So here we have a diagram of a certain production line in this production line.

We'll have information from whatever you are monitoring on top of it.

So it could have information on. You know. Production, units, or depictive units and versus good quality, units, and things like this so what we're struggling to to or try to get is all disability between it and ot so from the lowest level of the sensors and the

Actuators through the use of MoD. Bus opcua, and the converters that can give us information from, say Profanet or ethernet IP.

Into opcua, we are able to provide information on the the robotic arms, and very much anything that's connected on the lower level, and then we are also able to provide with information on the control layer.

As we see you can also monitor your your visualization layer, pro t. Right.

So if you have orchestrators, if you have data systems, if you have Hmi, you can also see what's going on with them and then go all the way to your manufacturing execution system and your erp as well right so in this case we have some sap

Sensors here. So the idea is you can get access to see not only what are the conditions in all the layers, but also track information if needed.

If you need to eventually have information and temperatures and your cooling system, or an overview similar to this for your data center in the shop floor you can do that, and if that doesn't work out for you I mean this case you have you know power, and then you have all the operations for different

Devices connected to it. But if that doesn't work out for you doesn't matter, because you have the possibility to create other visualizations like this right?

Where you can see what's going on from. You know a very simple way, even though not necessarily getting to the details of you know the traffic, etc.

So here you might be looking at the different errors and problems that you have here right, and you might be looking at.

Okay. I have a certain certain water pressure which is a 126 psi. Right?

This is above what I should have, so the idea is, you can jump from the visualization in case you don't have this data system.

We can provide you with visualization of the data that you, your environment is creating right.

And this is very important. Because again, just think about the possibility of using this tool to get, you know, access to just store this data for a long period of time without being charged for that that is very important.

Because then then you can use that data for further process later on. Right?

So the last things I want to show before we go for a. Q.

A are a couple of resources that I can encourage you to look at.

Some of them are the success stories from customers, I mean.

You have customers from all over the world. We have some from the Us.

We have some from Latin America. We have many from Europe.

Of course. Right. Some big names are there which are using our tool like Rex Roth from Bosch or Siemens, for instance.

And the other thing is you know there is a video here of how how important it is not to only take care about the network, but everything which is connected to it.

Right this case. A server running a curriculum application on the mining side.

We're loading trucks was having a trouble, and they were able to figure it out by actually monitoring that which was completely out of this cope of it, because they were not part of this kind of you know production.

Process. So with that being said, I will stop sharing my screen.

Now again, and we are going to go for the Q. A.

Session, and I saw that we already had some

Some questions. But let's see what we get.

Well in the meantime I'm going to get this here, because then you can get access to holds or my email address until you want to get more information afterwards.

But we some well, we had some questions here about you actually pull.

And there is quite a few. There's quite a few good ones there.

Yeah, it was good. Sure. I think one of the ones that were most important.

As far as set up in those attending this Webinar was as from an anonymous attendee.

But what is the typical deployment effort to configure application and various network devices on the network to report back so pretty much?

How long would it take to set up UV explorer and prtg on an environment and get it up and running it's a good question, I think, on our side.

It really depends on how big your network is what you're trying to do for UV explorer.

We can have that up and running probably in 7 to 10 min, and discovering looking for different devices what we can find at that.

Point it's troubleshooting. It's it's exploring parts of your network that have protocols or don't.

Some of your devices may not be set up correctly.

You have already answer several questions in Brian. Yeah, you would want to read them

We have to troubleshoot that as far as a Prtg side.

I think, David, you can speak to that

Yeah, I mean having a the basic configuration can take less than maybe 30 min, and then it's a matter of creating, you know the proper.

The proper things right. So how do you want to deal with notifications?

How do you want to deal with? You know Overall Dashboard to etc.

But it shouldn't be an effort of maybe more than 2 weeks to get everything you know in place the way you need it

We have some other questions here. How did the business process insert the urine prote, as shown in the day?

I believe this is separately configured in Prtg.

The business process sensor actually is a way in which you can bring information from multiple sensors that you have set up independently right.

So the idea is, whenever you're looking at a full service that you're providing in your in your environment.

Do you want to? Let's say you want to see specific production line which has a bunch of different plcs, and perhaps it has you know information from the sensors and the actuators.

That you have there. But altogether you are looking at a single thing.

So in that case, what you do is you just ring information from the multiple individual sensors you set up a hierarchy for them, you set up a certain weight for them.

So you can tell if I don't know 50% of these sensors are running.

Then my my my services running correctly, and it's not going to be stopped.

But if I have 51% of them not working, then I'm in trouble, because I won't be able to provide or deliver the service that I have.

So, Shankar if you want to learn more about the business processors, I'm definitely going to send you some literature about it.

You can see some, you will be able to watch some videos, also on Youtube, on how to to set them up right, and if you still have any, questions, just let me know and we can get over that

And I see that there are at least another 7 questions right.

But I guess given the the time, probably we won't be able to answer them all here I mean.

Brian has a answered several of them. But what I could encourage you is, if you wanna you know get access to more information either about UV.

Explorer, or Prd. But you can see our our email.

Address is here in on screen right and just send us a note.

We can we'll be glad to reach out to you.

Maybe set up a meeting or whatever is needed, so that you can get access to know more about both tools, either separately or working together, right. And in any case we are going to get access to all your questions and any missing answer will be sent out by email

Sounds, good

Okay. So I guess we can wrap it up then.

Well, Brian, yeah.

Yeah, yeah, that's it's great. Thank you, David, for having us join as a pleasure to to talk with Prtg Prtgs.

We've been integrated with you guys for 6 years, and you guys are one of our best partners.

We appreciate the chance to join and co-host with you on this, and talk about ot networks, and we're looking forward to the conversations this sparks with our our viewers and also the rest of the network out there that's having issues here at ot we're here to kind

Of help with that and help. These companies kind of address these new issues that are popping up

Awesome. Thank you very much, Paul and Brian, for the presentations likewise we really enjoy working with you guys, and we really appreciate everybody's time today to join the Webinar.

And learn a little bit more about. How can we support you in your daily efforts with ot networks?

So have a very nice, hey, everybody, and see you next time