Junos OS

Hi,

I've stumbled upon a problem where I can not use a patch file on EX4500.

I get the following error and I automatically get kicked off cli:

cli: remote side unexpectedly closed connection

cat: stdin: Input/output error

Also a coredump is generated under /var/tmp

root@EPC-EX4500-2> show version
fpc0:
--------------------------------------------------------------------------
Hostname: EPC-EX4500-2
Model: ex4500-40f
JUNOS Base OS boot [12.2R2.4]
JUNOS Base OS Software Suite [12.2R2.4]
JUNOS Kernel Software Suite [12.2R2.4]
JUNOS Crypto Software Suite [12.2R2.4]
JUNOS Online Documentation [12.2R2.4]
JUNOS Enterprise Software Suite [12.2R2.4]
JUNOS Packet Forwarding Engine Enterprise Software Suite [12.2R2.4]
JUNOS Routing Software Suite [12.2R2.4]
JUNOS Web Management [12.2R2.4]
JUNOS FIPS mode utilities [12.2R2.4]

A patch looks the following:

[edit interfaces ae2]

+   vlan-tagging;

[edit interfaces ae2]

-    unit 0 {

-        family ethernet-switching {

-            port-mode trunk;

-            vlan {

-                members [ vlan202 vlan208 ];

-            }

-        }

-    }

+    unit 202 {

+        description "EPC_2 MME S6a-1";

+        vlan-id 202;

+        family inet {

+            address 10.88.46.25/29;

+        }

+    }

+    unit 208 {

+        description "EPC_2 MME SGs-1";

+        vlan-id 208;

+        family inet {

+            address 10.88.46.105/29;

+        }

+    }

[edit interfaces vlan]

-    unit 202 {

-        description "EPC_2 MME S6a-1";

-        family inet {

-            address 10.88.46.25/29;

-        }

-    }

-    unit 208 {

-        description "EPC_2 MME SGs-1";

-        family inet {

-            address 10.88.46.105/29;

-        }

-    }

[edit protocols rstp]

-    interface ae2.0 {

-        disable;

-        no-root-port;

-    }

[edit routing-instances CORE]

+    interface ae2.202;

+    interface ae2.208;

-    interface vlan.202;

-    interface vlan.208;

[edit routing-instances CORE protocols ospf area 0.0.0.2]

        interface vlan.320 { ... }

+       interface ae2.202 {

+           passive;

+       }

+       interface ae2.208 {

+           passive;

+       }

-       interface vlan.202 {

-           passive;

-       }

-       interface vlan.208 {

-           passive;

-       }

[edit ethernet-switching-options analyzer remote-analyzer-all input ingress]

       interface ge-0/0/21.0 { ... }

+      interface ae2.0;

[edit ethernet-switching-options analyzer remote-analyzer-all input ingress]

-      vlan vlan202;

-      vlan vlan208;

[edit vlans]

-   vlan202 {

-       description "EPC_2 MME S6a-01";

-       vlan-id 202;

-       l3-interface vlan.202;

-   }

-   vlan208 {

-       description "EPC_2 MME SGs-1";

-       vlan-id 208;

-       l3-interface vlan.208;

-   }

Do you have any suggestions or is it a bug ?

Br,

Michal

Hey Michal,

 I think there are parts of the configuration (ae2.0 trunk for instance) that are not correct, hence it can't be applied:

{master:0}[edit interfaces ae2]
erdems@homer# show
vlan-tagging;
unit 0 {
    ##
    ## Warning: An interface cannot have both family ethernet-switching and vlan-tagging configured
    ##
    family ethernet-switching {
        port-mode trunk;
    }
}

 I would recommend opening a case if only the CLI should handle the situation better IMHO.

 Cheers,

The configuration deletes the family ethernet-switching, though, so I think it should have worked. I am wondering if the config file was edited with some application which had some kind of weird fromatting. Like you advised open a case with juniper. BTW, what kind of application is used to connect to the switch? SSH, Telnet via putty, SecureCRT? Console? I guess the core dump will tell Juniper what has happened. If he edited the file like this, I wonder if that would make a difference when he commits the config? Also instead of commiting, try a commit check and see if the results are still the same. Maybe at the very least it would probably tell him what is spooky before crashing!

[edit interfaces ae2]
- unit 0 {
- family ethernet-switching {
- port-mode trunk;
- vlan {
- members [ vlan202 vlan208 ];
- }
- }
- }
[edit interfaces ae2]

It sounds like you get kicked off when loading / applying the patch, not when committing.  Is that correct?  And is the core file for mgd?  If so, almost certainly a bug.

Here's the mistake in the patch:

[edit ethernet-switching-options analyzer remote-analyzer-all input ingress]

       interface ge-0/0/21.0 { ... }

+      interface ae2.0;

There have been some bugs on platforms in the past where renaming something would break, but deleting, committing, then adding it back with the new name would work.  That's similar to what you are doing with the vlan => routed 802.1q tagged port.

If it is a similar bug you could try to get around it by splitting the back apart into two pieces.  One that does all of the - bits and a second that does all of the + bits.  The [edit blah] portions would be in both parts.  Or cheat and do this in two steps without the patch.

Step 1:

delete interfaces ae2.0
delete interfaces vlan.202
delete interfaces vlan.208
delete protocols rstp interface ae2.0
delete routing-instances CORE interface vlan.202
delete routing-instances CORE interface vlan.208
delete routing-instances CORE protocols ospf area 0.0.0.2 interface vlan.202
delete routing-instances CORE protocols ospf area 0.0.0.2 interface vlan.208
delete ethernet-switching-options analyzer remote-analyzer-all input ingress vlan vlan202
delete ethernet-switching-options analyzer remote-analyzer-all input ingress vlan vlan208
delete vlans vlan202
delete vlans vlan208

 At a minimum do a commit check, but ideally commit before doing step 2.

Step 2:

set interfaces ae2 vlan-tagging
set interfaces ae2.202 description "EPC_2 MME S6a-1"
set interfaces ae2.202 vlan-id 202 family inet address 10.88.46.25/29
set interfaces ae2.208 description "EPC_2 MME SGs-1"
set interfaces ae2.208 vlan-id 208 family inet address 10.88.46.105/29
set routing-instances CORE interface ae2.202
set routing-instances CORE interface ae2.208
set routing-instances CORE protocols ospf area 0.0.0.2 interface ae2.202 passive
set routing-instances CORE protocols ospf area 0.0.0.2 interface ae2.208 passive
set ethernet-switching-options analyzer remote-analyzer-all input ingress interface ae2.202
set ethernet-switching-options analyzer remote-analyzer-all input ingress interface ae2.208

Cheers!

-Chad

Thank you all for replies.

@Chad I think that you might have been right - I do not rember now how I had solved the problem but probably it was command by command and at that time I was simply checking out patch option to apply. 

Btw. core dumps were for mgd and but I do not remember whether they were generated during commit or during pasting.

-rw-rw---- 1 root wheel 4063885 Feb 8 2013 mgd.core.0.gz
-rw-rw---- 1 root wheel 4156989 Feb 8 2013 mgd.core.1.gz

Br,

Michal