WEBVTT 00:05.950 --> 00:12.050 The exchange management shall include several command letters that allow you to configure the network 00:12.380 --> 00:15.970 connections used by the servers in a dock. 00:16.010 --> 00:24.860 After you created the dock networks or after they've been added automatically by a dark network discovery 00:25.190 --> 00:32.900 you can view the dock networks and their settings modify the replication configuration or remove them 00:32.900 --> 00:34.100 completely. 00:34.100 --> 00:41.650 This video provides multiple examples of how you can perform all of these tasks from the shell. 00:41.660 --> 00:43.550 Now for your information. 00:43.550 --> 00:52.850 In previous versions of exchange Microsoft commanded at least two networks for dogs one mapping network 00:52.850 --> 00:59.150 for client connections and one replication network with exchange 2016. 00:59.150 --> 01:03.170 Multiple networks are still supported by Microsoft. 01:03.180 --> 01:08.190 The recommendation depends on the physical network topology. 01:08.240 --> 01:16.400 While there are multiple physical networks between dark members that are physically separate from one 01:16.400 --> 01:22.980 another using a separate map and replication network provides additional redundancy. 01:23.180 --> 01:32.150 However if there are multiple networks that are part partially physically separate but converge into 01:32.150 --> 01:40.300 a single physical network then you then a single network for both my band replication traffic is the 01:40.320 --> 01:41.180 recommended 02:12.870 --> 02:21.000 to view the configuration set and so your existent dark networks you get data base availability to group 02:21.030 --> 02:29.970 Network Command let the output of the command will reveal the network CNN an organization with a single 02:29.970 --> 02:32.910 dog the identity of the network. 02:32.910 --> 02:40.600 The replication state and those four shaded networks will be provided when you create a dark exchange 02:40.620 --> 02:49.110 will automatically discover the existing network configurations and connections on each server and create 02:49.110 --> 02:52.460 a dark network for the corresponding IP subnet. 02:52.740 --> 03:00.060 Although there is a common blood cold new database availability group network you would rarely need 03:00.060 --> 03:04.370 to use it as this is generally done automatically. 03:04.500 --> 03:11.550 If you need to force exchange to rediscover the Dark Matter network configuration after all changes 03:11.550 --> 03:19.470 have been made you can use the set database availability to Group Command led so Let's type in said 03:19.470 --> 03:20.940 database availability. 03:20.940 --> 03:29.490 Group dark dash discover networks will simply provide the name of the dark and you the Discover network 03:29.490 --> 03:36.960 switch parameter to indicate that exchange should search for changes in the network configuration. 03:36.960 --> 03:43.020 Now by default all dark networks are used for lock shape and unseat him. 03:43.050 --> 03:50.010 If you do not want to allow replication on a specific network use the set database availability. 03:50.010 --> 03:51.410 Group Command led. 03:51.480 --> 03:56.060 So lets type the following one liner said database availability. 03:56.070 --> 03:58.360 Group dog manual. 03:58.420 --> 04:05.010 Dog network configuration equals 2 True set database availability. 04:05.040 --> 04:14.510 Group Network dog backslash market dog network with replication enabled equal into false. 04:14.610 --> 04:22.730 You may consider doing this if you want to set dedicated dog networks for replication and hard beating. 04:22.740 --> 04:29.700 Please note that in the event of a failure affecting their replication network it is a market network 04:29.700 --> 04:38.520 is unaffected by the failure log shaping and seed and operations will revert to using their market network. 04:38.580 --> 04:44.440 Even if the mapping network has its replication enabled properties set to false. 04:44.730 --> 04:51.960 Additionally you may have other networks connections on your mailbox sorrows that should not be used 04:51.960 --> 04:53.670 by the dog at all. 04:53.670 --> 05:01.530 This is commonly seen with ice cores and network adapters that are used only for connecting to a storage 05:01.650 --> 05:10.230 area network since exchange will attempt to discover all network interfaces and add a dark network for 05:10.230 --> 05:11.160 each one. 05:11.220 --> 05:18.390 You'll need to completely disable those dark networks if they are not to be used. 05:18.390 --> 05:20.350 Take a look at this example. 05:20.430 --> 05:24.120 Set database availability group network. 05:24.240 --> 05:26.770 Dog backslash dog network. 05:26.940 --> 05:29.190 Or example dog network. 05:29.190 --> 05:30.920 Ignore network set. 05:31.030 --> 05:31.960 To true. 05:32.140 --> 05:39.510 And this example dog network which is example dog network will be ignored by the dog to remove this 05:39.510 --> 05:40.580 restriction. 05:40.580 --> 05:48.600 Use the same command letter and said the ignore network parameter to false for the required dog network. 05:48.600 --> 05:56.760 Now when making modifications to dog networks you may need to rename or remove one or more networks. 05:56.760 --> 06:02.820 This can be easily done in league change management council but if you like to work in the shell you 06:02.820 --> 06:05.330 can do this quickly with the built in command. 06:05.340 --> 06:15.030 Let's for example assume that you need to rename some example dark natural or to remove some dark matter. 06:15.060 --> 06:22.860 For this you can use the remove database availability group Network Command lad to deliver the network. 06:22.980 --> 06:27.610 To do this just type remove database availability group network. 06:27.720 --> 06:33.150 The name of the network and confirm parameter set to false. 06:33.150 --> 06:39.510 Alternatively we can tell exchange to automatically configure the docs network which is the default 06:39.540 --> 06:44.020 behavior and this will remove the unwanted network. 06:44.040 --> 06:47.700 You can type the following command set database availability. 06:47.700 --> 06:54.150 Group dark manual dark natural configuration set to false. 06:54.150 --> 07:01.200 If for any reason you need to or want to rename a network then this can be done using the following 07:01.200 --> 07:03.980 command set database availability. 07:03.990 --> 07:05.160 Group Network. 07:05.250 --> 07:09.540 The name of the network you want to remove and then dash. 07:09.540 --> 07:17.670 Name parameter followed by can you name some words about replication compression and encryption Lee 07:17.670 --> 07:26.490 change management shall allows you to configure some dark properties that are not available in the exchange. 07:26.640 --> 07:34.780 Administrative Center some of these include the dark IP addresses when used the disappear port used 07:34.780 --> 07:42.850 for replication and the network encryption and compression settings docs support the use of encryption 07:42.850 --> 07:52.260 by leveraging the encryption capabilities of the vendor server docs use Cerberus authentication between 07:52.280 --> 08:01.510 exchange service and its security support provider or SSP so it uses for encryption encrypt message 08:01.520 --> 08:10.480 chant and group decrypt message API is to handle encryption and decryption of dark network traffic. 08:10.540 --> 08:20.980 This typically uses advanced encryption standard or a C S 256 bit encryption protocol potentially with 08:20.980 --> 08:31.310 the NSA Shay harsh based message authentication code to maintain integrity of the data in order to configure 08:31.330 --> 08:33.260 dark network encryption. 08:33.370 --> 08:41.040 You use a set database availability Group Command led with the network encryption parameter so lets 08:41.040 --> 08:50.650 type set database availability group Dog Dish Network encryption enabled the possible encryption settings 08:50.740 --> 08:59.080 are disabled network encryption is not used in this case enabled in this case network encryption is 08:59.080 --> 09:04.270 used for both replication and seeding into a sub now only. 09:04.390 --> 09:12.040 This is the default setting network encryption is used when replicate and across different subnets and 09:12.300 --> 09:21.500 see it only network encryption in this case is only used for CRM similarly to network encryption docs. 09:21.520 --> 09:30.040 Also support built in compression when using compression Express is used for dark matter communication 09:30.310 --> 09:38.040 which is Microsoft's implementation of the LC 77 compression algorithm. 09:38.040 --> 09:48.070 This is the same type of compression used in other Microsoft protocols such as Ma PR P.C. network compression 09:48.070 --> 09:54.050 is also proper to the entire dark and of a dark network. 09:54.100 --> 10:02.600 You can configure dark network compression using the set database availability Group Command led with 10:02.600 --> 10:08.590 a network compression parameter so lets type it set database availability. 10:08.590 --> 10:16.730 Group dark dash network compression enabled the possible compression sentence for the doc network communication 10:16.910 --> 10:26.230 SA disabled network compression is not used enabled network compression is used for both replication 10:26.230 --> 10:29.930 and seeding and intra subnet only. 10:30.010 --> 10:36.610 This is a default set and again network compression is used when replicate and across different subnets 10:36.790 --> 10:41.920 and it seemed only natural compression is only used for seeding.