WEBVTT

1
00:00.000 --> 00:08.550
So next, let's jump into SD-WAN Manager or VManage and take a look at some of

2
00:08.550 --> 00:09.080
the tools

3
00:09.080 --> 00:14.270
available in the Graphical Interface to help us troubleshoot problems,

4
00:14.270 --> 00:15.400
specifically focusing

5
00:15.400 --> 00:17.600
on Cloud OnRAMP.

6
00:17.600 --> 00:22.880
Now for this discussion, we're going to be focusing on CloudRAMP for AWS, but

7
00:22.880 --> 00:23.720
understand

8
00:23.720 --> 00:28.940
that the information available in SD-WAN Manager is effectively the same for

9
00:28.940 --> 00:30.240
the different Cloud
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:28.940 --> 00:30.240
the different Cloud

10
00:30.240 --> 00:31.240
providers.

11
00:31.240 --> 00:35.870
What's shown for troubleshooting tools and logs and things like that doesn't

12
00:35.870 --> 00:36.680
really change

13
00:36.680 --> 00:39.680
dramatically for different Cloud providers.

14
00:39.680 --> 00:47.060
So that said, let's jump into SD-WAN Manager and take a look at the available

15
00:47.060 --> 00:48.120
tools.

16
00:48.120 --> 00:53.880
So our very first troubleshooting tool here in SD-WAN Manager is the landing

17
00:53.880 --> 00:54.760
page which

18
00:54.760 --> 00:57.040
is Monitor Overview.

19
00:57.040 --> 01:03.200
If we have errors on our control components or on our WAN edges, any of these,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:57.040 --> 01:03.200
If we have errors on our control components or on our WAN edges, any of these,

20
01:03.200 --> 01:03.640
these will

21
01:03.640 --> 01:05.880
have errors on them.

22
01:05.880 --> 01:09.920
Same with our various widgets here on this page, they would be showing things

23
01:09.920 --> 01:10.440
as good,

24
01:10.440 --> 01:14.640
fair, or poor if things are not performing well.

25
01:14.640 --> 01:20.400
Also be aware that there are different views available on this overview page.

26
01:20.400 --> 01:26.000
Over here in the top right corner, we have some other views such as we can

27
01:26.000 --> 01:26.920
click here

28
01:26.920 --> 01:30.560
and we can bring up just the site list view.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
01:26.920 --> 01:30.560
and we can bring up just the site list view.

29
01:30.560 --> 01:35.080
And again, we get some nice checkboxes here about our site health, our devices

30
01:35.080 --> 01:35.680
health,

31
01:35.680 --> 01:38.440
tunnels health, and so on.

32
01:38.440 --> 01:42.810
There's also a block diagram here that will show us during different times for

33
01:42.810 --> 01:43.480
different

34
01:43.480 --> 01:49.370
sites which ones have been again, good, fair, poor, or of course no data if

35
01:49.370 --> 01:50.320
there was no

36
01:50.320 --> 01:52.360
data available.

37
01:52.360 --> 01:57.110
And finally, there's also a geographic view which will bring up our various

38
01:57.110 --> 01:58.160
sites in relation

39
01:58.160 --> 02:00.520
to the world map.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:58.160 --> 02:00.520
to the world map.

40
02:00.520 --> 02:03.000
We take a look here if I scroll this over.

41
02:03.000 --> 02:05.400
I'm in the United States of course.

42
02:05.400 --> 02:11.390
Now here we can see that my site 20 is listed approximately where AWS is here

43
02:11.390 --> 02:12.160
on the east

44
02:12.160 --> 02:13.160
coast.

45
02:13.160 --> 02:18.280
However, my site 100 is not at all where it's supposed to be.

46
02:18.280 --> 02:22.220
In fact, I believe it's hard to tell on this output we could zoom in maybe, but

47
02:22.220 --> 02:22.640
I believe

48
02:22.640 --> 02:26.890
it's defaulting to Cisco's headquarters in California, but it's certainly not

49
02:26.890 --> 02:27.440
showing

50
02:27.440 --> 02:31.280
my current location just because I haven't configured those things.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

50
02:27.440 --> 02:31.280
my current location just because I haven't configured those things.

51
02:31.280 --> 02:34.920
But again, this is a good place to go for more information.

