Change ucs FI system name

Is it possible to change the already deployed system name on a paired cluster of 6248up fi's? Firmware is 2.2 3b...
Thanks

According to the config guide, this is possible.
F241-POD-1-UCS-1-A# scope system
F241-POD-1-UCS-1-A /system # set
F241-POD-1-UCS-1-A /system # set name niles
Warning: System name modification changes FC zone name and redeploys them non-disruptively
F241-POD-1-UCS-1-A /system* # commit-buffer
F241-POD-1-UCS-1-A /system #
niles-A /system #
niles-A /system # set name F241-POD-1-UCS-1
Warning: System name modification changes FC zone name and redeploys them non-disruptively
niles-A /system* # commit-buffer
F241-POD-1-UCS-1-A /system #
http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/cli/config/guide/2-2/b_UCSM_CLI_Configuration_Guide_2_2/b_UCSM_CLI_Configuration_Guide_2_2_chapter_0101.html#task_4F5115C9511C4870A30B890BF0EEFC78
HTH,
/niles

Similar Messages

JDBC to Idoc scenario - change of logical system name

Hi,
I have a JDBC to idoc scenario that worked. Now i had to change the logical system name from my sender system from ABC_123 into ABC123 in the SLD (Business System - Integration - Logical System name). I did so and also refreshed my Cache.
Afterwards I started the process, but it failed in the Receiver system. The idoc is correct expect of the partner name. My receiver system expect ABC123 - as I changed in the SLD - but PI send ABC_123.
If io look in SXI_CACHE - Services my Business System still got the "old" name (ABC_123).
Did i miss something resp. how can i load the current configuration from SLD?
Thanks in advance
Michael

Hi Michael,
Again Import the changed logical system in the Integration directory of you PI system.
And check the scenario (Sender Agreement, Receiver agreement ) what system they are reflecting.
If they are showing old system then you have to replace the business system in all the scenario.
Edited by: Rajhans Abhay on Jan 7, 2010 3:14 PM

RSA1 - Source system connection : Change in logical system name

Dear friends,
Can you please tell me how can i change the logical system name for a source system connection.
There is no change in source system & source system connection check works well, just we have decided that from current logical system name SID_100 should be changed to SIDCLNT100.
Can i do this by running BDLS in BW for RSBASIDOC table from SID_100 to SIDCLNT100 ?
thanks
ashish

HI Sunny,
This is not the same problem, may be similar though..i am not getting a way.
let me describe u in a bit more details.
Currently, we have a working source system connection to a system SID_CLT. there is no change in source system.
now, can i change this system connection technical name from SID_CLT to SIDCLNT*** ..
thanks
ashish

Changing Default logical system names of a model.

Hi
    How could i change the
     Default logical system name for model instances:
     Default logical syatem name for RFC metadata:
    values for existing model? without recreating the model.
     Thanx

Hi shah kond,
you can change rfc destinations of model in 2 differnet ways.
firs one: right clcik on project
          from the context menu select propeties
          it will open a dialogbox from that select dynpro references then click on jco references tab
by using add and remove buttons u can add and remove joc destnations
2.expand ur model class double click output class.now seelct properties view.there u can change the jco destination
hope this will use ful for u
Regards
Naidu

Change of logical system name

Dear Experts,
I have following situation in ECC 6 EHP4 system:
a system copy of PRD system was peformed on QAS. POst system copy BDLS was NOT run, and logical system of QAS client was maintained manually.
Now client 300 in QAS has logical system as QASCLNT300 (after copy it was PRDCLNT300). The problem is that many accounting documents still point to PRDCLNT300 and hence can not be viewed now since log sys is QASCLNT300 now.
I can not run bdls now bcoz for BDLS target logical system should be new. Also for last few months new accounting docs has been generated for QASCLNT300.
Is there any way around? pls suggest
-Thanks,
Richa

This is a situation , where you cannot run BDLS now and you face issues with accounting docs .
As far as I feel , you will have have to redo the system copy and run BDLS again. The logical system name should never be maintained manually in SCC4.
Edited by: Ratnajit Dey on Jan 2, 2012 12:16 PM

