You can connect a CIP to a remote 3745 as a PU4 but the 3745 will need to have another connection back to its owning VTAM, either via a channel or another FEP because VTAM cannot aquire ownership of a FEP via the CIP connection not can it be loaded over this connection.
I am not sure what you mean by SDLC/TR? Is this FEP SDLC or Token ring attached? But in any case, you can use DLSW to connect to the local mainframe via the CIP. All SNA traffic will be recognised but the CIP does not appear as a PU to the mainframe only the XCA major node is required. The session established is PU5 - PU4.
The following URL gives an example and some caveats for an SDLC connected FEP -
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...