52
02:34.920 --> 02:38.680
Also of course, we can check things on the devices tab.

53
02:38.680 --> 02:43.010
Here we can look again for things like health and reachability, making sure our

54
02:43.010 --> 02:43.560
control

55
02:43.560 --> 02:48.540
and BFD tunnels are up, how many T locks are available on each of these and so

56
02:48.540 --> 02:48.880
on.

57
02:48.880 --> 02:53.810
We can also of course out on the edge here see things like CPU load and memory

58
02:53.810 --> 02:54.960
utilization.

59
02:54.960 --> 02:59.080
So this is a good overview page for how our devices are behaving.

60
02:59.080 --> 03:02.960
We can see the same basic thing for tunnels if we go to tunnels.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

60
02:59.080 --> 03:02.960
We can see the same basic thing for tunnels if we go to tunnels.

61
03:02.960 --> 03:07.680
We can see our QOE value here or quality of experience and that is what

62
03:07.680 --> 03:08.760
determines how

63
03:08.760 --> 03:10.400
the health is.

64
03:10.400 --> 03:14.220
In fact, if you click on this little I next to the health or just put your

65
03:14.220 --> 03:14.920
mouse over

66
03:14.920 --> 03:21.200
it, it'll tell you at what QOE values it changes this rating.

67
03:21.200 --> 03:25.400
So at an 8.0 and up, it's listed as good.

68
03:25.400 --> 03:29.760
Once again, if you look at all of mine here, they're all clearly above eight.

69
03:29.760 --> 03:34.640
Now another good one here again specifically for troubleshooting would be logs.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

69
03:29.760 --> 03:34.640
Now another good one here again specifically for troubleshooting would be logs.

70
03:34.640 --> 03:36.920
So let's go over here to our logs.

71
03:36.920 --> 03:41.700
And here we see on our logs, notice that most of mine are states going up and

72
03:41.700 --> 03:42.840
down for various

73
03:42.840 --> 03:43.840
items.

74
03:43.840 --> 03:48.270
This is because I reset and change the configuration on my lab environment a

75
03:48.270 --> 03:48.760
lot.

76
03:48.760 --> 03:52.120
So of course, I have a lot of entries like this.

77
03:52.120 --> 03:56.630
Another useful tool because of course this can get quite long is we can come

78
03:56.630 --> 03:57.320
over here

79
03:57.320 --> 04:02.770
to advanced filter and if we click on this, we could for example under object
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

79
03:57.320 --> 04:02.770
to advanced filter and if we click on this, we could for example under object

80
04:02.770 --> 04:03.360
type, let's

81
04:03.360 --> 04:09.400
just say we want to see devices for the object list, let's say all again, we

82
04:09.400 --> 04:10.320
can filter by

83
04:10.320 --> 04:13.160
a specific device here if we want to.

84
04:13.160 --> 04:17.360
And then on severity, we can actually choose the severity level.

85
04:17.360 --> 04:24.080
Now again, we can choose all or we can choose critical major medium minor.

86
04:24.080 --> 04:28.690
Others are the levels for the alarms here in SD WAN manager with of course

87
04:28.690 --> 04:29.600
critical being

88
04:29.600 --> 04:33.880
the most important and minor being the least important.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

88
04:29.600 --> 04:33.880
the most important and minor being the least important.

89
04:33.880 --> 04:37.960
So let's say for example, we just said show me the critical errors and then for

90
04:37.960 --> 04:38.640
the type,

91
04:38.640 --> 04:40.680
we'll just say all.

92
04:40.680 --> 04:45.980
Then we'll apply the filter and we can see now we're just getting device errors

93
04:45.980 --> 04:46.240
with

94
04:46.240 --> 04:49.160
a severity of critical.

95
04:49.160 --> 04:53.540
And of course down here under action, you can actually view the alarm details

96
04:53.540 --> 04:54.240
and this will

97
04:54.240 --> 04:56.920
give you more information.

98
04:56.920 --> 05:01.670
This is simply telling me at some point the V bond state changed with the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

98
04:56.920 --> 05:01.670
This is simply telling me at some point the V bond state changed with the

99
05:01.670 --> 05:02.560
manager and

100
05:02.560 --> 05:04.720
it went down.

