Release Notes

9
Cisco Prime DCNM Release Notes, Release 7.0.(2)
OL-31385-01
Supported Cisco Platforms and Software Versions
• Migration from DCNM 7.0.(1) to DCNM 7.0.(2), page 9
Auto Instantiation of OSPF config profiles behind VPC+
OSPF config behind vPC+ needs different IP addresses for VPC peering, primary switch and secondary
switch need different gateway IP Address. In order to support this, a new field Secondary Gateway IP
has been added to the Cisco DCNM Web Client at Config>Auto Configuration>network screen, in the
Service Configuration Parameters area. Also, you must provide and receive this attribute when you use
the DCNM REST API to create, update and get a network.
Service Automation
once the tenant and associated service segments are created, service virtual machines should be
instantiated dynamically. In order to support this, in the Cisco DCNM Web Client, a new Network Role
mandatory field has been added to the network screen at Config>Auto Configuration. The following
values are available for the Network Role.
• Host network (Default)
• Service-ES Network
• Service-LB Network
• Management Network
• External Network
• Service-vPath Network
DFA template/script support for In-band POAP and Management
Updated DFA POAP templates are included with added options including In-band POAP and
Management. This option allows POAP, as well as management through the fabric (rather than using an
out-of-band management network connected to mgmt0 ports); also XMPP, LDAP, and VPC keep-alive
traffic will be sent over a management VLAN.
Migration from DCNM 7.0.(1) to DCNM 7.0.(2)
There are types of migration scenario from DCNM 7.0.(1) to DCNM 7.0.(2).
• Cisco DCNM Migration with a local PostgreSQL database.
• Cisco DCNM Migration with an external Oracle database.
• Cisco DCNM migration in a HA environment.
Supported Cisco Platforms and Software Versions
For information about the software platforms and versions that Cisco DCNM supports, see the Cisco
DCNM Release Compatibility Matrix.