We can use the Get-NetIPInterface cmdelt to list all network interfaces that start with the word “Ethernet” and verify they’re using DHCP to acquire their IP addresses: PS C:\> Get-NetAdapter -Name “Ethernet” | Format-List -Property Virtual We can use the -Physical option to make sure these are physical adapters not virtual ones: Name InterfaceDescription ifIndex Status MacAddress LinkSpeedĮthernet 2 Broadcom NetXtreme Gigabit Ethernet #2 13 Up A4-BA-DB-0A-96-0C 100 MbpsĮthernet Broadcom NetXtreme Gigabit Ethernet 12 Up A4-BA-DB-0A-96-0B 100 Mbps The Get-NetAdapter cmdlet can be used to display the available network adapters as follows: PS C:\> Get-NetAdapter Let’s use Windows PowerShell to examine the initial network configuration of the server. Examining the initial network configuration I didn’t have a spare Gigabit Ethernet switch in my lab so I’m using a 100 Mbps Fast Ethernet switch instead, so the server’s built-in network adapters autonegotiate 100 Mbps link speeds. The server is on a test network that has another server deployed as the domain controller, DNS server and DHCP server for the Active Directory domain. I’ve performed a clean install of Windows Server 2012 R2 on the server and am logged on as Administrator.
Test environmentįor my test environment I’m using an old Dell T300 server that has two built-in GbE network adapters.
#Powershell mac address table how to#
We’ll begin by examining how to do this on a physical server and then in the next article we’ll look at how to do it in a virtual machine. Now that we’ve examined what Windows NIC Teaming is, how it works, what scenarios it supports, and what considerations matter when implementing it, we can finally move forward and look at how to implement it using Windows PowerShell. Windows NIC Teaming using PowerShell (Part 8).Windows NIC Teaming using PowerShell (Part 7).
0 kommentar(er)
