Sponsored Content
Full Discussion: Jumpstart Question
Operating Systems Solaris Jumpstart Question Post 302734375 by DukeNuke2 on Thursday 22nd of November 2012 02:45:51 AM
Old 11-22-2012
yes you need the mac if you like to install a server via jumpstart... getting the mac depends on how you are connected to the remote server. to use jumpstart you need access to the servers console/obp. from there you'll find the mac address easily.

show-nets will give you the physical path to your networkdevices. use cd to navigate to the device and view all information about that device with .properties
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Jumpstart?

I have been asked to research Jumpstart and don't know where to begin! Any ideas would be much appreciated! Thanks! :-) (1 Reply)
Discussion started by: avana100
1 Replies

2. UNIX for Dummies Questions & Answers

JumpStart

Hi, Which sites have general information on JumpStart for Solaris 8? I would like to know more about boot server, installation server, and configuration server.... and all other good things about JumpStart....Thanks..:p Doo... (2 Replies)
Discussion started by: dookeobih
2 Replies

3. UNIX for Advanced & Expert Users

JUmpstart on a pc

HI. i was wondering if you can jumpstart using the solaris intel platform? please help thanks (3 Replies)
Discussion started by: souldier
3 Replies

4. UNIX for Advanced & Expert Users

Jumpstart

Hi, where can i find documention on how to create a jumpstart system? dori (2 Replies)
Discussion started by: dorilevy
2 Replies

5. Solaris

help with jumpstart

Hello all, I configured a jumpstart server ( the server is in the same subnet as the client) and gave boot net - install in the client. The client boots up shows the banner and then displays error: cant read disk label cant open disk label package and then goes to OK prompt. What... (1 Reply)
Discussion started by: Pratik Gharti
1 Replies

6. Solaris

Jumpstart Help

Hi Peeps, Created a jumpstart server for an unattened install and it works, but got 2 bugs in the config which I would like to work out: when you boot net install It still asks you to select a language and locale, after you do this it kicks of an unattended install. So my question is,... (5 Replies)
Discussion started by: callmebob
5 Replies

7. Solaris

Jumpstart basic question

Hello All, Do I really need to add the install server name in the /etc/hosts file? Why do we need to add? If I don't add it is not working. Isn't it only arp/rarp works here? I thought it works in mac address level. thanks in advance. (3 Replies)
Discussion started by: mokkan
3 Replies

8. Solaris

Jumpstart issue

Keep getting this message after system identification portion. Search complete. Discovering additional network configuration... Completing system identification... Starting remote procedure call (RPC) services:Assertion failed: *count <= max, file ns_dns_misc.c, line 189 Abort - core dumped... (0 Replies)
Discussion started by: soupbone38
0 Replies

9. Solaris

Jumpstart Question: Update Image?

Hi everyone, We have a T5240 and noticed we were having issues booting the system using our jumpstart server (it seems as though we don't have the correct drivers for the nxge NIC) We thought we needed to update our jumpstart server image 9/10 Solaris SPARC image. Now I'm still learning... (4 Replies)
Discussion started by: Keepcase
4 Replies

10. Solaris

Jumpstart from DVD

I want to have a bootable DVD that will perform a jumpstart install of Solaris 10 x86 I've mainly used JumpStart DVD (with Solaris flash archive) for x86 platform as a reference, and I used the sysidcfg, profile, rules, etc. from a working jumpstart server. For the life of me, though, I cannot... (1 Reply)
Discussion started by: jnojr
1 Replies
vblade-persist(8)					      System Manager's Manual						 vblade-persist(8)

NAME
vblade-persist - manage persistent exported ATA-over-Ethernet devices SYNOPSIS
vblade-persist ls [--no-header] vblade-persist setup shelf slot netif blockdev vblade-persist destroy shelf slot vblade-persist { start | stop | restart | auto | noauto } shelf slot vblade-persist { start | stop | restart | auto | noauto } all vblade-persist mac shelf slot { ls | clear } vblade-persist mac shelf slot { add | del } [ addr ... ] DESCRIPTION
The vblade-persist script is used to show and manipulate persistently-exported ATA-over-Ethernet devices. It has a simple subcommand syn- tax. Persistent AoE device exports can be configured to come up at boot time. For each running persistent AoE export, a symlink pointing to the backing device is created in /dev/etherd/, mirroring the devices seen by clients of the AoE device. MANAGEMENT SUBCOMMANDS
ls [--noheader] vblade-persist ls shows all existing persistent AoE exports. The columns of the output are, in order: AoE Shelf, AoE Slot, Network Inter- face, Backing Device, AutoStart, Status. AutoStart is either "auto" (start automatically at boot), or "noauto" (don't start automatically at boot). Status should be either "run" (running) or "down" (not running). The optional --no-header argument suppresses the header line. This may be convenient for machine-parseable output. setup shelf slot netif source vblade-persist setup creates a new persistent exported AoE block device. You must supply all four additional arguments. These are the same arguments supplied to vblade(8). You should specify source using an absolute path. New devices set up this way are noauto (not brought up automatically at boot) and down (not exported immediately). destroy shelf slot vblade-persist destroy halts any running exported AoE block device managed by vblade-persist and removes the service directory used to man- age it. start shelf slot stop shelf slot restart shelf slot These commands control a specific exported AoE device. Instead of specifying shelf and slot , you can also provide the special keyword all which will act on every exported AoE device. auto shelf slot noauto shelf slot These commands control whether a specific exported AoE device should be started automatically ( auto ) or not ( noauto ) at system boot time. Instead of specifying shelf and slot , you can also provide the special keyword all which will act on every exported AoE device. MAC-ADDRESS FILTERING You can use vblade-persist to restrict access to specific exports by MAC address, using the mac subcommand. mac shelf slot ls List all MAC addresses allowed to access the specified device, one per line. If the list is empty, no MAC address limits are imposed on this device. mac shelf slot clear Remove all MAC address filtering from the specified device. No MAC address limits will be imposed on this device. mac shelf slot add [ addr ... ] Add a MAC address (or more than one) to the list of allowed addresses for the specified device. Note that if there were no MAC addresses listed previously, this will enable MAC address filtering for the device. mac shelf slot del [ addr ... ] Remove a MAC address (or more than one) from the list of allowed addresses for the specific device. Note that if you remove all the MAC addresses from the list, this will disable MAC address filtering for the device. EXAMPLES
Set up /dev/sda2 as shelf 2, slot 3 on the network served by interface eth0. Make sure it starts automatically at boot, and start it up now: vblade-persist setup 2 3 eth0 /dev/sda2 vblade-persist auto 2 3 vblade-persist start 2 3 Limit that same export to MAC addresses aa:bb:cc:dd:ee:ff and 11:22:33:44:55:66: vblade-persist mac 2 3 add aa:bb:cc:dd:ee:ff 11:22:33:44:55:66 Remove all MAC address restrictions on the same export: vblade-persist mac 2 3 clear BUGS
You can't currently use the vblade-persist framework to export a device (or two) with the same shelf/slot identifier on two different net- work interfaces. DEPENDENCIES
The exports themselves are handled by vblade(8). Supervision of the exports and convenient management is enabled by runsv(8), from the runit suite. SEE ALSO
vblade(8), runsv(8) AUTHOR
Daniel Kahn Gillmor <dkg@fifthhorseman.net> vblade-persist 2007-11-11 vblade-persist(8)
All times are GMT -4. The time now is 09:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy