Initially Configuring the T640 Router
The T640 Core Router is shipped with the Junos OS preinstalled and ready to be configured when the T640 router is powered on. These procedures connect a router to the network but do not enable it to forward traffic. For complete information about enabling the router to forward traffic, including examples, see the Junos OS configuration guides.
You configure the router by issuing Junos OS command-line interface (CLI) commands, either on a console device attached to the CONSOLE port on the CIP, or over a telnet connection to a network connected to the ETHERNET port on the CIP.
![]() | Note: These procedures enable you to use the ETHERNET management port. For the initial configuration, use a device attached to the CONSOLE port on the CIP. |
- Entering Configuration Mode
- Configuring User Accounts and Passwords
- Configuring System Attributes
- Committing the Configuration
Entering Configuration Mode
- Verify that the router is powered on.
- Log in as the root user. There is no password.
Amnesiac <ttyd0>
login: root - Start the CLI.root@% cliroot>
- Enter configuration mode.root> configure Entering configuration mode.[edit]root@#
Configuring User Accounts and Passwords
For information about using an encrypted password, or an SSH public key string (DSA or RSA), see the Junos System Basics Configuration Guide.
- Add a password to the root administration user
account. Enter a clear-text password. [edit]root@# set system root-authentication plain-text-passwordNew password: password Retype new password: password
- Create a management console user account.
[edit]
root# set system login user user-name authentication plain-text-password
New Password: password
Retype new password: password - Set the user account class to super-user.
[edit]
root# set system login user user-name class super-user
Configuring System Attributes
For more information on the backup router and static routes, see the Junos System Basics Configuration Guide.
- Configure the
name of the router. If the name includes spaces, enclose the name
in quotation marks (“ ”).[edit]root@# set system host-name host-name

Note: The DNS server does not use the hostname to resolve to the correct IP address. This hostname is used to display the name of the routing engine in the CLI. For example, this hostname shows on the command-line prompt when the user is logged on to the CLI:
user-name@host-name>
- Configure the IP address of the DNS server.
[edit]
root# set system name-server address - Configure the router’s domain name.[edit]root@# set system domain-name domain-name
- Configure the IP address and prefix length
for the router’s Ethernet interface.[edit]root@# set interfaces em0 unit 0 family inet address address/prefix-length
- Configure the IP address of a backup
routing engine. The backup routing engine is used while the local
router is booting and if the routing process fails to start. After
the routing process starts, the backup routing engine address is removed
from the local routing and forwarding tables.
[edit]
root# set system backup-router address - (Optional) Configure the static routes
to remote subnets with access to the management port. Access to the
management port is limited to the local subnet. To access the management
port from a remote subnet, you must add a static route to that subnet
within the routing table.
[edit] root# set routing-options static route remote-subnet next-hop destination-IP retain no-readvertise
- Configure the telnet service at the [edit system services] hierarchy level.
[edit]
set system services telnet
Committing the Configuration
- Display the configuration to verify that it
is correct.[edit]root@# showsystem {host-name host-name;domain-name domain-name;backup-router address;root-authentication {authentication-method (password | public-key);}name-server {address;}}interfaces {fxp0 {unit 0 {family inet {address address/prefix-length;}}}}
- Commit
the configuration to activate it on the router.[edit]root@# commit
- Optionally,
configure additional properties by adding the necessary configuration
statements. Then commit the changes to activate them on the router.[edit]root@host# commit
- When you have finished configuring the
router, exit configuration mode.[edit]root@host# exitroot@host>
