with duplicate MAC addresses in an ethernet environment. It works by keeping one of the 2 adapters inactive. There is an LLC session between the HSMA control adapters that is used to determine which adapter should be active and to determine whether the other adapter is alive.
Yes you can share the IP address among multiple PUs.
The easy answer to (1.) is that it's the only way to provide more than 255 LU Sessions (the limit for a PU Type 2 device) at a single IP address. For (2.) the answer is that it hints at the more complete answer below. And the answer to (3.) is that you can't, that it shouldn't matter, only what LU it connects to, and again see more below.
In the simplest design, all of the LUs would be dynamically created, so would effectively be one large pool, and you wouldn't care which IP address or token adapter the client attached to. For most people, some or most of their TN3270 works this way. But most also have some applications for which they need to have a deterministic mapping between TN3270 Client and SNA LU. So they will have multiple IP address's, some representing pools of LUs, and some representing specific, or small groups of, LUs.
Within these constraints there are options for how the specific LUs are created. Ranging from static pre definitions, through the lu-seed wildcard naming shown in your sample, to taking the names directly from TN3270E Clients. The last of these allowing the possibility of moving all sessions into the large pool model, but at the cost of implementing and maintaining client configurations. There's more on this, and better addressed, in the design guide.
What I think is important though, is that it is the IP side of the TN3270 Server that can provide the better hot standby - high availability solution. Because it's a TCP connection, any of a variety of load balancing products or features, from NAT, Local Director, Distributed Director,... through CSM and CSS can be used to send connections to the best and/or an available TN3270 Server. As a starting point you may want to consider the advantages of all clients connecting to DNS supplied names, rather than to a coded IP address.
You should be able to create a much larger number of PUs. The last parameter in your example is the key. It's the Local SAP (lsap), and has a range of 04 to DE in multiples of 2, which yields 109 possibilities.
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...