Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Technical Instruction Sure Solution 1004884.1 : How To Configure the "NET MGT" Port (ALOM (Advanced Lights Out Manager) Ethernet) Port
PreviouslyPublishedAs 206847 Description This Technical Instruction article describes how to configure the ALOM "NET MGT" port for use on a network. Steps to Follow How to configure the NET MGT (ALOM Ethernet) Port: 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 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 parameter value 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 The parameters that need to be configured to make the NET MGT port if_network true 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 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 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 Here is the usage page for the "scadm" command: #/usr/platform/`uname -i`/sbin/scadm help USAGE: scadm <command> [options] scadm - COMMANDS SUPPORTED scadm - COMMAND DETAILS 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 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 #ndd -get /dev/bge3 adv_autoneg_cap 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 #ifconfig bge3 plumb 129.148.173.1 129.148.173.27 up bge3: flags=1000851<UP,POINTOPOINT,RUNNING,MULTICAST,IPv4> mtu 1500 index 3 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. Product Sun Fire V240 Server Sun Fire V210 Server Internal Comments To generate traffic from the netmgt port, the ping command can be used. To enable ping on alom use the following commands.
sc> setsc sc_servicemode true ALOM, v210, v240, NET MGT Previously Published As 72110 Change History Date: 2011-05-24 User name: Dencho Kojucharov Action: Currency check Comments: audited by Entry-Level SPARC Content Lead Date: 2009-12-01 User Name: Anthony Rulli Action: updated Comment: currency check, audited by Anthony Rulli, Entry Level SPARC Content team Action: Update Canceled Comment: *** Restored Published Content *** Just fixed tag, not anything in doc. Version: 0 Date: 2005-09-23 User Name: 7058 Action: Update Started Comment: fixing missing tech group Version: 0 Date: 2005-06-27 User Name: 95826 Action: Update Canceled Attachments This solution has no attachment |
||||||||||||
|