IPAM enables
automated, periodic service monitoring of DHCP and DNS servers across a forest.
Monitoring and managing is organized into the views listed in the following
table.
|
View
|
Description
|
|
DNS and DHCP servers
|
By default, managed DHCP and DNS servers are arranged by
their network interface in /16 subnets for IPv4 and /48 subnets for IPv6. You
can select the view to see just DHCP scope properties, just DNS server
properties, or both.
|
|
DHCP scopes
|
The DHCP scope view enables scope utilization monitoring.
Utilization statistics are collected periodically and automatically from a
managed DHCP server. You can track important scope properties such as Name,
ID, Prefix Length, and Status.
|
|
DNS zone monitoring
|
Zone monitoring is enabled for forward and reverse lookup
zones. Zone status is based on events collected by IPAM. The status of each
zone is summarized.
|
|
Server groups
|
You can organize your managed DHCP and DNS servers into
logical groups. For example, you might organize servers by business unit or
geography. Groups are defined by selecting the grouping criteria from
built-in fields or user-defined fields.
|
Adding Address Spaces to IPAM
An
address space is a container that consists of a set of connected IP blocks, IP
subnets, IP ranges or IP addresses. The IP ADDRESS SPACE pane contains all the
IP objects discovered or created. Non-virtualized network objects are always in
the IP ADDRESS SPACE pane.
When
you manually add IP addresses to IPAM, you can add either IPv4 or IPv6
addresses. When you use the IPAM console to add IP addresses, default values
are automatically filled in for required fields, except for the IP addresses.
You can add or import any of the following:
•
IP Address Block. When you add an IP Address Block, supplying the Network ID
and Prefix length allows the start IP address and End IP address to be
calculated automatically for you. Additionally, if you enter a non-private IP
address range, you must specify the Regional Internet Registry where the
addresses are registered and the date range for the registration. Optionally,
you can add a brief description and an owner.
The
following Windows PowerShell cmdlet Add-IpamBlock can also be used to
add an IP Address block:
Add-IpamBlock –NetworkID <network
prefix, in Classless InterDomain Routing (CIDR) notation> - Rir <string>
The RIR value is
optional for private addresses. If you are specifying the RIR then the value
must be one of: AFRNIC, APNIC, ARIN, LACNIC, or RIPE.
IP Address Subnet. When you add
an IP Address subnet, you must provide a friendly name for the subnet.
Additionally, you must specify the Network ID and Prefix length.
There are several optional
settings when adding an IP Address subnet. You can specify one or more VLANs to
be associated with the subnet, whether or not the subnet is virtualized, or
custom fields such as AD site or VMM IP Pool Name. As with the other IP address
types, you can add a brief description and an owner.
The Windows PowerShell cmdlet Add-IpamSubnet
can also be used to add an IP address subnet. When using Add-IpamSubnet you
must also specify it the network type is NonVirtualized, Provider, or Customer
IP Subnet. You must specify the address space to which the Customer IP Subnet
will be added.
Add-IpamSubnet –NetworkID <network prefix, in Classless InterDomain Routing (CIDR)
notation> - Rir <string>
• IP Address Range. You can use
an IP Address range to further divide an IP Subnet. When you create an IP
address range you must specify the Network ID and either the Prefix length or
Subnet mask. Additionally, if an IP address does not already exist that contains
the addresses in the IP address range you are creating, you can select to have
one automatically created. The other required fields, Managed by Service,
Service Instance, and Assignment Type will use default values unless otherwise
specified. As with the other IP address types, there is a large variety of
custom fields available to describe the IP address range.
You can also use the Windows
PowerShell cmdlet Add-IpamRange to add an IP Address range. When you use
Add-IpamRange, you must also specify if the network type is
NonVirtualized, Provider, or Customer IP range. You must specify the address
space to which the Customer IP Subnet will be added.
Add-IpamRange –NetworkID <network prefix, in Classless InterDomain Routing (CIDR)
notation> - CreateSubnetIfNotFound
• IP Address. IPAM provides
end-to-end management of IP addresses, including synchronization with DHCP and
DNS. You can use the IP address to associate the address with DHCP
reservations; however, when you use Windows PowerShell to create the IP
address, IPAM does not automatically create the reservation. You can discover
duplicate addresses by the Managed by Service and Service Instance properties
of an IP address. IPAM automatically maps an address to the range containing
the address. When creating IP an address, the only required information that
you have to provide is the IP address itself. The other required fields,
Managed by Service, Service Instance, Device Type, Address State, and
Assignment Type will use default values unless otherwise specified. As with the
other IP address types, there is a large variety of custom fields available to
describe the IP address.
You can use the Windows PowerShell cmdlet Add-IpamAddress
to add an IP Address. When you use Add-IpamAddress, you must also
specify the IP address
0 التعليقات:
إرسال تعليق