Dell PowerConnect J-SRX240 Hardware Guide - Page 83

Table 27: Port Settings When Connecting the Services Gateway to the CLI Locally

Page 83 highlights

Chapter 13: Connecting the J-SRX240 Services Gateway to Management Devices 5. Connect the other end of the Ethernet cable to the console port on the services gateway. 6. Turn on the power to the management device. 7. Start your asynchronous terminal emulation application (such as Microsoft Windows HyperTerminal) and select the appropriate COM port to use (for example, COM1). 8. Configure the port settings shown in Table 27 on page 67. Table 27: Port Settings When Connecting the Services Gateway to the CLI Locally Port Settings Value Bits per second 9600 Data bits 8 Parity None Stop bits 1 Flow control None 9. Power on the services gateway by pressing the Power button on the front panel. Verify that the Power LED on the front panel turns green. The terminal emulation screen on your management device displays the startup sequence. When the services gateway has finished starting up, a login prompt appears. 10. Log in as the user root. No password is required at initial connection, but you must assign a root password before committing any configuration settings. Connecting a Services Gateway to the CLI Remotely You can connect the services gateway to the CLI from a remote location through two dial-up modems: • A modem that is connected to the console port on the services gateway • A second modem connected to a remote management device The modem connection allows you to remotely perform the same console operations you can perform locally. Related Topics • Connecting the J-SRX240 Services Gateway to the J-Web Interface on page 63 • Connecting to the CLI at the User End for the J-SRX240 Services Gateway on page 69 • Connecting the Modem at the J-SRX240 Services Gateway End on page 68 • Connecting the Modem to the Console Port on the J-SRX240 Services Gateway on page 69 67

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160

5.
Connect the other end of the Ethernet cable to the console port on the services
gateway.
6.
Turn on the power to the management device.
7.
Start your asynchronous terminal emulation application (such as Microsoft Windows
HyperTerminal) and select the appropriate
COM
port to use (for example,
COM1
).
8.
Configure the port settings shown in Table 27 on page 67.
Table 27: Port Settings When Connecting the Services Gateway to the CLI Locally
Value
Port Settings
9600
Bits per second
8
Data bits
None
Parity
1
Stop bits
None
Flow control
9.
Power on the services gateway by pressing the Power button on the front panel.
Verify that the Power LED on the front panel turns green.
The terminal emulation screen on your management device displays the startup
sequence. When the services gateway has finished starting up, a login prompt
appears.
10.
Log in as the user
root
. No password is required at initial connection, but you must
assign a root password before committing any configuration settings.
Connecting a Services Gateway to the CLI Remotely
You can connect the services gateway to the CLI from a remote location through two
dial-up modems:
A modem that is connected to the console port on the services gateway
A second modem connected to a remote management device
The modem connection allows you to remotely perform the same console operations
you can perform locally.
Related Topics
Connecting the J-SRX240 Services Gateway to the J-Web Interface on page 63
Connecting to the CLI at the User End for the J-SRX240 Services Gateway on page 69
Connecting the Modem at the J-SRX240 Services Gateway End on page 68
Connecting the Modem to the Console Port on the J-SRX240 Services Gateway on
page 69
67
Chapter 13: Connecting the J-SRX240 Services Gateway to Management Devices