Professional Documents
Culture Documents
XSCF Solaris Notes
XSCF Solaris Notes
net/~gkeen/notes_dir/Solarisnotes/xscf_console
#######################################################################
# Searchable Keywords: console terminal xscf XSCF extended system console
facility bmc IPMI ipmi ilom alom idrac
Getting started:
So you have a new M class box and you have a few questions.
- To find out what a command will do at thje xscf command line. XSCF help or
man intro
This will get you started with your new M class machine.
1. Turn the key on the front of the chassis to the "Service" position.
This is the position that doesn't have a little lock by it, pretty easy.
If you don't have a key this won't work.
2. At the login prompt type "default"
3. You will be prompted to turn the key to the "Locked" position, and hit
enter. Do so.
4. You will be told to leave the key in this position for at least 5
seconds, and then return it to the "Service" position and hit enter again.
- Whats is the default domain and how can see it's status ?
xscf> poweron -d 0
xscf> console -d 0
or
xscf> console -d 0 -f
the -f will force anyone currently on the console, off.
hostname % #.
The pound sign and a period is the default for switching between console
and the xscf prompt.
---------------------------------------------------
Setup networking and accounts
The networking you will configure here will be the for console access over
ssh and interdomain communication. NOT for any host that you are planning
on putting in any logical domain. This will be an interface, an xscf
interface
to be exact(which is usually the top board on the back of a M-series along
with the serial port. Looks like a ethernet port). It will be an interface
assessible from your local LAN. If your IP space is in 192.168.0.0/24. This
interface will have an IP in that space. NOT TO BE CONFUSED, with the
interdomain communications done over dscp IP space. That is something you
will just make up, but will be IP space that will NEVER be on your local lan.
NOTE:
- lan#0 = xscf#0-lan#0 These two options are interchangable
- In most networks the netmask option should be used to set the IP as
well as the default route ( some switch configs will not route improper
netmasks). See "Full example" below.
Short example:
with out the -m netmask option the default will be set. ie 255.255.0.0
interface :xscf#0-lan#0
status :up
IP address :172.23.14.113
netmask :255.255.255.0
route :-n 0.0.0.0 -m 255.255.255.0 -g 172.23.14.1
route :-n 0.0.0.0 -m 0.0.0.0 -g 192.168.1.1
interface :xscf#0-lan#1
status :down
IP address :
netmask :
route :
Continue? [y|n] :y
Please reset the XSCF by rebootxscf to apply the network settings.
Please confirm that the settings have been applied by executing
showhostname, shownetwork, showroute and shownameserver after rebooting
the XSCF.
XSCF> rebootxscf
The XSCF will be reset. Continue? [y|n] :y
----------------------------------
Removing a route
XSCF> setroute -c del -n 0.0.0.0 -m 0.0.0.0 -g 172.23.14.1 xscf#0-lan#0
----------------------------------
Adding a route
XSCF> setroute -c add -n 0.0.0.0 -m 255.255.255.0 172.23.14.1 xscf#0-lan#0
You can add another staic route by forming the same command
for the additional network, netmask and gateway.
interface :xscf#0-lan#1
status :down
IP address :
netmask :
route :
Continue? [y|n] :y
Please reset the XSCF by rebootxscf to apply the network settings.
Please confirm that the settings have been applied by executing
showhostname, shownetwork, showroute and shownameserver after rebooting
the XSCF.
XSCF> rebootxscf
The XSCF will be reset. Continue? [y|n] :y
----------------------------------
xscf> setdscp
( questions follow thos cmd concerning interdomain communications
choose an IP space not in your local lan). I liked 192.168.255.254/24
setssh -c enable -y
Now you should be ready to reset the xscf to make your changes take effect.
rebootxscf -y
After a few minutes you should be able to ping and ssh into the
xscf using the username and password you just created.
---------------------------------------------------
Collect and send xscf info to another host
---------------------------------------------------
List all or some of the xscf commands. Use the -h with each command to
deisplay options.
xscf> <tab> <tab>
Symptoms
XSCF> showdevices -d 00
Can't get device information from DomainID 0.
XSCF>
Since DSCP is used by FMA to transfer data between fmd on the domain and on
the SP, FMA logs and /var/adm/messages on the domain will log failures if
DSCP is not properly configured; filling up the fmd logs with MBs of
ereport.fm.fmd.module .
Please validate that each troubleshooting step below is true for your
environment.
The steps will provide instructions or a link to a document, for validating
the
step and taking corrective action as necessary. The steps are ordered in the
most appropriate sequence to isolate the issue and identify the proper
resolution.
Please do not skip a step.
Steps to Follow
Note: This procedure requires that the Solaris domain that cannot be
reached via DSCP service be rebooted in order to complete the resolution
steps.
1. Verify via Solaris that the required packages for the DSCP service are
installed on the Solaris domain
- pkginfo | grep SUNWdscp indicates the SUNWdscpr and SUNWdscpu packages
are installed on the domain
Reference : < Solution: 215610 > - Sun SPARC[R] Enterprise Mx000 Servers
(OPL)
packages for minimal Solaris[TM] Installation
....
sppp0: flags=10010008d1<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST,IPv4,FIXEDMTU>
mtu 1500 index
inet 192.168.224.3 --> 192.168.224.1 netmask ffffff00
ether 0
Example:
# svcs -l dscp
fmri svc:/platform/sun4u/dscp:default
enabled true
state online
next_state none
....
Note : The absence of the appropriate SUNWppp* packages, the absence of the
spp0 interface or the DSCP service disabled, as described above, will be
reported on the domain via ereport.fm.fmd.module in the 'fmdump -e'.
Further investigation using 'fmdump -V' will report the following signatures
:
and
To enable sckmd services, from the Solaris domain type svcadm enable sckmd
.
Example:
# svcs -l sckmd
fmri svc:/platform/sun4u/sckmd:default
enabled true
state online
next_state none
Note : The absence of the appropriate packages for sckmd or the sckmd
service disabled will be reported on the domain via ereport.fm.fmd.module
in the 'fmdump -e'. Further investigation using 'fmdump -V' will report the
following signature :
5. Verify on the problematic Solaris domain that the ipseckey dump command
returns security key information in addition to Dump succeeded for SA type
0.
If the ipseckey dump does not return any keys, raise an escalation to
assist
in the resolution..
Example:
# ipseckey dump
.....
Reboot (via shutdown, init 6, reboot, or some other orderly process) the
problematic Solaris domain that has been unable to use the DSCP interface.
6. Verify on the problematic domain that svcs -l dcs shows enabled true
and state online .
1.
Example:
# svcs -l dcs
fmri svc:/platform/sun4u/dcs:default
enabled true
state online
next_state none
7. Verify on the problematic domain that a ping from the domain to the
XSCF via the DSCP interface is working ( ping shows alive ):
IP Address Example:
....
sppp0:
flags=10010008d1<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST,IPv4,FIXEDMTU> mtu
1500 index
inet 192.168.224.3 --> 192.168.224.1 netmask ffffff00
ether 0
Ping Example:
# ping 192.168.224.1
192.168.224.1 is alive
At this point, if you have validated that each troubleshooting step above
is true for your environment, and the issue still exists, further
troubleshooting is required. For additional support contact Sun Support.
See, Well lets just see what Sun does with this ? Like ilom and xscf