HP StorageWorks 4/8 Brocade Troubleshooting and Diagnostics Guide v6.1.0 (53-1 - Page 48

Fabric OS Administrator's, Guide, For more information on these types of restrictions, refer to

Page 48 highlights

4 Configupload and download issues Example of a successful ping C:\>ping 192.163.163.50 Pinging 192.163.163.50 with 32 bytes of data: Reply from 192.163.163.50: bytes=32 time=5ms TTL=61 Ping statistics for 192.163.163.50: Packets: Sent = 4, Received = 4, Lost = 0 (0%loss), Approximate round trip times in milli-seconds: Minimum = 4ms, Maximum = 5ms, Average = 4ms If your ping is successful from your computer, but you cannot reach it from inside your data center, there could be a block on the firewall to not allow FTP connections from inside the data center. Contact your network administrator to determine if this is the cause and to resolve it by opening the port up on both inbound and outbound UDP and TCP traffic. Example of a failed ping C:\> ping 192.163.163.50 Pinging 192.163.163.50 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.163.163.50: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), If your ping has failed then you should verify the following: - The ports are open on the firewall. - The FTP server is up and running. Example of a failed login to the FTP server The output should be similar to the following on an unsuccessful login: C:\>ftp 192.163.163.50 Connected to 192.163.163.50 220 Welcome to Education Services FTP service. User (10.255.252.50:(none)): upd20 331 Please specify the password. Password: 530 Login incorrect. Login failed. If your login to the FTP or SCP server has failed, verify the username and password are correct. • You do not have configuration upload permission on the switch. There may be some restrictions if you are using Admin Domains or Role-Based Access Control. For more information on these types of restrictions, refer to the Fabric OS Administrator's Guide. • You do not have permission to write to directory on the FTP or SCP server. Implement one change at a time, then issue the command again. By implementing one change at a time, you will be able to determine what works and what does not work. Knowing which change corrected the problems will help you to avoid this problem in future endeavors. 34 Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-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

34
Fabric OS Troubleshooting and Diagnostics Guide
53-1000853-01
Configupload and download issues
4
Example of a successful ping
C:\>ping 192.163.163.50
Pinging 192.163.163.50 with 32 bytes of data:
Reply from 192.163.163.50: bytes=32 time=5ms TTL=61
Ping statistics for 192.163.163.50:
Packets: Sent = 4, Received = 4, Lost = 0 (0%loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 5ms, Average = 4ms
If your ping is successful from your computer, but you cannot reach it from inside your data
center, there could be a block on the firewall to not allow FTP connections from inside the data
center. Contact your network administrator to determine if this is the cause and to resolve it by
opening the port up on both inbound and outbound UDP and TCP traffic.
Example of a failed ping
C:\> ping 192.163.163.50
Pinging 192.163.163.50 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.163.163.50:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
If your ping has failed then you should verify the following:
-
The ports are open on the firewall.
-
The FTP server is up and running.
Example of a failed login to the FTP server
The output should be similar to the following on an unsuccessful login:
C:\>ftp 192.163.163.50
Connected to 192.163.163.50
220 Welcome to Education Services FTP service.
User (10.255.252.50:(none)): upd20
331 Please specify the password.
Password:
530 Login incorrect.
Login failed.
If your login to the FTP or SCP server has failed, verify the username and password are correct.
You do not have configuration upload permission on the switch.
There may be some restrictions if you are using Admin Domains or Role-Based Access Control.
For more information on these types of restrictions, refer to the
Fabric OS Administrator’s
Guide
.
You do not have permission to write to directory on the FTP or SCP server.
Implement one change at a time, then issue the command again. By implementing one change at a
time, you will be able to determine what works and what does not work. Knowing which change
corrected the problems will help you to avoid this problem in future endeavors.