Administrators must use the following procedure for correct configuration of a Virtual Gateway Central Deployment. Steps are as per below.
Step 1 Before you connect both interfaces of the CAS to the switch, physically disconnect the eth1 interface.
Step 2 Physically connect the eth0 interface of the CAS to the network.
Step 3 Add the CAS to the CAM in the CAM web console under Device Management > CCA Servers > New Server
Step 4 Manage the CAS by accessing the CAS management pages, via Device Management > CCA Servers > Manage [CAS_IP]
Step 5 Configure VLAN mapping. This is a mandatory step for a Central Deployment where both interfaces of the CAS connect to the same switch. (Note that you can configure VLAN mapping in Edge Deployments with no adverse affect, but you are not required to do so.)
a. Make sure you check the "Enable VLAN Mapping" checkbox and click Update.
b. Make sure to set the Untrusted VLAN-to-Trusted VLAN mapping under Device Management > CCA Servers > Manage [CAS_IP] > Advanced > VLAN Mapping.
Thank you for the reply. Was able to resolve this issue thru TAC. The problem was that the IP address I used to managed the switch from the CAM was not the same one used by the switch to connect back to the CAM.
Long story short, I re-added using the IP address of the switch (3750) that it uses to communicate back to CAM and it fixed it.
Looking at it, it kinda makes sense as I have several SVI's on this 3750 with 'ip routing' enabled.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...