Routing

Hi everyone.

Today I was in my routine revision of the equipment, and I saw this:

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

 {master}
user@MX480> request routing-engine login other-routing-engine

€
--- JUNOS 12.1R1 built 2012-02-24 11:27:32 UTC

error: Aborted! This command can only be used on the master routing engine.

{backup}
user@MX480>

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Someone, know why see this message?, if I have not executed any CLI command.

Best regards.

if you login backup routing engine, before that command  You can not login master routing engine. You have to use that  command on master routing engine.

{master} <<<<<<<<<<<<<<<<<<< 
user@MX480> request routing-engine login other-routing-engine

€
--- JUNOS 12.1R1 built 2012-02-24 11:27:32 UTC

error: Aborted! This command can only be used on the master routing engine.

{backup} <<<<<<<<<<<<<<<<<<<<
user@MX480>

By looking @  the output I think the switchover is been successfull <please correct me if I am wrong> 

If it <logging to other RE> is successfull and even then you see the log message we need to check what is happening ... <JTAC case>

Else it is normal ! 

Hi.

I didn't make switchover. I did logging in the other routing-engine, only.

And the first prompt that can I see is that:

error: Aborted! This command can only be used on the master routing engine.

This is exactly what I saw and typed.

{master}

user@MX480> request routing-engine login other-routing-engine       ===> I typed that. (For logging in the other RE.)

€ --- JUNOS 12.1R1 built 2012-02-24 11:27:32 UTC

error: Aborted! This command can only be used on the master routing engine. ===> This is the message.

{backup}

user@MX480>

 -----------------------------------------------------------------------------------------------------------------

Best regards.

Most likely because the login class you are a member of is set to show chassis alarms on login.  Show chassis commands generally don't work on the backup RE since it doesn't have control of the chassis.  

Inside system / login:

class c-super_user {
    idle-timeout 15;
    login-alarms;
    login-tip;
    permissions all;
}
user cmyers {
    full-name "Chad Myers";
    uid 2001;
    class c-super_user;
 }

 The "login-alarms" line is what looks for any system or chassis alarms and displays them to you when you log in.  I don't recall if the built in superuser class has that applied since we never use it.

-Chad