Cisco Cisco Prime Network 3.8 Release Notes

In VLAN view, a path trace that ends on a LAG port does not run

BGP Neighbor Loss syslog is not correlated to Device Unreachable ticket

Tickets generated for link down and LAG link down alarms on an unreachable 
device do not correlate

Terminating Ethernet flow points under a switching entity that are not connected 
to another Ethernet flow point in the same NetworkVlan are not recognized as 
edges

OSPF neighbor down event may not correlate to link down or interface status down 
event

Duplicate switching entities are created after deleting and then recreating a VLAN

AVM 11 stops after continuous Find EVC by Name operations

Trunk service link is disconnected after configuring a static VLAN mapping that 
includes an inner VLAN tag

BFD links are not removed from the GUI after clearing a BFD connectivity down 
ticket

ISIS neighbor data is not created for both IPv4 and IPv6 address families

Duplicate MPLS-TP network service objects are not automatically removed

After a P2MP tunnel's status changes from Up to Down, the change is not reflected 
in Prime Network

Some OSPF interfaces and neighbors are not modeled for CRS device

Incorrect BDF links might be discovered for a BDF configuration that has 2 of the 
same source IP addresses with different destinations

Wrong serial connection through CDP in MLPPP technology

Modification of destination and source port not reflected in Prime Network

Links table may display links which have no context but are not marked as external

LAG link is not rediscovered after clearing and removing the ticket

Physical and Ethernet links disappear after moving and restarting AVM

Error messages sometimes appear when trying to connect devices that were once 
connected to the cloud and later removed back to the cloud

BGP does not model in Prime Network if the BGP AS number contains a dot 

Extra EVCs are created for network VLANs whose bridge domain (that contains a 
terminating Ethernet flow point) is not recognized