I found my mistake, if we can call it as a mistake
Yesterday I was using just a class-maps (without any types) to define source ranges but then with applying those classes in policy-maps ACE complained that this class is not expected to be here or also Error: Specified class-map is not consistent with the policy-map type, depends on the configuration I tried to create.
I just tried to create
class-map match-anyNAME and then use it in the policy-map type loadbalance first-match NAME
but I have to create class-map type http to use it in the policy-map type loadbalance first-match NAME
or to create class-map type generic NAME and use it in the policy-map type loadbalance generic first-match NAME, both configurations are working.
Maybe I`m not understanding the main idea of all those types but this stuff is quite confusing...
Would you please to explain my main mistake in the association between class-map type and policy-map.
Normal class-maps are used to define the L4 information of a VIP (mainly address and port). These classes are then configured under a multi-match policy-map and associated to an interface.
The class-maps defined by type, however, are designed to match on L7 parameters (HTTP URL, cookies...). These are defined under a load-balance policy-map and then associated with a L4 class.
The idea is that the ACE will first match on the L4, and then, go into the load-balance policy-map and try to match on the different L7 classes.
You're case is a bit more complex to understand because common sense says that source address should be a L4 parameter, and in a way it is. It is possible to define a VIP by a combination of destination address and source address (it would be a match-all class map), but it is normally preferred to define it as a L7 parameter because most people consider L4 the "basic" load-balancing parameters and L7 the "advanced" ones.
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...