Management and Configuration Guide K/KA/KB.15.15

Trunking ports together does not affect friendly naming for the individual ports. (If you want
the same name for all ports in a trunk, you must individually assign the name to each port.)
A friendly port name can have up to 64 contiguous alphanumeric characters.
Blank spaces within friendly port names are not allowed, and if used, cause an invalid input
error. (The switch interprets a blank space as a name terminator.)
In a port listing, not assigned indicates that the port does not have a name assignment other
than its fixed port number.
To retain friendly port names across reboots, you must save the current running-configuration
to the startup-config file after entering the friendly port names. (In the CLI, use the write
memory command.)
About configuring transceivers and modules that have not been inserted
Transceivers
Previously, a port had to be valid and verified for the switch to allow it to be configured. Transceivers
are removable ports and considered invalid when not present in the switch, so they cannot be
configured unless they are already in the switch. For HP switches, the verification for allowable
port configurations performed by the CLI is removed and configuration of transceivers is allowed
even if they are not yet inserted in the switch.
Modules
You can create or edit configuration files (as text files) that can be uploaded to the switch without
the modules having been installed yet. Additionally, you can pre-configure the modules with the
CLI module command.
The same module command used in an uploaded configuration file is used to define a module
that is being pre-configured. The validation performed when issued through the CLI is still performed
just as if the command was executed on the switch, in other words, as if the module were actually
present in the switch.
NOTE: You cannot use this method to change the configuration of a module that has already
been configured. The slot must be empty and the configuration file must not have a configuration
associated with it.
About clearing the module configuration
Because of the hot-swap capabilities of the modules, when a module is removed from the chassis,
the module configuration remains in the configuration file. [no] module slot allows you to
remove the module configuration information from the configuration file.
NOTE: This does not change how hot-swap works.
Restrictions
The following restrictions apply:
The slot being cleared must be empty
There was no module present in the slot since the last boot
If there was a module present after the switch was booted, the switch will have to be rebooted
before any module (new or same) can be used in the slot.
This does not clear the configuration of a module still in use by the switch.
About configuring transceivers and modules that have not been inserted 105