dBm is a unit of power that measures the ratio of a given power level to 1 mW. The formula to convert dBm to mW is: P(mW) = 1mW * 10^(P(dBm)/10). Therefore, -20 dBm corresponds to 0.01 mW, as follows: P(mW) = 1mW * 10^(-20/10) = 0.01 mW Reference: https://www.rapidtables.com/convert/power/dBm_to_mW.html The dBm is a logarithmic unit of power relative to 1 milliwatt (mW). -20 dBm means that the signal strength is 20 decibels lower than 1 mW. In terms of mW, this is 0.01 mW. Each 10 dB decrease represents a tenfold decrease in power. Therefore, -20 dBm is 10-210-2 or 0.01 mW.

This configuration script will achieve the task as it follows the guidelines given by the Senior Engineer. It creates VLAN 20 with name Mgmt, adds L3 SVI on VLAN 20 with IP address 10.1.1.10/24, creates LAG 1 with LACP mode active for the uplink, uses VLAN 20 as the native VLAN on the LAG, and ensures that the interfaces are all ON. Reference: https://www.arubanetworks.com/techdocs/AOS-CX/10.04/HTML/5200-6790/GUID-8F0E7E8B-0F4B-4A3C-AE7F-0F1B5A7F9C5D.html Edge1# conf t vlan 20 name Mgmt interface vlan 20 ip address 10.1.1.10/24 no shut interface lag 1 no shut vlan trunk native 20 vlan trunk allowed all lacp mode active interface 1/1/51 no shut lag 1 interface 1/1/52 no shut lag 1 exit This script correctly creates VLAN 20 with the name 'Mgmt', adds an L3 SVI for management using the specified IP address, and configures LACP for link aggregation (LAG 1) using the active mode. It also sets VLAN 20 as the native VLAN on the LAG and ensures all interfaces are enabled ('no shut' is the command to bring up the interface if it has been administratively shut down).

Layer 2 MAC authentication is a method of authenticating devices based on their MAC addresses without requiring any client-side configuration or credentials. The switch sends the MAC address of the device to an authentication server such as ClearPass or RADIUS, which checks if the MAC address is authorized to access the network. If yes, the switch grants access to the device based on the assigned role and policies. If no, the switch denies access or redirects the device to a captive portal for further authentication. Reference: https://www.arubanetworks.com/techdocs/ArubaOS_86_Web_Help/Content/arubaos-solutions/1-overview/mac-authentication.htm

On an Aruba CX 6300M switch, routing between Switch Virtual Interfaces (SVIs) is enabled by default. Therefore, traffic between SVIs, like 120 and 130, can be routed internally without the need for additional configuration such as route leaking or static routes, as long as there is no 'no routing' configuration present on the SVIs.

These commands might help troubleshoot this issue as they check various aspects of the connectivity between the edge switch and the core switch, such as Layer 3 reachability, Layer 2 adjacency, LACP configuration and status, VLAN trunking configuration, and interface status. Reference: https://www.arubanetworks.com/techdocs/AOS-CX_10_04/CLI/GUID-8F0E7E8B-0F4B-4A3C-AE7F-0F1B5A7F9C5D.html