Re: Can we bind secondary IP segment on CIP connection
Communication between a channel-attached mainframe that runs virtual telecommunications access method (VTAM) and a LAN/WAN-attached Physical Unit (PU) 2.0 SNA node.
Communication between a channel-attached mainframe that runs VTAM and a LAN/WAN-attached PU 2.1 SNA node.
Communication between a channel-attached mainframe that runs VTAM and a LAN/WAN-attached PU 5/4 SNA node. WAN attachment is restricted to RSRB and DLSw+.
Communication between two channel-attached mainframes that run VTAM to the same CIP card, or different CIP cards, in a 7000 router. The two VTAMs can be configured as PU5s or PU 2.1 nodes. External communications adapter (XCA) major nodes do not provide network boundary function. Therefore, the remote connection must be to an NCP, a PU4, if the CIP is configured as an SNI link.
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...