Dynamic configuration loading | 6 |
NOTE
If you
•Make sure you enter each command at the correct CLI level. Since some commands have identical forms at both the global CONFIG level and individual configuration levels, if the CLI’s response to the configuration file results in the CLI entering a configuration level you did not intend, then you can get unexpected results.
For example, if a trunk group is active on the device, and the configuration file contains a command to disable STP on one of the secondary ports in the trunk group, the CLI rejects the commands to enter the interface configuration level for the port and moves on to the next command in the file you are loading. If the next command is a
The configuration file contains these commands:
interface ethernet 4/2 no
The CLI responds like this:
BigIron | RX(config)# interface ethernet 4/2 |
Error - | cannot configure secondary ports of a trunk |
BigIron | RX(config)# no |
BigIron | RX(config)# |
•If the file contains commands that must be entered in a specific order, the commands must appear in the file in the required order. For example, if you want to use the file to replace an IP address on an interface, you must first remove the old address using “no” in front of the ip address command, then add the new address. Otherwise, the CLI displays an error message and does not implement the command. Here is an example:
The configuration file contains these commands:
interface ethernet 3/1 ip address 10.10.10.1/24
The
BigIron RX(config)# interface ethernet 3/1
BigIron
Error: can only assign one primary ip address per subnet
BigIron
To successfully replace the address, enter commands into the file as follows:
interface ethernet 3/1
no ip address 10.10.10.1/24 ip address 10.10.10.69/24
This time, the CLI accepts the command, and no error message is displayed:
Brocade BigIron RX Series Hardware Installation Guide | 149 |
|