Access point models

Access points represent functions that a computer provides to other entities for their use, such as a network address or an IP address. Each access point is modeled by the BMC_AccessPoint class. This characteristic is further defined by the BMC_ProtocolEndpoint class, the only direct subclass of the BMC_AccessPoint class. Among other types of access points, a network address, such as an IP address, MAC address, or IPX address is captured as a subclass of the BMC_AccessPoint class.

Logical identity of the BMC_IPEndpoint class

An IP address is modeled as an instance of the BMC_IPEndpoint class. Like any child instance of the BMC_ComputerSystem class, an instance of the BMC_IPEndpoint class is identified by the Name attribute in conjunction with the SystemName attribute. Therefore, the Name attribute represents the local name of the CI in the context of the computer that is hosting it, as described in the following table:

Attribute	Usage
Name	Identifies the child instance in the context of the parent instance of the BMC_ComputerSystem. Name must be an IPv4 or IPv6 address, and must be formatted as decimal numbers delimited by a period, with no leading zeros.
NameFormat	Sets the heuristic used to generate the Name value. This value must be set to IP.
SystemName	Specifies the name of the system. This must be the same as the parent instance of the BMC_ComputerSystemName attribute. This attribute is automatically populated from the related CI when a weak relationship is created between the computer system and the operating system.

Additional attributes of BMC_IPEndpoint class

The following table describes the additional attributes of the BMC_IPEndpoint class:

Attribute	Description
Address	The IP address. This value must be compliant with AddressType.
AddressType	The enumeration that defines the type of address. This value must be set to either 0 (Unknown), 1 (IPv4), or 2 (IPv6).
DNSName	The system name based on its DNS name. The DNS name corresponds to the IP address; therefore, when you want to search a system by DNS name, you should look up the IPEndpoint CIs, and then the parent computer.
ProtocolType	The enumeration that categorizes and classifies instances of this class.
ShortDescription	A caption of the IP address.
SubnetMask	The IP address subnet mask.
ManagementAddress	The selection that defines if the IP address is a management address such as a discovered address or an SNMP address.

Logical identity of BMC_LANEndpoint class

A MAC address is modeled as an instance of BMC_LANEndpoint. Like any child instance of BMC_ComputerSystem, a MAC address is identified by the Name attribute in conjunction with the SystemName attribute that represents the name of the parent instance of the computer. Therefore, the Name attribute represents the local name of the CI in the context of the computer that is hosting it, as described in the following table:

Attribute	Usage
Name	Identifies the MAC address. The value must be an address suffixed by an index. The index uniquely identifies a MAC address for situations where multiple identical MAC addresses are configured within the same system. The index is generally the index of the MAC address entry in the SNMP MIB.
NameFormat	Specifies the heuristic used to generate the Name value. This value must be set to MACAddress:Index.
SystemName	Specifies the name of the system. This must be the same as the parent instance of the BMC_ComputerSystemName attribute. This attribute is automatically populated from the related CI when a weak relationship is created between the computer system and the operating system.

Additional attributes of BMC_LANEndpoint class

The following table describes additional attributes of the BMC_LANEndpoint class:

Attribute	Description
Address	The MAC address.
ProtocolType	The enumeration that categorizes and classifies instances of this class, such as for 14 (for Ethernet).
ShortDescription	A caption of the MAC address.

Access point binding

Some access points use the services provided through another access point. You can use access point binding to establish a layering of two protocols, with the upper layer represented by the dependent and the lower layer represented by the antecedent. This binding is modeled in the CDM by the BMC_Dependency relationship with the Name attribute set to BindsTo.