74 lines
4.8 KiB
HTML
74 lines
4.8 KiB
HTML
|
<?xml version="1.0" encoding="utf-8"?>
|
||
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
||
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
||
|
<head>
|
||
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
<meta name="dc.language" scheme="rfc1766" content="en-us" />
|
||
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
<!-- US Government Users Restricted Rights -->
|
||
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
<meta name="dc.date" scheme="iso8601" content="2005-09-13" />
|
||
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
<meta name="security" content="public" />
|
||
|
<meta name="Robots" content="index,follow"/>
|
||
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
<title>Service Location Protocol (SLP) using multicast addressing</title>
|
||
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
||
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
||
|
</head>
|
||
|
<body>
|
||
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
||
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
||
|
<img src="delta.gif" alt="Start of change" /><img src="delta.gif" alt="Start of change" />
|
||
|
<a name="rzahqslpdisc"></a>
|
||
|
<h5 id="rzahqslpdisc">Service Location Protocol (SLP) using multicast addressing</h5>
|
||
|
<p>If you are not using the service processor host name or internet address
|
||
|
to discover the server on the network, then multicast addressing with Service
|
||
|
Location Protocol (SLP) is used. To configure SLP discovery, you must configure
|
||
|
your iSeries™ server. Do the following steps.</p>
|
||
|
<ol type="1">
|
||
|
<li>Using the procedure described in <a href="rzahqchangespprops.htm#rzahqchangespprops">Change service processor configuration properties</a>:
|
||
|
<ol type="a">
|
||
|
<li>Ensure that the <span class="bold">Use service processor connection to determine
|
||
|
remote system enclosure identity</span> option is not selected.</li>
|
||
|
<li>In the <span class="bold">Serial number</span> field, specify the serial number
|
||
|
of the stand-alone server enclosure or the IBM® BladeCenter™ chassis.</li></ol></li>
|
||
|
<li>Using the procedure described in <a href="rzahqchangeremotesysconfig.htm#rzahqchangeremotesysconfig">Change remote system configuration properties</a>,
|
||
|
ensure that the remote system identity is set correctly:
|
||
|
<ol type="a">
|
||
|
<li>For a stand-alone server, select the <span class="bold">Use enclosure identity
|
||
|
from the service processor configuration</span> option.</li>
|
||
|
<li>For a IBM BladeCenter blade, select the <span class="bold">Use the
|
||
|
following values</span> option and specify the blade serial number.</li></ol></li></ol>
|
||
|
<p>The service processor advertises itself with a SLP packet sent on the network
|
||
|
using multicast addressing. This packet includes attributes such as the serial
|
||
|
number, type, and model of the remote server. IBM Director receives this packet and saves
|
||
|
information about the server. The serial number from the service processor
|
||
|
configuration enclosure identifier or the remote system configuration remote
|
||
|
system identifier are mapped to the attributes learned from the SLP discovery
|
||
|
process to identify a specific remote server.</p>
|
||
|
<p>Advantages:</p>
|
||
|
<ul>
|
||
|
<li>Only the serial number, which can be obtained from a label on the server,
|
||
|
is needed to discover the remote server.</li>
|
||
|
<li>If the service processor obtains its IP address from a DHCP server and
|
||
|
the network supports IP multicasting, then the factory default settings of
|
||
|
the service processor can be used.</li></ul>
|
||
|
<p>Disadvantages:</p>
|
||
|
<ul>
|
||
|
<li>SLP is only supported by the Remote Supervisor Adapter II service processor
|
||
|
and the IBM BladeCenter Management Module service processor. It is
|
||
|
not supported by Baseboard Management Controller (BMC) service processors.</li>
|
||
|
<li>Routers and switches located between the service processor and the iSeries LAN adapter must be configured to support multicast addressing. If not
|
||
|
properly configured, routers will not propagate multicast packets. Consult
|
||
|
your router documentation to determine how to configure it to allow multicast
|
||
|
addressing. The Service Location Protocol uses IP address 239.255.255.253
|
||
|
and port number 427. This information may be required to configure routers
|
||
|
to support multicast SLP packets.</li></ul><img src="deltaend.gif" alt="End of change" /><img src="deltaend.gif" alt="End of change" />
|
||
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
</body>
|
||
|
</html>
|