クラウドおよびシステム管理 : Cisco Network Registrar

CNR Nrcmd の戻りコード

2003 年 7 月 8 日 - ライター翻訳版
その他のバージョン: PDFpdf | 機械翻訳版 (2013 年 8 月 21 日) | 英語版 (2005 年 10 月 26 日) | フィードバック

目次


概要

この文書では、Cisco Network Registrar(CNR)の各バージョンで使用される、nrcmd のすべての戻りコードの定義について説明します。

戻りコード(バージョン 3.5.3)

100 { "100 Ok" }
 101 { "101 Ok, with warnings" }
 102 { "102 Lease already reserved to this client" }
 103 { "103 Lease not reserved" }
 104 { "104 Lease deleted along with reservation" }
 105 { "105 Lease created along with reservation" }
 204 { "204 Assigned host is not contained in pool zone" }
 301 { "301 No Server Found" }
 302 { "302 Not Found" }
 303 { "303 Read only property" }
 304 { "304 No Policy Found" }
 305 { "305 Too many" }
 306 { "306 Unknown command" }
 307 { "307 Unknown keyword" }
 308 { "308 Unknown parameter" }
 309 { "309 Too many arguments" }
 310 { "310 Too few arguments" }
 311 { "311 No response to lease request" }
 312 { "312 Unexpected response from server" }
 313 { "313 No match" }
 314 { "314 Duplicate object" }
 315 { "315 Import Failure"  }
 316 { "316 Invalid" }
 317 { "317 Open failed" }
 318 { "318 No MAC Address Found" }
 319 { "319 No Lease Found" }
 320 { "320 generic error } (This code may have multiple meanings. You need to examine 
     the exact text returned on this error to determine the cause.)
 321 { "321 Invalid name" }
 322 { "322 Feature not supported" }
 323 { "323 Read error" }
 324 { "324 Invalid IP address list" }
 325 { "325 Invalid type" }
 326 { "326 ODBC Database access error" }
 327 { "327 IP address not contained within pool subnet" }
 328 { "328 Identical MX resource record already exists" }
 329 { "329 Identical TXT resource record already exists" }
 330 { "330 Address is not contained in pool" }
 331 { "331 Host is already assigned to an address" }
 332 { "332 Address is already assigned to a host" }
 333 { "333 No unassigned IP address found in pool" }
 334 { "334 Address has not been assigned to a host" }
 335 { "335 Static address pools are not enabled, create a pool to enable" }
 336 { "336 Range overlaps another pool" }
 337 { "337 Host has multiple IP address assignments" }
 338 { "338 Address has multiple host assignments, must supply argument" }
 339 { "339 Expected unsigned 16-bit preference value" }
 340 { "340 ODBC 3.x or higher required; "}
 350 { "350 Generic DHCP error"}
 351 { "351 Cannot resolve partner name to an IP address"}
 352 { "352 No failover object for specified partner"}
 353 { "353 Still communicating with partner"}
 354 { "354 Server is already in partner-down state"}
 355 { "355 Can't set partner-down while in recover"}
 356 { "356 Not allowed in read-only mode"}
 357 { "357 Not a secondary"}
 358 { "358 Not a primary"}
 359 { "359 No zone matached"}
 360 { "360 Forcexfer for this zone is already scheduled"}
 361 { "361 Lease is not reserved" }
 362 { "362 Scope unknown in server" }
 363 { "363 Invalid IP address in server" }
 364 { "364 Invalid MAC address in server" }
 365 { "365 Failure creating MAC address in server" }
 366 { "366 Unknown object in server" }
 367 { "367 Command not supported by server" }
 368 { "368 Bad length in server" }
 369 { "369 Inconsistent scope in server" }
 370 { "370 updateSMS not configured in server" }
 371 { "371 Server out of memory" }
 372 { "372 SMS interface .dll did not load correctly" }
 373 { "373 updateSMS already processing in server" }
 374 { "374 Invalid word array" }
 375 { "375 updateSMS Invalid argument" }
 376 { "376 Lease is reserved to a different client" }
 377 { "377 Client already reserved a different lease" }
 378 { "378 Field name or number not found"}
 379 { "379 Suboption name or number already exists"}
 380 { "380 Suboption name or number not found "}
 381 { "381 Invalid character '-' in vendor-option name"}
 382 { "382 Data not found for vendor-option"}
 383 { "383 Field name or number already exists"}
 401 { "401 Login Failure" }
 402 { "402 Permission denied" }
 403 { "403 Couldn't lock database" }
 404 { "404 Login Required" }
 405 { "405 Invalid license key" }
 406 { "406 A lock is required for this operation" }
 407 { "407 Unable to release lock" }
 408 { "408 Unable to obtain lock" }
 409 { "409 Couldn't lock static address pool" }
 501 { "501 Connection Failure" }
 502 { "502 Server Failure" }

バージョン 5.0 で追加された戻りコード

 106 { return "106 Assertion failed" }
 384 { return "384 counted-array can only be used with array types"}
 

バージョン 5.5 で追加された戻りコード

 107 { return "107 Namespace id currently in use by at least one scope" }
 385 { return "385 Read-only attribute cannot be modified"}
 386 { return "386 Required attribute cannot be unset"}
 387 { return "387 Invalid namespace ID"}
 388 { return "388 Invalid IP Address syntax"}
 389 { return "389 Invalid namespace name"}
 390 { return "390 Invalid IP Address value"}
 391 { return "391 Invalid namespace specification"}
 392 { return "392 Cannot remove sessions current namespace"}
 393 { return "393 Duplicate property"}
 394 { return "394 Invalid namespace id specification"}
 395 { return "395 Lease has no scope pointer -- internal error"}
 396 { return "396 Invalid vpn-id specification"}
 503 { return "503 Cluster Version Failure" }
 

CNR 6.0 での戻りコード

CNR 6.0 の戻りコード」に関する情報については、『Network Registrar CLI リファレンス、6.0』の第 4 章を参照してください。

関連するシスコ サポート コミュニティ ディスカッション

シスコ サポート コミュニティは、どなたでも投稿や回答ができる情報交換スペースです。


関連情報


Document ID: 13400