101
05:04.720 --> 05:08.960
Other things on this same tab of logs, we have of course the alarms.

102
05:08.960 --> 05:11.080
There's also events.

103
05:11.080 --> 05:14.550
Once again, we can filter on these as well plus we get a little bar graph at

104
05:14.550 --> 05:15.280
the top telling

105
05:15.280 --> 05:17.600
us when events happened.

106
05:17.600 --> 05:21.600
There's audit logs and there's ACL logs.

107
05:21.600 --> 05:24.970
We don't have anything under ACL logs here because I don't have any ACLs

108
05:24.970 --> 05:25.760
configured in

109
05:25.760 --> 05:27.720
my environment right now.

110
05:27.720 --> 05:31.760
The main thing of course we're here to look at though is multi cloud.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

110
05:27.720 --> 05:31.760
The main thing of course we're here to look at though is multi cloud.

111
05:31.760 --> 05:34.240
So let's click here on multi cloud.

112
05:34.240 --> 05:39.330
This will give us a nice little box again specifically about AWS because that's

113
05:39.330 --> 05:40.280
the only

114
05:40.280 --> 05:43.760
cloud on ramp that I have deployed right now.

115
05:43.760 --> 05:48.830
This though, it tells us things like if the cloud gateways are up, in this case

116
05:48.830 --> 05:49.400
we have

117
05:49.400 --> 05:51.600
one cloud gateway up.

118
05:51.600 --> 05:55.670
We can see if we have the cloud edge devices are up there are currently two up

119
05:55.670 --> 05:56.520
and connected

120
05:56.520 --> 05:57.520
sites.

121
05:57.520 --> 05:59.280
We have one connected site.

122
05:59.280 --> 06:02.580
There's some more generic information of course here at the bottom telling us
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

122
05:59.280 --> 06:02.580
There's some more generic information of course here at the bottom telling us

123
06:02.580 --> 06:02.960
we have

124
06:02.960 --> 06:10.230
four tunnels, one connected tag for our routing, one connected host VPC and one

125
06:10.230 --> 06:11.960
connected VPN

126
06:11.960 --> 06:13.520
connection.

127
06:13.520 --> 06:16.380
If you want more information on any one of these, you can also click on the

128
06:16.380 --> 06:17.080
little numbers

129
06:17.080 --> 06:22.250
here and it'll do a pop out giving you more information about that particular

130
06:22.250 --> 06:23.240
gateway.

131
06:23.240 --> 06:28.080
Here we can see my cloud gateway CGW one and we see things like it's got a

132
06:28.080 --> 06:29.360
green checkmark

133
06:29.360 --> 06:30.520
for health.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

133
06:29.360 --> 06:30.520
for health.

134
06:30.520 --> 06:34.520
We've called the account connecting to it Amazon AWS.

135
06:34.520 --> 06:36.560
It's in us East one.

136
06:36.560 --> 06:42.400
We can see the cloud account ID that it's an AWS cloud type and so on.

137
06:42.400 --> 06:46.000
If we shrink this down, we could look at the cloud edges.

138
06:46.000 --> 06:49.310
Notice what this is actually doing though is it's really just taking us back to

139
06:49.310 --> 06:49.880
the device

140
06:49.880 --> 06:57.520
tab with a built in filter showing us just the devices that are running in AWS.

141
06:57.520 --> 07:01.840
In fact, it even says right here that there are currently two filters applied.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

141
06:57.520 --> 07:01.840
In fact, it even says right here that there are currently two filters applied.

142
07:01.840 --> 07:04.840
So it just really filters this output.

143
07:04.840 --> 07:09.490
But overall, this is the information we can see about the cloud from the

144
07:09.490 --> 07:10.720
monitor page.

145
07:10.720 --> 07:16.760
However, another good place to go to get information is configuration.

146
07:16.760 --> 07:21.920
So if we come over here and we go to configuration cloud on ramp for multi

147
07:21.920 --> 07:22.560
cloud and just so you're

148
07:22.560 --> 07:26.520
aware by default, this network snapshot may not be open.

149
07:26.520 --> 07:30.620
It simply expands this section right here, but this will show you information
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

149
07:26.520 --> 07:30.620
It simply expands this section right here, but this will show you information

150
07:30.620 --> 07:31.240
about all

