The hardware set up is very basic. A standard network cable with RJ45 connectors needs to be plugged into the port on the I/O panel labeled “NET MGT” with the other end connected to the network.

Note: This interface is 10HDX so please ensure that the network hardware can negotiate to that speed or be forced to 10hdx. Some older hubs/switches are 100MB only, and are unable to establish link with the ALOM ethernet port.

There are multiple ways to configure the ALOM NET MGT port. You can establish a tip session into the ALOM SERIAL MGT port. The method assuming a tip connection to the ALOM serial port is functioning first.
1) Use the “showsc” command to show the current config.

sc> showsc
Advanced Lights Out Manager v1.0

parameter value
——— —–
if_network true
if_modem false
if_snmp false
if_emailalerts false
sys_autorestart xir
netsc_tpelinktest true
netsc_dhcp false
netsc_ipaddr 0.0.0.0
netsc_ipnetmask 255.255.255.0
netsc_ipgateway 0.0.0.0
mgt_mailhost
mgt_mailalert
sc_customerinfo
sc_escapechars #.
sc_powerondelay false
sc_clipasswdecho true
sc_cliprompt sc
sc_clitimeout 0
sc_clieventlevel 2
sys_eventlevel 2
ser_baudrate 9600
ser_parity none
ser_stopbits 1
ser_data 8
netsc_enetaddr 00:03:ba:29:5e:34
sys_hostname
sys_enetaddr 00:03:ba:29:5e:2b
sc>

If there are prior configuration settings that need to kept intact, then proceed from this point. If unsure of what has been set and want to go back to the default settings before configuring, then issue a “setdefaults” command.

sc> setdefaults
Are you sure you want to reset the SC configuration [y/n]? y

The parameters that need to be configured to make the NET MGT port
functional are:

if_network true
netsc_tpelinktest true
netsc_dhcp false
netsc_ipaddr 0.0.0.0
netsc_ipnetmask 255.255.255.0
netsc_ipgateway 0.0.0.0

2a) Use the “setsc”command to set the needed parameters.

sc> setsc if_network true

This command enables the NET MGT port.

sc> setsc netsc_tpelinktest true

This command enable/disables the link integrity test. Please check with your network admin to see if the network hardware supports this 10BaseT standard.

Note: When set to true, in the absence of network traffic, a 100ns heartbeat
pulse is sent every 16ms within a range of +/- 8 ms. A link fail condition
is entered if the receiver does not receive a packet or a link test pulse
within 50-150 ms. The link fail condition disables the data transmit, data
receive, and loopback functions. The link test pulses continue to be
transmitted and received during the link failure. The link is reestablished
when two consecutive link test pulses or a single data packet have been
received.

sc> setsc netsc_dhcp false

This command should be set to false unless you want DHCP to obtain your network configuration, which is not part of this example.

sc> setsc netsc_ipaddr 129.148.173.27

This command sets the the unique IP address for the NET MGT port, please see the network admin to get this address.

sc> setsc netsc_ipnetmask 255.255.255.0

This command sets the netmask and will depend on the class of network, please see the network admin to get this value.

sc> setsc netsc_ipgateway 129.148.173.253

This command sets the IP address of the gateway or router, please see the network admin to get this value.

If a change is made to the “if_network” or “netsc_tpelinktest” variable, it will not change until after the next ALOM reset(sc>resetsc -y) but is otherwise not needed.

Now verify the settings with the “shownetwork” command.

sc> shownetwork
SC network configuration is:
IP Address: 129.148.173.27
Gateway address: 129.148.173.253
Netmask: 255.255.255.0
Ethernet address: 00:03:ba:29:5e:34

The ALOM NET MGT port should now be functional. If at this point if unable to telnet/ping the ip address of the ALOM, see section 3 for suggestions to verify the port.

2b) The next steps will show how to do the same configuration but with the
Solaris based “scadm” command.

Here is the usage page for the “scadm” command:

#/usr/platform/`uname -i`/sbin/scadm help

USAGE: scadm [options]
For a list of commands, type “scadm help”

scadm – COMMANDS SUPPORTED
help, date, set, show, resetrsc, download, send_event, modem_setup,
useradd, userdel, usershow, userpassword, userperm, shownetwork,
loghistory, version

scadm – COMMAND DETAILS
scadm help => this message
scadm date [-s] | [[mmdd]HHMM | mmddHHMM[cc]yy][.SS] => print or set date
scadm set => set variable to value
scadm show [variable] => show variable(s)
scadm resetrsc [-s] => reset SC (-s soft reset)
scadm download [boot] => program firmware or [boot] monitor
scadm send_event [-c] “message” => send message as event (-c CRITICAL)
scadm modem_setup => connect to modem port
scadm useradd => add SC user account
scadm userdel => delete SC user account
scadm usershow [username] => show user details
scadm userpassword => set user password
scadm userperm [cuar] => set user permissions
scadm shownetwork => show network configuration
scadm loghistory => show SC event log
scadm version [-v] => show SC version (-v verbose)

Use the “scadm set” command to set the same variables as described above.

#scadm set if_network true

#scadm set netsc_tpelinktest true

#scadm set netsc_dhcp false

#scadm set netsc_ipaddr 129.148.173.27

#scadm set netsc_ipnetmask 255.255.255.0

#scadm set netsc_ipgateway 129.148.173.253

#scadm shownetwork
IP Address: 129.148.173.27
Gateway address: 129.148.173.253
Netmask: 255.255.255.0
Ethernet address: 00:03:ba:29:5e:34

NOTE: There is also an interactive configuration process possible through the use of the “setupsc” command, which is beyond the scope of this document.

3) Link verification

If there are issues connecting into the NET MGT port try moving the rj45 connector from the switch/hub port to one of the bge (a cluster transport adapter) interfaces. When the connection is made the link led on both the bge and NET MGT port should light.

NOTE: When the bge is setup for autonegotiation it will connect up at 10HDX and
negotiate MDI/MDX. To verify the bge is setup for autoneg run the following:

#ndd -get /dev/bge3 adv_autoneg_cap
1

1=autoneg enabled 0=no autoneg

Next configure the bge as a point to point connection to avoid routing issues.

From the above example, the Alom IP is 129.148.173.27, then config bge3 for
an ip on the same subnet.

#ifconfig bge3 plumb 129.148.173.1 129.148.173.27 up

bge3: flags=1000851mtu 1500 index 3
inet 129.148.173.1 –> 129.148.173.27 netmask ffff0000
ether 0:3:ba:29:37:96

Next, run snoop (snoop -d bge3), and telnet from the system to the ALOM IP addr. Observe the telnet traffic in the snoop.

1 5.58497 129.148.173.1 -> (broadcast) ARP C Who is 129.148.173.27,
129.148.173.27 ?
2 0.00079 129.148.173.27 -> 129.148.173.1 ARP R 129.148.173.27,
129.148.173.27 is 0:3:ba:29:37:9c
3 0.00017 129.148.173.1 -> 129.148.173.27 TELNET C port=32818
4 0.00149 129.148.173.27 -> 129.148.173.1 TELNET R port=32818
5 0.00009 129.148.173.1 -> 129.148.173.27 TELNET C port=32818
6 0.00039 129.148.173.1 -> 129.148.173.27 TELNET C port=32818
7 0.00238 129.148.173.27 -> 129.148.173.1 TELNET R port=32818
8 0.00005 129.148.173.1 -> 129.148.173.27 TELNET C port=32818
If you do not see led lights on the bge or NET MGT port then try another cable. If there is a link but no response in snoop check the configuration or suspect a port issue