How to reproduce:
1.down the latest build
2.[detached]
[root@c910f04x27v02 ~]#
[root@c910f04x27v02 ~]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 42:F6:0A:04:1B:02
inet addr:10.4.27.2 Bcast:10.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::40f6:aff:fe04:1b02/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4765261 errors:0 dropped:0 overruns:0 frame:0
TX packets:10896845 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4752997594 (4.4 GiB) TX bytes:7497863630 (6.9 GiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:932127 errors:0 dropped:0 overruns:0 frame:0
TX packets:932127 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:126096298 (120.2 MiB) TX bytes:126096298 (120.2 MiB)
[root@c910f04x27v02 ~]#
[root@c910f04x27v02 ~]# switchdiscover
Discovering switches using nmap. It may take long time...
You can modify the --range parameters to cut down the time.
------------->this command run about 24 h ,but no result
I'd like to get on your machine to try. Please send me the login info through email.
I logged on your machine and ran the switchdiscover command with -V option, it in turn called
[root@c910f04x27v02 ~]# switchdiscover -V
Discovering switches using nmap for . It may take long time...
You can modify the --range parameters to cut down the time.
Process command: /usr/bin/nmap -sP -oX - 10.0.0.0/8
Looks like the correct nmap range was used in nmap command.
Since this network is wide open (255.0.0.0), it will take long time. My experience is that for a 255.255.0.0 net it will take about 40 minutes. So this network will take approximately 40*255/60/24 = 7.8 days for this command to finish.
Please close this defect.