Dell PowerConnect B-RX16 Installation Guide - Page 122

Testing network connectivity, Pinging an IP address, Tracing a route

Get Dell PowerConnect B-RX16 PDF manuals and user guides View all Dell PowerConnect B-RX16 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 122 highlights

4 Testing network connectivity Testing network connectivity After you cable the fiber optic modules, you can test connectivity to other network devices by pinging those devices. You also can perform trace routes. To resolve problems that may arise with network connections: • For the indicated port, verify that both ends of the cabling (at the Brocade device and the connected device) are snug. • Verify that the Brocade device and the connected device are both powered on and operating correctly. • Verify that you have used the correct cable type for the connection: • For twisted-pair connections to an end node, use straight-through cabling. • For fiber optic connections, verify that the transmit port on the device is connected to the receive port on the connected device, and that the receive port on device is connected to the transmit port on the connected device. • Verify that the port has not been disabled through a configuration change. You can use the CLI. If you have configured an IP address on the device, you also can use the Web management interface or IronView Network Manager. • For copper ports, you can test the cable using Virtual Cable Testing. Refer to "Using virtual cable testing to diagnose a cable" on page 111. • If the other procedures do not resolve the problem, try using a different port or a different cable. Pinging an IP address To verify that a BigIron RX Series switch can reach another device through the network, enter a command such as the following at any level of the CLI on the BigIron RX Series switch: BigIron RX> ping 192.33.4.7 Syntax: ping | [source ] [count ] [timeout ] [ttl ] [size ] [quiet] [numeric] [no-fragment] [verify] [data ] [brief] NOTE If you address the ping to the IP broadcast address, the device lists the first four responses to the ping. Tracing a route To determine the path through which a BigIron RX Series switch can reach another network device, enter a command such as the following at any level of the CLI on the BigIron RX Series switch: BigIron RX> traceroute 192.33.4.7 Syntax: traceroute [maxttl ] [minttl ] [numeric] [timeout ] [source-ip ] The CLI displays trace route information for each hop as soon as the information is received. Traceroute requests display all responses to a given TTL. In addition, if there are multiple equal-cost routes to the destination, the Brocade device displays up to three responses by default. 110 BigIron RX Installation Guide 53-1001811-01

  • 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
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
110
BigIron RX Installation Guide
53-1001811-01
Testing network connectivity
4
Testing network connectivity
After you cable the fiber optic modules, you can test connectivity to other network devices by
pinging those devices. You also can perform trace routes.
To resolve problems that may arise with network connections:
•
For the indicated port, verify that both ends of the cabling (at the Brocade device and the
connected device) are snug.
•
Verify that the Brocade device and the connected device are both powered on and operating
correctly.
•
Verify that you have used the correct cable type for the connection:
•
For twisted-pair connections to an end node, use straight-through cabling.
•
For fiber optic connections, verify that the transmit port on the device is connected to the
receive port on the connected device, and that the receive port on device is connected to
the transmit port on the connected device.
•
Verify that the port has not been disabled through a configuration change. You can use the CLI.
If you have configured an IP address on the device, you also can use the Web management
interface or IronView Network Manager.
•
For copper ports, you can test the cable using Virtual Cable Testing. Refer to
“Using virtual
cable testing to diagnose a cable”
on page 111.
•
If the other procedures do not resolve the problem, try using a different port or a different
cable.
Pinging an IP address
To verify that a BigIron RX Series switch can reach another device through the network, enter a
command such as the following at any level of the CLI on the BigIron RX Series switch:
BigIron RX> ping 192.33.4.7
Syntax:
ping <ip addr> | <hostname> [source <ip addr>] [count <num>] [timeout <msec>] [ttl
<num>] [size <byte>] [quiet] [numeric] [no-fragment] [verify] [data <1-to-4 byte hex>]
[brief]
NOTE
If you address the ping to the IP broadcast address, the device lists the first four responses to the
ping.
Tracing a route
To determine the path through which a BigIron RX Series switch can reach another network device,
enter a command such as the following at any level of the CLI on the BigIron RX Series switch:
BigIron RX> traceroute 192.33.4.7
Syntax:
traceroute <host-ip-addr> [maxttl <value>] [minttl <value>] [numeric] [timeout <value>]
[source-ip <ip addr>]
The CLI displays trace route information for each hop as soon as the information is received.
Traceroute requests display all responses to a given TTL. In addition, if there are multiple equal-cost
routes to the destination, the Brocade device displays up to three responses by default.