hello everyone I'm should become taker marketing manager clapping thank you for joining us in our closed multi webinar today we will be discussing about getting started with ServiceNow discovery and how is the first step towards spread the better IT operations management so now would you like to share your screen at the point should you just control me if you are able to see my screen yeah thank you so here's the agenda I'm going to take a few minutes to go through housekeeping talk about flowed followed by the presentation and finally the Q&A next slide please this webinar will be recorded and you will be able to access it later for Q&A you're on mute if you have any questions please use the Q&A section in your screen control panel and our panelist will answer them if you have any questions that are not directly related to this webinar please email me at Hsu the Expo Center for more sales at closed intercom our social media channels are listed here you can access a free webinar set up so Channel next a little box wrote we are so is my apartment since 2011 based out of Santa Clara very close to the service from headquarters we are a full-service now shop the 250 plus customers for hundreds of implementations and executed projects globally next slightly in terms of services we provide end-to-end services our focus has been on TSM and use the portals and HRSD our panelists today is gonna turn on a slightly the prana is a technical consultant at closing and run off thank you for joining us I will let you take over Thank You city for the warm welcome so guys let's start off with first what we're gonna cover in this session today so firstly we're going to talk about I Tom then we'll just review our concepts about CMDB then we'll start our discussion on the discovery and mid server then we'll have a quick demo of how we can have like how we can discover a particular C I'll just show you how we can discover our own system that we are using and then we will talk about some of the best practices for implementing discovery and then after implementing discovery what's next after discovery so that's what we're gonna talk about today so firstly what is ID on so I see item or ID operation management in ServiceNow is a suite of application that work together to automate operations management within your organization so these are the certain applications that are part of item discovery is their operational intelligence even management service mapping orchestration and cloud management so in easy terms we can say item as an umbrella term for these applications so coming to a short description of each and every application so what is service now discovering so service not discovery helps us create a single system of record for the IT infrastructure so basically it helps us create all the records basically it helps us from the CMDB that we're gonna discuss in the upcoming slide then comes to operational intelligence so the service no operational intelligence proactively identifies anomalous behavior in the IT infrastructure before it causes service outage so it's its main goal is it proactively identifies the anomalous behavior and then comes original ilke management so service not even management reduces they even floods from monitoring tools and provide a single dashboard to proactively identify service issues so the one of the like best part of event management is it integrates with the different monitoring tools so that it helps us like like it provides us a really good dashboard which can be used to monitor all the activities in our service then comes the service mapping so service mapping Maps there between IT components and business service in a dynamic environment so discovery and service mapping are very much linked a lot of people get confused when we talk about discovery and sell is nothing do you think it's both are same but it's not both are totally different so in the end we're gonna talk about what is the difference between discovery and service mapping so then comes our service now orchestration so service now orchestration is like it's it just orchestrates our or automates the IT processes on a third party system so it eliminates a manual task and remediate service issues so far so for example when there is a new hire in the company so as soon as the new hair is there we should create an LDAP account for it so there comes orchestration so we can use the out-of-the-box activities of orchestration to do all that stuff to create an account directly into the server so that's that's a manual job but we can automate those things up then comes the cloud management so ServiceNow cloud management delivers a cloud resources through self-service and reducing businesses and managing costs so it also helps us managing all the services in the cloud right so today so we are going to talk about discovery application and so these are the certain benefits of item solution if you go from a service new items initiate enhances the service visibility it improves service availability it increases service agility manages hybrid clouds and in the last it leverages ITSM investment so the most important one let's talk about the fifth point leverages ITSM investment so basically service man integrates with the current ServiceNow ITSM solution so that it provides all these like it provides us in eliminating all the service outages and managing the hybrid clouds so all these are very important stuff of ServiceNow Arita so now coming to CMDB so ServiceNow CMDB 10 thought of as a database containing configuration item where configuration items are the infrastructure components they can be hardware or software required to deliver a service the main key tables in the configuration CMDB is the configuration item table and the see a relationship table so a lot of people when I talk about C and D a lot of people think it's just a large database but it's not so the ServiceNow approach is to extend the general configuration item table to create a new table so the new table we call as CI classes so we're more granular information can be stored about the CI so that's one thing that service they provide so a lot of people think ok we have the CMDB CI table is there which will contain all the CI as and all so it just large database but it's not so it's divided into the sea ice for example you can talk about hardware so hardware is a table that is extended from CMDB CID so all the hardware things charge go under it then hardware can have like servers or they can have Linux servers Windows servers Reuters all these things are there then [Music] another table for application service LVL main servers are there or the applications are there so all these things are stood in the particular classes or we can call it tables then the relationship so this table holds all the relationships between the CIS so for example when I talk about mail server so mail server is part of the window server so it runs on that so all this relationship that mail server runs on windows server all these things are stored in the relationship later basically it shows all the relationships between two CIS so so now coming to the benefits of cis emt-b so it provides a single data model so ServiceNow CMDB uses a single data model to manage all configuration data this enables it to standardize process and data as a result of which you don't need to update configuration changes in my little sister so this is one of the most powerful thing in CMD that it provides a single data model where you don't need to update in multiple systems go into different different places and update all these things so that is one top-quality thing of service now CMD then comes the ServiceNow CMDB automatically propagates these changes across related systems thus enabling a single system of Records with minimum redundancy so as you know on the incident form we have the C and BBC I field where we have like the particular CI record is there so if there is any update that happens in the CI whether it's in the name that will reflect in the incident table also so that's what is the power of CA ServiceNow CMD so now the second thing is the visualization and reporting so it's service mapping functionality provides a concise graphical view of infrastructure with relationships dependencies and lot more stuff and it has a very powerful reporting engine which enables users to generate - force reports to be distributed on regular basis so the thing is that when like and then we are maintaining a large infrastructure so we get not many challenges but those challenges can be reduced if we can visualize our stop what is happening so that's what the ServiceNow CMDB provides it has its very powerful reporting engine which helps us and it's service mapping cabinetry that's part of the item which helps us visualize all these ID infrastructure with its relationships and dependencies and lot more strong and lasting it's all in the same platform so like you have the other IDs M solution you have the customer service management you have discovery service management service mapping management orchestration all these things are part of the same platform so it provides an integration between all these things so that's why it's very easy to go when you are opening an incident you can go and select the particular CI and because it's part of the same application so that's how easy it becomes so so if you say like like what what is in like CMD final thoughts on C and E it helps key decision-makers to quickly make accurate and informed decision it will help support team to investigate and resolve issues in a timely manner so that's what CMDB provides to the customers if it's implemented properly so coming to now discovery so ServiceNow discovery also known as infrastructure and application discovery integrates the enterprise network for recognization recognizable devices and application a host so because ServiceNow is normally hosted in a datacenter so instances lack the ability to access enterprise network and subnets that directly so it must delegate the work to the MEP server so basically so we know that CMD contains all the sea-ice that are there now there are different ways populating the CME one way is like manually but as the infrastructure are very big so the manual updation it's not possible we can also so maintaining that manual is also like a challenging thing because the infrastructure keeps on changing every it's very volatile it keeps on changing so there comes service not disturbing so basically what it will do it will discover all the devices in our infrastructure so making our job much more easy and once I'll show you the demo you will just see how easy it is to discover any device without like without without without need to worry about like the servers and other thing so it's one thing and now coming to what's a mid server so a mid server is nothing but management instrumentation and discovery it's a lightweight Java schedule Java process running under a Linux or a Windows platform that resides within the enterprise network as the mid-surface resource consumption is very low and definitely it's controllable so dedicated hardware is usually not required its sole function is to execute work request and return the result to a service constant for processing in effect a mid server can be considered a remote extension of service for instance on an enterprise neck so basically as I talked before so ServiceNow is hosted in the cloud right so it doesn't have access to any company network any private network so it needs to delegate its work to some other system that is called as mid server so mid servers only job is to execute the work that's it that is sent from ServiceNow to the mid server and return there is results from of that work and it's like it's very lightweight so it doesn't require a lot of like it doesn't require a dedicated hardware to run this thing so that's what a mixed server is and connections are initiated from the mid server inside the enterprise firewall no inbound rules from the cloud instances are required and all communication use soap on HTTP port 443 meaning that all the traffic is encrypted and usually no special firewall rules or VPNs are required so this this is a so mid server all the communication that is happening is very much encrypted and protected so in respect of security we don't need to worry about the security of mid server that maybe that I can move out of it because all these things are encrypted and coming to now we know what is discovery now we know about the mid-summer so now how ServiceNow communicates with the mid cell so it communicates with the mid server using the ECC queue so ECC queue or external communication channel is a simple database table it's just a simple table like any other table in your system but unlike the other tables in the system that ECC queue is normally queried updated and inserted into the system into by other sister so this is like totally managed by the system so mix server will update this table as well as ServiceNow will update this table so all these things happen so it's in the middle of mix server and service now it's a place where the communication happens from mid server to ServiceNow or ServiceNow to myself so each record in the ECC queue is a message either from the ServiceNow instance through some other system as an output message or from some other system to the ServiceNow instance as an input message ECC queue is the normal connection between its ServiceNow instance and other system that integrates with it it it is also a point in ServiceNow instance where mid server used in discovery on orchestration Amit management and some other integration connect together so that's what ECC queue means so basically it's a middle thing between ServiceNow instance and the midsummer so this diagram will show you like it will help you visualize how it works so basically this is a ServiceNow ECC queue is it just a table and there are outputs and inputs that are there so like ServiceNow send some output to the mid server and in return mid server processes those things and it returns they so that's what it does so now now let's talk about how discovery works with the use of MEK server so first step is like instructions are placed in the ECC queue as an output product so all these things like the whatever the activities the need should be performed on the infrastructure by mid-summer data place as instructions in the ACC queue then the mid server pulls the ECC queue and finds the work that needs to be done that is one thing then on the basis of like what type of probe it is it can be a port scan classification identification and exploration poll I'll talk about this phases later on so depending on those ports so it will just interpret the particular infrastructure and get there is a desired result for us and then the main server report responses today to the service now as an input record on the ECC queue and in the last service now processes those inputs using sensors and it will just populate the CME so one example can be like you have a Windows Server so the mid server is installed there so what it will do is like that when the phase like in the first field like ports countries that's the first phase of discovery so this is an probably sent so that is just as an output it is sent to the mid server then what it what has happen is like after it is sent to the mid server mid server processes is that probe and performs the activities for that particular problem it returns some data like in the form of input in the ACC q ServiceNow picks up that input processes it and perform the particular like processing on it and just populate the particular CI or whatever the resultant is so that's what this particular how amid server works fair discovery so now question comes up where mid server needs to be installed so ServiceNow is normally hosted in ServiceNow data center and it does not have the ability to access enterprise network directly so this is what we already talked about like it it's like it's resides in ServiceNow data center so many enterprises have multiple networks often separated by slow van lengths or security barriers and discovery needs to access to all of them so mid server can be installed behind the company firewall annoying for communication between service now and rest of the country network so it should be installed behind the company firewall so that it can perform the proper communication between service now and the in front so and one more thing that I just want to add on it is like or as I talked about like whatever the mid server is it's very much controllable so we can just enable and disable a lot of stuff in it so in terms of security it's very secure so now comes the credentials so credentials such as usernames and passwords of certificates are required to be an access to a computer or network device for service or discovery so the platform shows these credentials in an encrypted field on the credential table so basically like it's very simple like if you want to go into ServiceNow instance you need a username and password right similarly if you go into any Windows Server device or Linux device or SNMP device so you need some credentials for it or some certificates so all these things need to be provided to the ServiceNow instance so it is stored in a even in an encrypted format so that and it's a one-way encryption so what what I mean my one-way encryption is that this thing cannot be decrypted again without like like because there are certain things like you might be seeing two-way encryption on one-way encryption two-way encryption can be decrypted using the code and all but one way can't be decrypted like that so that's how much securities and coming to the credential part there is always a best practice for if you are either a ServiceNow professional services or if you are service the partner or if you are implementing the service now for any client ask the client to enter that credential don't enter yourself ask them to enter it so that if the it's like is they are entering it so it's the best practice that we should always fall over the credential so there are different types of credential in service now one is the SSH credential is there then we have the SNMP is there then Windows reom where same credentials AWS so SSH credential is basically used to discover the UNIX or the Linux devices the SNMP credentials are basically used to discover the devices that run on the SNMP protocol windows are used for Windows devices and VMware are used for VMware vCenter is running on Windows machine so and same credentials are used for storing devices and AWS are used for the Amazon ec2 web service environment so these are the different types of credentials that are available in ServiceNow so you can use any of this depending on your infrastructure device so now comes the four different traces of discovering so these are the port scan fails the classification phase identification and exploration so let's start off with the port scan phase so now like we know about how discovery is like it will go to the system to the infra and get the particulars yet through the mid server and ECC queue but what is the process that made it what is the process that discovery follows so when discovery is initiated a single suzanne probe is launched and place in the ECC queue as an output and scanning for the open tcp ports on the network connectible note so so what it will do is like the first thing that is there is the suzanne it will go to the system to the infrastructure and just check whether they were the infer where the particular device is responding on which particular port the device is responding for example like the unix unix based devices usually respond on port 22 and windows devices usually perform all old 135 so this is what the this particular thing service that will make certain assumptions based on these ports so now people will be thinking like ok you were telling about port 22 or 135 but like they can change it so actually yes they can change it but these are the standard ports so if you go to the like list of standard pools you will be seeing that the port 22 is reserved for ssh communication and port 135 is reserved for windows combination so all these things are standard that's why service no discovery make certain assumptions based on this scan so now first step is the port scan 1 so discovery makes certain assumption about the devices application and processes running on these ports and launches the appropriate classifier props to find out what exactly it is so if it responds to WMI so it will classify it as will do device so that's what port scan does so now the other phase that comes up is the classification piece so now we got to know that from the suzanne probe that it is responding on 135 so it's clear that it's it's a Windows device so classification so classify sense process the data returned from the classified probe and compare against the criteria for each class of device attempting to classify that device specifically so for example if we know that it's a Windows device so it can be a Windows 2003 2008 2012 like I'm talking about printer servers so all these Windows Server 2003 2008 or 2012 so that is the classification that it needs to go because we if we are we know that it's running on port 135 which means it's a Windows but what will dos its whether it's Windows Server 2003 2008 or credit so this is what the classification phase will do for us it will classify it according to the particular version we can say worship from and then the last two things are their identification and exploration phase so using the CMD a using the CI a identifies an attempt is made to match information against the CMDB record so basically like because discovery runs in a schedule mean it will run every day because as I told you maybe it runs every day because you can set up this thing but generally it's done almost every so as the system infrastructures are very volatile so these things can change up right so now if we have the identification rules and all these things so that if there is something that changes up it should not create a duplicate CI right suppose like so there comes the identification rules which are part of the identification phase so like suppose you have Windows one and there is some parameter that got changed so it should not happen like it is just creating a new yet because ultimately those things are same so this identification phase will take care of that thing it will see whether I have seen you before or not if it hasn't seen it before it will create a new CI if it's it has seen it before then it will create it will just update the particular CI and in the last phase explanation phase patterns are launched gathering more detailed information or what else can tell me about yourself to populate the CI attributes accordingly so both hardware and software so like after it is identified okay it's we need to create a news here now other parameters can be taken care from my in the explanation so there in the exploration phase we can have the custom probes and sensors to get certain certain information from the infra all we can have the discovery patterns come into picture in the exploration phase so this is in a nutshell what the phases of discovery may do so port scan phase will say are you there how will I classify you classification will say how should I classify that value specifically and identification phase will say have I seen it before or not an exploration phase will say what else can you tell me about yourself so it's very simple so firstly it goes to the particular device it will see on which port it's working and based on that it will run with the particular classification probes and then it will classify that thing and it will depending on whether it was there in the infrastructure or not it will create or update the particulars here and in the exploration phase it will get more details about that so that's how the discovery is like the full process of discovery years these are the four major phases and discovery port scan phase classification phase identification phase and exploration so the these things should be always taken care into account when we are implementing discovered so now coming to the some of the best practices for implementing discovery so for implementing this company we should always follow a phase approach so what I mean by loop phase approaches by when because it's very easy to just enable the discovery plugins add the particular IP ranges and click on discover now and it will discover all these things but if you do in this way so they there are a lot of chances of errors that can come out right so that errors to reduce those errors like we should always follow phase approach we should start with the critical devices like the Windows devices are there or the Linux servers are there then we should go into the less critical devices so critical or less critical devices totally varies based on the system right so based on the like particular client how they exactly classify those things whether it's a critical or non-critical device so always it's a best practice to follow a phased approach so next thing is the review your class architecture so sometimes what happens is like a particular device can run on the same protocols like it can like run on it can be an SNMP device or it can be in Linux SSH it can run on different protocols at the same time so this is very much common in an infrastructure so their impact this way you should be moving that where it needs to be classified so always sit with the engine running to see whether this classifier whether what's the class architecture how these things need to be classified so that you can create a proper class criterias for them and always like when I am implementing any discovery project or something so I keep one thing in mind that we can't be subject matter experts for everything so it's always to concern the proper entropy so that you get a proper knowledge on that particular class system so next thing is like the minimized manual updates to CMV so this is something that I always happen in like in any CME so just the CME admins or the class admins go to a particular class and open a particular SIA and just update it them right so this thing is like it causes a lot of issues because discovery is also running and later on it will just update that thing up if there is any change and all so this should always mean like all these manual updates should be very less and if you should like if there is any need for that manual update it should follow a proper change process so that all these manual changes take place in control so this is very important thing that should be okay and the last thing is like understanding the KPI or the success criteria so basically always like when you are getting a new product or something you should always consider like what is the benefits of it so all these kpi's will help you whether you have achieved your target or not whether you whether this particular product is helpful for you or not so for example discovered versus non discovered zi so before like this is this can be a KPI where like before implementing discovery there are only twenty twenty servers in the CL maybe but after we got into discovery we got like 80 or something so this is should be taken care so all these KPIs are totally dependent on the the client or the customer that's implementing those things because there is certain standard capias but sometimes those doesn't make sense to certain clients because they are not into that particular thing so always like from my experience I can just say that these KPIs are mostly dependent on client it can vary in different ways and one last thing that I have mentioned with a gap there are eight insulation tools in get assistance so what these things are basically if you have multiple sources operating your CMDB CL u CM DV tape so basically what happens is like you have certain integrations with your service now so what it does is like it will also try to update your CMP right and discovery is also updating most so there come these reconciliation rules in data source precedents which will help to when you have multiple data sources updating your CFD so always use these things so it's like if you only have discovery then you don't need to care about these things but if you have multiple sources multiple integrations and other things are updating CMD just always use these things so this this is one of best practices from ServiceNow that they are giving us and so now after we have implemented discovery so what's next so that thing that is a service nothing so service mapping discovers all the services in an organization and builds a comprehensive map of all devices application and confidential profile using these URLs so it's like it will just generate all this map so basically what is the difference between a service mapping and discovery is like service mapping will try to just like discover only the see eyes which are related to a particular service whereas service the discovery what it will do is it will discover everything whatever there is in the infrastructure right so that is the major difference between service mapping and discover both uses the discovery link but it will only discover this but the service mapping will only discover the sea ice that are related to a particular service whereas the service now horizontal discovery will discover like all the CS whether it's all the road balances are not prime so that is the major difference between service mapping and discovery so these are the major differences between service mapping so service mapping with only discovers component offer the server service and ignore everything else it allows IT operations to become service aware and provides a targeted discovery of the IT infrastructure directly related to the service and W to discovery discovery finds everything whether it's helpful or not identifies all the devices located in an IP address range and it's very good in addressing all ID devices from an inventory perspective on foreign asset management initiative so that's the major difference between service mapping and discovery so a lot of times people will say ok like we both are same but it's not service mapping is a way to make your idea organization like aware of a particularly to make it service up here that's what the use of service mapping is and discovery is like it's just normal it will discover everything so that's the major difference between service mapping and discovery so well that's all I have for you in discovery one and we got to know what is discovery then we got in a water like and different phases of discovery when we got to see the credentials and all these things now let's see a quick demo of how we can set up a discovery so let me just so guys I'm into my ServiceNow instance what I'm gonna do is like first thing is like let's go into the mid server and type the mid server yeah and you can see a download options so here you can download the particular med server that you want you can download 64 bit or 32 or 32 or 64 depending on your sister so in interest of time and already downloaded this thing so once you download this thing you will be able to see something like this you will get a zip file like this so when you extract that zip file you will see this agent that comes up so you can just put it anywhere in the system because right now I'm using a normal text shop it's not a server machine it's just a normal windows so you can just click on this agent and you can now click on the installer so just click on this installer now so it will open you this particular service now it will ask you to give the ServiceNow instance you are in the service of make server username and pass so let me just quickly give it like the particular this and in interest of time I have created a mid server user with the username make sure it has a role of mid server so I've already done that let me just add this thing and the password and I'll just test the connection so that it's working so because sometimes it takes some time so you can just see that connection tested successfully now let me just click on next it will ask me to specify the mixer so I just specify in the mid 70 and just demo server like that and I click on next and that's it will show us what is the configuration that I have said click on next and I can just start them itself so it can just say just set mates ever started so that's how you can install the mid server now now I can go into the mid servers so now I can just go into the discovery module and into the mid server and if I click on this one so I'll be able to see my mid server it will take some time to load up and it will then come up so these are all ready that I have so now let me just keep on refreshing and you can just see that demo server 2 came up right so that's how it is easy to set up and it's over now one important thing that is always there is like we have to validate the mixer so always because you can just see that status is down and because why it's down because it's not validated so let me just quickly validate it and I can just save it so it takes around one or two minutes to violate it and you can just say it's down and it's validating right so we can wait till 1 or 2 minutes and it will just show up as validated it yes like this and status is equal to but you can just see that it's running on the next server user who is the logged in user and all that so that's how it's very easy to set up a mid server like you just go and extract that thing and the particular staff like your username and password for that Miss America always remember don't use the admin user because admin has all the right just create a new user with the mid server rule and just then you can just add that right so I think it just takes some time so now till the time I have already set up one more mid server that is demo server to so we can utilize that mid server yeah you can just see it's up and running now so now we can just go to the discovery do so when you type discovery schedules you can open it and there are two options one is new and one is quick discount so I'll be you doing a quick discovery to show you how we can discover a particular CI or something so I'm using a loopback address so basically what is the new parameter X is look bad IP address is a special kind of IP address which is used to discover the localhost so that's what because I just want to discover my MedStar host that is Magnum news machine so that's what I am doing and let me just select them demos over to that is there and I click on this so now you can just see that there is a new discovery that's being created so if I click on this thing you can just see that first thing in the ECC queue you are saying that Suzanne prop is there so this is the phase one or the boots can face that is there so Suzanne prompt is sent it send different WMI SNMP SSH probes so that it get to know what type of device it is right so if i refresh it now so this is you see this is an output that is there right so there is an output that is sent from ServiceNow to that particular mixer right so now there is an input that's being returned to service now with it from the mid server so you can just see that it returned for this particular thing so now ServiceNow will process this particular thing input and on the basis of that you can just see it like put W in my classify WMA means for Windows right because it get to know that it's it's a big nas device if I just refresh now so you can just see that all this windows classification Tran and all these like pattern is launched for Windows operating system and these are all these things that are happening so this is in the particular exploration structure so if i refresh this particular thing so you can just see that it's been classified and it's in the identification in exploration phase cause on the current activities being identified right so now it will take around two minutes to discover it so let's wait for two minutes so you can just see that this two says I have one are the particular the ports can't fix then the WMI runner or the classified this is the classification phase and this thing is the particular identification and the exploration phase that is what is all in discovering so it's just by four different phases port scan phase classification phase identification and explanation so just refresh it [Music] so it takes around two minutes to discover this thing because it's going through the internet and go coming returning those response so basically you can just see that it's been it's waiting for the input for this particular pattern on July 2 Windows OS the next job it takes around 1 or 2 minutes more and you can just see it's being classified as a computer so all these my computer classifiers and and all these things classified it as computers and they just wait for another 1 or 2 minutes to see it so you can just see that now it the input came up and this is another so it's now getting them on the application that are there inside of that so you can just see that ready fresh it so it's it has discovered the localhost and let's wait for it to complete so once it gets complete the status will change completed in just refresh it so all these things are happening in the exploration identification and exploration phase so you can just see that this particular like patterns for this thing are launched so to find the details of that particular device right so you can just see that the state is completed now so we have the CA discovered so if I click on this CI you can see all the information about my device so it has like trend gigs of RAM and it so it has this CPU speed and all of these things are coming from there from discovery pattern so you just saw that I didn't do anything I didn't have to write any script and also all these are the features of service discovery and this is how easy it is to discover a particular CI so just if you want you guys can try just to add a mid server to your particular device and just try to discover it and you can just see that all these things will come up you can just see that it also discovered the storages so I have like 1 TB hard scan another 251 so all these things are discovered that these are all the software's that are being discovered in my system so you can just see that how good it is in discovering all these things right so so that was all about in the demo of ServiceNow discovery that I just showed you so now let's all I have for you in service no discovery now you guys can if you have any questions you can just post your question in an answer so I see one question please explain explain the phrases once again okay so as I told you like there are four different reasons so one is puts countries then is the classification then identification in explanation place so in a nutshell if I go back to that particular slide this one so ports can freeze is like it will just let you know how whether it's there or not whether there is any active device or not classification will just classify it based on that particular whether it what type of device it is like if it's up Windows whether it's a Windows 2003 Windows Server 2008 or 12 an identification will see whether it's there or whether it's not if it's there it will update it if it's not then it will create an exploration phase it will just explore other things what else you can take it out so that's what phases of discovery it isn't so so another question that is there is service mapping do we want to define the business service in advance see you don't need to define anything in advance you what you have to do is like you will be having the earth which you use to access that business service right so one when you give that particular thing then there are different phases inside it uses mostly discovery patterns for that so when all these discovery patterns will be used and in that we have to in pattern also we have different phases and all that so there you can use the service mapping and another question is there most of the organization will be having so-called business away which may be altered later once we go on maturity yes definitely as I told you like infrastructure is many monitor so all these things needs to be like it will keep on changing so these discovery schedules that we make will help us making it active like it will just make sure that it's this is the real picture of what our infrastructure is right so that's what discovery needs to run on like on am schedule it can be in one day or today or any other thing so another thing is many touch points on mid server sizing will help so sizing so mid server sizing so what I have to do is like there is a good access sheet that I have created for determining how the mid server should be like if you it totally depends on the infrastructure like and how your discoveries are getting slower so so the thing that comes in like sizing is like if you have lot of IP ranges and your discovery schedules are taking lot of file right because I have seen one example where one discovery schedule was taking around like five to ten hours right so we installed a load balancer mid server like we divided the work between different mid server and we grouped those things together right so that in that way it like it reduced the load on one mid server and the discovery was happening in nest so it totally depends on how we are infrastructure so what I can do is like I can share you access sheet which can help you determine the size depending on your infrastructure another question that has come up things like how frequently should we discover so it totally depends see so because when you are discovering it will also in that they like infrastructure right so mostly it's sometimes some clients prefer on daily basis in in that time which is like when they are not using service now so but if they're using service now 24/7 then they can do a weekly one or like it can be bi-weekly or dependent it totally depends on how they're using the service that's it because what happens is like when you're running service now discovery so it will just impact the performance other things also because if it's discovering a lot of things and if you have multiple schedules that are running so it will impact of it so we have to take care of that thing that we should discover in a time in which it's not being used so that it doesn't affect other work right so it totally depends so I have so I think these are all the questions so I see one more question let me just see okay one of my client faced an issue with oh I DS Julianne discovery - device it get updated with say moiety what could you what could you be troubleshoot method okay so already so two ideas come into picture when you're discovering the SNMP devices right so in SNMP devices you have something consists object ID right so the if you go into like just show you that so that it will make sense to you though so why TV so if you go to the OID information in this so you will be able to see this is the OID depository so because Hadees are based on manufacture so when you go into your particular SNMP you will be seeing the particular varieties such that OID here just enter that thing and see what type of manufacturer is it then you can go into the SNMP system - right so here you define those things in Javaid right if you click on this you can just enter the particular ID and what is the manufacturer and model this thing you can get from the OID later sweetie so that's what you can so I think this will help you in solving relation right so okay so one more thing that come up regarding duplicates when identifiers finds a match when it add a record and mark has duplicate or just ignore it see if there is something that comes up there is like duplicate kind of thing that when it comes up right so it will just create a new record if there is no identifier rule that'll match it won't ignore it right so that's why the identifiers rules the all these things should be created properly so that it doesn't even like create lot of like this or sometimes like that would I that's what I have seen is like in certain classifiers the identification rule is based on name is on the name right but name might be like Windows Server or Windows or something so we should like make it like name contains not like name is you know how the filters and all that thing in that works right so it totally depends so for your question if there is anything that is new it will create a new record it won't ignore it so can you explain few steps or trouble which troubleshooting discovery errors is there any is there a tool like command manager to execute prop commands directly from ServiceNow okay so like there are troubleshooting methods so it totally troubleshooting errors comes totally dependent on your particular phase in which phase you are working right so if you are working in the port scan fields so you might see errors or credentials that is that's the most common error that you see because credentials and all that or the ports are blocked these are certain thing that comma and the when you are talking about the classification so the in that classification what can come up is like you're like the classifier like there is no particular classifier that's there which is not able to so you have to create a particular class affair or again the credential issue might be there it's not able to access it so sometimes you might see that active couldn't Asif I so that means that the classifier is not particular it's not able to go there so these are it totally depends and coming to the identification and exploration phase maybe you don't have the proper privilege because when you talk about any infrastructure device so one thing that always come up is the privileges as you have in ServiceNow right so ServiceNow will have like different rules right similarly we have the different accesses in Windows or Linux right so you might not have a particular access to access that particular thing so these are the some of the common things that come up right so and there are lot other things also maybe some sometimes you will see like active like device is active that means it's active means it means there is no device that's connected but the IP side so these are the certain things that come up is there a tool like command manager to execute prop commands directly from ServiceNow so if if I talk about this thing is there is a debug mode in the pattern designer where you can perform the life commands directly and so there you can just test those things and see what's the result that's returned so if you go to the discovery patterns right so in that pattern you see you will be seeing a particular debug mode so where you can activate you can just execute the particular commands so basically when you are writing all these things you will be using that and there is another option that is command manager in as you were talking so you can use that thing once right so let me just key so here if you just define and just quickly type something so that I can just show you okay so if you open this particular net when you save it when you open this particular identification section you will be able to see that particular debug mode on the top so there you can run those commands up right let me just open this thing so you can just see this is the debug mode that is there where you can add your host name and you can just connect it then you can perform this thing so right now I can show you that particular how you can debug using the command manager right because I'm on a Windows Server machine so I'm just gonna stop machine and I need a pin to service we will exams from there so it's one thing so I think I think that's all the questions that we have for this thing so should be I'm handing back to you now yes Thank You Bruno and thank you everybody for attending the webinar today just a quick update we will be at knowledge next month at boot number 7 22 demoing some nice cool innovative stuff so it will be great if you can come and stop by at a booth and we'll see you next month on super onyx closed webinar thank you no thank you all for joining