Hi. I have a device that can talk SNA only over the DIX/Ethernet2 frame format. For this reason, it cannot communicate via Ethernet transparent bridging with our mainframe OSA Express, which requires SNA to ride the 802.3/802.2 Ethernet frame format.
My intention has been to try to resolve this by configuring DLSW (Ethernet-to-Ethernet) between two routers placed between these non-communicating devices. The hope is that DLSW will use the required 802.3 frame format to communicate on one side with the mainframe (which of course does work) and use the DIX Ethernet frame format to communicate on the other side (separate router) with the device that requires SNA to use DIX.
There is a command for this purpose, source-bridge enable-80d5, but I don't know if that command has any effect Ethernet-to-Ethernet, transparent bridging only. Without it, over Ethernet, is DLSW "smart enough" to use the frame format required by the end host?
Re: Will or can DLSW talk SNA over DIX/EthernetII?
source-bridge enable-80d5 is local significant. It does not know the interface type of the remote dlsw router. In other words, the router with source-bridge enable-80d5 configured (say Router_a) understands DIX frames. The Router_a converts the DIX frames into information required by DLSw SSP protocol (i.e. SSAP, DSAP, MAC addresses and so on). Router_a has no idea how the remote DLSw router use the information.
Similarly, Router_a converts a DLSw frame into DIX frames. The remote DLSw router has no idea that Router_a is using DIX frame format.
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...
RBAC users like email@example.com may fail HX Connect login. At that time, "Incorrect user name or password(100005)" is shown as a failure reason.
RBAC users can login to vCenter server. So, RBAC username and passwo...