Avamar Gen4T >> How to reconfigure RMM4 root user to alternative user name (avoid Error message: Login failed. User does not have ‘Login to Embedded Management Software’ privilege.)

— All commands to be executed as root on the node where RMM4 user is being configured.

1 — Verify that RMM4 is configured for dedicated access (in case there is no valid IP address configured, replace “lan print 4” with “lan print 1” to check for shared access):

root@avamar:~/#: ipmitool lan print 4 |egrep “IP Address|Subnet Mask|Default Gateway” |egrep -v “Source|Header|Backup|MAC”

IP Address :

Subnet Mask :

Default Gateway IP :

2 — To list configured users (in case RMM access is configured as shared, replace “summary 4” with “summary 1” and “list 4” with “list 1”):

root@avamar:~/#: ipmitool user summary 4

Maximum IDs : 16

Enabled User Count : 1

Fixed Name Count : 1

root@avamar:~/#: ipmitool user list 4

ID Name Callin Link Auth IPMI Msg Channel Priv Limit

2 root true true true ADMINISTRATOR

3 — To rename user ID#2 [root](where “NewName” shall be replaced with the desired username and “Password” replaced with desired password):

root@avamar:~/#: ipmitool user set name 2 NewName

root@avamar:~/#: ipmitool user set password 2 Password

root@avamar:~/#: ipmitool user enable 2

root@avamar:~/#: ipmitool channel setaccess 4 2 link=on ipmi=on callin=on privilege=4

root@avamar:~/#: ipmitool channel getaccess 4 2

Maximum User IDs : 16

Enabled User IDs : 1

User ID : 2

User Name : NewName

Fixed Name : No

Access Available : call-in / callback

Link Authentication : enabled

IPMI Messaging : enabled

Privilege Level : ADMINISTRATOR

5 — List users again:

root@avamar:~/#: ipmitool user list 4

ID Name Callin Link Auth IPMI Msg Channel Priv Limit

2 NewName true true true ADMINISTRATOR


  • No Related Posts

Re: Avamar GEN4T using dedicated replication ports

On the Avamar side, this depends on the routing configuration.

If 172.x on the source and target are on the same subnet, configuring the Avamar replication to point to the target’s 172.x address will ensure the data is sent across the dedicated replication network. However, if there is a gateway in between these two devices, you will likely need to specify a static route on the Avamar to ensure the packets are sent out the 172.x interface. If the source and target are on different networks and there is no static route, the data will be sent from the 10.x backup network on the source to the 172.x replication network on the target which is probably not what you want.

For the DD side, data transit is controlled by DDBoost. Dedicated replication interfaces are normally configured on the DD side using ifgroups. Avamar will ask the source DD to copy data to the target but how the data actually gets there is controlled on the DD side.


  • No Related Posts

VDA’s do not register with XenDesktop controllers when there is NAT in place between VDA and DDC

– There is NAT in place between VDA and DDC’s

RegistrationManager.AttemptRegistrationWithSingleDdc: Failed to register with http://DDC.domainname/Citrix/CdsController/IRegistrar. WCF Fault with detail Fail worker callback using SPN HOST/VDA.domainname and IP address <>, message ‘Fail worker callback using SPN HOST/VDA.domainname and IP address <>’

FindAttributesForComputerSid exit: SID=S-1-5-21-4084703721-986140599-3389830516-41493, DNS=c-testcu-d-a02.hosting.local, SAM=C-TESTCU-D-A02$

SetWorkerHostUriSpn: ipAddress:, workerAddress:c-testcu-d-a02.hosting.local, workerSpn:HOST/c-testcu-d-a02.hosting.local


  • No Related Posts

vethx inteface support speed after bonding

hi, all

I have a DD6300, i have already configured veth0 – it’s bonded two eth3a, eth3c – they connect over fiber cable to SW Cisco 4500, two ports 10gb uplink,

On Sw Cisco 4500 : port-chanel up, BW 20 Gb/s

But my veth0 only 10Gb/s

Interface Name:


Auto Negotiate:


Hardware Address:







10 Gb/s



Supported Speeds:


Any problem with my config, everybody help me to solve it ?

Here is my configuration :

lv@dd6300-backup# net show settings

port enabled state DHCP IP address netmask type additional setting

/prefix length

—– ——- ——- —- ————————– ————– —- ——————————-

ethMa yes running no n/a

fe80::260:16ff:fe86:c7c6** /64

eth3a yes running n/a n/a n/a n/a bonded to veth0

eth3b no down no n/a n/a n/a

eth3c yes running n/a n/a n/a n/a bonded to veth0

eth3d no down no n/a n/a n/a

veth0 yes running no n/a lacp hash xor-L2L3: eth3a,eth3c

fe80::260:16ff:fe85:22c8** /64

—– ——- ——- —- ————————– ————– —- ——————————-

** auto_generated IPv6 address

Thanks !


  • No Related Posts

Re: Does anyone know the meaning of “isi_stats_d: connect() to devid 0 : Connection reset by peer”?

I often see the following message in /var/log/messages of some nodes.

>isi_stats_d[1893]: connect() to devid 0 Connection reset by peer

I know “” is corresponding to the internal failover IP of node 7.

>nfs06-data-kks-7: lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384

>nfs06-data-kks-7: inet6 ::1 prefixlen 128 zone 1

>nfs06-data-kks-7: inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 zone 1

>nfs06-data-kks-7: inet netmask 0xff000000 zone 1

>nfs06-data-kks-7: inet netmask 0xffffff00 zone 1

Does it indicate any failure of HW or S/W?

If anyone knows the meaning of such message, please kindly tell me.

The cluster is IQ108NL x 13 nodes cluster, running with OneFS


  • No Related Posts

7022474: How to configure “external” network in network.json

Define an “external” network in network.json according to “Custom Network Configuration, Providing Access to External Networks” chapter in SUSE OpenStack Cloud 7 Deployment Guide.

“external” : {

“add_bridge” : false,

“vlan” : XXX,

“ranges” : {

“host” : {

“start” : “”,

“end” : “”



“broadcast” : “”,

“netmask” : “”,

“conduit” : “intf1”,

“subnet” : “”,

“use_vlan” : true


To have this “external” network before configuring barclamps use ‘crowbarctl’ command for a particular node.

On admin node:

#crowbarctl network interface enable default d52-54-00-63-a1-01.example.com external

#crowbarctl network hostip allocate default d52-54-00-63-a1-01.example.com external host

Then on d52-54-00-63-a1-01.example.com:

#systemctl restart chef-client.service

Afterwards configure iscsi initiator on the nodes. Deploy pacemaker, rabbitmq and database barclamps.


  • No Related Posts