WEBVTT 1 00:00.000 --> 00:03.360 You're probably wondering how we can keep track of continuous integration and 2 00:03.360 --> 00:08.000 continuous development all at the same time while maintaining the rest of our 3 00:08.000 --> 00:12.460 cloud environment. Well, I'm glad you asked because again we're going back to 4 00:12.460 --> 00:16.150 our example and inside of depth that we're going to be taking a look at Cisco 5 00:16.150 --> 00:18.000 network services orchestrator. 6 00:18.000 --> 00:22.970 And once we go in here, we're going to do a search for NSO November Sierra 7 00:22.970 --> 00:28.870 Oscar and we're going to see that we have NSO always on. Now we are limited in 8 00:28.870 --> 00:33.970 scope and ability as far as configuration goes, but this is more of a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 8 00:28.870 --> 00:33.970 scope and ability as far as configuration goes, but this is more of a 9 00:33.970 --> 00:37.770 demonstration to show you that such an ability does exist for practice and 10 00:37.770 --> 00:40.000 training and getting familiar with everything. 11 00:40.000 --> 00:43.770 So you can go in here and hit launch and you can set up this in your 12 00:43.770 --> 00:48.630 environment. Now remember as a demo, you only get to run one instance at a time 13 00:48.630 --> 00:53.000 . So we have our network services orchestrator actually running. 14 00:53.000 --> 00:57.080 When we open it up, we see that we have four servers. Now connection for this 15 00:57.080 --> 01:00.410 is going to be very similar to how we've done in the past couple of skills as WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 15 00:57.080 --> 01:00.410 is going to be very similar to how we've done in the past couple of skills as 16 01:00.410 --> 01:02.000 far as the VPN connection goes. 17 01:02.000 --> 01:05.640 We go to the quick access. Let me zoom in for you real quick. You can see here 18 01:05.640 --> 01:09.460 that we have a quick access tab button and we're going to click on it. You can 19 01:09.460 --> 01:14.600 see we have the VPN address username and password again this password is only 20 01:14.600 --> 01:15.000 good for 24 hours. 21 01:15.000 --> 01:18.720 So by the time the skill goes up, you're not going to be able to get into this 22 01:18.720 --> 01:22.980 account anyway because the services are going to be terminated because this 23 01:22.980 --> 01:27.000 right here is only good for 24 hours. You can extend it, but I'm not for this 24 01:27.000 --> 01:27.000 one. 25 01:27.000 --> 01:31.650 So we're going to copy the actual VPN addressing go to our settings. And if you WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 25 01:27.000 --> 01:31.650 So we're going to copy the actual VPN addressing go to our settings. And if you 26 01:31.650 --> 01:35.560 remember, we have to select any connect for our actual connection. And we're 27 01:35.560 --> 01:39.980 going to call this one in a scope for connection name and just put punch in the 28 01:39.980 --> 01:41.000 actual server address. 29 01:41.000 --> 01:44.930 Now it's not going to ask us for a user name or we can't fill in a username or 30 01:44.930 --> 01:49.800 password here. But that's okay. When we hit save and actually go to connect to 31 01:49.800 --> 01:53.000 the actual VPN for it, it will come up and say we do need a password. 32 01:53.000 --> 01:59.520 Now this information is stored inside of the actual quick access information as 33 01:59.520 --> 02:04.000 well. You'll also get an email concerning the login information of VPN access. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 33 01:59.520 --> 02:04.000 well. You'll also get an email concerning the login information of VPN access. 34 02:04.000 --> 02:10.130 Go in and type in our actual password controls V for paste and we're connected, 35 02:10.130 --> 02:14.000 which means that we can access these servers. 36 02:14.000 --> 02:17.790 Now if you go back to your instructions button, which is right next to quick 37 02:17.790 --> 02:21.400 access, you could scroll down to access and see that we have a couple of 38 02:21.400 --> 02:23.000 different servers on here. 39 02:23.000 --> 02:27.940 The NSO has multiple different addresses, but if you're really curious, you can 40 02:27.940 --> 02:31.000 actually go inside here and see which ones they are. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 40 02:27.940 --> 02:31.000 actually go inside here and see which ones they are. 41 02:31.000 --> 02:35.150 We have dev tools, which allows us for the continuous integration and 42 02:35.150 --> 02:40.000 development of tools that are going to be live and currently being developed. 43 02:40.000 --> 02:43.720 We also have our dev box, which is kind of behind the scenes and running our 44 02:43.720 --> 02:46.000 virtual environment on the bottom left. 45 02:46.000 --> 02:50.890 Our CML, our modeling lab on the bottom right to allow us to be able to go in 46 02:50.890 --> 02:54.000 implement different devices in our network. 47 02:54.000 --> 02:57.960 Or demonstration purposes and then on the top right, we have our actual NSO 48 02:57.960 --> 03:00.000 network services orchestrator. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 49 03:00.000 --> 03:04.090 Now we're going to see back on our information tab that we have different IP 50 03:04.090 --> 03:08.470 addresses than what's on the actual servers themselves because we have the NSO 51 03:08.470 --> 03:15.670 being 10, 10, 2010, but we have GUI and API access on port 8080 available at 47 52 03:15.670 --> 03:17.000 , 48 and 49. 53 03:17.000 --> 03:20.710 So I'm just going to right click on one of them and go to open a new tab and we 54 03:20.710 --> 03:23.000 can see right here that we're at the log in. 55 03:23.000 --> 03:27.470 Do note that you'll have to scroll down and look at the actual log ends for 56 03:27.470 --> 03:32.250 your actual servers here because we have a different password for the actual WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 56 03:27.470 --> 03:32.250 your actual servers here because we have a different password for the actual 57 03:32.250 --> 03:37.000 dev box, the net dev ops and different different systems on here. 58 03:37.000 --> 03:40.820 So just something to keep in mind as you're going through here and taking a 59 03:40.820 --> 03:45.200 look at also the different operating systems and environments that they have on 60 03:45.200 --> 03:51.080 the different IP address schemes inside of our network topology, which will be 61 03:51.080 --> 03:52.000 inside of the actual modeling lab itself. 62 03:52.000 --> 03:57.970 So if we go back up and we look for our username password, we can see that 63 03:57.970 --> 04:03.570 under NC, NC NSO, we have developers are long and we have Cisco once you three WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 63 03:57.970 --> 04:03.570 under NC, NC NSO, we have developers are long and we have Cisco once you three 64 04:03.570 --> 04:06.000 four five with the one at the front as our password. 65 04:06.000 --> 04:09.000 Go over here and type in developer. 66 04:09.000 --> 04:15.000 I can spell correctly and go ahead and paste in that password and log in. 67 04:15.000 --> 04:19.130 Says that we need to change our password based on the fact that it's a default 68 04:19.130 --> 04:23.180 password and we could go in here and see that we have different aspects of our 69 04:23.180 --> 04:27.410 network services orchestrator that allow us to integrate the monitoring and 70 04:27.410 --> 04:32.020 continuous integration and continuous development of our actual organization WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 70 04:27.410 --> 04:32.020 continuous integration and continuous development of our actual organization 71 04:32.020 --> 04:34.000 and cloud environment. 72 04:34.000 --> 04:38.570 We have configured we are broken down into three different areas right so it's 73 04:38.570 --> 04:43.190 configuration which allows us to be able to go through and manage edit, look at 74 04:43.190 --> 04:47.900 devices, be a service manager and package upgrade or and then we have 75 04:47.900 --> 04:53.070 monitoring which allows us to be able to integrate different capabilities such 76 04:53.070 --> 04:58.000 as so and seems and making sure that all of our devices are communicating 77 04:58.000 --> 05:03.000 correctly over things like net comp, rest comp, syslog, SNP, V3. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 77 04:58.000 --> 05:03.000 correctly over things like net comp, rest comp, syslog, SNP, V3. 78 05:03.000 --> 05:08.030 And however you decide to be able to monitor your systems out there, we have an 79 05:08.030 --> 05:13.000 alarm manager that tells us based on our rules that we set up whether they be 80 05:13.000 --> 05:17.480 rule signature based or a nonally based to come back and tell us if anything is 81 05:17.480 --> 05:21.820 going on a dashboard to give us a complete overview of systems which we will 82 05:21.820 --> 05:23.000 check momentarily. 83 05:23.000 --> 05:27.040 H a cluster high availability to for that load balance and environment that we 84 05:27.040 --> 05:30.610 've been kind of hitting on a little bit through the past few skills and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 84 05:27.040 --> 05:30.610 've been kind of hitting on a little bit through the past few skills and 85 05:30.610 --> 05:35.020 compliance reporting and insights manager club compliance reporting this is 86 05:35.020 --> 05:39.000 really handy when we're in situations to where we have to deal with 87 05:39.000 --> 05:43.000 jurisdiction, different types of requirements in our area whether they be 88 05:43.000 --> 05:47.640 company policy, letter of the law, whatever whatever have you and so we can 89 05:47.640 --> 05:52.000 build out however we want to be able to monitor whether our devices and systems 90 05:52.000 --> 05:52.000 and possibly data. 91 05:52.000 --> 05:57.620 Or within spec of the a specific piece of compliance policy put into place and 92 05:57.620 --> 06:03.190 then at the bottom you have your packages, which is the rest API explorer now WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 92 05:57.620 --> 06:03.190 then at the bottom you have your packages, which is the rest API explorer now 93 06:03.190 --> 06:07.450 we're not going to be going too much into this because we're just focusing on 94 06:07.450 --> 06:12.530 the configuration and monitoring but let's go into our dashboard and see that 95 06:12.530 --> 06:16.890 we have nine devices connected one user session, which is actually us logged 96 06:16.890 --> 06:18.000 into the system. 97 06:18.000 --> 06:23.140 Now if you wondered about these actual nine devices we'll go back into our view 98 06:23.140 --> 06:27.900 environment for the dev net altogether and take a look at our C LL which is our 99 06:27.900 --> 06:33.150 Cisco modeling lab now do note that this has potentially a different username WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 99 06:27.900 --> 06:33.150 Cisco modeling lab now do note that this has potentially a different username 100 06:33.150 --> 06:37.000 and password scrolling for it right now. 101 06:37.000 --> 06:42.940 But we'll go into the next tab over and once that in there for us on HTTPS and 102 06:42.940 --> 06:48.920 see if that pops up for us it does but remember top left we have not secure 103 06:48.920 --> 06:54.700 which means that you need to keep an eye on the SSL CLS certificates that are 104 06:54.700 --> 07:00.640 associated with this modeling lab if you go back over and look for the actual WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 104 06:54.700 --> 07:00.640 associated with this modeling lab if you go back over and look for the actual 105 07:00.640 --> 07:03.000 username and password. 106 07:03.000 --> 07:07.560 I'm going to scroll down just a little bit and log in with my credentials that 107 07:07.560 --> 07:12.290 were the same as the actual network services orchestrator and you can see here 108 07:12.290 --> 07:16.000 in our multi platform network previously was had been gold. 109 07:16.000 --> 07:19.610 Just different names that we can actually double click on it and go in and see 110 07:19.610 --> 07:22.000 the actual layout and design of the network. 111 07:22.000 --> 07:26.730 Now I want to try to move it over a little bit to where you see and then zoom 112 07:26.730 --> 07:28.000 in. 113 07:28.000 --> 07:32.010 There we go and you can see that we have multiple different devices within our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 113 07:28.000 --> 07:32.010 There we go and you can see that we have multiple different devices within our 114 07:32.010 --> 07:36.830 infrastructure for the actual NSO to be able to collect for monitoring and also 115 07:36.830 --> 07:39.000 to send out configurations. 116 07:39.000 --> 07:43.690 Be it from firewall all the way down to individual host and actually a bridge 117 07:43.690 --> 07:47.000 back to the sandbox environment that we have as well. 118 07:47.000 --> 07:51.200 Now sandbox environment is something that we've been stressed on because that's 119 07:51.200 --> 07:54.820 where we kind of want to keep everything if we can afford and utilize one 120 07:54.820 --> 07:58.000 within our organization for actual testing purposes. 121 07:58.000 --> 08:01.820 I point this out because if we go back into our dashboard here is something WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 121 07:58.000 --> 08:01.820 I point this out because if we go back into our dashboard here is something 122 08:01.820 --> 08:05.820 that we'll have to remember as we look at the actual devices connected do know 123 08:05.820 --> 08:11.260 that on the bottom down here that we have the different shortcuts to be able to 124 08:11.260 --> 08:14.000 go through and do things like device management. 125 08:14.000 --> 08:18.070 We can actually go through and ping connect check system check the sync on 126 08:18.070 --> 08:22.000 everything and for that we'll just try one out real quick core router. 127 08:22.000 --> 08:26.710 One go ahead and ping it and look at that it's actually ping it through okay 128 08:26.710 --> 08:31.470 and the device was found gives you a little bit of feedback to this is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 128 08:26.710 --> 08:31.470 and the device was found gives you a little bit of feedback to this is 129 08:31.470 --> 08:34.740 basically a way for us to be able to integrate everything that we've been 130 08:34.740 --> 08:39.190 talking about to include continuous integration and continuous development into 131 08:39.190 --> 08:43.000 one monitoring and configuration service to allow applications. 132 08:43.000 --> 08:49.010 Application in the software development lifecycle for that continuing cycle of 133 08:49.010 --> 08:54.550 being able to implement and improve on our organization for security and also 134 08:54.550 --> 08:56.000 usability.