It is possible that the AS/400 is indicating "search me" on it's CP Capabilities when it starts CP-CP sessions with SNASw. This means it will not register its LUs, but instead wants it's NN server to forward ALL Locate searches to it.
Take a look at the DLC trace next time the AS/400 connects in. In the CP Capabilities (x12C1), look at CV33, byte 2, bit 0. If this bit is on, the AS/400 requests to be searched.
I think this is pretty inefficient, as it takes away one of the features of SNASw, which is the ability to limit its role in network searches. I don't know how to control the "search me" feature in AS/400, but I recommend turning it off. This will cause the AS/400 to register its LUs, and receive searches only for LUs it actually owns.
This is the only explanation I can think of for what you are seeing.
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...