(if allowable- multiple loopbacks with unique ipaddress) multiple DLSW LOCAL-PEERs in the same data center router (7204VXR's) for defining different keepalive values for different dlsw circuits. The different values needed to
properly support different PU2.0 devices and control network recovery.
Running IOS 12.1(11.3) at datacenter and 12.0 at remote sites.
Not using border or cluster functions. Multiple local-peers allowed ? If not,
If you need different dlsw keepalives, you do not need multiple dlsw local-peer ids. DLSw peers take the lower value of the keepalives of the two. For examples, if DLSw keepalives for the centrol site is 30 second and if the DLSw keepalives for remote site A is 5 seconds, the DLSw peer connection detects underneath IP network problems in 5 seconds (3 times of the keepalive values.) If remote site B has a DLSw keepalive value of 20 seconds, the dlsw connection between the central site and remote site B is 60 seconds (again 3 times of the keepalive value)
I would like to comment that the DLSw keepalives values detect the problem on the DLSw peer connection. (i.e. the TCP pipe between DLSw peer). DLSw circuit failures are detected by LLC2, SDLC, or QLLC timers.
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...