Last updated on AUGUST 14, 2017
Applies to:Oracle Communications IP Service Activator - Version 7.2.0 and later
Information in this document applies to any platform.
On performing an upgrade of IPSA from 220.127.116.11 to 18.104.22.168, we had problems with the managed devices and the service model after we started up the network processors on the patch 7 release.
They all have 'routeLimitIPv6' in common, and on the sample PEs I checked, we have no IPv6 configuration on the devices. The elements IPSA was expecting is 'exportMap, maxRoutes, defaultMdt, dataMdt, dataMdtReuse etc.'. This is with error 100.1221.
They were paired with a 100.3300 error saying 'Target device model for is not valid'.
Error Message NetworkProcessor log:
20141113-054844|978|DEBUG|Thread-8||||proxy_np|smcevoy-lnx-au|validateDm:Validation error: Expected elements 'maxRoutes defaultMdt dataMdt dataMdtReuse' instead of 'routeLimitIPv6' here in element vrf
20141113-054844|979|ERROR|Thread-8|22.214.171.124|||proxy_np|smcevoy-lnx-au|Caught XML exception org.apache.xmlbeans.XmlException: Target device model for device router1 is not valid
This issue only affects cisco devices managed by the Cisco IOS Cartridge.
Step's to reproduce:
- Create a VRF
- with both exportMap and routeLimit defined
This has been tested with just IPv4 and also with IPv6.
Upgrade to IPSA 7.2.0 Patch 7
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms