we have an AMD physical machine which is connected through a VLAN. Without using any identification of the active VLAN, the AMD could not have been reached through the network. Only when following red hat's instructions (https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s2-ne...), the system could have been reached, but at that point, the list of interfaces included the new vlan interface and when trying to change port modes, we recevied error messages.
Has anyone done something similar ?
This is a newly installed AMD which is connected (Communication wise) to the network through a specific VLAN. Without creating a manual definition for the VLAN on the ethernet ifcfg files, the AMD cannot be accessed from the network. However, when defined, it can be accessed, but then when using rtminst trying to change port modes for capturing ports, it fails because it says the configuration is wrong.
You can do the capture port definition manually by editing in VI () or using MC
But if what you describe is a fact then I suggest you open a ticket as RTMINST should be tolerant for VLAN's
PS - Support guys can help you with the editing as well as creating a ticket for the problem