Hello, What can we do, to can bring CPI3.2 avoiding endless IFMIB walking, causing outages at: WS-C3850-48P 16.3.3 CAT3K_CAA-UNIVERSALK9 devices? Workarround: You can stop this by setting the device in CPI to Maintanance and after waiting some minutes back to Managed. But this cant be a solution. show log: Jul 25 16:05:55.319 MEST: AUTH-EVENT: Next If index: 0 Jul 25 16:05:55.324 MEST: AUTH-EVENT: Next If index: 0 Jul 25 16:05:55.329 MEST: AUTH-EVENT: Next If index: 0 Jul 25 16:05:55.335 MEST: AUTH-EVENT: Next If index: 0 Jul 25 16:05:55.341 MEST: AUTH-EVENT: Next If index: 0 Events: Device 'xyz' is unreachable via SNMP and ping(ICMP) is successful. Steffen ... View more

Hello, Is there a known issue with Device Visualisation of Cat6800-VSS (Cisco Catalyst 68xx Virtual Switch), by means the colored device picture in top of the Device Details is missing. Is there something in plan? thx in advance for hints, Steffen ... View more

Hello, How can you make prime-infra ssh speaking with NX5K switches using cbr in place of cbc mode in their ciphers? Cisco Nexus 5672UP Switch, NXOS7.1, SSH v2 enabled No matching ciphers found: Client (x.y.z.a)supported ciphers: 3des-cbc,aes128-cbc,aes192-cbc,aes256-cbc .Server supported ciphers :aes128-ctr,aes192-ctr,aes256-ctr - dcos_sshd[2751] thx for hints in advance, Steffen ... View more

Hello,   after upgrading from LMS4.1 to 4.2.5 all UTU-Clients reach the new LMS server with IP only but not using name, that was working before. - Encrypted traces shows communication to same IP with both optionsIP versus name. - ping name, nslookup name is working - LMS server has been rebootet - one UTU has been un- and reinstalled without success    Situation behind: there are a lot of computers using UTU to th eLMS server and name scales much more than IP.   thx for hints, Steffen ... View more

Hello, after upgrading to 4.2.5 there was a problem with duplicate Cat2960 package (old and new version). After solving this with deinstall and reinstall aside the dependend autodev package, SW-Center->Device Updates shows 500.000 device packages under "Invenory, Config ...". After clicking the number you wil see a lot of duplicate OID's. What can we do, to solve the situation? thx, Steffen   ... View more

Hello, How can we increase Swap space at Prime Infrastructure v2.x? Do we keep TAC support? Will the installations with increased swapspace be still upgradeable? We monitor customer systems and there are CPI's as well via CA Spectrum. Some of them get into our attentention with Swap-Space alerts indicating to us we need to increase its Swapspace to improve the performance of the CPI's in question. thx for hints, Steffen  ... View more

Hello together,   I need help very urgently, because one Config Job actually to rollout banner, trap and syslog destinions was triggering an rollback and this rollback misconfigures devices.   1st of all I need a hint how to stop PI jobs out of control from CLI that cant be stopped via GUI (cancel = successful but keeps jub running, abort = unknown error) We shut down the Prime Network interface for urgent cause and reboot PI into a network without having access to network devices but can reach the GUI again..   Then the rollback seams to be wrong implemented: - 1st in the show logging at the afected devices you can see that  - 2nd the rollback confuse configs, by means uses config for device-1 for device-22, device-3 for device-43 and so far - all devices was accessed by this job shows in job-transcript "Failed while performing Config Archive Rollout"  with destroying the network finaly   thx for hints, Steffen ... View more

Hi,   Some devices got into Partial collection Failure. After checking trhe reason "Collection status: failed features" appaers. What does it mean? How can we solve this?   many thx for hints, Steffen ... View more

Hi, there is an unresolveable deadlock with new discovered devices stuck in syncing state, see attached screenshot. After try to delete them, "Cant delete ..., check ifm_inventory.log for details" will return. So we did: 1. rebooted NCS, because lots of "Cache status: false." found in ifm_inventory.log => no improvement 2. starting with a fresh installation, the problem reoccours. Just a little bit more devices get to a final Managed state. Discovery thread setting kept to standard. All devices in Syncing forever state are supported: 3560, 3750, 4500, 4510 Only one special circumstance: This customer is not allowed for cli-access (SSH,Telnet) to the devices, so we need to settle for SNMP access only. What can we do? Steffen ... View more