|
|
Table Of Contents
Connect the Management Interfaces and Perform Initial System Configuration
Perform the Initial System Configuration
Step 1: Configuring Initial Settings
Step 2: Configuring the Hostname
Step 4: Configuring Time Settings
Step 5: Configuring the DNS Settings
Step 6: Configuring the RDR Formatter Destination
Step 7: Configuring Access Control Lists (ACLs)
Step 9: Configuring the Topology-Dependent Parameters
Step 10: Completing and Saving the Configuration
Connect the Management Interface
Connect the Management Interfaces and Perform Initial System Configuration
This section explains how to connect the SCE 2000 platform to a local console and perform the initial system configuration via the setup wizard that runs automatically. Additionally, this section contains instructions for cabling the Fast Ethernet Management interface.
Note
When installing a cascaded system, it is extremely important to follow the sequence of procedures outlined in the section Installing a Cascaded System.
•
•
Connect the Local Console
Figure 4-1 Connecting to the Local Console
You must first connect the unit to a local console and configure the initial settings for the SCE 2000 to support remote management. When the initial connection is established, the setup utility will run automatically, prompting you to perform the initial system configuration.
Make sure that the terminal configuration is as follows:
•
•
•
•
•
The above SCE 2000 port parameters are fixed and are not configurable.
Step 1
Step 2
Step 3
--- System Configuration Dialog --- At any point you may enter a question mark `?' followed by `Enter' for help. Use ctrl-C to abort configuration dialog at any prompt. Use ctrl-Z to jump to the end of the configuration dialog at any prompt. Default settings are in square brackets `[]'. Would you like to continue with the System Configuration Dialog? [yes/no]: yStep 4
Enters the system configuration dialog.
Perform the Initial System Configuration
•
•
•
•
•
•
•
•
•
•
Initial System Configuration
•
The Setup Command
Upon initial connection to the local terminal, as described above, the system configuration wizard automatically runs to guide the user through the entire setup process. The wizard prompts for all necessary parameters, displaying default values, where applicable. You may accept the default values or define other values.
When the dialog is complete, you may review the new configuration before applying it. The system displays the configuration, including parameters that were not changed. The system also displays any errors that are detected in the configuration. When the configuration is satisfactory, you may apply and save the new configuration.
The following table lists all the parameters included in the initial configuration. It is recommended that you obtain values for any parameters that you will configure at this time before beginning the setup.
Note
Setup Command Parameters
Following are some general instructions regarding the setup dialog:
•
If no value appears in the brackets [], or more than one option appears [ yes/no ], then this parameter does not have a default value.
•
•
A help message will appear describing the expected format of the parameter and any other requirements.
•
•
"Sorry, Skipping is not allowed at this stage."•
Each group of related parameters is prefaced by a question, asking whether you want to enter the menu. To skip the menu, answer no ("n") to the question.
Example
Would you like to enter the SNMP configuration menu? n•
Step 1: Configuring Initial Settings
Verify the following initial settings for the SCE 2000:
•
•
•
All values are Internet addresses of the form `X.X.X.X', where each letter corresponds to a decimal number between 0 and 255.
Step 1
The current IP address is displayed.
•
•
Step 2
The current subnet mask is displayed.
•
•
Step 3
The current IP address of the default gateway is displayed.
•
•
Example
The following example displays a typical configuration of the IP address (10.1.5.109), subnet mask (255.255.0.0), and default gateway (10.1.1.3).
Since the IP address and the subnet mask are related, when the IP address is changed, there is no longer a default value of the subnet mask, and it must be entered explicitly.
Enter IP address [10.1.1.201]:10.1.5.109 Enter IP subnet mask:255.255.0.0 Enter IP address of default gateway [10.1.1.3]:Step 2: Configuring the Hostname
The hostname is used to identify the SCE 2000. It appears as part of the CLI prompt and is also returned as the value of the MIB-II object sysName.
The maximum length is 20 characters.
The default hostname is SCE 2000 .
Step 1
The default hostname is displayed.
•
•
Enter hostname [SCE 2000]:Step 3: Setting the Passwords
Configure the passwords as follows:
•
•
Note
Passwords must meet the following criteria:
•
•
•
•
Note
Note
Step 1
The default User password is displayed.
•
•
Step 2
The default Admin password is displayed.
•
•
Step 3
The default Root password is displayed.
•
•
Step 4
•
•
EXAMPLE:
Following is an example of changing all passwords. Password encryption is not enabled (default).
Enter a User password [cisco]: userin Enter an Admin password [cisco]: mng123 Enter a Root password [cisco]: cistech Enable passwords encryption? [no]:Step 4: Configuring Time Settings
The time settings menu configures all time and date related parameters in the system. The time settings menu includes the following:
•
•
•
•
You must enter the time setting menu in order to configure SNTP settings. You may choose to skip the time settings menu if you wish to accept all default values.
Note
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Step 1
Would you like to enter the Time settings menu? [no]: yType
yand press Enter.Step 2
Type the time zone abbreviation and press Enter.
Enter time zone name [UTC]: CET
Step 3
Type the minutes offset from UTC and press Enter.
Enter time zone minutes offset from UTC: 60Step 4
The local time and date are displayed, and you are asked whether you want to change them
The local time and date is 15:00:01 CET FRI 01 July 2002 Would you like to set a new time and date? [no]:•
•
Would you like to set a new time and date? [no]: y Confirm your response and type the new time and date. This change will take effect immediately both on the system clock and calendar; it will also set the time zone you entered. Are you sure? [yes/no]: y Enter new local time and date: 14:00:01 1 July 2002 Time zone was successfully set. The system clock and the calendar were successfully set.Step 5
If you do not wish to configure the SNTP, skip the rest of this section and go to .
To enter the SNTP configuration dialog, type y , and press Enter
Would you like to enter the SNTP configuration menu? [no]: yStep 6
•
•
•
Enable SNTP broadcast client? [no]:Step 7
•
Enter time interval in seconds between unicast updates [1024]:
Step 8
Type in the hostname or the IP address in the form x.x.x.x , and press Enter
Would you like to configure SNTP unicast servers? [no]: y Enter IP address or hostname of SNTP unicast server: 10.1.1.1EXAMPLE:
Following is a sample time setting dialog. In addition to setting the time zone, time and date are changed, and SNTP unicast updates are configured.
Would you like to enter the Time settings menu? [no]: y Enter time zone name [UTC]: ISR Enter time zone minutes offset from UTC: 120 The local time and date is 15:35:23 ISR FRI July 19 2002 Would you like to set a new time and date? [no]: y This change will take effect immediately both on the system clock and the calendar; it will also set the time zone you entered. Are you sure? [yes/no]: y Enter new local time and date: 14:35:23 19 July 2002 Time zone was successfully set. The system clock and the calendar were successfully set. Would you like to enter the SNTP configuration menu? [no]: y Enable SNTP broadcast client? [no]: y Enter time interval in seconds between unicast updates [900]: Would you like to configure SNTP unicast servers? [no]: y Enter IP address or hostname of SNTP unicast server: 10.1.1.1Step 5: Configuring the DNS Settings
The DNS configuration menu defines the IP address of the domain name server, which is used for DNS lookup, as well as the default domain name, which is used to complete unqualified host names.
You may choose to skip the DNS configuration menu if you wish to accept all default values.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Step 1
Would you like to enter the DNS configuration menu? [no]: yType y and press Enter.
The DNS settings dialog begins.
Step 2
•
•
nand press Enter.Enable IP DNS-based hostname translation? [yes]:If you choose to disable DNS lookup, skip the rest of this section and go to . The rest of the dialog is not presented, as it is irrelevant when DNS lookup is disabled.
Step 3
Note that there is no default domain name.
You may accept the default domain name or enter a new one.
Enter default domain name []:Step 4
Type the IP address of the primary domain name server and press Enter.
Enter Primary DNS IP address:
Note that there is no default for this parameter.
Step 5
You may configure up to three domain servers.
Would you like to add another Name Server? [no]:•
•
You are asked to enter the IP address of the next domain name server.
Enter Secondary DNS IP address:Step 6
When IP addresses for all servers have been entered, exit the dialog by pressing Enter.
Would you like to add another Name Server? [no]:EXAMPLE:
Following is a sample DNS configuration dialog. The default domain name is pcube.com, and the IP address of the Domain Name Server is 10.1.1.230.
Would you like to enter the DNS configuration menu? [no]: y Enable IP DNS-based hostname translation? [yes]: Enter default domain name []: pcube.com Enter Primary DNS IP address: 10.1.1.230 Would you like to add another Name Server? [no]:Step 6: Configuring the RDR Formatter Destination
The SCE 2000 passes Raw Data Records (RDRs) to an external collection system via the RDR-Formatter. In order for the data to reach the correct location, the IP address of the external collection system and its port number must be configured.
Step 1
Would you like to enter the RDR-formatter configuration menu? [no]: yType
yand press Enter.The RDR-formatter destination dialog begins.
Step 2
Type the IP address of the RDR-formatter destination and press Enter.
Enter RDR-formatter destination's IP address:Note that there is no default for this parameter.
Step 3
Type the TCP port number of the RDR-formatter destination and press Enter.
Note that there is no default for this parameter.
Enter RDR-formatter destination's TCP port number:EXAMPLE:
Following is a sample RDR-formatter configuration dialog, assigning the IP address and TCP port number.
Would you like to enter the RDR-formatter configuration menu? [no]: y Enter RDR-formatter destination's IP address: 10.1.1.230 Enter RDR-formatter destination's TCP port number: 33000Step 7: Configuring Access Control Lists (ACLs)
•
•
Information About Access Control Lists
Configuring ACLs
The SCE 2000 can be configured with Access Control Lists (ACLs), which are used to permit or deny incoming connections on any of the management interfaces.
Note
Configuration of access control lists is done in two stages:
1.
You may create 99 ACLs with a maximum of 20 entries per list. Each entry consists of an IP address, and an indication of whether access is permitted or denied to this IP address.
2.
The dialog permits you to skip the creation/editing of the ACLs and go directly to assigning ACLs to the management interfaces.
Entry Formats
Each ACL may permit/deny access to any IP address, one or more ranges of IP addresses, or one or more individual IP address. Three entry formats are available to support these options:
•
•
This wildcard functions like a reverse mask, in that all "1" bits in the wildcard indicate the corresponding bit in the IP address should be ignored. All other bits must match the corresponding bit in the specified IP address. Refer to the table below for examples.
Each range of IP addresses can be configured to be permitted or denied access.
•
Each individual IP address can be configured to be permitted or denied access.
Order of Entries
The order of the entries in the list is important. The entries in the list are tested sequentially, and the action is determined by the first entry that matches the connecting IP address. Therefore, when the entry "any" appears in an Access Control List, all succeeding entries are irrelevant.
Consider two hypothetical ACLs containing the same entries in a different order.
The following list would permit access to all IP addresses, including 10.1.1.0:
permit any
deny 10.1.1.0
Note that the above list could not actually be created using the setup utility, since after the "any" entry, no other entries could be added to the list.
The following list will deny access to IP address 10.1.1.0, but permit access to all others:
deny 10.1.1.0
permit any
If no entry in the assigned Access Control List matches the connection, or if the Access Control List is empty, the default action is deny.
To create the access control lists, complete the following steps:
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
DETAILED STEPS
Step 1
Would you like to enter the Access lists configuration menu? [no]:yType
yand press Enter.The Access Control Lists configuration dialog begins.
Step 2
Would you like to create new Access lists or modify existing lists? [no]: yIf you choose not to create or edit Access Control Lists, skip to .
Step 3
Note that there is no default for this parameter.
Step 4
Indicate whether this entry is permitted access or denied access.
•
•
nand press Enter.Step 5
Note that there is no default for this parameter.
Enter IP address or the word `any' to denote any IP address:Step 6
To define an individual IP address, type 0.0.0.0and press Enter.
There is no default for this parameter.
Enter wildcard bits:Step 7
If the "any" option was used, no other IP addresses may be added to the list.
•
yand press EnterWould you like to add another entry to this list? [no]:y•
•
Would you like to add another entry to this list? [no]:Step 8
•
yand press EnterWould you like to configure another list? [no]: y•
•
Would you like to configure another list? [no]:•
Step 9
Type the number of the ACL to be assigned to IP access and press Enter.
To accept the default ACL, press Enter.
Enter IP access-class [0]:Step 10
Type the number of the ACL to be assigned to the Telnet interface and press
Enter.To accept the default ACL, press
Enter.Enter Telnet access-class [0]: 2Examples
EXAMPLE 1:
This example illustrates a common access control scenario. Let us assume the following:
•
•
We therefore need to create two access control lists:
•
•
ACL #1 = permit any IP address. Assign to IP access.
ACL #2 = permit access to 10.1.1.0, 10.10.10.1, deny to all others. Assign to Telnet access.
Would you like to enter the Access lists configuration menu? [no]: y Would you like to create new Access lists or modify existing lists? [no]: y Enter ACL number: 1 Does this entry permit access? [yes]: Enter IP address or the word `any' to denote any IP address: any This entry matches every IP address, no use in adding more entries to this list. Would you like to configure another list? [no]: y Enter ACL number: 2 Does this entry permit access? [yes]: Enter IP address or the word `any' to denote any IP address: 10.1.1.0 Enter wildcard bits: 0.0.0.0 Would you like to add another entry to this list? [no]:y Does this entry permit access? [yes]: Enter IP address or the word `any' to denote any IP address: 10.10.10.1 Enter wildcard bits: 0.0.0.0 Would you like to add another entry to this list? [no]:y Does this entry permit access? [yes]:n Enter IP address or the word `any' to denote any IP address: any This entry matches every IP address, no use in adding more entries to this list. Would you like to configure another list? [no]: Enter IP access-class [0]: 1 Enter Telnet access-class [0]: 2EXAMPLE 2:
This example skips the first section of the dialog (creating/modifying), and proceeds directly to assign existing ACLs.
Would you like to enter the Access lists configuration menu? [no]: y Would you like to create new Access lists or modify existing lists? [no]: Enter IP access-class [0]: 10 Enter Telnet access-class [0]: 22Step 8: Configuring SNMP
Managing the SCE 2000 is possible also via a Network Management System (NMS) that supports SNMP. By default, SNMP is disabled on the SCE 2000.
To enable SNMP management you must configure the following basic SNMP parameters:
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
DETAILED STEPS
Step 1
Would you like to enter the SNMP configuration menu? [no]: yType
yand press Enter.The SNMP configuration dialog begins.
Step 2
Type
yand press Enter.Enable SNMP management? [no]: yIf you choose to disable SNMP management, skip the rest of this section and go to . The rest of the dialog is not presented, as it is irrelevant when SNMP management is disabled.
Step 3
1.
The SNMP agent that resides inside the SCE 2000 will respond only to GET requests that use this community string.
Enter SNMP GET community name:Note that there is no default for this parameter.
2.
Type a number (1 through 99) or type "0" to permit access to all IP addresses, and press Enter.
Enter Access list number allowing access with this community string, use `0' to allow all:Step 4
The maximum number of GET communities is 20.
1.
Would you like to add another SNMP GET community? [no]:yEnter up to 20 SNMP GET communities as described in step 3.
2.
Would you like to add another SNMP GET community? [no]:Step 5
1.
The SNMP agent that resides inside the SCE 2000 will respond only to SET requests that use this community string.
Enter SNMP SET community name:Note that there is no default for this parameter.
2.
Type a number (1 through 99) or type "0" to permit access to all IP addresses, and press Enter.
Enter Access list number allowing access with this community string, use `0' to allow all:Step 6
The maximum number of SET communities is 20.
1.
yand press EnterWould you like to add another SNMP SET community? [no]:y2.
3.
Would you like to add another SNMP SET community? [no]:Step 7
1.
Would you like to configure SNMP trap managers? [no]: y2.
The SNMP trap managers dialog begins.
If you choose not to configure SNMP trap managers, the dialog skips to the authentication failure trap status. (See step 9.)
3.
Enter SNMP trap manager IP address:Note that there is no default for this parameter.
4.
Enter SNMP trap manager community string:Note that there is no default for this parameter.
5.
Enter trap manager SNMP version:Note that there is no default for this parameter.
Step 8
The maximum number of trap managers is 20.
1.
Would you like to add another SNMP trap manager? [no]:y2.
3.
Would you like to add another SNMP trap manager? [no]:Step 9
•
•
Enable the `Authentication Failure' trap [no]:Step 10
•
npress Enter.•
yand press Enter.Enable the SCE enterprise traps []:Step 11
Type the name of the system administrator and press Enter.
Note that there is no default for this parameter.
Enter system administrator contact name []:EXAMPLE:
Following is a sample SNMP configuration, configuring one trap manager, one GET community, and one SET community, and enabling the authentication failure trap, as well as all enterprise traps.
Would you like to enter the SNMP configuration menu? [no]: y Enable SNMP management? [no]: y Enter SNMP GET community name[]: public Enter Access list number allowing access with this community string, use `0' to allow all: 0 Would you like to add another SNMP GET community? [no]: Enter SNMP SET community name[]: private Enter Access list number allowing access with this community string, use `0' to allow all: 2 Would you like to add another SNMP SET community? [no]: Would you like to configure SNMP trap managers? [no]: y Enter SNMP trap manager IP address: 10.1.1.253 Enter SNMP trap manager community string: public Enter trap manager SNMP version: 2c Would you like to add another SNMP trap manager? [no]: Enable the `Authentication Failure' trap [no]: y Enable SCE enterprise traps []: y Enter system administrator contact name []: John SmithStep 9: Configuring the Topology-Dependent Parameters
•
•
About the Topology-Dependent Parameters
The topology configuration menu is a series of guided questions relating to the deployment of the SCE 2000 in the network and its mode of operation. Values for the parameters are configured based on the user answers.
The correct value for each parameter must be ascertained before configuring the system to make sure that the system will function in the desired manner. (See Topology for a comprehensive discussion of topology and the related parameters.)
Note
There are six topology-related parameters:
•
–
–
•
–
–
•
In a single-SCE platform deployment, the indices of the links cannot be changed by the user and are:
–
–
•
–
–
•
–
–
•
–
–
•
–
–
•
Study the examples that follow to understand the procedure for various topologies.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Step 1
Would you like to enter the Topology configuration menu? [no]: y•
Type
yand press Enter.The topology configuration dialog begins.
Step 2
•
•
Enter Connection mode: 1- inline 2- receive-only Enter your choice [1]:Step 3
•
•
yand press Enter.Is this a cascade deployment? [no]:Step 4
•
•
Enter Physically connected link: 0- link-0 1- link-1 Enter your choice [0]:Step 5
•
•
Enter SCE 2000 priority: 1- primary 2- secondary Enter your choice [1]:Step 6
•
•
2and press Enter.Enter On-failure behavior: 1- bypass 2- cutoff Enter your choice [1]:Step 7
•
•
2and press Enter.Enter admin status of the SCE after abnormal boot: 1- Operational 2- Not-Operational Enter your choice [1]:Examples
The following examples present the procedure for configuring the topology-related parameters for various topologies.
EXAMPLE 1
Following is a sample topology configuration for a non-redundant topology using an optical splitter, that is, a single SCE 2000 connected in receive-only connection mode, to one or two GBE links
Would you like to enter the Topology configuration menu? [no]: y Would you like to enter the Topology configuration menu? [no]: y Enter Connection mode: 1- inline 2- receive-only Enter your choice [1]: 2 Is this a cascade deployment? [no]: no Enter admin status of the SCE after abnormal boot: 1- Operational 2- Not-Operational Enter your choice [1]: 1 Data collection for the system configuration is completed.All other parameter values are automatically assigned by the system.
EXAMPLE 2:
Following is a sample topology configuration for a non-redundant inline topology. In this topology, a single SCE 2000 is connected to one or two GBE links.
When the inline connection mode is specified, the user must specify the on-failure link behavior.
Would you like to enter the Topology configuration menu? [no]: y Enter Connection mode: 1- inline 2- receive-only Enter your choice [1]: 1 Is this a cascade deployment? [no]: no Enter On-failure behavior: 1- bypass 2- cutoff Enter your choice [1]: 1 Enter admin status of the SCE after abnormal boot: 1- Operational 2- Not-Operational Enter your choice [1]: 1 Data collection for the system configuration is completed.EXAMPLE 3:
Following is a sample topology configuration for a secondary SCE 2000 in a redundant inline topology. In this topology there are two SCE 2000s that are cascaded via the cascade GBE ports (ports 3 and 4). Each SCE 2000 is connected inline to both sides (subscribers/network) of one GBE link.
In this case, the user must specify the physically-connected-link index (link-0 in our example), the priority of the SCE 2000, and the on-failure link behavior.
Would you like to enter the Topology configuration menu? [no]: y Enter Connection mode: 1- inline 2- receive-only Enter your choice [1]: 1 Is this a cascade deployment ? [no]: yes Enter Physically connected link: 0- link-0 1- link-1 Enter your choice [0]: 0 Enter SCE 2000 priority: 1- primary 2- secondary Enter your choice [1]: 2 Enter On-failure behavior: 1- bypass 2- cutoff Enter your choice [1]: 1 Enter admin status of the SCE after abnormal boot: 1- Operational 2- Not-Operational Enter your choice [1]: 1 Data collection for the system configuration is completed.Step 10: Completing and Saving the Configuration
When you have completed the entire configuration, the system checks for errors. If errors are found, a warning message appears. When the configuration is error-free, you may apply and save it.
To complete and save the configuration, complete the following steps:
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Step 1
The system informs you that data collection is complete.
We recommend that you view the entire new configuration before it is applied.
Type
yand press Enter.Note that there is no default.
If there are no errors, go to step 3.
Data collection for the system configuration is completed. Would you like to view the new configuration before it is applied? [yes/no]: yStep 2
If any errors are detected, you may choose to view them.
Press Enter.
Found errors in the new configuration, would you like to view them? [yes]: The following errors were found: Warning - RDR formatter destination 10.1.1.1 is not allowed in the IP access-class.Step 3
You are asked whether to apply and save the configuration.
Apply and Save this configuration? [yes/no]:•
yand press Enter.Setup procedure aborted, no configuration changes made.•
Step 4
If there are no errors, the system requests confirmation of either a yes or no answer, in order to prevent mistakes.
Type the appropriate answer (y or n) and press Enter.
The running configuration would be overwritten by the changes you have just entered, are you sure? [yes/no]: The selected action is carried out by the system.The selected action is carried out by the system.
•
Setup procedure aborted, no configuration changes made.•
The new running configuration will be saved to the startup configuration.Step 5
If the configuration was applied and saved, you may also save a backup copy to a file at a remote station.
Do you want to save a copy of the startup configuration file in a remote station? [no]:To save the configuration to a remote station, type
yand press Enter.The system will ask for FTP path:
Enter a full FTP path of the remote destination:Step 6
The system informs you that the configuration is complete.
Committing configuration... Configuration completed successfully. Saving configuration... Writing general configuration file to temporary location... Backing-up general configuration file... Copy temporary file to final location... Done!Examples
EXAMPLE 1:
Following is an example of a configuration that the user aborted due to errors detected in the configuration.
Note that no confirmation is requested for the decision to abort the setup. Had there been no errors, confirmation would have been requested before aborting.
Data collection for the system configuration is completed. Would you like to view the new configuration before it is applied? [yes/no]: n Found errors in the new configuration, would you like to view them? [yes]: y The following errors were found: Warning - RDR formatter destination 10.1.1.1 is not allowed in the IP access-class. Warning - default Gateway 10.1.1.1 is not allowed in the IP access-class. Warning - IP Access list (1) conflicts with Telnet Access list (2) as follows: Access list 2 permits all addresses while Access list 1 denies it. Apply and Save this configuration? [yes/no]: n Setup procedure aborted, no configuration changes made.EXAMPLE 2:
Following is an example of a configuration that was applied and saved to the startup configuration as well as to an FTP site.
Although not demonstrated in this example, it is recommended that you always view the configuration before applying it.
Data collection for the system configuration is completed. Would you like to view the new configuration before it is applied? [yes/no]: Apply and Save this configuration? [yes/no]: y (New configuration would be displayed here) The running configuration would be overwritten by the changes you have just entered, are you sure? [yes/no]:y The new running configuration will be saved to the startup configuration. Do you want to save a copy of the startup configuration file in a remote station? [no]:y Enter a full FTP path of the remote destination: ftp://vk:vk@10.1.1.253/h:/copyofstartup.txt Committing configuration... Configuration completed successfully. Saving configuration... Writing general configuration file to temporary location... Backing-up general configuration file... Copy temporary file to final location... Done!EXAMPLE 3:
Following is an example of a configuration that was aborted, although no errors were detected.
Data collection for the system configuration is completed. Would you like to view the new configuration before it is applied? [yes/no]: Apply and Save this configuration? [yes/no]: n The changes you have just entered would be discarded, are you sure? [yes/no]:y Setup procedure aborted, no configuration changes made.Connect the Management Interface
Figure 4-2 Cabling the Management Port
Note
The SCE 2000 has two management ports, labeled Mng1 and Mng 2. Use the Mng 1 port.
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
Step 1
Step 2
The Link LED on the SCE 2000 management port should light up.
Step 3
This verifies that an active connection exists between the specified station and the management port.
EXAMPLE:
The following example displays a typical ping response where the target IP address is 10.1.1.201.
C:\>ping 10.1.1.201 pinging 10.1.1.201 ... PING 10.1.1.201: 56 data bytes 64 bytes from host (10.1.1.201): icmp_seq=0. time=0. ms 64 bytes from host (10.1.1.201): icmp_seq=1. time=0. ms 64 bytes from host (10.1.1.201): icmp_seq=2. time=0. ms 64 bytes from host (10.1.1.201): icmp_seq=3. time=0. ms ----10.1.1.201 PING Statistics---- 4 packets transmitted, 4 packets received, 0% packet loss round-trip (ms) min/avg/max = 0/0/0
Posted: Thu May 31 05:38:29 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
