When NETLABAE loads a configuration file, the Ethernet, FastEthernet, or Serial interface commands are rejected?
NETLABAE allows different router types in each equipment pod. When a configuration is saved on one pod, then loaded onto another pod, it is possible that the source router interface names (e.g. Ethernet0, Serial0) are different than the destination router (e.g. FastEthernet0/0, Serial0/0). This situation would normally be handled by manually editing the interface names before loading the configurations on the destination routers. To avoid this time consuming task, NETLABAE automatically performs this translation if: • The configuration files were created using NETLABAE automates save option, or • They are NETLABAE default configuration files for a lab exercise For this to work properly: • The router types configured in NETLABAE must match the actual router types. Otherwise configurations may not load properly since NETLABAE is translating interface names based on the wrong router type. • Interface names on the actual router must match the interface names that are expected by NETLABAE.
Related Questions
- tool to ping a router, the destination IP address is the Ethernet interface rather than the serial interface. What determines the default destination interface for a ping?
- When NETLABAE loads a configuration file, the Ethernet, FastEthernet, or Serial interface commands are rejected?
- Does the EZ serial switch have a user configuration interface like a router?
