Tag Archives: Hello Everyone

Linux

AIX Production Readiness Checklist (PRC) – check list

Leave a comment

By System Admin 77

Hello Everyone,

Can anyone please provide me the checklist for validating our newly built AIX LPARs. AIX is new in our environment. So I’m looking for a reference document or checklist to verify new LPARs.

I believe most of the companies does have some kind of check list to verify. please provide me any kind of general reference checklist. (*i know it depends on environment, but looking for a generalized doc)

I am trying put the things together, so that it will be useful for new builds.

Thanks,

…read more

Source: FULL ARTICLE at The UNIX and Linux Forums

Linux

NTP in AIX

Leave a comment

By System Admin 77

Hello Everyone,

I got a question regarding NTP (Network time protocal) in AIX.

AIX is new in our environment. so’ we do not have any time server that is useful for new LPARs.
so’ i tried using IBM steps to configure NTP server on one of our test/lab LPARs.

I used the below link to make it work. But it did not working.

IBM Configuring NTP on AIX 5L – United States

ON one of AIX LPAR –> to make it as NTP server
===============================================

[root@LPAR1]> tail -7 /etc/ntp.conf
# Broadcast client, no authentication.
#
#broadcastclient
server 127.127.1.0
driftfile /etc/ntp.drift
tracefile /etc/ntp.trace
—

[root@LPAR1]/>lssrc -ls xntpd
Program name: /usr/sbin/xntpd
Version: 3
Leap indicator: 00 (No leap second today.)
Sys peer: 127.127.1.0
Sys stratum: 4
Sys precision: -18
Debug/Tracing: DISABLED
Root distance: 0.000000
Root dispersion: 0.010010
Reference ID: 127.127.1.0
Reference time: d597cdae.de0e3000 Mon, Jul 22 2013 11:26:38.867
Broadcast delay: 0.003906 (sec)
Auth delay: 0.000122 (sec)
System flags: pll monitor filegen
System uptime: 1576 (sec)
Clock stability: 0.000000 (sec)
Clock frequency: 0.000000 (sec)
Peer: 127.127.1.0
flags: (configured)(refclock)(sys peer)
stratum: 3, version: 3
our mode: client, his mode: server
Subsystem Group PID Status
xntpd tcpip 8585346 active

another LPAR (Client)

=====================

[root@LPAR2]/>ntpdate -d 127.127.1.0
22 Jul 11:24:58 ntpdate[9437240]: 3.4y
transmit(127.127.1.0)
transmit(127.127.1.0)
transmit(127.127.1.0)
transmit(127.127.1.0)
transmit(127.127.1.0)
server 127.127.1.0, port 123
stratum 0, precision 0, leap 00, trust 000
refid [0.0.0.0], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time: 00000000.00000000 Thu, Feb 7 2036 1:28:16.000
originate timestamp: 00000000.00000000 Thu, Feb 7 2036 1:28:16.000
transmit timestamp: d597cd4d.f8c23000 Mon, Jul 22 2013 11:25:01.971
filter delay: 0.00000 0.00000 0.00000 0.00000
0.00000 0.00000 0.00000 0.00000
filter offset: 0.000000 0.000000 0.000000 0.000000
0.000000 0.000000 0.000000 0.000000
delay 0.00000, dispersion 64.00000
offset 0.000000

22 Jul 11:25:02 ntpdate[9437240]: no server suitable for synchronization found<br …read more

Source: FULL ARTICLE at The UNIX and Linux Forums

Do it yourself

200 amp service upgrade questions

Leave a comment

By timjsowards

Hello Everyone, I have a few questions that I would like some help with. Im planning on upgrading to a 200 Amp service within the next year but it will be a piece by piece upgrade. What I would like to do is replace my load center that is currently in my basement first. I am knowledgeable of electricity and have done a lot of home repairs and so forth but this would be my first panel replacement so my first question is 1. Can I purchase a 200 amp panel with a main breaker and for the time being replace the 200 amp breaker with a 125 amp breaker which is what I currently have?

2. I know that my feed line from the drop will need replaced and I plan on having an electrician replace from the drop to the top end of the meter but can I replace the lower from the meter to the panel with the upgraded 2/0 copper or 4/0 aluminum prior to replacing the meter box?

3. I have an older house built in the late 60’s and most of the wire in the house is the older wire, its wrapped in a paper material but inside the paper the 3 wires are in vinyl. Is there any unforeseen issue when upgrading this to a 200 amp service? I would think not being that the breaker size on each wire will remain the same and the only difference is that I’ll be able to add additional wiring in after the upgrade has been complete but just to make sure I wanted to ask.

4. Does the drop wire have to be replaced from the pole to the house? The reason I ask is that ive been told yes and no but my neighbor just upgraded to 200 amp service about a month ago and they replaced hers, this added a lot of cost and total was over $3500.00 for the total upgrade.

