HTTPS Access configuration
The following table describes the HTTPS Access Configuration commands.
Table 75 HTTPS Access Configuration commands
Command | Description | |
[no] access https | Enables or disables BBI access (Web access) using HTTPS. The default value is | |
enable | disabled. | |
| Command mode: Global configuration | |
access https port <TCP | Defines the HTTPS Web server port number. | |
port number> | Command mode: Global configuration | |
access https generate- | Allows you to generate a certificate to connect to the SSL to be used during the key | |
certificate | exchange. A default certificate is created when HTTPS is enabled for the first time. | |
| The user can create a new certificate defining the information that they want to be | |
| used in the various fields. For example: | |
| • | Country Name (2 letter code) [ ]: JP |
| • | State or Province Name (full name) [ ]: Tokyo |
| • | Locality Name (for example, city) [ ]: Fuchu |
| • | Organization Name (for example, company) [ ]: NEC |
| • | Organizational Unit Name (for example, section) [ ]: SIGMABLADE |
| • | Common Name (for example, user’s name) [ ]: Taro |
| • | Email (for example, email address) [ ]: info@nec.com |
| You must confirm if you want to generate the certificate. It takes approximately | |
| 30 seconds to generate the certificate. Then the switch restarts SSL agent. | |
| Command mode: Global configuration | |
access https save- | Allows the client, or the Web browser, to accept the certificate and save the | |
certificate | certificate to Flash to be used when the switch is rebooted. | |
| Command mode: Global configuration | |
show access | Displays the current SSL Web Access configuration. | |
| Command mode: All except User EXEC | |
Configuration Commands 72
