Configuring JCS Management Module Settings

You use the JCS management module CLI to configure basic system parameters on the JCS 1200 platform:

• Restoring the Default JCS Management Module Configuration
• Configuring the JCS Management Module Ethernet Interface
• Configuring the Switch Module Ethernet Interface
• Configuring User Accounts
• Configuring the NTP Server
• Configuring the Time Zone
• Configuring the System Name and Contact Information

Restoring the Default JCS Management Module Configuration

Before you configure the JCS management module, we recommend clearing any existing configurations on the JCS management module and restoring the defaults.

Clearing a configuration results in the following changes:

• Sets the JCS management module to its default state.

  This is equivalent to pressing the recessed button on the front panel of the JCS management module for more than 5 seconds.

• Initializes the serial port to 9600 baud.
• Initializes the internal SNMP community string.

  An SNMP community string is a text string that acts as a password. It is used to authenticate messages that are sent between the management station (the SNMP manager) and the device (the SNMP agent). The community string is included in every packet that is transmitted between the SNMP manager and the SNMP agent.

• Disables web access.

To clear an existing JCS management module configuration:

1. Log in to the JCS management module.

   If you are logging on for the first time, use the default username and password:

   
   

   Username: USERID

   
   

   Password: PASSW0RD

   The 0 in PASSW0RD is a zero, not the letter O.

2. Use the env command to set JCS management module 1 (mm[1]) as the configuration target. For example:
   
   

   system> env —T mm[1]
3. Use the clear command to clear the configuration. For example:
   
   

   system:mm[1]> clear —cnfg

   This example clears the configuration on mm[1] and returns the JCS management module to the factory default settings.

Configuring the JCS Management Module Ethernet Interface

To configure the network interface on the JCS management module:

1. Log in to the JCS management module.
2. Use the env command to set JCS management module 1 (mm[1]) as the configuration target. For example:
   
   

   system:mm[1]> env —T mm[1]
3. Use the ifconfig command to configure the interface. For example:
   
   

   system:mm[1]> ifconfig —eth0 —i 192.168.171.96 —g 192.168.171.254 —s 255.255.252.0 —c static

   In this example, Ethernet channel 0 is configured for a static IP address of 192.168.171.96 and a gateway address of 192.168.171.254. The subnet mask is 255.255.252.0.

Note: You only need to configure the Ethernet interface on the primary management module. The backup management module will use the IP address from the primary if it becomes the primary management module.

Configuring the Switch Module Ethernet Interface

You must configure the Ethernet interface for both JCS switch modules (switch[1] and switch[2]) on the JCS management module.

Note: The IP address for the JCS switch modules must be on the same subnet as the IP address for the JCS management module.

To configure the JCS switch module Ethernet interface on the JCS management module:

1. Log in to the JCS management module.
2. Use the env command to set JCS switch module 1 (switch[1]) as the configuration target. For example:
   
   

   system> env —T switch[1]
3. Use the ifconfig command to configure the interface. For example:
   
   

   system:switch[1]> ifconfig —i 192.168.171.98 —g 192.168.171.254 —s 255.255.252.0 —em enabled —ep enabled

   In this example, the Ethernet interface for JCS switch module 1 is configured for an IP address of 192.168.171.98 and a gateway address of 192.168.171.254. The subnet mask is 255.255.252.0. The external ports (ep) of the switch module are enabled.

4. Repeat this procedure for JCS switch module 2. Use the env command to set switch module 2 (switch[2]) as the configuration target. For example:
   
   

   system> env —T switch[2]
5. Use the ifconfig command to configure the interface. For example:
   
   

   system:switch[2]> ifconfig —i 192.168.171.99 —g 192.168.171.254 —s 255.255.252.0 —em enabled —ep enabled

   In this example, the Ethernet interface for JCS switch module 2 is configured for an IP address of 192.168.171.99 and a gateway address of 192.168.171.254. The subnet mask is 255.255.252.0. The external ports (ep) of the switch module are enabled.

Configuring User Accounts

You configure user accounts on the JCS management module to control access to the module. The JCS 1200 platform supports the following types of security roles for user accounts:

• Supervisor

  This role has full read and write access to the JCS 1200 platform. Users can configure the JCS management module, the JCS switch module, and Routing Engines (blades) on the JCS 1200 platform. You must configure at least one user to have a Supervisor role.

• Operator

  This role has read-only access to the JCS. Users can view the configuration of the JCS management module, the JCS switch module, and the JCS Routing Engines. They can monitor JCS operations, but they cannot change the JCS configuration.

You can add up to 12 users to the JCS management module. Each user you add must be assigned a unique number (1 through 12).

To configure user accounts:

1. Log in to the JCS management module.
2. Use the env command to set JCS management module 1 (mm[1]) as the configuration target. For example:
   
   

   system> env —T mm[1]
3. Use the users command to configure user accounts. For example:
   
   

   system:mm[1]> users -2 —n chang —p SPASS1 —a super

   
   

   system:mm[1]> users —3 —n markham —p OPASS1 —a operator

   In these examples, User 2 is configured with a username (chang) and a password (SPASS1). User 2 has Supervisor access (full read/write). User 3 is configured with a username (markham) and a password (OPASS1). User 2 has Operator access (read-only).

Configuring the NTP Server

To synchronize the JCS 1200 platform with other servers on the network, you must configure a Network Time Protocol (NTP) server.

To configure an NTP server:

1. Log in to the JCS management module.
2. Use the env command to set JCS management module 1(mm[1]) as the configuration target. For example:
   
   

   system> env —T mm[1]
3. Use the ntp command to configure an NTP server. For example:
   
   

   system:mm[1]> ntp —i 172.17.28.5 —f 60 —en enabled

   In this example, the IP address of the NTP server is 172.17.28.5, the JCS management module clock is updated by the NTP server every 60 minutes, and NTP is enabled.

Configuring the Time Zone

To configure the time zone on the JCS management module:

1. Log in to the JCS management module.
2. Use the env command to set JCS management module 1(mm[1]) as the configuration target. For example:
   
   

   system> env —T mm[1]
3. Use the clock command to configure the time zone. For example:
   
   

   system:mm[1]> clock —g —8 —dst uc

   In this example, the clock is configured for 8 hours earlier than UTC (GMT) (-g -8), and daylight saving time for the USA and Canada (-dst uc) is set.

Configuring the System Name and Contact Information

JCS management module configuration should include the system name of the JCS 1200 platform (to identify the JCS 1200 platform on the network), the physical location of the JCS 1200 platform, and a contact person for the JCS 1200 platform. Typically, the contact is someone who has Supervisor access to the JCS 1200 platform.

To configure the system name, location, and contact information for the JCS management module:

1. Log in to the JCS management module.
2. Use the env command to set JCS management module 1(mm[1]) as the configuration target. For example:
   
   

   system> env —T mm[1]
3. Use the config command to configure the system name, location, and contact information for the JCS. For example:
   
   

   system:mm[1]> config -name system5 -contact “George Chang email=chang@corp.net phone=x2368” —loc “Software Lab, Main Campus, Building 12”

   In this example, the system name is system5. This name identifies the JCS on the network, appears in monitoring command output, and so on. The contact information is for George Chang and the location is Software Lab.