151
07:31.240 --> 07:32.840
of your clouds.

152
07:32.840 --> 07:37.220
Notice again, AWS is the only one I have a cloud gateway configured for, but

153
07:37.220 --> 07:37.720
notice it's

154
07:37.720 --> 07:40.280
giving us that same basic information.

155
07:40.280 --> 07:42.560
We can see we have one cloud gateway.

156
07:42.560 --> 07:48.520
We have one host VPC, four connections going to two WAN edges down here towards

157
07:48.520 --> 07:49.440
the bottom

158
07:49.440 --> 07:50.440
of the page.

159
07:50.440 --> 07:53.400
We can then see that we have good health.

160
07:53.400 --> 07:57.040
If we click on the two reachable devices, it's going to give us a little pop up

161
07:57.040 --> 07:57.400
here

162
07:57.400 --> 08:01.500
with some more information on these two routers that are deployed into the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

162
07:57.400 --> 08:01.500
with some more information on these two routers that are deployed into the

163
08:01.500 --> 08:02.120
cloud.

164
08:02.120 --> 08:05.880
So we see here that we have AWS are one and our two.

165
08:05.880 --> 08:09.740
We see their system IPs, their site IDs and so on.

166
08:09.740 --> 08:14.610
If we cancel this, we can put our mouse over the four reachable connections

167
08:14.610 --> 08:15.400
here and we

168
08:15.400 --> 08:19.300
can see the different connections, whether they're primary or secondary going

169
08:19.300 --> 08:19.780
between

170
08:19.780 --> 08:25.100
our devices here on our on-prem network and the cloud.

171
08:25.100 --> 08:27.680
Of course, other information that may be critical when we're trying to do

172
08:27.680 --> 08:28.400
troubleshooting

173
08:28.400 --> 08:33.570
is we come down here to the bottom and we go to intent management, we can go to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

173
08:28.400 --> 08:33.570
is we come down here to the bottom and we go to intent management, we can go to

174
08:33.570 --> 08:34.120
cloud

175
08:34.120 --> 08:35.720
connectivity.

176
08:35.720 --> 08:39.220
We choose our cloud provider up here at the top and then down here at the

177
08:39.220 --> 08:40.060
bottom, it's

178
08:40.060 --> 08:45.740
showing us what we intend to connect to which other networks.

179
08:45.740 --> 08:50.940
So for example, here I'm connecting my VPN 10 to the server network that I've

180
08:50.940 --> 08:51.660
deployed

181
08:51.660 --> 08:53.660
into the cloud.

182
08:53.660 --> 08:58.240
And since this is marked in green, then we can see on our legend over here that

183
08:58.240 --> 08:58.580
this

184
08:58.580 --> 09:00.900
intent is realized.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

184
08:58.580 --> 09:00.900
intent is realized.

185
09:00.900 --> 09:05.010
Essentially what that means is it's telling me this has been correctly deployed

186
09:05.010 --> 09:05.340
to all

187
09:05.340 --> 09:10.520
the devices that are needed and our tunnels are up and functional.

188
09:10.520 --> 09:15.130
So these are some really good tools that are available in SD-WAN manager in

189
09:15.130 --> 09:15.840
relation to

190
09:15.840 --> 09:18.040
cloud on-ramp.

191
09:18.040 --> 09:23.380
So in this video, we jumped into SD-WAN manager or of course V-Manage and we

192
09:23.380 --> 09:24.500
took a look at

193
09:24.500 --> 09:30.770
some of the outputs, tools, logs and alerts that we have available to us to try
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

193
09:24.500 --> 09:30.770
some of the outputs, tools, logs and alerts that we have available to us to try

194
09:30.770 --> 09:32.200
to troubleshoot

195
09:32.200 --> 09:37.680
SD-WAN in general, but with a little bit of a focus on our cloud on-ramp.

196
09:37.680 --> 09:42.320
So that actually concludes everything that we need to discuss in this skill.

197
09:42.320 --> 09:45.480
So that leaves us with just the challenge.

198
09:45.480 --> 09:47.880
Go ahead and give that challenge a shot.

199
09:47.880 --> 09:52.120
Good luck and I'll see you in the solution video on the other side.

200
09:52.120 --> 10:02.120
[BLANK_AUDIO]