Hi we got a MSFC and a CSM module on Cisco 6513 switch. Csm is in bridged mode. The problem is we can reach the servers behind CSM with no problem. But we can not ping any of the VLAN interfaces on the MSFC from the servers . What might be the problem ?
The problem may be that both the CSM client and server vlans are configured in the MSFC. When using a CSM, only the client or the server vlans can be configured in the MSFC, but not both. If both are configured, the MSFC will route traffic rather than passing it through the CSM.
The first test you should try is to ping the CSM server vlan address from the reals. Ensure that the default gateway configured in the reals is the MSFC ip address for the CSM's client vlan, which should also be pingable from the reals.
The CSM only functions correctly with a single "gateway" configured. In CSM bridge mode, you do not require any gateway configured, so if you have multiple then you should remove them all, then test again.
Try pinging MSFC interfaces or to networks beyond the MSFC for your testing, rather than the CSM interfaces. When using multiple client and server vlans on the CSM, problems such as this are not uncommon, but frequently the routing is actually working fine beyond the CSM.
If the CSM is the cause, you will see "Drops vs/vlan" in the output of "show module csm tech all", indicating that the CSM is trying to route, then dropping the packets because the ingress+egress ports for the ping and response do not match. Often removing all route and gateway statements from the CSM config can resolve this.
Strange things going on again. We tried to move vlan 143 behing FWSM module and we are started having problems again. And even the case engineers couldnt find a solution to this. We can ping some of the servers from behind the msfc and we can NOT ping some of them from the FWSM. Im attaching all the sh tech outputs. If someone can figure this out Ill really appreciate it.
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...