Is it possible to change the Logical System name in ID

Hi,
I am doing a file to Idoc scenario. My requirement is to overwrite the logical system name, which is set in SLD for sender (system). Is it possible to overwrite it in ID or in mapping somewhere.
Thanks,
Dehra

Hi Dehra,
Go through the below help file of SLD. It will give you information regarding logical name as well:
<a href="http://xiserver:50100/sld/doc/sld.pdf">http://xiserver:50100/sld/doc/sld.pdf</a>
Regards,
Subhasha

How to change the SystemID (system name) of the HP StoreOnce Virtual Storage Appliance (VSA)

I can't seem to find a darned way to post a question regarding the HP StoreOnce Virtual Storage Appliance. I want to change the name (SystemID) of a StoreOnce VSA that has already been deployed. The web interface has NO way of changing any value.
The command line interface (through ssh) doesn't seem to have any way to change the SystemID value in any way. I want to change this value so that when I have it join the Active Directory domain it is a meaningful name, and NOT the serial number of the VSA.
I KNOW that I am asking in the wrong place, but I don't know what the proper place is to ask this question.
Unless you have either of the below keep your comments to yourself:
1) a real suggestion on where to post this
2) an answer to my question

Bill, welcome to the forum.
I believe you will receive the help that you need if you start a thread here.
Please click the "Thumbs up + button" if I have helped you and click "Accept as Solution" if your problem is solved.
Signature:
HP TouchPad - 1.2 GHz; 1 GB memory; 32 GB storage; WebOS/CyanogenMod 11(Kit Kat)
HP 10 Plus; Android-Kit Kat; 1.0 GHz Allwinner A31 ARM Cortex A7 Quad Core Processor ; 2GB RAM Memory Long: 2 GB DDR3L SDRAM (1600MHz); 16GB disable eMMC 16GB v4.51
HP Omen; i7-4710QH; 8 GB memory; 256 GB San Disk SSD; Win 8.1
HP Photosmart 7520 AIO
++++++++++++++++++
**Click the Thumbs Up+ to say 'Thanks' and the 'Accept as Solution' if I have solved your problem.**
Intelligence is God given; Wisdom is the sum of our mistakes!
I am not an HP employee.

How to change or rename the logical system name T90CLNT090 IN BI 7

HI Expert's,
i am really digging for the solution of changing or renaming the logical system name technical name T90CLNT090.
in our company we are using ecc5.0 with bi 3.5 and ecc6 with bi 7. In BW 3.5 having a connection with R/3 and the technical name of the myself bw source system(logical system) is T90CLNT090.
In bi 7 also the logical system name is same as T90CLNT090. Because of the same system name(Logical name) it is not active in BI7 and also it's giving error when i am activating the DSO Object as Transfer structure prefix for source system T90CLNT090 is not defined.
because of this i am not able to create the source system between r/3 also.
so how to change this source system name for T90CLNT090.
regards
harikrishna N

Hi,
Pls follow this OSS note : 325525.
Note 325525 - Copying and renaming systems in a BW environment
Summary
Symptom WARNING: THIS NOTE HAS BEEN REPLACED. FOR MORE CURRENT AND MORE COMPREHENSIVE INFORMATION SEE NEW NOTE 886102.
You want to copy and or rename one or more systems (database or client copy). One or more of the systems is a BW system or is connected to a BW system.
Caution: This note only deals with problems that occur in the BW source system connections. Other problems that occur in the BW environment (indexes) are NOT dealt with. See URL http://www.service.sap.com/bw --> Services & Implementation --> System copy & Migration.
Other terms BW, source system, OLTP, database copy, client copy, system infrastructure, transport system, connections, RFC connection, trfc, transfer structure, IDoc, ALE customizing, logical system name, system changeability, renaming systems, system copy
Solution Several scenarios are possible in this environment. Find the scenario relevant to your situation below and execute the steps listed or read the note(s) specified:
Scenario 1) You do not want to copy a system but only want to rename one (changing a logical system name).
           Solution scenario 1): Execute Transaction BDLS both in the client to be renamed and in the connected BWs or BW source systems. To do this, see Notes 121163 and 369758.
           Check the RFC destinations in all connected BWs/BW source systems as described in Note 524554.
           Reactivate all partner agreements that carry the new logical system name after renaming.
