Alex ..... below is the prtconf for the P81. Below that is the return for ifconfig -a If I do an ifconfig hme1 up hme1 goes on the network, quess the question is how do I get it to happen at boot up and also get the machine to load the defaultrouter? The defaultrouter has been added to rc.foxapps and also to etc defaultrouter (both files are executable). This one has me stumped as I never have problems getting the machines on the company WAN # prtconf System Configuration: Sun Microsystems sun4u Memory size: 2048 Megabytes System Peripherals (Software Nodes): SUNW,Sun-Blade-1500 packages (driver not attached) SUNW,builtin-drivers (driver not attached) deblocker (driver not attached) disk-label (driver not attached) terminal-emulator (driver not attached) dropins (driver not attached) kbd-translator (driver not attached) obp-tftp (driver not attached) SUNW,i2c-ram-device (driver not attached) SUNW,fru-device (driver not attached) ufs-file-system (driver not attached) chosen (driver not attached) openprom (driver not attached) client-services (driver not attached) options, instance #0 aliases (driver not attached) memory (driver not attached) virtual-memory (driver not attached) SUNW,UltraSPARC-IIIi, instance #0 memory-controller, instance #0 pci, instance #0 isa, instance #0 flashprom (driver not attached) rtc (driver not attached) i2c, instance #0 hardware-monitor, instance #0 motherboard-fru-prom, instance #0 (driver not attached) dimm-spd, instance #1 (driver not attached) dimm-spd, instance #2 (driver not attached) dimm-spd, instance #3 (driver not attached) dimm-spd, instance #4 (driver not attached) clock-generator, instance #0 power, instance #0 serial, instance #0 serial, instance #1 dma (driver not attached) parallel (driver not attached) pmu, instance #0 i2c (driver not attached) card-reader (driver not attached) beep, instance #0 ppm, instance #0 sound (driver not attached) usb, instance #0 storage, instance #0 disk, instance #0 (driver not attached) usb, instance #1 mouse, instance #0 keyboard, instance #1 ide, instance #0 disk (driver not attached) cdrom (driver not attached) dad, instance #0 dad, instance #1 pci, instance #1 usb, instance #0 usb, instance #1 usb, instance #0 firewire, instance #0 pci, instance #0 pci108e,1000 (driver not attached) SUNW,hme, instance #0 SUNW,isptwo, instance #0 sd (driver not attached) st (driver not attached) pci108e,1000 (driver not attached) SUNW,hme, instance #1 pci114f,1c, instance #0 ppm, instance #0 pci, instance #1 network (driver not attached) SUNW,XVR-100, instance #0 i2c (driver not attached) nvram (driver not attached) idprom (driver not attached) os-io (driver not attached) pseudo, instance #0 X ed the IP to keep IT from putting me in jail!!! # netstat -r Routing Table: IPv4 Destination Gateway Flags Ref Use Interface -------------------- -------------------- ----- ----- ------ --------- 151.128.0.0 AW5101 U 1 0 hme0 224.0.0.0 AW5101 U 1 0 hme0 localhost localhost UH 2 6 lo0 # ifconfig -a lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 151.128.8.65 netmask ffff0000 broadcast 151.128.255.255 ether 8:0:20:c3:da:c0 hme1: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3 inet XX.XXX.XXX.XX netmask ff000000 broadcast 10.255.255.255 ether 0:3:ba:31:6d:46 Troy L. Brazell Duke Energy Field Services Sr. Process Control Analyst ISA CCST Phone (405) 263 4810 ext. 24 Cell (806) 898 4340 Okarche C&M Route 4 P.O. Box 40 Okarche, OK. 73762 "Johnson, Alex (Foxboro)" To: foxboro@xxxxxxxxxxxxx <ajohnson@Foxboro cc: .com> Subject: Re: [foxboro] Server 70 for V8 Sent by: foxboro-bounce@fr eelists.org 01/15/2005 10:00 AM Please respond to foxboro I was referring to the quantity more than anything. The full scope of the ATS includes boot services. At this time the full scope of boot support is not completely defined, e.g., should a V8 host be able to boot a CP10? Regards, Alex Johnson Invensys Process Systems Invensys Systems, Inc. 10707 Haddington Houston, TX 77043 713.722.2859 (voice) 713.722.2700 (switchboard) 713.932.0222 (fax) ajohnson@xxxxxxxxxxx -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of john kinsley Sent: Saturday, January 15, 2005 3:39 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Server 70 for V8 Alex, Regarding item #2, I thought hosting across the ATS was a done deal. If not, I'll have to replace all controllers to 270 if I want to upgrade the existing 51B host (Which means I'll be using the 51B a lot longer than I had planned). Or is the comment regarding AW70 TS only? Thanks and Regards, John Kinsley P&CSD/PCD/PASU Phone: 966-3-873-0952 -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Johnson, Alex (Foxboro) Sent: Thursday, January 13, 2005 4:37 PM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Server 70 for V8 Re: AW70 Terminal Server release date The target release date for a Server 70 (Win2K3 Server OS) for V8 is May of this year. Quotations require our Account Representatives to go through our commitment control process since it is not a released product. Re: AW70 Terminal Server Hosting I'm not sure of the specific limits of hosting across the ATS. There are some details that we are working out so I can't give you a complete answer at this time. Regards, Alex Johnson Invensys Process Systems Invensys Systems, Inc. 10707 Haddington Houston, TX 77043 713.722.2859 (voice) 713.722.2700 (switchboard) 713.932.0222 (fax) ajohnson@xxxxxxxxxxx -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Ashley Davey Sent: Thursday, January 13, 2005 4:03 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Reply to Neil Martin Hi Alex Same question - different angle! 1. When can we expect the AW70 Terminal Server to be at a revision level that will support CP270? (We are currently running at NT4.0 and Fox Version 6.3). 2. In a mixed CP40a, CP30a, CP60, AW51B, WP51F, environment, could the AW70 Terminal Server host ALL the CP's, WP's (51's & 70's) and the CSA. Thanks Ashley Davey Systems Engineer African Products (Pty) Ltd Gauteng Republic of South Africa Tel : +27 11 458 5342 Fax : +27 11 458 5343 Mobile: +27 83 4535169 >>> ajohnson@xxxxxxxxxxx 18:57:03 12 January 2005 >>> Re: V8.1 The target date for V8.1 is late summer 2005. The core elements are: 1) ATS 2) 100-Series I/O Support for FCP270 and ZCP270 3) Associated software changes Solaris users don't panic. The project is budgeted for the FY05/06, but won't complete by late summer 2005 so it will be post-V8.1. We need the ATS and 100-Series I/O support out yesterday. Nothing beyond this list should be expected at this point though it is possible that more might be included. Also, ALL quotations for V8.1 have to go through our commitment control process before we can make an offer. Re: In a mixed CP270, CP40a, CP60 environment, at 8.1, can we have the AW70 host the CP270s, and the remaining CPs still hosted by an AW51 station? Yes. The AW51 stations can remain on the Nodebus unchanged doing what they have always done. If the AW70 is hosting CPs, it will need to run CSA as well. Regards, Alex Johnson Invensys Process Systems Invensys Systems, Inc. 10707 Haddington Houston, TX 77043 713.722.2859 (voice) 713.722.2700 (switchboard) 713.932.0222 (fax) ajohnson@xxxxxxxxxxx ____________________________________________________________ ___________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave ____________________________________________________________ ___________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave ____________________________________________________________ ___________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave