The native VLAN is defined in the configuration of the switch. In this situation, the Ignite server might not have access to the native VLAN of the client.
If the Ignite server does not have access to the native VLAN, it will not have access to any of the untagged traffic from the client. This becomes a problem, since during an
Problems with VLAN configuration can be difficult to detect, since a system can be configured to use a nonnative VLAN when the operating system is running. This would, for example, allow you to create a recovery archive for the client on an Ignite server, but not allow you to recover the client from that same Ignite server.
To remedy this problem, you must provide routing between the VLANs for systems that use nonnative VLANs.
Complex network solutions
The approaches outlined in this section can be used to resolve the challenges outlined previously. In some cases, one solution will resolve multiple challenges. Other challenges might require multiple solutions.
Automating HP-UX OS version selection
During
The boot loader AUTO file controls the menu of
ln
ln
ln
ln
ln
cp /opt/ignite/boot/AUTO \ /opt/ignite/boot/Rel_B.11.23/AUTO
ln
ln
ln
ln
ln
cp /opt/ignite/boot/AUTO \ /opt/ignite/boot/Rel_B.11.31/AUTO
The B.11.23 and B.11.31 AUTO files must be edited to have different boot defaults. It is recommended you keep the other boot menu entries so users have the ability to interactively select their desired
52 Complex networks: challenges and solutions