New and Changed Information
The following tables provide an overview of the significant changes to this guide up to this current release. The table does not provide an exhaustive list of all changes made to the guide or of the new features up to this release.
Changed Feature |
Description |
Where Documented |
---|---|---|
NTP server |
Enables client switches to also act as NTP servers to provide NTP time information to downstream clients. |
NTP Server |
Port Profiles | Added instructions to configure the port type as uplink or downlink. | Provisioning Core ACI Fabric Services |
NTP Authentication Support |
HMAC NTP authentication support |
Provisioning Core ACI Fabric Services |
System Settings |
Added fabric-wide System Settings instructions |
Provisioning Core ACI Fabric Services |
The SNMP Trap Aggregation |
Enables SNMP traps from the fabric nodes to be delivered to one of the APICs in the cluster. |
SNMP Trap Aggregation |
Basic GUI topics removed |
Basic GUI procedures are no longer supported |
The following topics have been removed:
|
Changed Feature |
Description |
Where Documented |
---|---|---|
Contract Preferred Groups |
The contract preferred group feature enables greater control of communication between EPGs in a VRF. If most of the EPGs in the VRF should have open communication, but a few should only have limited communication with the other EPGs, you can configure a combination of a contract preferred group and contracts with filters to control inter-EPG communication precisely. This feature was introduced in Cisco APIC, release 2.2(1n), and added to this guide in release 3.0(2h) |
Basic User Tenant Configuration |
Basic User Tenant Configuration reorganized |
The chapter table of contents was reorganized for ease of searching. |
Basic User Tenant Configuration |
Changed Feature |
Description |
Where Documented |
---|---|---|
Intra-EPG contracts |
You can crate intra-EPG contracts to control traffic between endpoints in the same EPG, allowing some traffic and barring the rest. Without intra-EPG contracts, communication between endpoints in the same EPG is either unrestricted (by default) or completely barred through intra-EPG isolation. |
Basic User Tenant Configuration |