Scenario 2) You want to copy the entire system infrastructure connected by the BW source system connections (that means the entire system group) by a database copy. SAP recommends this procedure for copying systems.
           Solution scenario 2):
If you want to rename one or more of the copied systems, then execute Transaction BDLS both in the client you wish to rename and in all the connected BW and BW source systems. See Note 121163.
                    Make sure that an RFC destination exists with the new logical name in every connected BW or BW source system.
                    Reactivate all partner agreements that carry the new logical system name after renaming.
Change the hosts in the appropriate RFC destinations so that they refer to the correct computer. For this, see Note 524554.
Scenario 3) You want to copy a single BW system of the group by database copy.
Scenario 3)a) You only want to exchange the hardware of your system but do not want to rename the system.
                     Solution scenario 3)a): You do not need to execute follow-up work regarding the system connections, except for adjusting the IP address in the RFC destinations of the connected system.
Scenario 3)b) You want to keep the original system of the copy so that you have two systems after copying.
                     Solution scenario 3)b): See Note 184754.
Scenario 4) You want to copy a single source system of the group by database copy.
Scenario 4)a) You only want to exchange the hardware of your system but do not want to rename the system.
                     Solution scenario 4)a): You do not need to execute follow-up work regarding the system connections, except for adjusting the IP address in the RFC destinations of the connected system.
Scenario 4)b) You want to keep the original system of the copy so that you have two systems after copying.
           Solution scenario 4)b): See Note 184322.
Scenario 5) You want to import a client copy in a source system.
           Solution scenario 5): See Note 325470.
Thanks & Regards,
Suchitra.V

Change Receiving System Name in BD64

Hi folks,
               We have our production instance and QA instance; we have copied all data from Production to QA ENV (Client Copy). After that when I login in to QA system I saw in BD64 all the system pointing to receiving production system. I ran BDLS ( transaction ) which convert production logical system name to QA logical system name in tables and as well as in SCC4 transaction.
I again went to BD64 and I noticed after running BDLS my production system name replace to QA system name. But Receiving systems names are still pointing to production systems. I know that BDLS just change the sending system logical name not receiving.
My question is that how I can change or modify the receiving system production names to testing name. Is there any way or program?
I try to change the receiving system name but its not letting me change. You guys have any idea how to change the receiving system production name to test name.
I dont want to create all distribution model names with test systems as I have 30 distribution models and client copy is keep on going after every 1 or 2 months.
Please help me in this regards.
Thanks

The OSS notes just tell about the BDLS. I already done with BDLS Scenarios is like that say we have one distribution model name in Production
Model name = ZXYZ
(Sender system) Production system name = PRD_123
(Receiving production System in UK)      = PRD_UK
These above are the setting for Production client.
We copy data from Production to Quality, so its copy all the data and Distribution name in QA ENV
So now my QA looks like
Model name = ZXYZ
Sender system) Production system name = PRD_123
Receiving production System in UK)      = PRD_UK
After that I ran T-code BDLS and give logical system name = QA_123, then when I go back to BD64 the model is looks like following
Model name = ZXYZ
Sender system) Production system name = QA_123
Receiving production System in UK)      = <b>PRD_UK </b>
But PRD_UK isnt change because its the production system for receiving one , so Now I need to modify <b>PRD_UK to QA_UK in BD64</b> , How Ill do it ?
I am trying to change receiving system but it doesnt allowing me.
I hope, now I made my self more clear.
Thanks in Advanced.
Bye
Message was edited by: Suleman Javed

SLD Logical System Name Changes not taking effect in IDOC

All -
I've had to change a logical system name in the SLD, everything appears to be okay but new Idocs are still posting with the old LS name - any suggestions as to where to look for the old name would be most appreciated.
Thanks!

