01-29-2021 10:11 AM - edited 01-29-2021 10:13 AM
So iam setting up a C3160 for a client and i have updated all the firmware.
Currently i am having trouble finding the CLI command to change the 2nd VIC in SIOC slot 2 to processor node 2.
In the update utility i noticed it showed both VIC 1227s connected to CPU node 1. I think there is a fabric interconnect command to change the 2nd VIC to node 2. Searching through the UCS Cisco documentation I did find the acknowledgement commands but these seem to be for new UCS servers as a lot of the commands are not recognized.... I did happen to find some more documentation that VIC slot acknowledgment configuration can be done with UCS manager software via GUI. I noticed the UCS manager software is in a .bin file. So would I drop the 1GB .bin file inside a USB and run a boot command on it via ssh? If that's the case how do i get to the GUI configuration? I would be more comfortable just running a CLI command to change the 2nd VIC to node 2. So far i have tried about everything else i can but i can find out where to do this for the life of me.
Alot of commands seem to be different that whats in the UCS documentation for example when i scope and tab i get the following.
C3X60M3-FCH18487950 /chassis # scope adapter cmc dimm-summary drive-update firmware network-adapter pid-catalog sas-expander storageadapter
Solved! Go to Solution.
01-30-2021 06:35 AM
In you first post you mentioned the UCS .bin file. This .bin file is to upgrade the UCS software/firmware. You don't "run" the .bin file, but upload the file to UCS Manager and the firmware auto-upgrade following video:
This has nothing to do with NUMA. This is just assigning network resources to a blade. . .
I'd just configure it via the Web GUI (point your web browser at the UCSM IP) instead of CLI.
I think what you want is connectivity like this:
Via UCSM GUI:
Chassis / Policies / Compute Connection Policies / default
Server SIOC Connectivity = Single Server Single SIOC
[Save Changes]
Unsure if the Chassis has to be decomissioned/reacknowledged for that to take effect.
This may work for CLI:
01-29-2021 02:26 PM
Are you talking about trying to add a 2nd blade/server to a 3160 (I'm thinking those only supported one compute/blade), or trying to do numa type assignment for the 2nd SIOC vic?
Kirk...
01-29-2021 02:55 PM
Yes it has 2 blades inside of it and everything is working besides the network connection on blade 2. Trying to assignee SIOC 2 to the 2nd blade / NUMA node set. I see how to do it for newer UCS models and they all say to configure the fabric interconnect via CLI or UCS server manager GUI, but the commands are different for this server from what i see. I am also trying to do it over the LAN via SSH after login using scope based commands in CLI. Is UCS Manager compatible with the C3160?
01-30-2021 06:35 AM
In you first post you mentioned the UCS .bin file. This .bin file is to upgrade the UCS software/firmware. You don't "run" the .bin file, but upload the file to UCS Manager and the firmware auto-upgrade following video:
This has nothing to do with NUMA. This is just assigning network resources to a blade. . .
I'd just configure it via the Web GUI (point your web browser at the UCSM IP) instead of CLI.
I think what you want is connectivity like this:
Via UCSM GUI:
Chassis / Policies / Compute Connection Policies / default
Server SIOC Connectivity = Single Server Single SIOC
[Save Changes]
Unsure if the Chassis has to be decomissioned/reacknowledged for that to take effect.
This may work for CLI:
02-01-2021 08:47 AM - edited 02-01-2021 09:53 AM
I understand your comment about NUMA.
Ok so the guide you posted is for the S3260 and i have went the C3260 documentation awhile ago regarding the SIOC.
By default the C3160 does not come with UCS server manager. I have been through every setting possible on the web interface, i have updated all the all firmware on the C3160 and i have tried a range of CLI commands with no success in assigning the 2nd SIOC to the 2nd node for network connectivity. I have been looking in C3160 documentation, but the range of CLI commands seems very limited. I cant locate anything about SIOC policy for the C3160.
This seems to be all i can find as well when it comes to the C3160 CLI commands, but i see nothing regarding the SIOC.
Again both SIOCS are assigned to the 1st NODE card, so i know this is a matter of moving one of the SIOCs to NODE number 1.
Seems like the C3160 is an odd ball unit and you guys seem to be recommending what i have already tried.
This seems to be all i can find regarding the CLI commands for the C3160 and it seems it is lacking proper documentation of SIOC configuration.
In addition to our remarks on the UCS .bin file.
Is it possible to load UCS manager into the C3160 at all via the CLI than load up the web interface.
02-01-2021 11:13 AM
I have already tried the commands in the 3260 Guide and alot of the commands are not recognized in the C3160 CLI.
The C3160 does not come with UCS server manager by default.
In regards to the .bin file is there anyway to load it into a flash drive, access and install it via the CLI and than access its webinterface? That is if the C3160 even supports it.
There seems to be a lack of documentation for SIOC configuration and the C3160.
I have also been through the follow guide for CLI commands for some of the older UCS servers and it seems to be lacking information regarding the SIOC.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide