planarmap – tells you what is where

code:


lsdev -Cc adapter | grep "^ent" | while read A B
do
lscfg -vl $A
done | grep Network | cut -c 37- | tr 'A-Z' 'a-z' | while read MAC
        do
        echo $MAC | cut -c 1-4 | read MAC1
        echo $MAC | cut -c 5-8 | read MAC2
        echo $MAC | cut -c 9-12 | read MAC3
        echo $MAC1.$MAC2.$MAC3
        done

example:

$ planarmap
001.DQDGMFC------------------------------------------
---pci25---------------------------------------------
        pci29 sisscsia0 PCI-X Ultra320 SCSI Adapter
T7      pci30 ent0 2-Port 10/100/1000 Base-TX PCI-X Adapter (14108902)
T6      pci30 ent1 2-Port 10/100/1000 Base-TX PCI-X Adapter (14108902)
---pci26---------------------------------------------
C3-T1   pci31 fcs0 FC Adapter
C4-T1   pci32 fcs1 FC Adapter
---pci27---------------------------------------------
        pci33 sisscsia1 PCI-X Ultra320 SCSI Adapter

Don’t panic if your boot hangs on led 538

538 The configuration manager is going to invoke a configuration method.

Tonight, we had to reboot one of our servers after an old version of powerpath freaked out while discovering LUNs. The LUNs were discovered again on boot and we set on 538 for about 15 minutes. When you are used to the whole LPAR coming up in less then 10 minutes, this can be scary, but just as we were about to make other plans, the led moved on and cfgmgr finished.

When trying to bring the same LUNs online in normal mode, the server would hang on 538 forever for some reason, I suspect it is because we are at 5200-08 and powerpath 3.0.4.0, really old stuff.

Of course something similar happens when installing upgrades, it seems to hang forever.

If the network config is wrong, it will get past config manager and hang on NSF or something like that. In this case, I usually boot up with an alternate profile that doesn’t have any network adapters, then from the console I just rmdev everything and then reboot back with my old profile. Works every time.

We saw this again later and it took more like 40 minutes but then came up.