2010-01-25 - Working with Mike. Tried to connect to NAT-MCH using USB console. Worked once on Mike's vista laptop, then not again.
Try again on L3 XP machine. First time USB device is unrecognized, but observe that Mike has downloaded the nat-mch.inf file. Use the device manager to load this driver file, then it works using teraterm.
Only problem seen is that one must exit teraterm before power cycling the uTCA crate, otherwise it won't connect.
The recover procedure which seems to always work is to exit Teraterm, then (with uTCA power on) unplug the USB cable, count to 5, then replug and count to 5. Then start Teraterm and select 'com4'. This has now worked many times.
2010-01-26 - Still can't connect via ethernet. Using eth1 with x-over cable on cms1. Capture packets with nmap... see arp request with no replay. Manually add to arp tables with:
sudo /sbin/arp -s 192.168.1.41 00:e0:81:32:12:b3
Still fails. Try cabling to regular switch on 43 subnet, assign unused I/P address 'cms3.bu.edu'.
Same problem. Have to take a break for now.
10am - still no luck. Tried tracking with wireshark... see a 'Ping' sent to port 623, reply is 'destination unreachable'
Try C client/server pair on port 623 and it works but requires sudo. Try running natview with sudo... no luck.
Also try ipmitool (normal and sudo) with same results.
Back to private network. Set I/P =
192.168.1.10.
Change cables. Switch from long "Cat 5" (cross-over?) cable to 15' "Cat 6" new yellow cable.
Ping works, so no need for crossover. Same problem.
--
EricHazen - 26 Jan 2010