|

nmap returns "Host <ip_address> appears to be up" instead of "Host <hostname> appears to be up" for some of the nodes

View: New views

6 Messages — Rating Filter: Alert me

	nmap returns "Host <ip_address> appears to be up" instead of "Host <hostname> appears to be up" for some of the nodes by Guang Cheng Li :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message HI, OS: SLES 11 on IBM System p nmap version: 4.75 and 5.00 I am using nmap to detect whether all of the nodes in my cluster and up and running, nmap returns "Host <ip_address> appears to be up" for some nodes but returns "Host <hostname> appears to be up" for the other nodes. Since a script is used to parse the output, so it is difficult for me to write the script. Could someone let me know that why the nmap returns both "Host <ip_address> appears to be up" and "Host <hostname> appears to be up"? thank you. c906mgrs2:~ # nmap -PE --send-ip -sP c906f06c01p05 c906f06c01p09 c906f06c01p13 c906f06c01p17 c906f06c01p21 c906f06c01p25 c906f06c01p28 c906f06c02p01 c906f06c02p05 c906f06c02p09 c906f06c02p13 c906f06c02p17 c906f06c02p21 c906f06c02p25 c906f06c02p28 c906f06c03p01 c906f06c03p05 c906f06c03p09 c906f06c03p13 c906f06c03p17 c906f06c03p21 c906f06c03p25 c906f06c03p28 c906f06c04p01 c906f06c04p05 c906f06c04p09 c906f06c04p13 c906f06c04p17 c906f06c04p21 c906f06c04p25 c906f06c04p28 c906f06c05p05 c906f06c05p09 c906f06c05p13 c906f06c05p17 c906f06c05p21 c906f06c05p25 c906f06c05p28 c906f06c06p01 c906f06c06p05 c906f06c06p09 c906f06c06p13 c906f06c06p17 c906f06c06p21 c906f06c06p25 c906f06c06p28 c906f06c07p01 c906f06c07p05 c906f06c07p09 c906f06c07p13 c906f06c07p17 c906f06c07p21 c906f06c07p25 c906f06c07p28 c906f06c08p01 c906f06c08p05 c906f06c08p09 c906f06c08p13 c906f06c08p17 c906f06c08p21 c906f06c08p25 c906f06c08p28 c906f07c01p05 c906f07c01p09 c906f07c01p13 c906f07c01p17 c906f07c01p21 c906f07c01p25 c906f07c01p28 c906f07c02p01 c906f07c02p05 c906f07c02p09 c906f07c02p13 c906f07c02p17 c906f07c02p21 c906f07c02p25 c906f07c02p28 c906f07c03p01 c906f07c03p05 c906f07c03p09 c906f07c03p13 c906f07c03p17 c906f07c03p21 c906f07c03p25 c906f07c03p28 c906f07c04p01 c906f07c04p05 c906f07c04p09 c906f07c04p13 c906f07c04p17 c906f07c04p21 c906f07c04p25 c906f07c04p28 c906f07c05p05 c906f07c05p09 c906f07c05p13 c906f07c05p17 c906f07c05p21 c906f07c05p25 c906f07c05p28 c906f07c06p01 c906f07c06p05 c906f07c06p09 c906f07c06p13 c906f07c06p17 c906f07c06p21 c906f07c06p25 c906f07c06p28 c906f07c07p01 c906f07c07p05 c906f07c07p09 c906f07c07p13 c906f07c07p17 c906f07c07p21 c906f07c07p25 c906f07c07p28 c906f07c08p01 c906f07c08p05 c906f07c08p09 c906f07c08p13 c906f07c08p17 c906f07c08p21 c906f07c08p25 c906f07c08p28 c906f08c01p05 c906f08c01p09 c906f08c01p13 c906f08c01p17 c906f08c01p21 c906f08c01p25 c906f08c01p28 c906f08c02p01 c906f08c02p05 c906f08c02p09 c906f08c02p13 c906f08c02p17 c906f08c02p21 c906f08c02p25 c906f08c02p28 c906f08c03p01 c906f08c03p05 c906f08c03p09 c906f08c03p13 c906f08c03p17 c906f08c03p21 c906f08c03p25 c906f08c03p28 c906f08c04p01 c906f08c04p05 c906f08c04p09 c906f08c04p13 c906f08c04p17 c906f08c04p21 c906f08c04p25 c906f08c04p28 c906f08c05p05 c906f08c05p09 c906f08c05p13 c906f08c05p17 c906f08c05p21 c906f08c05p25 c906f08c05p28 c906f08c06p01 c906f08c06p05 c906f08c06p09 c906f08c06p13 c906f08c06p17 c906f08c06p21 c906f08c06p25 c906f08c06p28 c906f08c07p01 c906f08c07p05 c906f08c07p09 c906f08c07p13 c906f08c07p17 c906f08c07p21 c906f08c07p25 c906f08c07p28 c906f08c08p01 c906f08c08p05 c906f08c08p09 c906f08c08p13 c906f08c08p17 c906f08c08p21 c906f08c08p25 c906f08c08p28 c906f09c01p05 c906f09c01p09 c906f09c01p13 c906f09c01p17 c906f09c01p21 c906f09c01p25 c906f09c01p28 c906f09c02p01 c906f09c02p05 c906f09c02p09 c906f09c02p13 c906f09c02p17 c906f09c02p21 c906f09c02p25 c906f09c02p28 c906f09c03p01 c906f09c03p05 c906f09c03p09 c906f09c03p13 c906f09c03p17 c906f09c03p21 c906f09c03p25 c906f09c03p28 c906f09c04p01 c906f09c04p05 c906f09c04p09 c906f09c04p13 c906f09c04p17 c906f09c04p21 c906f09c04p25 c906f09c04p28 c906f09c05p05 c906f09c05p09 c906f09c05p13 c906f09c05p17 c906f09c05p21 c906f09c05p25 c906f09c05p28 c906f09c06p01 c906f09c06p05 c906f09c06p09 c906f09c06p13 c906f09c06p17 c906f09c06p21 c906f09c06p25 c906f09c06p28 c906f09c07p01 c906f09c07p05 c906f09c07p09 c906f09c07p13 c906f09c07p17 c906f09c07p21 c906f09c07p25 c906f09c07p28 c906f09c08p01 c906f09c08p05 c906f09c08p09 c906f09c08p13 c906f09c08p17 c906f09c08p21 c906f09c08p25 c906f09c08p28 Starting Nmap 4.75 ( http://nmap.org ) at 2009-11-12 03:39 EST Host 10.6.1.5 appears to be up. ===========================> ip address MAC Address: 00:1A:64:FC:0A:37 (IBM) Host c906f06c01p09.cluster.com (10.6.1.9) appears to be up. MAC Address: 00:1A:64:FC:0A:3B (IBM) Host c906f06c01p13.cluster.com (10.6.1.13) appears to be up. MAC Address: 00:1A:64:FC:0A:3F (IBM) Host 10.6.1.17 appears to be up. ===========================> ip address MAC Address: 00:1A:64:FC:0A:43 (IBM) Host 10.6.1.21 appears to be up. ===========================> ip address MAC Address: 00:1A:64:FC:0A:47 (IBM) Host c906f06c01p25.cluster.com (10.6.1.25) appears to be up. MAC Address: 00:1A:64:FC:0A:4B (IBM) Host c906f06c01p28.cluster.com (10.6.1.28) appears to be up. MAC Address: 00:1A:64:FC:0A:4E (IBM) Host 10.6.2.1 appears to be up. ===========================> ip address MAC Address: 00:1A:64:FA:28:DB (IBM) Host 10.6.2.5 appears to be up. ===========================> ip address MAC Address: 00:1A:64:FA:28:DF (IBM) Host c906f06c02p09.cluster.com (10.6.2.9) appears to be up. MAC Address: 00:1A:64:FA:28:E3 (IBM) Host c906f06c02p13.cluster.com (10.6.2.13) appears to be up. MAC Address: 00:1A:64:FA:28:E7 (IBM) Host 10.6.2.17 appears to be up. ===========================> ip address MAC Address: 00:1A:64:FA:28:EB (IBM) Host 10.6.2.21 appears to be up. ===========================> ip address MAC Address: 00:1A:64:FA:28:EF (IBM) Host c906f06c02p25.cluster.com (10.6.2.25) appears to be up. MAC Address: 00:1A:64:FA:28:F3 (IBM) Host c906f06c02p28.cluster.com (10.6.2.28) appears to be up. MAC Address: 00:1A:64:FA:28:F6 (IBM) Host 10.6.3.1 appears to be up. ===========================> ip address MAC Address: 00:1A:64:FC:0B:7D (IBM) Host 10.6.3.5 appears to be up. ===========================> ip address MAC Address: 00:1A:64:FC:0B:81 (IBM) Host c906f06c03p09.cluster.com (10.6.3.9) appears to be up. MAC Address: 00:1A:64:FC:0B:85 (IBM) Host c906f06c03p13.cluster.com (10.6.3.13) appears to be up. MAC Address: 00:1A:64:FC:0B:89 (IBM) Host 10.6.3.17 appears to be up. ===========================> ip address MAC Address: 00:1A:64:FC:0B:8D (IBM) Host c906f06c03p21.cluster.com (10.6.3.21) appears to be up. MAC Address: 00:1A:64:FC:0B:91 (IBM) Host c906f06c03p25.cluster.com (10.6.3.25) appears to be up. MAC Address: 00:1A:64:FC:0B:95 (IBM) Host c906f06c03p28.cluster.com (10.6.3.28) appears to be up. MAC Address: 00:1A:64:FC:0B:98 (IBM) Host c906f06c04p01.cluster.com (10.6.4.1) appears to be up. MAC Address: 00:1A:64:FA:22:27 (IBM) Host c906f06c04p05.cluster.com (10.6.4.5) appears to be up. MAC Address: 00:1A:64:FA:22:2B (IBM) Host c906f06c04p09.cluster.com (10.6.4.9) appears to be up. MAC Address: 00:1A:64:FA:22:2F (IBM) Host c906f06c04p13.cluster.com (10.6.4.13) appears to be up. MAC Address: 00:1A:64:FA:22:33 (IBM) Host c906f06c04p17.cluster.com (10.6.4.17) appears to be up. MAC Address: 00:1A:64:FA:22:37 (IBM) Host c906f06c04p21.cluster.com (10.6.4.21) appears to be up. MAC Address: 00:1A:64:FA:22:3B (IBM) Host c906f06c04p25.cluster.com (10.6.4.25) appears to be up. MAC Address: 00:1A:64:FA:22:3F (IBM) Host c906f06c04p28.cluster.com (10.6.4.28) appears to be up. MAC Address: 00:1A:64:FA:22:42 (IBM) Host c906f06c05p05.cluster.com (10.6.5.5) appears to be up. MAC Address: 00:1A:64:FC:09:B3 (IBM) Host c906f06c05p09.cluster.com (10.6.5.9) appears to be up. MAC Address: 00:1A:64:FC:09:B7 (IBM) Host c906f06c05p13.cluster.com (10.6.5.13) appears to be up. MAC Address: 00:1A:64:FC:09:BB (IBM) Host c906f06c05p17.cluster.com (10.6.5.17) appears to be up. MAC Address: 00:1A:64:FC:09:BF (IBM) Host c906f06c05p21.cluster.com (10.6.5.21) appears to be up. MAC Address: 00:1A:64:FC:09:C3 (IBM) Host c906f06c05p25.cluster.com (10.6.5.25) appears to be up. MAC Address: 00:1A:64:FC:09:C7 (IBM) Host c906f06c05p28.cluster.com (10.6.5.28) appears to be up. MAC Address: 00:1A:64:FC:09:CA (IBM) Host c906f06c06p01.cluster.com (10.6.6.1) appears to be up. MAC Address: 00:1A:64:FC:09:F1 (IBM) Host c906f06c06p05.cluster.com (10.6.6.5) appears to be up. MAC Address: 00:1A:64:FC:09:F5 (IBM) Host c906f06c06p09.cluster.com (10.6.6.9) appears to be up. MAC Address: 00:1A:64:FC:09:F9 (IBM) Host c906f06c06p13.cluster.com (10.6.6.13) appears to be up. MAC Address: 00:1A:64:FC:09:FD (IBM) Host c906f06c06p17.cluster.com (10.6.6.17) appears to be up. MAC Address: 00:1A:64:FC:0A:01 (IBM) Host c906f06c06p21.cluster.com (10.6.6.21) appears to be up. MAC Address: 00:1A:64:FC:0A:05 (IBM) Host c906f06c06p25.cluster.com (10.6.6.25) appears to be up. MAC Address: 00:1A:64:FC:0A:09 (IBM) Host c906f06c06p28.cluster.com (10.6.6.28) appears to be up. MAC Address: 00:1A:64:FC:0A:0C (IBM) Host c906f06c07p01.cluster.com (10.6.7.1) appears to be up. MAC Address: 00:1A:64:FB:D9:7F (IBM) Host c906f06c07p05.cluster.com (10.6.7.5) appears to be up. MAC Address: 00:1A:64:FB:D9:83 (IBM) Host c906f06c07p09.cluster.com (10.6.7.9) appears to be up. MAC Address: 00:1A:64:FB:D9:87 (IBM) Host c906f06c07p13.cluster.com (10.6.7.13) appears to be up. MAC Address: 00:1A:64:FB:D9:8B (IBM) Host c906f06c07p17.cluster.com (10.6.7.17) appears to be up. MAC Address: 00:1A:64:FB:D9:8F (IBM) Host c906f06c07p21.cluster.com (10.6.7.21) appears to be up. MAC Address: 00:1A:64:FB:D9:93 (IBM) Host c906f06c07p25.cluster.com (10.6.7.25) appears to be up. MAC Address: 00:1A:64:FB:D9:97 (IBM) Host c906f06c07p28.cluster.com (10.6.7.28) appears to be up. MAC Address: 00:1A:64:FB:D9:9A (IBM) Host c906f06c08p01.cluster.com (10.6.8.1) appears to be up. MAC Address: 00:1A:64:FB:86:E9 (IBM) Host c906f06c08p05.cluster.com (10.6.8.5) appears to be up. MAC Address: 00:1A:64:FB:86:ED (IBM) Host c906f06c08p09.cluster.com (10.6.8.9) appears to be up. MAC Address: 00:1A:64:FB:86:F1 (IBM) Host c906f06c08p13.cluster.com (10.6.8.13) appears to be up. MAC Address: 00:1A:64:FB:86:F5 (IBM) Host c906f06c08p17.cluster.com (10.6.8.17) appears to be up. MAC Address: 00:1A:64:FB:86:F9 (IBM) Host c906f06c08p21.cluster.com (10.6.8.21) appears to be up. MAC Address: 00:1A:64:FB:86:FD (IBM) Host c906f06c08p25.cluster.com (10.6.8.25) appears to be up. MAC Address: 00:1A:64:FB:87:01 (IBM) Host c906f06c08p28.cluster.com (10.6.8.28) appears to be up. MAC Address: 00:1A:64:FB:87:04 (IBM) Host c906f07c01p05.cluster.com (10.7.1.5) appears to be up. MAC Address: 00:1A:64:FA:20:9F (IBM) Host c906f07c01p09.cluster.com (10.7.1.9) appears to be up. MAC Address: 00:1A:64:FA:20:A3 (IBM) Host c906f07c01p13.cluster.com (10.7.1.13) appears to be up. MAC Address: 00:1A:64:FA:20:A7 (IBM) Host c906f07c01p17.cluster.com (10.7.1.17) appears to be up. MAC Address: 00:1A:64:FA:20:AB (IBM) Host c906f07c01p21.cluster.com (10.7.1.21) appears to be up. MAC Address: 00:1A:64:FA:20:AF (IBM) Host c906f07c01p25.cluster.com (10.7.1.25) appears to be up. MAC Address: 00:1A:64:FA:20:B3 (IBM) Host c906f07c01p28.cluster.com (10.7.1.28) appears to be up. MAC Address: 00:1A:64:FA:20:B6 (IBM) Host c906f07c02p01.cluster.com (10.7.2.1) appears to be up. MAC Address: 00:1A:64:FA:21:A3 (IBM) Host c906f07c02p05.cluster.com (10.7.2.5) appears to be up. MAC Address: 00:1A:64:FA:21:A7 (IBM) Host c906f07c02p09.cluster.com (10.7.2.9) appears to be up. MAC Address: 00:1A:64:FA:21:AB (IBM) Host c906f07c02p13.cluster.com (10.7.2.13) appears to be up. MAC Address: 00:1A:64:FA:21:AF (IBM) Host c906f07c02p17.cluster.com (10.7.2.17) appears to be up. MAC Address: 00:1A:64:FA:21:B3 (IBM) Host c906f07c02p21.cluster.com (10.7.2.21) appears to be up. MAC Address: 00:1A:64:FA:21:B7 (IBM) Host c906f07c02p25.cluster.com (10.7.2.25) appears to be up. MAC Address: 00:1A:64:FA:21:BB (IBM) Host c906f07c02p28.cluster.com (10.7.2.28) appears to be up. MAC Address: 00:1A:64:FA:21:BE (IBM) Host c906f07c03p01.cluster.com (10.7.3.1) appears to be up. MAC Address: 00:1A:64:FC:09:6D (IBM) Host c906f07c03p05.cluster.com (10.7.3.5) appears to be up. MAC Address: 00:1A:64:FC:09:71 (IBM) Host c906f07c03p09.cluster.com (10.7.3.9) appears to be up. MAC Address: 00:1A:64:FC:09:75 (IBM) Host c906f07c03p13.cluster.com (10.7.3.13) appears to be up. MAC Address: 00:1A:64:FC:09:79 (IBM) Host c906f07c03p17.cluster.com (10.7.3.17) appears to be up. MAC Address: 00:1A:64:FC:09:7D (IBM) Host c906f07c03p21.cluster.com (10.7.3.21) appears to be up. MAC Address: 00:1A:64:FC:09:81 (IBM) Host c906f07c03p25.cluster.com (10.7.3.25) appears to be up. MAC Address: 00:1A:64:FC:09:85 (IBM) Host c906f07c03p28.cluster.com (10.7.3.28) appears to be up. MAC Address: 00:1A:64:FC:09:88 (IBM) Host c906f07c04p01.cluster.com (10.7.4.1) appears to be up. MAC Address: 00:14:5E:B5:54:83 (IBM) Host c906f07c04p05.cluster.com (10.7.4.5) appears to be up. MAC Address: 00:14:5E:B5:54:87 (IBM) Host c906f07c04p09.cluster.com (10.7.4.9) appears to be up. MAC Address: 00:14:5E:B5:54:8B (IBM) Host c906f07c04p13.cluster.com (10.7.4.13) appears to be up. MAC Address: 00:14:5E:B5:54:8F (IBM) Host c906f07c04p17.cluster.com (10.7.4.17) appears to be up. MAC Address: 00:14:5E:B5:54:93 (IBM) Host c906f07c04p21.cluster.com (10.7.4.21) appears to be up. MAC Address: 00:14:5E:B5:54:97 (IBM) Host c906f07c04p25.cluster.com (10.7.4.25) appears to be up. MAC Address: 00:14:5E:B5:54:9B (IBM) Host c906f07c04p28.cluster.com (10.7.4.28) appears to be up. MAC Address: 00:14:5E:B5:54:9E (IBM) Host c906f07c05p05.cluster.com (10.7.5.5) appears to be up. MAC Address: 00:14:5E:B5:53:C1 (IBM) Host c906f07c05p09.cluster.com (10.7.5.9) appears to be up. MAC Address: 00:14:5E:B5:53:C5 (IBM) Host c906f07c05p13.cluster.com (10.7.5.13) appears to be up. MAC Address: 00:14:5E:B5:53:C9 (IBM) Host c906f07c05p17.cluster.com (10.7.5.17) appears to be up. MAC Address: 00:14:5E:B5:53:CD (IBM) Host c906f07c05p21.cluster.com (10.7.5.21) appears to be up. MAC Address: 00:14:5E:B5:53:D1 (IBM) Host c906f07c05p25.cluster.com (10.7.5.25) appears to be up. MAC Address: 00:14:5E:B5:53:D5 (IBM) Host c906f07c05p28.cluster.com (10.7.5.28) appears to be up. MAC Address: 00:14:5E:B5:53:D8 (IBM) Host c906f07c06p01.cluster.com (10.7.6.1) appears to be up. MAC Address: 00:1A:64:FB:58:AF (IBM) Host c906f07c06p05.cluster.com (10.7.6.5) appears to be up. MAC Address: 00:1A:64:FB:58:B3 (IBM) Host c906f07c06p09.cluster.com (10.7.6.9) appears to be up. MAC Address: 00:1A:64:FB:58:B7 (IBM) Host c906f07c06p13.cluster.com (10.7.6.13) appears to be up. MAC Address: 00:1A:64:FB:58:BB (IBM) Host c906f07c06p17.cluster.com (10.7.6.17) appears to be up. MAC Address: 00:1A:64:FB:58:BF (IBM) Host c906f07c06p21.cluster.com (10.7.6.21) appears to be up. MAC Address: 00:1A:64:FB:58:C3 (IBM) Host c906f07c06p25.cluster.com (10.7.6.25) appears to be up. MAC Address: 00:1A:64:FB:58:C7 (IBM) Host c906f07c06p28.cluster.com (10.7.6.28) appears to be up. MAC Address: 00:1A:64:FB:58:CA (IBM) Host c906f07c07p01.cluster.com (10.7.7.1) appears to be up. MAC Address: 00:1A:64:FC:13:F5 (IBM) Host c906f07c07p05.cluster.com (10.7.7.5) appears to be up. MAC Address: 00:1A:64:FC:13:F9 (IBM) Host c906f07c07p09.cluster.com (10.7.7.9) appears to be up. MAC Address: 00:1A:64:FC:13:FD (IBM) Host c906f07c07p13.cluster.com (10.7.7.13) appears to be up. MAC Address: 00:1A:64:FC:14:01 (IBM) Host c906f07c07p17.cluster.com (10.7.7.17) appears to be up. MAC Address: 00:1A:64:FC:14:05 (IBM) Host c906f07c07p21.cluster.com (10.7.7.21) appears to be up. MAC Address: 00:1A:64:FC:14:09 (IBM) Host c906f07c07p25.cluster.com (10.7.7.25) appears to be up. MAC Address: 00:1A:64:FC:14:0D (IBM) Host c906f07c07p28.cluster.com (10.7.7.28) appears to be up. MAC Address: 00:1A:64:FC:14:10 (IBM) Host c906f07c08p01.cluster.com (10.7.8.1) appears to be up. MAC Address: 00:1A:64:FB:D1:4D (IBM) Host c906f07c08p05.cluster.com (10.7.8.5) appears to be up. MAC Address: 00:1A:64:FB:D1:51 (IBM) Host c906f07c08p09.cluster.com (10.7.8.9) appears to be up. MAC Address: 00:1A:64:FB:D1:55 (IBM) Host c906f07c08p13.cluster.com (10.7.8.13) appears to be up. MAC Address: 00:1A:64:FB:D1:59 (IBM) Host c906f07c08p17.cluster.com (10.7.8.17) appears to be up. MAC Address: 00:1A:64:FB:D1:5D (IBM) Host c906f07c08p21.cluster.com (10.7.8.21) appears to be up. MAC Address: 00:1A:64:FB:D1:61 (IBM) Host c906f07c08p25.cluster.com (10.7.8.25) appears to be up. MAC Address: 00:1A:64:FB:D1:65 (IBM) Host c906f07c08p28.cluster.com (10.7.8.28) appears to be up. MAC Address: 00:1A:64:FB:D1:68 (IBM) Host c906f08c01p05.cluster.com (10.8.1.5) appears to be up. MAC Address: 00:1A:64:FC:0C:89 (IBM) Host c906f08c01p09.cluster.com (10.8.1.9) appears to be up. MAC Address: 00:1A:64:FC:0C:8D (IBM) Host c906f08c01p13.cluster.com (10.8.1.13) appears to be up. MAC Address: 00:1A:64:FC:0C:91 (IBM) Host c906f08c01p17.cluster.com (10.8.1.17) appears to be up. MAC Address: 00:1A:64:FC:0C:95 (IBM) Host c906f08c01p21.cluster.com (10.8.1.21) appears to be up. MAC Address: 00:1A:64:FC:0C:99 (IBM) Host c906f08c01p25.cluster.com (10.8.1.25) appears to be up. MAC Address: 00:1A:64:FC:0C:9D (IBM) Host c906f08c01p28.cluster.com (10.8.1.28) appears to be up. MAC Address: 00:1A:64:FC:0C:A0 (IBM) Host c906f08c02p01.cluster.com (10.8.2.1) appears to be up. MAC Address: 00:1A:64:FB:E2:77 (IBM) Host c906f08c02p05.cluster.com (10.8.2.5) appears to be up. MAC Address: 00:1A:64:FB:E2:7B (IBM) Host c906f08c02p09.cluster.com (10.8.2.9) appears to be up. MAC Address: 00:1A:64:FB:E2:7F (IBM) Host c906f08c02p13.cluster.com (10.8.2.13) appears to be up. MAC Address: 00:1A:64:FB:E2:83 (IBM) Host c906f08c02p17.cluster.com (10.8.2.17) appears to be up. MAC Address: 00:1A:64:FB:E2:87 (IBM) Host c906f08c02p21.cluster.com (10.8.2.21) appears to be up. MAC Address: 00:1A:64:FB:E2:8B (IBM) Host c906f08c02p25.cluster.com (10.8.2.25) appears to be up. MAC Address: 00:1A:64:FB:E2:8F (IBM) Host c906f08c02p28.cluster.com (10.8.2.28) appears to be up. MAC Address: 00:1A:64:FB:E2:92 (IBM) Host c906f08c03p01.cluster.com (10.8.3.1) appears to be up. MAC Address: 00:1A:64:FB:E9:2B (IBM) Host c906f08c03p05.cluster.com (10.8.3.5) appears to be up. MAC Address: 00:1A:64:FB:E9:2F (IBM) Host c906f08c03p09.cluster.com (10.8.3.9) appears to be up. MAC Address: 00:1A:64:FB:E9:33 (IBM) Host c906f08c03p13.cluster.com (10.8.3.13) appears to be up. MAC Address: 00:1A:64:FB:E9:37 (IBM) Host c906f08c03p17.cluster.com (10.8.3.17) appears to be up. MAC Address: 00:1A:64:FB:E9:3B (IBM) Host c906f08c03p21.cluster.com (10.8.3.21) appears to be up. MAC Address: 00:1A:64:FB:E9:3F (IBM) Host c906f08c03p25.cluster.com (10.8.3.25) appears to be up. MAC Address: 00:1A:64:FB:E9:43 (IBM) Host c906f08c03p28.cluster.com (10.8.3.28) appears to be up. MAC Address: 00:1A:64:FB:E9:46 (IBM) Host c906f08c04p01.cluster.com (10.8.4.1) appears to be up. MAC Address: 00:1A:64:FC:0D:09 (IBM) Host c906f08c04p05.cluster.com (10.8.4.5) appears to be up. MAC Address: 00:1A:64:FC:0D:0D (IBM) Host c906f08c04p09.cluster.com (10.8.4.9) appears to be up. MAC Address: 00:1A:64:FC:0D:11 (IBM) Host c906f08c04p13.cluster.com (10.8.4.13) appears to be up. MAC Address: 00:1A:64:FC:0D:15 (IBM) Host c906f08c04p17.cluster.com (10.8.4.17) appears to be up. MAC Address: 00:1A:64:FC:0D:19 (IBM) Host c906f08c04p21.cluster.com (10.8.4.21) appears to be up. MAC Address: 00:1A:64:FC:0D:1D (IBM) Host c906f08c04p25.cluster.com (10.8.4.25) appears to be up. MAC Address: 00:1A:64:FC:0D:21 (IBM) Host c906f08c04p28.cluster.com (10.8.4.28) appears to be up. MAC Address: 00:1A:64:FC:0D:24 (IBM) Host c906f08c05p05.cluster.com (10.8.5.5) appears to be up. MAC Address: 00:1A:64:FB:73:33 (IBM) Host c906f08c05p09.cluster.com (10.8.5.9) appears to be up. MAC Address: 00:1A:64:FB:73:37 (IBM) Host c906f08c05p13.cluster.com (10.8.5.13) appears to be up. MAC Address: 00:1A:64:FB:73:3B (IBM) Host c906f08c05p17.cluster.com (10.8.5.17) appears to be up. MAC Address: 00:1A:64:FB:73:3F (IBM) Host c906f08c05p21.cluster.com (10.8.5.21) appears to be up. MAC Address: 00:1A:64:FB:73:43 (IBM) Host c906f08c05p25.cluster.com (10.8.5.25) appears to be up. MAC Address: 00:1A:64:FB:73:47 (IBM) Host c906f08c05p28.cluster.com (10.8.5.28) appears to be up. MAC Address: 00:1A:64:FB:73:4A (IBM) Host c906f08c06p01.cluster.com (10.8.6.1) appears to be up. MAC Address: 00:1A:64:FB:B1:27 (IBM) Host c906f08c06p05.cluster.com (10.8.6.5) appears to be up. MAC Address: 00:1A:64:FB:B1:2B (IBM) Host c906f08c06p09.cluster.com (10.8.6.9) appears to be up. MAC Address: 00:1A:64:FB:B1:2F (IBM) Host c906f08c06p13.cluster.com (10.8.6.13) appears to be up. MAC Address: 00:1A:64:FB:B1:33 (IBM) Host c906f08c06p17.cluster.com (10.8.6.17) appears to be up. MAC Address: 00:1A:64:FB:B1:37 (IBM) Host c906f08c06p21.cluster.com (10.8.6.21) appears to be up. MAC Address: 00:1A:64:FB:B1:3B (IBM) Host c906f08c06p25.cluster.com (10.8.6.25) appears to be up. MAC Address: 00:1A:64:FB:B1:3F (IBM) Host c906f08c06p28.cluster.com (10.8.6.28) appears to be up. MAC Address: 00:1A:64:FB:B1:42 (IBM) Host c906f08c07p01.cluster.com (10.8.7.1) appears to be up. MAC Address: 00:1A:64:FC:20:69 (IBM) Host c906f08c07p05.cluster.com (10.8.7.5) appears to be up. MAC Address: 00:1A:64:FC:20:6D (IBM) Host c906f08c07p09.cluster.com (10.8.7.9) appears to be up. MAC Address: 00:1A:64:FC:20:71 (IBM) Host c906f08c07p13.cluster.com (10.8.7.13) appears to be up. MAC Address: 00:1A:64:FC:20:75 (IBM) Host c906f08c07p17.cluster.com (10.8.7.17) appears to be up. MAC Address: 00:1A:64:FC:20:79 (IBM) Host c906f08c07p21.cluster.com (10.8.7.21) appears to be up. MAC Address: 00:1A:64:FC:20:7D (IBM) Host c906f08c07p25.cluster.com (10.8.7.25) appears to be up. MAC Address: 00:1A:64:FC:20:81 (IBM) Host c906f08c07p28.cluster.com (10.8.7.28) appears to be up. MAC Address: 00:1A:64:FC:20:84 (IBM) Host c906f08c08p01.cluster.com (10.8.8.1) appears to be up. MAC Address: 00:1A:64:FB:D3:F5 (IBM) Host c906f08c08p05.cluster.com (10.8.8.5) appears to be up. MAC Address: 00:1A:64:FB:D3:F9 (IBM) Host c906f08c08p09.cluster.com (10.8.8.9) appears to be up. MAC Address: 00:1A:64:FB:D3:FD (IBM) Host c906f08c08p13.cluster.com (10.8.8.13) appears to be up. MAC Address: 00:1A:64:FB:D4:01 (IBM) Host c906f08c08p17.cluster.com (10.8.8.17) appears to be up. MAC Address: 00:1A:64:FB:D4:05 (IBM) Host c906f08c08p21.cluster.com (10.8.8.21) appears to be up. MAC Address: 00:1A:64:FB:D4:09 (IBM) Host c906f08c08p25.cluster.com (10.8.8.25) appears to be up. MAC Address: 00:1A:64:FB:D4:0D (IBM) Host c906f08c08p28.cluster.com (10.8.8.28) appears to be up. MAC Address: 00:1A:64:FB:D4:10 (IBM) Host c906f09c01p05.cluster.com (10.9.1.5) appears to be up. MAC Address: 00:1A:64:F9:A4:CD (IBM) Host c906f09c01p09.cluster.com (10.9.1.9) appears to be up. MAC Address: 00:1A:64:F9:A4:D1 (IBM) Host c906f09c01p13.cluster.com (10.9.1.13) appears to be up. MAC Address: 00:1A:64:F9:A4:D5 (IBM) Host c906f09c01p17.cluster.com (10.9.1.17) appears to be up. MAC Address: 00:1A:64:F9:A4:D9 (IBM) Host c906f09c01p21.cluster.com (10.9.1.21) appears to be up. MAC Address: 00:1A:64:F9:A4:DD (IBM) Host c906f09c01p25.cluster.com (10.9.1.25) appears to be up. MAC Address: 00:1A:64:F9:A4:E1 (IBM) Host c906f09c01p28.cluster.com (10.9.1.28) appears to be up. MAC Address: 00:1A:64:F9:A4:E4 (IBM) Host c906f09c02p01.cluster.com (10.9.2.1) appears to be up. MAC Address: 00:1A:64:FB:DD:A9 (IBM) Host c906f09c02p05.cluster.com (10.9.2.5) appears to be up. MAC Address: 00:1A:64:FB:DD:AD (IBM) Host c906f09c02p09.cluster.com (10.9.2.9) appears to be up. MAC Address: 00:1A:64:FB:DD:B1 (IBM) Host c906f09c02p13.cluster.com (10.9.2.13) appears to be up. MAC Address: 00:1A:64:FB:DD:B5 (IBM) Host c906f09c02p17.cluster.com (10.9.2.17) appears to be up. MAC Address: 00:1A:64:FB:DD:B9 (IBM) Host c906f09c02p21.cluster.com (10.9.2.21) appears to be up. MAC Address: 00:1A:64:FB:DD:BD (IBM) Host c906f09c02p25.cluster.com (10.9.2.25) appears to be up. MAC Address: 00:1A:64:FB:DD:C1 (IBM) Host c906f09c02p28.cluster.com (10.9.2.28) appears to be up. MAC Address: 00:1A:64:FB:DD:C4 (IBM) Host c906f09c03p01.cluster.com (10.9.3.1) appears to be up. MAC Address: 00:1A:64:FB:85:33 (IBM) Host c906f09c03p05.cluster.com (10.9.3.5) appears to be up. MAC Address: 00:1A:64:FB:85:37 (IBM) Host c906f09c03p09.cluster.com (10.9.3.9) appears to be up. MAC Address: 00:1A:64:FB:85:3B (IBM) Host c906f09c03p13.cluster.com (10.9.3.13) appears to be up. MAC Address: 00:1A:64:FB:85:3F (IBM) Host c906f09c03p17.cluster.com (10.9.3.17) appears to be up. MAC Address: 00:1A:64:FB:85:43 (IBM) Host c906f09c03p21.cluster.com (10.9.3.21) appears to be up. MAC Address: 00:1A:64:FB:85:47 (IBM) Host c906f09c03p25.cluster.com (10.9.3.25) appears to be up. MAC Address: 00:1A:64:FB:85:4B (IBM) Host c906f09c03p28.cluster.com (10.9.3.28) appears to be up. MAC Address: 00:1A:64:FB:85:4E (IBM) Host c906f09c04p01.cluster.com (10.9.4.1) appears to be up. MAC Address: 00:1A:64:FC:0A:F9 (IBM) Host c906f09c04p05.cluster.com (10.9.4.5) appears to be up. MAC Address: 00:1A:64:FC:0A:FD (IBM) Host c906f09c04p09.cluster.com (10.9.4.9) appears to be up. MAC Address: 00:1A:64:FC:0B:01 (IBM) Host c906f09c04p13.cluster.com (10.9.4.13) appears to be up. MAC Address: 00:1A:64:FC:0B:05 (IBM) Host c906f09c04p17.cluster.com (10.9.4.17) appears to be up. MAC Address: 00:1A:64:FC:0B:09 (IBM) Host c906f09c04p21.cluster.com (10.9.4.21) appears to be up. MAC Address: 00:1A:64:FC:0B:0D (IBM) Host c906f09c04p25.cluster.com (10.9.4.25) appears to be up. MAC Address: 00:1A:64:FC:0B:11 (IBM) Host c906f09c04p28.cluster.com (10.9.4.28) appears to be up. MAC Address: 00:1A:64:FC:0B:14 (IBM) Host c906f09c05p05.cluster.com (10.9.5.5) appears to be up. MAC Address: 00:1A:64:FB:46:79 (IBM) Host c906f09c05p09.cluster.com (10.9.5.9) appears to be up. MAC Address: 00:1A:64:FB:46:7D (IBM) Host c906f09c05p13.cluster.com (10.9.5.13) appears to be up. MAC Address: 00:1A:64:FB:46:81 (IBM) Host c906f09c05p17.cluster.com (10.9.5.17) appears to be up. MAC Address: 00:1A:64:FB:46:85 (IBM) Host c906f09c05p21.cluster.com (10.9.5.21) appears to be up. MAC Address: 00:1A:64:FB:46:89 (IBM) Host c906f09c05p25.cluster.com (10.9.5.25) appears to be up. MAC Address: 00:1A:64:FB:46:8D (IBM) Host c906f09c05p28.cluster.com (10.9.5.28) appears to be up. MAC Address: 00:1A:64:FB:46:90 (IBM) Host c906f09c06p01.cluster.com (10.9.6.1) appears to be up. MAC Address: 00:1A:64:FB:4F:5F (IBM) Host c906f09c06p05.cluster.com (10.9.6.5) appears to be up. MAC Address: 00:1A:64:FB:4F:63 (IBM) Host c906f09c06p09.cluster.com (10.9.6.9) appears to be up. MAC Address: 00:1A:64:FB:4F:67 (IBM) Host c906f09c06p13.cluster.com (10.9.6.13) appears to be up. MAC Address: 00:1A:64:FB:4F:6B (IBM) Host c906f09c06p17.cluster.com (10.9.6.17) appears to be up. MAC Address: 00:1A:64:FB:4F:6F (IBM) Host c906f09c06p21.cluster.com (10.9.6.21) appears to be up. MAC Address: 00:1A:64:FB:4F:73 (IBM) Host c906f09c06p25.cluster.com (10.9.6.25) appears to be up. MAC Address: 00:1A:64:FB:4F:77 (IBM) Host c906f09c06p28.cluster.com (10.9.6.28) appears to be up. MAC Address: 00:1A:64:FB:4F:7A (IBM) Host c906f09c07p01.cluster.com (10.9.7.1) appears to be up. MAC Address: 00:1A:64:FC:13:4B (IBM) Host c906f09c07p05.cluster.com (10.9.7.5) appears to be up. MAC Address: 00:1A:64:FC:13:4F (IBM) Host c906f09c07p09.cluster.com (10.9.7.9) appears to be up. MAC Address: 00:1A:64:FC:13:53 (IBM) Host c906f09c07p13.cluster.com (10.9.7.13) appears to be up. MAC Address: 00:1A:64:FC:13:57 (IBM) Host c906f09c07p17.cluster.com (10.9.7.17) appears to be up. MAC Address: 00:1A:64:FC:13:5B (IBM) Host c906f09c07p21.cluster.com (10.9.7.21) appears to be up. MAC Address: 00:1A:64:FC:13:5F (IBM) Host c906f09c07p25.cluster.com (10.9.7.25) appears to be up. MAC Address: 00:1A:64:FC:13:63 (IBM) Host c906f09c07p28.cluster.com (10.9.7.28) appears to be up. MAC Address: 00:1A:64:FC:13:66 (IBM) Host c906f09c08p01.cluster.com (10.9.8.1) appears to be up. MAC Address: 00:1A:64:FC:27:51 (IBM) Host c906f09c08p05.cluster.com (10.9.8.5) appears to be up. MAC Address: 00:1A:64:FC:27:55 (IBM) Host c906f09c08p09.cluster.com (10.9.8.9) appears to be up. MAC Address: 00:1A:64:FC:27:59 (IBM) Host c906f09c08p13.cluster.com (10.9.8.13) appears to be up. MAC Address: 00:1A:64:FC:27:5D (IBM) Host c906f09c08p17.cluster.com (10.9.8.17) appears to be up. MAC Address: 00:1A:64:FC:27:61 (IBM) Host c906f09c08p21.cluster.com (10.9.8.21) appears to be up. MAC Address: 00:1A:64:FC:27:65 (IBM) Host c906f09c08p25.cluster.com (10.9.8.25) appears to be up. MAC Address: 00:1A:64:FC:27:69 (IBM) Host c906f09c08p28.cluster.com (10.9.8.28) appears to be up. MAC Address: 00:1A:64:FC:27:6C (IBM) Nmap done: 248 IP addresses (248 hosts up) scanned in 3.97 seconds c906mgrs2:~ # Thanks, ------------------------------------------------------------------------- Li,Guang Cheng (李光成) IBM China Software Development Laboratory Tel: 86-10-82453499 Tie-Line: 9053499 Email: liguangc@... Address: Building 28, ZhongGuanCun Software Park, No.8, Dong Bei Wang West Road, Haidian District Beijing 100193, PRC 北京市海淀区东北旺西路8号中关村软件园28号楼邮编: 100193 _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
	Re: nmap returns "Host <ip_address> appears to be up" instead of "Host <hostname> appears to be up" for some of the nodes by David Fifield :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message On Thu, Nov 12, 2009 at 04:41:57PM +0800, Guang Cheng Li wrote: > HI, > > OS: SLES 11 on IBM System p > nmap version: 4.75 and 5.00 > > I am using nmap to detect whether all of the nodes in my cluster and up and > running, nmap returns "Host <ip_address> appears to be up" for some nodes > but returns "Host <hostname> appears to be up" for the other nodes. Since a > script is used to parse the output, so it is difficult for me to write the > script. Could someone let me know that why the nmap returns both "Host > <ip_address> appears to be up" and "Host <hostname> appears to be up"? > thank you. > > Starting Nmap 4.75 ( http://nmap.org ) at 2009-11-12 03:39 EST > Host 10.6.1.5 appears to be up. > Host c906f06c03p21.cluster.com (10.6.3.21) appears to be up. Nmap's normal output to the screen is meant to be read by humans, so often lines will have different forms depending on what information is available. In version 4.76, the form "Host <hostname> (<ip address>) appears to be up" means that a reverse-DNS record for the IP address was found. For parsing with a script you should use the XML (-oX) or grepable output formats (-oG). This is especially important because normal output may change from time to time, and it will definitely be different in the next release so that it can hold reverse-DNS records. Try running nmap -oX output.xml -PE --send-ip -sP c906f06c01p05 or if you want to pipe the output directly to a script, nmap -oX - -PE --send-ip -sP c906f06c01p05 Sometimes I parse Nmap's normal output just for convenience. If you do that you have to make your parser handle all these cases and be ware that the output can change in the future. Here is the documentation on all the output formats: http://nmap.org/book/output.html David Fifield _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
	Re: nmap returns "Host <ip_address> appears to be up" instead of "Host <hostname> appears to be up" for some of the nodes by Rob Nicholls-3 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message On Thu, 12 Nov 2009 08:52:05 -0700, David Fifield <david@...> > Nmap's normal output to the screen is meant to be read by humans, so > often lines will have different forms depending on what information is > available. In version 4.76, the form "Host <hostname> (<ip address>) > appears to be up" means that a reverse-DNS record for the IP address was > found. So a possible workaround might be to perform the scan using "-n" to prevent DNS resolution, so it'll only print out the IP address? Rob _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
	Re: nmap returns "Host <ip_address> appears to be up" instead of "Host <hostname> appears to be up" for some of the nodes by Guang Cheng Li :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message HI David, Thank you for your reponse. The -oX and -oG does change the output format to make it easier for the output parsing, but the "hostname" information is still not available for some nodes. I can update my script to check both the ip address and the hostname, but I have to call lot of hostname resolution system calls to resolve the hostnames/ip addresses, the performance degradation might be a problem for me because I can have at most 64,000 nodes in my cluster. Actually we are using /etc/hosts to resolve the host names because the DNS itself also has some kind of scaling issues, though the DNS hostname resolution also works in the cluster. Do you think the flag "--system-dns" will be a better choice for us because we are using /etc/hosts for hostname resolution? The experiment also shows that the "--system-dns" runs faster in my environment, is there any other side effects by specifying the "--system-dns" flag? Thanks, ------------------------------------------------------------------------- Li,Guang Cheng (李光成) IBM China Software Development Laboratory David Fifield <david@bamsoftwar e.com> To Guang Cheng Li/China/IBM@IBMCN 2009-11-12 23:52 cc nmap-dev@... Subject Re: nmap returns "Host <ip_address> appears to be up" instead of "Host <hostname> appears to be up" for some of the nodes On Thu, Nov 12, 2009 at 04:41:57PM +0800, Guang Cheng Li wrote: > HI, > > OS: SLES 11 on IBM System p > nmap version: 4.75 and 5.00 > > I am using nmap to detect whether all of the nodes in my cluster and up and > running, nmap returns "Host <ip_address> appears to be up" for some nodes > but returns "Host <hostname> appears to be up" for the other nodes. Since a > script is used to parse the output, so it is difficult for me to write the > script. Could someone let me know that why the nmap returns both "Host > <ip_address> appears to be up" and "Host <hostname> appears to be up"? > thank you. > > Starting Nmap 4.75 ( http://nmap.org ) at 2009-11-12 03:39 EST > Host 10.6.1.5 appears to be up. > Host c906f06c03p21.cluster.com (10.6.3.21) appears to be up. Nmap's normal output to the screen is meant to be read by humans, so often lines will have different forms depending on what information is available. In version 4.76, the form "Host <hostname> (<ip address>) appears to be up" means that a reverse-DNS record for the IP address was found. For parsing with a script you should use the XML (-oX) or grepable output formats (-oG). This is especially important because normal output may change from time to time, and it will definitely be different in the next release so that it can hold reverse-DNS records. Try running nmap -oX output.xml -PE --send-ip -sP c906f06c01p05 or if you want to pipe the output directly to a script, nmap -oX - -PE --send-ip -sP c906f06c01p05 Sometimes I parse Nmap's normal output just for convenience. If you do that you have to make your parser handle all these cases and be ware that the output can change in the future. Here is the documentation on all the output formats: http://nmap.org/book/output.html David Fifield _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/ graycol.gif (144 bytes) Download Attachment pic30966.gif (1K) Download Attachment ecblank.gif (62 bytes) Download Attachment
	Re: nmap returns "Host <ip_address> appears to be up" instead of "Host <hostname> appears to be up" for some of the nodes by David Fifield :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message On Fri, Nov 13, 2009 at 09:27:59AM +0800, Guang Cheng Li wrote: > HI David, > > Thank you for your reponse. > > The -oX and -oG does change the output format to make it easier for the > output parsing, but the "hostname" information is still not available for > some nodes. I can update my script to check both the ip address and the > hostname, but I have to call lot of hostname resolution system calls to > resolve the hostnames/ip addresses, the performance degradation might be a > problem for me because I can have at most 64,000 nodes in my cluster. Even if you're using the normal output, you don't have to look up the hostnames when they are present. The IP address is always there too, in parentheses. If the hostname is not present, it means that reverse DNS for that address failed. If there is a host whose name you can get through your system resolver but not with Nmap, then it is likely a bug and we would like to have more information about it. > Actually we are using /etc/hosts to resolve the host names because the DNS > itself also has some kind of scaling issues, though the DNS hostname > resolution also works in the cluster. Do you think the flag "--system-dns" > will be a better choice for us because we are using /etc/hosts for hostname > resolution? The experiment also shows that the "--system-dns" runs faster > in my environment, is there any other side effects by specifying the > "--system-dns" flag? Nmap's parallel DNS resolver also looks in /etc/hosts, so if all the hosts are in there it shouldn't have an effect. You will have to test yourself to see which is faster. David Fifield _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
	Re: nmap returns "Host <ip_address> appears to be up" instead of "Host <hostname> appears to be up" for some of the nodes by Guang Cheng Li :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message I use hostname everywhere in my scripts and in our product, so it will be difficult for us to change to use ip address unless we resolve the hostnames to ip addresses before passing to nmap, hostname resolution will bring in performance degradation, I hesitate to do this. All the host names could get through the system resolver, if I add the flag "--system-dns" to nmap, then all the hostnames will be returned from nmap. From this point view, I am suspecting this may be a nmap bug. I noticed a special configuration in my cluster, this may be causing problem, we use two nameservers in /etc/resolv.conf, one is for private subnet and one is for public subnet, the private subnet name server will be checked first because it is the first nameserver in /etc/resolv.conf, I turned on the nmap -d9, seems the nmap is sending the DNS resolver to the public subnet name server. c906mgrs2:/opt/xcat/bin # cat /etc/resolv.conf \| grep nameserver nameserver 10.0.0.242 ==========> private subnet nameserver nameserver 9.114.8.1 =========> public subnet nameserver c906mgrs2:/opt/xcat/bin # c906mgrs2:/opt/xcat/bin # nslookup c906f06c01p05 =============> system resolver works Server: 10.0.0.242 Address: 10.0.0.242#53 Name: c906f06c01p05.cluster.com Address: 10.6.1.5 c906mgrs2:/opt/xcat/bin # ping c906f06c01p05 PING c906f06c01p05 (10.6.1.5) 56(84) bytes of data. 64 bytes from c906f06c01p05 (10.6.1.5): icmp_seq=1 ttl=64 time=0.112 ms ^C --- c906f06c01p05 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.112/0.112/0.112/0.000 ms c906mgrs2:/opt/xcat/bin # c906mgrs2:/opt/xcat/bin # nmap -PE -d9 --send-ip -sP c906f06c01p05 Starting Nmap 4.75 ( http://nmap.org ) at 2009-11-12 23:45 EST Fetchfile found /usr/share/nmap/nmap-services PORTS: Using top 1000 ports found open (TCP:0, UDP:0) The max # of sockets we are using is: 0 --------------- Timing report --------------- hostgroups: min 1, max 100000 rtt-timeouts: init 1000, min 100, max 10000 max-scan-delay: TCP 1000, UDP 1000 parallelism: min 0, max 0 max-retries: 10, host-timeout: 0 min-rate: 0, max-rate: 0 --------------------------------------------- Initiating Ping Scan at 23:45 Scanning 10.6.1.5 [1 port] Pcap filter: dst host 10.0.0.242 and (icmp or ((tcp or udp) and (src host 10.6.1.5))) Packet capture filter (device eth1): dst host 10.0.0.242 and (icmp or ((tcp or udp) and (src host 10.6.1.5))) SENT (0.1550s) ICMP 10.0.0.242 > 10.6.1.5 echo request (type=8/code=0) ttl=59 id=38149 iplen=28 TIMING STATS (0.1550s): IP, probes active/freshportsleft/retry_stack/outstanding/retranwait/onbench, cwnd/ccthresh/delay, timeout/srtt/rttvar/ Groupstats (1/1 incomplete): 1/////* 10.00/75/* 1000000/-1/-1 10.6.1.5: 1/0/0/1/0/0 10.00/75/0 1000000/-1/-1 Current sending rates: 15.34 packets / s, 429.57 bytes / s. Overall sending rates: 15.34 packets / s, 429.57 bytes / s. RCVD (0.1550s) ICMP 10.6.1.5 > 10.0.0.242 echo reply (type=0/code=0) ttl=64 id=61717 iplen=28 Found 10.6.1.5 in incomplete hosts list. We got a ping packet back from 10.6.1.5: id = 45799 seq = 0 checksum = 19736 ultrascan_host_probe_update called for machine 10.6.1.5 state UNKNOWN -> HOST_UP (trynum 0 time: 212) Timeout vals: srtt: -1 rttvar: -1 to: 1000000 delta 124 ==> srtt: 124 rttvar: 5000 to: 100000 Timeout vals: srtt: -1 rttvar: -1 to: 1000000 delta 124 ==> srtt: 124 rttvar: 5000 to: 100000 Changing ping technique for 10.6.1.5 to icmp type 8 code 0 Moving 10.6.1.5 to completed hosts list with 0 outstanding probes. Completed Ping Scan at 23:45, 0.07s elapsed (1 total hosts) Overall sending rates: 15.31 packets / s, 428.57 bytes / s. pcap stats: 1 packets received by filter, 0 dropped by kernel. mass_rdns: Using DNS server 10.0.0.242 mass_rdns: Using DNS server 9.114.8.1 NSOCK (0.2620s) msevent_new (IOD #1) (EID #8) NSOCK (0.2620s) UDP connection requested to 9.114.8.1:53 (IOD #1) EID 8 NSOCK (0.2620s) msevent_new (IOD #1) (EID #18) NSOCK (0.2620s) Read request from IOD #1 [9.114.8.1:53] (timeout: -1ms) EID 18 NSOCK (0.2630s) msevent_new (IOD #2) (EID #24) NSOCK (0.2630s) UDP connection requested to 10.0.0.242:53 (IOD #2) EID 24 NSOCK (0.2630s) msevent_new (IOD #2) (EID #34) NSOCK (0.2630s) Read request from IOD #2 [10.0.0.242:53] (timeout: -1ms) EID 34 Initiating Parallel DNS resolution of 1 host. at 23:45 mass_rdns: TRANSMITTING for <10.6.1.5> (server <9.114.8.1>) ====================> Wrong name server is selected. NSOCK (0.2630s) msevent_new (IOD #1) (EID #43) NSOCK (0.2630s) Write request for 39 bytes to IOD #1 EID 43 [9.114.8.1:53]: .............5.1.6.10.in-addr.arpa..... NSOCK (0.2630s) nsock_loop() started (timeout=500ms). 5 events pending NSOCK (0.2630s) wait_for_events NSOCK (0.2630s) Callback: CONNECT SUCCESS for EID 24 [10.0.0.242:53] NSOCK (0.2630s) msevent_delete (IOD #2) (EID #24) NSOCK (0.2630s) Callback: CONNECT SUCCESS for EID 8 [9.114.8.1:53] NSOCK (0.2630s) msevent_delete (IOD #1) (EID #8) NSOCK (0.2630s) Callback: WRITE SUCCESS for EID 43 [9.114.8.1:53] NSOCK (0.2630s) msevent_delete (IOD #1) (EID #43) NSOCK (0.2630s) wait_for_events NSOCK (0.2630s) Callback: READ SUCCESS for EID 18 [9.114.8.1:53] (116 bytes) NSOCK (0.2630s) msevent_new (IOD #1) (EID #50) NSOCK (0.2630s) Read request from IOD #1 [9.114.8.1:53] (timeout: -1ms) EID 50 CAPACITY <9.114.8.1> = 12 NSOCK (0.2630s) msevent_delete (IOD #1) (EID #50) NSOCK (0.2630s) msevent_delete (IOD #2) (EID #34) mass_rdns: NXDOMAIN <id = 37127> mass_rdns: 0.02s 0/1 [#: 2, OK: 0, NX: 0, DR: 0, SF: 0, TR: 1] NSOCK (0.2630s) msevent_delete (IOD #1) (EID #18) Completed Parallel DNS resolution of 1 host. at 23:45, 0.00s elapsed DNS resolution of 1 IPs took 0.02s. Mode: Async [#: 2, OK: 0, NX: 1, DR: 0, SF: 0, TR: 1, CN: 0] Fetchfile found /usr/share/nmap/nmap-mac-prefixes Host 10.6.1.5 appears to be up, received echo-reply. =======================> ip address is returned MAC Address: 00:1A:64:FC:0A:37 (IBM) Read from /usr/share/nmap: nmap-mac-prefixes nmap-services. Nmap done: 1 IP address (1 host up) scanned in 0.46 seconds Raw packets sent: 1 (28B) \| Rcvd: 1 (28B) c906mgrs2:/opt/xcat/bin # Thanks, ------------------------------------------------------------------------- Li,Guang Cheng (李光成) IBM China Software Development Laboratory David Fifield <david@bamsoftwar e.com> To Guang Cheng Li/China/IBM@IBMCN 2009-11-13 11:24 cc nmap-dev@... Subject Re: nmap returns "Host <ip_address> appears to be up" instead of "Host <hostname> appears to be up" for some of the nodes On Fri, Nov 13, 2009 at 09:27:59AM +0800, Guang Cheng Li wrote: > HI David, > > Thank you for your reponse. > > The -oX and -oG does change the output format to make it easier for the > output parsing, but the "hostname" information is still not available for > some nodes. I can update my script to check both the ip address and the > hostname, but I have to call lot of hostname resolution system calls to > resolve the hostnames/ip addresses, the performance degradation might be a > problem for me because I can have at most 64,000 nodes in my cluster. Even if you're using the normal output, you don't have to look up the hostnames when they are present. The IP address is always there too, in parentheses. If the hostname is not present, it means that reverse DNS for that address failed. If there is a host whose name you can get through your system resolver but not with Nmap, then it is likely a bug and we would like to have more information about it. > Actually we are using /etc/hosts to resolve the host names because the DNS > itself also has some kind of scaling issues, though the DNS hostname > resolution also works in the cluster. Do you think the flag "--system-dns" > will be a better choice for us because we are using /etc/hosts for hostname > resolution? The experiment also shows that the "--system-dns" runs faster > in my environment, is there any other side effects by specifying the > "--system-dns" flag? Nmap's parallel DNS resolver also looks in /etc/hosts, so if all the hosts are in there it shouldn't have an effect. You will have to test yourself to see which is faster. David Fifield _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/ graycol.gif (144 bytes) Download Attachment pic11260.gif (1K) Download Attachment ecblank.gif (62 bytes) Download Attachment