Ericsson RBS 6402 (pico)

Equipment
,
1

Good day! Do u know how to activate brmfailsafebackup (time remaining) on rbs6402pico? I need to change oam address, but timer not active, (confirm restore doesn’t work) I can set only brmrollbackatrestore, it does not start.

2

Hi, @Vladimir, this algo is for baseband, but I believe it should be the same:

lt all
l+
confb+
set BrmFailsafeBackup timeoutLength 600

for 10
    acc BrmFailsafeBackup activate
    if $nr_of_mos_ok = 0
        wait 10
    else
        l echo "Brm Failsafe Backup activated!"
        break
    fi
done

if $nr_of_mos_ok != 1
    return
fi

wait 5

get BrmFailsafeBackup progressReport > $failsafe_state
if $failsafe_state[actionName] = DEACTIVATE
    return
else
    l echo 'proceeding...'
fi

// change oam ip here

for 10
    acc BrmFailsafeBackup deactivate 
    1
    if $nr_of_mos_ok = 0
        wait 10
    else
        l echo "Brm Failsafe Backup deactivated!"
        break
    fi
done

cvrm new_oam_ip

for 10
    cvmk new_oam_ip
    if $nr_of_mos_ok = 0
        wait 10
    else
        l echo "Backup created!"
        break
    fi
done

confb-

l-
2 Likes
4

Thanks, I have similar file.mos but with Amos commands for bb. Now I checking brm… on b and pico, and saw that, pico did not crate brmfailsafebackup=1. I thought it’s normal))) check elex, he should be created))) I try to create (cr system…brm…backup=1 but rbs noticed “error Can not instantiate system created object

5

Hi Vladimir. What is SW version on your pico6402?

6

Hi, R4B240,19. Q1

7

Hi. Ok. It’s the latest UP for 6402 and MO BrmFailsafeBackup=1 should be already present in configuration comparted to L16 versions. Could you share lpr SystemFunctions=1,BrM=1 printout? And get . RbsConfigLevel.

8

IMG_20250401_133545
IMG_20250401_1335451920×1180 360 KB

9

Done…

10

Hi, Vladimir. I checked it on our node from the same UP and there is no this MO as well. So, I would say that it’s SW bug, but pico6402 isn’t supported anymore. But if you have time for experiments you may check, if this MO is present on some older UPs (17-18), check behavior during SW upgrades and LKF installation.

1 Like
11

Thanks a lot, no any UP’s except installed), try to change without rollback or reintegration)

1 Like
12

Changed) by run1 changeOAM.mos
Set host_oam ip
Set host_oam nexthope
Set host_peerip (same nexthop)
Set vlan oam
Cvms aaaa
All changes confirmed after restart node

3 Likes