Hi Dennis,
After changing the logical system name in SLD have you done "Compare with SLD" from Service --> "Adapter-Specific Identifiers" for Business system in Integration Directory?
- Pinkle

Change logical system names after system copy

Hi!
We successfully installed SAP ECC 6.0 system as system copy.
All the logical system names of old system have been copied to new system.
Question
What is the approach to change the logical system names for new SAP system?
a) just via tcode SCC4
b) via BDLS
c) other tcodes, reports
Thank you very much!
regards
Jürgen

Hi,
Go though the system copy guide.
http://service.sap.com/instguides
After system copy,
If you need to change logical system names in the system that results from the copy, change the logical system names as described in SAP Notes 103228 and 544509.
https://service.sap.com/sap/support/notes/103228
https://service.sap.com/sap/support/notes/544509
Before running BDLS to change the logical system name, you have to define the correct logical system name in the new copied system. in tcode BD54.
- while running BDLS, execute in background.
Regards,
Debasis.

Scm:Logical system Name is changed. cannot access BW system.

Hi,
plz help me to solve thi problem.
SCM : Logical system Name is changed. cannot access BW system. system throw an error "Logical System has changed".

Hi Raj,
We can create the Logical system name in SALE or BD54 and we can assign the same logical system name in SCC4 for that particular Client.
If you want to change the logical system name after a client copy or System copy. Use BDLS.
Thanks,
Pundari

Logical system name to be updated while client copy--URGENT HELP REQUIRED

Hello All,
I have a query regarding the "Logical System name" updation during Client copy.
When we make a client copy(SRM Masters) for the Production system(SRM),the Old Logical system name for backend(which is attached to the SRM masters) gets copied to the new Client (Copy) which needs to be updated.
There is a std transaction BDLS through whcih w e can change the current Logical system name to a new one but this seems to work fine for System copy but not for Client copy.
So when i make a client copy of SRM masters for Production system,is there any other std way wherein i can change the "Logical system name " for the backend or do i have to write a CUSTOM program wherein entries for the Backend Logical system name in tables like CRMMLSGUID will be updated with the new Logical system name?
Any help on this is appreciated.
Thanks & Regards,
Disha.

Disha,
Yes, I did it twice and it worked fine.
The R/3 GUID is sent by the OLTP system (R/3) in R/3 message header.
SRM checks this GUID in CRMMLSGUID table.
If is not the same one, then replication process fails.
The only solution I found was to delete this entry. It is automatically recreated with the new GUID with the next replication, with FM CRMT_OLTP_LOGSYS1, called in BAPI_CRM_SAVE.
Look at OSS note 588701 & 765018 for deletion of CRMMLSGUID.
The issue is exactly ours: around system/client copy.
In an CRM environment, this is more critical, because we make a huge use of the middleware. But in our case, and especially after system/client copies, we can go, even if SAP does not guaranty anything, because we don't care about "old" replicated data (I don't care about old BDOCs, that should even be deleted after processing).
We have to take some risks sometimes...
Rgds
Christophe

I need help in logical system name in business system

i created two business system with same logical system name and now am getting error in ID when i try to activate business system"" Logical system LSSUN already exists in service | BS_RCVESUN"" So,i again changed a logical system name in SLD and tried to activate it again but changes is not reflected back in ID.again it show logiacal system alredy exists.
pls giv me a steps to reflect changes back in ID.
thanks & Regards
Manikandan Shanmugam

open BS in edit mode,
choose from menu: Adepter Specific Identifiers
Here you push button: Compare SLD data
Save and activate

Logical system name

Hi,
I have done the system copy from production system to quality system yesterday.After that i am unable to change the logical system name in Quality syste in scc4.The logical system field disabled.Why?
Regards,
Mani

Hi,
What we do after system copy is run BDLS in target system & this changes logical system name.
Check below link for more details
Re: about assigning logical system name to client
Thanks
Sushil

Change ucs FI system name

Similar Messages

Maybe you are looking for