01-10-2016
Quote:
Originally Posted by
DukeNuke2
The DSCP network is a hardwired connection between the XSCF and the Solaris domain. If you do an
ifconfig -a in Solaris you should be able to see the interface named
sppp0.
Read here for some more informations:
https://blogs.oracle.com/olympus/entry/dscp
The two XCSF network interface are for external connections to two different subnets for management. With one XSCF there is no automatic failover between network interfaces. The larger systems have two XSCF with combined 4 interfaces in two different subnets, which can automaticly failover if one XSCF fails.
So:
- M3000, M4000 and M5000 -> One XSCF
- M8000 and M9000 -> Two XSCF
and all the newer M10-1, M10-4 and M10-4S only have one XSCF (build in) again with two network interfaces and an internal DSCP network.
Hi DukeNuke2,
Thanks for the insight.
Can i confirm
Between XSCF to the external network, the interfaces are the actual "physical" interfaces that we can see on the physical box itself, whereas
Between XSCF to the domains, the interface are internally wired and is not "visible" to the naked eye.
Right?
===============
However, i am not so sure about the benefits of configuring DSCP (it seems like in the blog, the only purpose is to access the SP from domain as well as ntp, archiving purposes).
Without DSCP, i can still connect to XSCF from external network and i can still use it to poweron/off the domains (without the "internal network" ).
Having said that, it seems like XSCF can still access the domain (power on/off), even without DSCP.
So what are the real benefits of having a domain being able to reach a SP ? (beside NTP) ?
Maybe i am not seeing the full picture here..
Hope to hear from you soon.
Regards,
Noob
10 More Discussions You Might Find Interesting
1. Solaris
is there a way to force an error on an xscf much the same way you can with logger on solaris 10? i would like to test and make sure setarchiving is appropriately configured. however, i do not want to just pull a power source as the system is in production. anyway have any insight? showarchiving... (0 Replies)
Discussion started by: pupp
0 Replies
2. Solaris
While entering to service mode on XSCF i getting following error
XSCF> service
Account is not enabled for service mode.
What could be the reason for this ? (5 Replies)
Discussion started by: fugitive
5 Replies
3. Solaris
Hi all
A couple of new M5000 servers will be arriving soon and I need to work out how to configure the underlying domains.
It will come with 4 x CPUS, 32 Gb of memory, 4 x HD, 2 x IOtrays.
Reading the XSCF manual, I can configure the item into 2 domains, something about uni / quad xsb.... (9 Replies)
Discussion started by: sbk1972
9 Replies
4. IP Networking
Hello,
I'm having an issue with TCP sockets.
When the TCP connection is terminated on one end, TCP packet with RST flag set is being sent to the sender. All the packets sent so far were carrying the DSCP 'AF21' set by me. But packet with RST flag is carrying DSCP '0'.
Is this expected or... (0 Replies)
Discussion started by: Solace
0 Replies
5. Solaris
Hi, I've got an issue here: After I logon to the xscf prompt of this Sun M5000 and did 'XSCF> version -c xcp', the xscf prompt disappeared. I can't get it back and can't log out.
exit
rebootxscf
logout
#.
#>
#>
~#
~#
exit
sendbreak
exit
I tried to set the Mode Switch to the service... (3 Replies)
Discussion started by: aixlover
3 Replies
6. Solaris
Hi,
I've updated a few M3000s to new firmware without any hassle, but on one of them the following is happening:
XSCF> getflashimage -u wayner ftp://10.16.122.200/tftpboot/IKXCP1102.tar.gz
Error: insufficient free space
Any idea how to delete whatever old firmware is on there so I can... (7 Replies)
Discussion started by: cabaiste
7 Replies
7. Emergency UNIX and Linux Support
Hi All,
I have SPARC T4-4 connected with XSCF console. By mistake console user name is set to "root" instead of "sunadmin" (This is what we keep as standard). How can I change it ? Please help me
-> show /SP/users/root
/SP/users/root
Targets:
ssh
Properties:
role... (1 Reply)
Discussion started by: solaris_1977
1 Replies
8. Solaris
Trying to update my M5000 firmware. trying to mount my USB to upload firmware and getting the following message.
XSCF> getflashimage -v file:///media/usb_msd/FFXCP1115.tar.gz
Free space: 97MB
Making sure mount point is clear
umount: /media/usb_msd is not mounted (according to mtab)
Trying... (2 Replies)
Discussion started by: soupbone38
2 Replies
9. Solaris
Hi All,
I have an Oracle M4000 server with Solaris 10 OS. I have access to Solaris root prompt.
But I don't know the XSCF IP of this server.
Is there any way to display XSCF IP from Solaris OS? (2 Replies)
Discussion started by: byrusber
2 Replies
10. IP Networking
I took over an M5000 and have a jumper server with a nic to connect to the console IP of an M5000. access via ssh user@ip.
it was working fine, another person can connect remotely on the subnet, but when I ssh,it just hangs and then times out.
so my question is,
any ideas of what I might... (4 Replies)
Discussion started by: rrodgers
4 Replies
LEARN ABOUT PLAN9
smf_security
smf_security(5) Standards, Environments, and Macros smf_security(5)
NAME
smf_security - service management facility security behavior
DESCRIPTION
The configuration subsystem for the service management facility, smf(5), requires privilege to modify the configuration of a service. Priv-
ileges are granted to a user by associating the authorizations described below to the user through user_attr(4) and prof_attr(4). See
rbac(5).
The following authorization is used to manipulate services and service instances.
solaris.smf.modify Authorized to add, delete, or modify services, service instances, or their properties.
Property Group Authorizations
The smf(5) configuration subsystem associates properties with each service and service instance. Related properties are grouped. Groups may
represent an execution method, credential information, application data, or restarter state. The ability to create or modify property
groups can cause smf(5) components to perform actions that may require operating system privilege. Accordingly, the framework requires
appropriate authorization to manipulate property groups.
Each property group has a type corresponding to its purpose. The core property group types are method, dependency, application, and frame-
work. Additional property group types can be introduced, provided they conform to the extended naming convention in smf(5). The following
basic authorizations, however, apply only to the core property group types:
solaris.smf.modify.method
Authorized to change values or create, delete, or modify a property group of type method.
solaris.smf.modify.dependency
Authorized to change values or create, delete, or modify a property group of type dependency.
solaris.smf.modify.application
Authorized to change values or create, delete, or modify a property group of type application.
solaris.smf.modify.framework
Authorized to change values or create, delete, or modify a property group of type framework.
solaris.smf.modify
Authorized to add, delete, or modify services, service instances, or their properties.
Property group-specific authorization can be specified by properties contained in the property group.
modify_authorization Authorizations allow the addition, deletion, or modification of properties within the property group.
value_authorization Authorizations allow changing the values of any property of the property group except modify_authorization.
The above authorization properties are only used if they have type astring. If an instance property group does not have one of the proper-
ties, but the instance's service has a property group of the same name with the property, its values are used.
Service Action Authorization
Certain actions on service instances may result in service interruption or deactivation. These actions require an authorization to ensure
that any denial of service is a deliberate administrative action. Such actions include a request for execution of the refresh or restart
methods, or placement of a service instance in the maintenance or other non-operational state. The following authorization allows such
actions to be requested:
solaris.smf.manage Authorized to request restart, refresh, or other state modification of any service instance.
In addition, the general/action_authorization property can specify additional authorizations that permit service actions to be requested
for that service instance. The solaris.smf.manage authorization is required to modify this property.
Defined Rights Profiles
Two rights profiles are included that offer grouped authorizations for manipulating typical smf(5) operations.
Service Management
A service manager can manipulate any service in the repository in any way. It corresponds to the solaris.smf.manage and
solaris.smf.modify authorizations.
The service management profile is the minimum required to use the pkgadd(1M) or pkgrm(1M) commands to add or remove software packages
that contain an inventory of services in its service manifest.
Service Operator
A service operator has the ability to enable or disable any service instance on the system, as well as request that its restart or
refresh method be executed. It corresponds to the solaris.smf.manage and solaris.smf.modify.framework authorizations.
Sites can define additional rights profiles customized to their needs.
Remote Repository Modification
Remote repository servers may deny modification attempts due to additional privilege checks. See NOTES.
SEE ALSO
auths(1), profiles(1), pkgadd(1M), pkgrm(1M), prof_attr(4), user_attr(4), rbac(5), smf(5)
NOTES
The present version of smf(5) does not support remote repositories.
SunOS 5.10 2 Dec 04 smf_security(5)