Again Ive done electrical work but not on this scale, I do plan on removing the meter prior to the panel replacement and am just looking to clear some things up. Thanks for the help.

From: http://www.doityourself.com/forum/electrical-c-d-c/493051-200-amp-service-upgrade-questions.html

Linux

Message in /var/adm

Leave a comment

By alexelchivo

Good Morning..

Hello Everyone, I’ve been receiving this message in /Var/adm 2 days ago, I’m a new administrator for Solaris 10 and don’t know what it means..

Thanks for your help

Here is the full message:

Feb 18 03:30:45 sun3000 ebus: [ID 521012 kern.info] se0 at ebus0: offset 1,400000
Feb 18 03:30:45 sun3000 genunix: [ID 936769 kern.info] se0 is /pci@9,700000/ebus@1/serial@1,400000
Feb 18 03:30:46 sun3000 ebus: [ID 521012 kern.info] gpio_873170 at ebus0: offset 1,300600
Feb 18 03:30:46 sun3000 genunix: [ID 936769 kern.info] gpio_873170 is /pci@9,700000/ebus@1/gpio@1,300600
Feb 18 03:30:46 sun3000 ebus: [ID 521012 kern.info] su0 at ebus0: offset 1,3062f8
Feb 18 03:30:46 sun3000 genunix: [ID 936769 kern.info] su0 is /pci@9,700000/ebus@1/rsc-control@1,3062f8
Feb 18 03:30:46 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: fssnap0
Feb 18 03:30:46 sun3000 genunix: [ID 936769 kern.info] fssnap0 is /pseudo/fssnap@0
Feb 18 03:30:46 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: ramdisk1024
Feb 18 03:30:46 sun3000 genunix: [ID 936769 kern.info] ramdisk1024 is /pseudo/ramdisk@1024
Feb 18 03:30:46 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: winlock0
Feb 18 03:30:46 sun3000 genunix: [ID 936769 kern.info] winlock0 is /pseudo/winlock@0
Feb 18 03:30:46 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: lofi0
Feb 18 03:30:46 sun3000 genunix: [ID 936769 kern.info] lofi0 is /pseudo/lofi@0
Feb 18 03:30:46 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: trapstat0
Feb 18 03:30:46 sun3000 genunix: [ID 936769 kern.info] trapstat0 is /pseudo/trapstat@0
Feb 18 03:30:46 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: mem_cache0
Feb 18 03:30:46 sun3000 genunix: [ID 936769 kern.info] mem_cache0 is /pseudo/mem_cache@0
Feb 18 03:30:46 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: lockstat0
Feb 18 03:30:46 sun3000 genunix: [ID 936769 kern.info] lockstat0 is /pseudo/lockstat@0
Feb 18 03:30:46 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: tod0
Feb 18 03:30:46 sun3000 genunix: [ID 936769 kern.info] tod0 is /pseudo/tod@0
Feb 18 03:30:47 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: rsm0
Feb 18 03:30:47 sun3000 genunix: [ID 936769 kern.info] rsm0 is /pseudo/rsm@0
Feb 18 03:30:47 sun3000 ebus: [ID 521012 kern.info] su1 at ebus0: offset 1,3083f8
Feb 18 03:30:47 sun3000 genunix: [ID 936769 kern.info] su1 is /pci@9,700000/ebus@1/rsc-console@1,3083f8
Feb 18 03:30:47 sun3000 scsi: [ID 193665 kern.info] st20 at qus2: target 5 lun 0
Feb 18 03:30:47 sun3000 genunix: [ID 936769 kern.info] st20 is /pci@9,700000/pci@3/scsi@4/st@5,0
Feb 18 03:30:47 sun3000 scsi: [ID 365881 kern.info] /pci@9,700000/pci@3/scsi@4/st@5,0 (st20):
Feb 18 03:30:47 sun3000
Feb 18 03:30:47 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: fbt0
Feb 18 03:30:47 sun3000 genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt@0
Feb 18 03:30:47 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: profile0
Feb 18 03:30:47 sun3000 genunix: [ID 936769 kern.info] profile0 is /pseudo/profile@0
Feb 18 03:30:47 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: systrace0
Feb 18 03:30:47 sun3000 genunix: [ID 936769 kern.info] systrace0 is /pseudo/systrace@0
Feb 18 03:30:47 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: sdt0
Feb 18 03:30:47 sun3000 genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt@0
Feb 18 03:30:47 sun3000 scsi: [ID 799468 kern.info] ses0 at fp5: name w50800200001e1ba1,0, bus address dc
Feb 18 03:30:47 sun3000 genunix: [ID 936769 kern.info] ses0 is /pci@8,600000/SUNW,qlc@2/fp@0,0/ses@w50800200001e1ba1,0
Feb 18 03:30:56 sun3000 fcip: [ID 842839 kern.warning] WARNING: fcip(9): port attach failed<br ...read more
Source: FULL ARTICLE at The UNIX and Linux Forums