Dell PowerVault NX3500 Administrator's Guide - Page 177

Specific Subnet Clients Cannot Access the PowerVault NX3500 System, Strange UID and GID Numbers

Get Dell PowerVault NX3500 PDF manuals and user guides View all Dell PowerVault NX3500 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 177 highlights

Specific Subnet Clients Cannot Access the PowerVault NX3500 System Description Cause Workaround Users (new or old), accessing from specific network(s), cannot access the PowerVault NX3500 system. This issue is due to a conflict between the users' subnet addresses and the NAS system internal network's address. The NAS system routes the response packets to the wrong network. 1 Check the internal network addresses of the NAS system and verify if there is a conflict with the problematic client network addresses. 2 If a conflict exists, manually change the conflicting NAS internal network address using either the NAS Manager or CLI. Strange UID and GID Numbers on Dell NAS System Files Description Cause Workaround New files created from ubuntu 7.x clients get the UID and GID of 4294967294 (nfsnone). By default, ubuntu 7.x nfs clients do not specify rpc credentials on their nfs calls. As a result, files created from these clients, by any user, are owned by 4294967294 (nfsnone) UID and GID. To force UNIX credentials on nfs calls, add the sec=sys option to the PowerVault NX3500 mounts in the ubuntu fstab file. Troubleshooting 177

  • 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
Troubleshooting
177
Specific Subnet Clients Cannot Access the
PowerVault NX3500 System
Strange UID and GID Numbers on Dell NAS
System Files
Description
Users (new or old), accessing from specific network(s), cannot
access the PowerVault NX3500 system.
Cause
This issue is due to a conflict between the users' subnet addresses
and the NAS system internal network's address. The NAS system
routes the response packets to the wrong network.
Workaround
1
Check the internal network addresses of the NAS system and
verify if there is a conflict with the problematic client network
addresses.
2
If a conflict exists, manually change the conflicting NAS internal
network address using either the NAS Manager or CLI.
Description
New files created from ubuntu 7.
x
clients get the UID and GID of
4294967294 (nfsnone).
Cause
By default, ubuntu 7.
x
nfs clients do not specify rpc credentials on
their nfs calls. As a result, files created from these clients, by any
user, are owned by 4294967294 (nfsnone) UID and GID.
Workaround
To force UNIX credentials on nfs calls, add the
sec=sys
option to
the PowerVault NX3500 mounts in the ubuntu fstab file.