Dell PowerVault NX3500 Administrator's Guide - Page 164

NFS Insecure Access to Secure Export, NFS Mount Fails Due to Export Options

Page 164 highlights

NFS Insecure Access to Secure Export Description Cause Workaround User tries to access a secure export from an insecure port. Secure export requirement means that the accessing clients must use a well-known port (below 1024), which usually means that they must be root (uid=0) on the client. • Identify the relevant export and verify that it is set as secure (requires secure client port). • If the export must remain secure, see the NFS client documentation in order to issue the mount request from a wellknown port (below 1024). • If a secure export is not required (e.g., the network is not public), ensure that the export is insecure and retry accessing it. NFS Mount Fails Due to Export Options Description Cause Workaround This event is issued when NFS mount fails due to export options. The export list filters client access by IP, network or netgroup, and screens the accessing client. 1 Verify the relevant export details. Write down all existing options so that you are able to revert to them. 2 Remove IP/client restrictions on the export and retry the mount. 3 If the mount succeeds, verify that the IP or domain is explicitly specified, or that it is part of the defined network or netgroups. Pay attention to pitfall scenarios, where the network netmask is not intuitive, for example, 192.175.255.254 is part of 192.168.0.0/12 but not of 192.168.0.0/16. 4 Once the mount succeeds, adjust the original options accordingly. 164 Troubleshooting

  • 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

164
Troubleshooting
NFS Insecure Access to Secure Export
NFS Mount Fails Due to Export Options
Description
User tries to access a secure export from an insecure port.
Cause
Secure export requirement means that the accessing clients must
use a well-known port (below 1024), which usually means that they
must be root (uid=0) on the client.
Workaround
Identify the relevant export and verify that it is set as secure
(requires secure client port).
If the export must remain secure, see the NFS client
documentation in order to issue the mount request from a well-
known port (below 1024).
If a secure export is not required (e.g., the network is not public),
ensure that the export is insecure and retry accessing it.
Description
This event is issued when NFS mount fails due to export options.
Cause
The export list filters client access by IP, network or netgroup, and
screens the accessing client.
Workaround
1
Verify the relevant export details. Write down all existing options
so that you are able to revert to them.
2
Remove IP/client restrictions on the export and retry the mount.
3
If the mount succeeds, verify that the IP or domain is explicitly
specified, or that it is part of the defined network or netgroups.
Pay attention to pitfall scenarios, where the network netmask is
not intuitive, for example, 192.175.255.254 is part of
192.168.0.0/12 but not of 192.168.0.0/16.
4
Once the mount succeeds, adjust the original options accordingly.