The answer to #1 is No. Both CIP and 3172 are defined as XCA in VTAM. XCA does not provide network boundary function. In SNI scenario, at least one side of a SNI connection has to perform network boundary function. From your proposed configuration, both side of the SNI will be XCA (i.e one side is CIP, and another side is 3172) Neither side performs network boundary function. There are a couple of options for #1:
a. replace the 3725 by a 3745
b. replace the SNI connection by APPN (i.e. HPR/IP or ISR)
I do not understand configuration #2. What is CITA?
What is the SNA device on the other side of the X.25 network? Is it a SNI link?
Cisco routers does support X.25 (i.e. QLLC) on DLSw. They also converts QLLC into all sorts of media, say token ring, ethernet, SDLC, and so on, to another local interface. I assume that you want to connect an X.25 node to the CIP. This is supported by DLSw as shown in the following URL:
However, the same restriction applies on SNI links. (i.e. XCA does not provide network boundary function) If the device on CITA is a CIP, you will not bring up the connection. The end stations fails during XID exchange.
The unmanaged mode is also known as Network only switching, which is introduced in Brazos release. It adds the flexibility for customer to use only network automation for service appliance.
If a device is configured a...
Usually, we can access ESXi Shell by pressing Alt+F1 from ESXi DCUI (Direct Console User Interface).
But on HyperFlex system, it just shows black window.
This is expected behavior because HyperFlex redirects ESXi Shell output to SoL...
Configuring an Export Policy Using the GUI
This procedure explains how to configure an Export policy using the APIC GUI. Follow these steps to trigger a backup of your data:
On the menu bar, choose Admi...