Quantcast
Channel: All Ethernet Switching posts
Viewing all 10307 articles
Browse latest View live
↧

Re: Juniper infrastrukture and IP cameras.

February 13, 2019, 12:35 am
$
0
0
Hi LOGTECH,

Answers inline:

Having in network currently 1000 end devices and using EX 3300 & EX 4300 switches should not be a problem correct?
Ans: This needs to be gauged based on the overall usage/throughput expected out of the switch (ports) and oversubscription ratio (ingress to egress interface bandwidth ratio). Its difficult for anyone to comment on this without complete study of your network. It may be helpful for you to have a brief chat with the nearest Juniper Systems a.k.a Sales Engineer for the best advice based on your network needs.

For more details on the EX Series Switches and QFX Series switches, you can refer to the following URLs; there’s a “Compare Product” option that will give you various numbers including port densities and throughput:
EX Series switches: http://w ww.juniper.net/us/en/products- services/switching/ex-series/
QFX Series switches: http://www.juniper.net /us/en/products-services/switching/qfx-series/


Any specific QoS on juniper for cameras or just separate VLAN? Any other thoughts?
Ans: QoS will help if you’re separating voice/video streams with the rest of the traffic. So it depends if you expect that traffic from these cameras or just regular data traffic.
Cameras generally don’t do 802.1X, so you may need to decide on the access control for them differently than regular desktop clients, like use MAC auth (or no auth 😊) and put them in the desired VLAN.

Hope this helps.

Regards,
-r
--------------------------------------------------
If this solves your problem, please mark this post as "Accepted Solution."
Kudos are always appreciated Smiley Happy.
↧
Search

Re: QFX5100 - mixing families

February 13, 2019, 12:59 am
$
0
0

Hi spuluka,

 

flexible-vlan-tagging has this descriptions:

"flexible-vlan-tagging          Support for no tagging, or single and double 802.1q VLAN tagging"

 

It doesn't say anthing of mixing family inet and ethernet-switching or services.

 

Take a look at the following, on an ge interface on a qfx5100 with version 14.1X53-D45.3:

 

flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 0 {
    vlan-id 10;
    family inet;
    ##
    ## Warning: Family ethernet-switching and rest of the families are mutually exclusive
    ##
    family ethernet-switching {
        interface-mode trunk;
        vlan {
            members vlan-8;
        }
    }
}
unit 20 {
    vlan-id 20;
    family inet {
        address 192.168.10.11/31;
    }
}

Apparantly the switch does not pass a configuration when using family inet and ethernet-switching under the same unit / logical interface.

 

 

Here I set flexible-vlan-tagging / flexible-ethernet-switching and on unit 0 i set VLAN 10 and below under ethernet-switching a trunk port with two members, vlan-8 and vlan-9. I also set family inet under unit 0.

 

It does, however, not fail on unit 20? Because that is where it went wrong.

Adding the unit 20 would have broken the switch capabilities of the port.

 

Would above configuration pass the test when the JunOS version is above 16.1R6?\

 

Beeelze

 

 

 

↧
↧

Re: QFX5100 - mixing families

February 13, 2019, 2:54 am
$
0
0

Hi Beeelzebub,

 

Thanks for sharing the config.  This config doesn't commit post Junos 16.1 too.  And it doesn't commit whichever unit (0 or otherwise) combines "inet+ethernet-switching", irrespective of whether we have a single unit or multiple units on the interface.  Please see sample commit check below.

 

We can mix the interface families on the same interface but on different units to get different logical/sub-interfaces.  And mixing families on different logical interfaces should achieve the purpose. 

 

The interface wouldn't route and switch on the same logical interface.  What's the idea of combining inet/ethernet-switching on the same unit? And on which code did that commit work earlier? If it's just that it was working earlier and commit doesn't go through now, then at best, the commit would have been allowed in error.  If you know the old Junos version, we can easily validate that.

 

**************************************************

{master:0}[edit]

root@R4# show | compare

[edit interfaces]

+   xe-0/0/7 {

+       flexible-vlan-tagging;

+       encapsulation flexible-ethernet-services;

+       unit 0 {

+           vlan-id 10;

+           family inet;

+           family ethernet-switching {

+               interface-mode trunk;

+               vlan {

+                   members vlan-8;

+               }

+           }

+       }

+       unit 20 {

+           vlan-id 20;

+           family inet {

+               address 192.168.10.11/31;

+           }

+       }

+   }

 

{master:0}[edit]

root@R4# commit check

[edit interfaces xe-0/0/7 unit 0 family]

  'ethernet-switching'

    Family ethernet-switching and rest of the families are mutually exclusive

[edit protocols]

  'bgp'

    warning: requires 'bgp' license

[edit protocols]

  'isis'

    warning: requires 'isis' license

error: configuration check-out failed: (statements constraint check failed)

 

{master:0}[edit]

root@R4# show interfaces xe-0/0/7 | display set

set interfaces xe-0/0/7 flexible-vlan-tagging

set interfaces xe-0/0/7 encapsulation flexible-ethernet-services

set interfaces xe-0/0/7 unit 0 vlan-id 10

set interfaces xe-0/0/7 unit 0 family inet

set interfaces xe-0/0/7 unit 0 family ethernet-switching interface-mode trunk

set interfaces xe-0/0/7 unit 0 family ethernet-switching vlan members vlan-8

set interfaces xe-0/0/7 unit 20 vlan-id 20

set interfaces xe-0/0/7 unit 20 family inet address 192.168.10.11/31

 

{master:0}[edit]

root@R4# delete interfaces xe-0/0/7 unit 0 family inet

 

{master:0}[edit]

root@R4# commit check

[edit protocols]

  'bgp'

    warning: requires 'bgp' license

[edit protocols]

  'isis'

    warning: requires 'isis' license

configuration check succeeds

 

{master:0}[edit]

root@R4# set interfaces xe-0/0/7 unit 20 family ethernet-switching

 

{master:0}[edit]

root@R4# show | compare

[edit interfaces]

+   xe-0/0/7 {

+       flexible-vlan-tagging;

+       encapsulation flexible-ethernet-services;

+       unit 0 {

+           vlan-id 10;

+           family ethernet-switching {

+               interface-mode trunk;

+               vlan {

+                   members vlan-8;

+               }

+           }

+       }

+       unit 20 {

+           vlan-id 20;

+           family inet {

+               address 192.168.10.11/31;

+           }

+           family ethernet-switching;

+       }

+   }

 

{master:0}[edit]

root@R4# commit check

[edit interfaces xe-0/0/7 unit 20 family]

  'ethernet-switching'

    Family ethernet-switching and rest of the families are mutually exclusive

[edit protocols]

  'bgp'

    warning: requires 'bgp' license

[edit protocols]

  'isis'

    warning: requires 'isis' license

error: configuration check-out failed: (statements constraint check failed)

 

{master:0}[edit]

root@R4# delete interfaces xe-0/0/7 unit 20

 

{master:0}[edit]

root@R4# set interfaces xe-0/0/7 unit 0 family inet                     

 

{master:0}[edit]

root@R4# show | compare

[edit interfaces]

+   xe-0/0/7 {

+       flexible-vlan-tagging;

+       encapsulation flexible-ethernet-services;

+       unit 0 {

+           vlan-id 10;

+           family inet;

+           family ethernet-switching {

+               interface-mode trunk;

+               vlan {

+                   members vlan-8;

+               }

+           }

+       }

+   }

 

{master:0}[edit]

root@R4# commit check

[edit interfaces xe-0/0/7 unit 0 family]

  'ethernet-switching'

    Family ethernet-switching and rest of the families are mutually exclusive

[edit protocols]

  'bgp'

    warning: requires 'bgp' license

[edit protocols]

  'isis'

    warning: requires 'isis' license

error: configuration check-out failed: (statements constraint check failed)

 

{master:0}[edit]

root@R4# run show version

fpc0:

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

Hostname: R4

Model: qfx5100-48s-6q

Junos: 18.3R1.9

**************************************************

 

Hope this helps.

 

Regards,
-r.

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

If this solves your problem, please mark this post as "Accepted Solution."
Kudos are always appreciated Smiley Happy.

↧

Re: QFX5100 - mixing families

February 13, 2019, 3:08 am
$
0
0

Thanks for testing on the QFX.  I've only ever mixed layer 2/3 like this on MX and SRX before.

I know it didn't work on the EX platforms we tried to use as well.

 

So I wasn't sure what other platforms allowed the mixing or not.

 

↧

Re: QFX5100 - mixing families

February 13, 2019, 3:42 am
$
0
0

mriyaz,

 

Thanks for testing indeed.

If I had a QFX5100 spare, then I would not have to ask you Smiley Sad

 

| We can mix the interface families on the same interface but on different units to get different logical/sub-interfaces.  And mixing   

families on different logical interfaces should achieve the purpose. 

 

Yes, that's exactly what I did a couple of weeks ago. But then, somehow, the ethernet-switching stopped working.

I'm not trying to mix the familes on the SAME UNIT, but on DIFFERENT UNITS.

 

And THAT is apparantly what broke the ethernet-switching portion:

 

flexible-vlan-tagging;

encapsulation flexible-ethernet-services;

unit 0 {

    family ethernet-switching {

        interface-mode trunk;

        vlan {

            members [ vlan-4 voice-vlan7 esxi-server vlan-60 ];

        }

    }

}

unit 10 {

    vlan-id 10;

    family inet {

    }

}

 

 

I want to know if my QFX is broken, but i'm almost 100% sure it is not.

I think it's also best practice to either configure the port with ethernet-switching (switch port) or with vlan-bridging/family inet (router port). All this combining of families is never good I think.

I hope I can convince management the switch is not broken for this matter.

 

Beelze

↧
↧

vQFX + OpenNTI Lab

February 13, 2019, 6:08 am
$
0
0

Hello,

 

my plan was to build a Lab with vQFX10k and OpenNTI to test the analytics functinallity.

 

I configured analytics as:

root@vqfx-re> show configuration services
analytics {
    streaming-server open-nti {
        remote-address 10.30.12.50;
        remote-port 50000;
    }
    export-profile opennti {
        local-address 10.30.12.1;
        local-port 21001;
        reporting-rate 5;
        format gpb;
        transport udp;
    }
    sensor interface-phy {
        server-name open-nti;
        export-name opennti;
        resource /junos/system/linecard/interface/;
    }
    sensor interface-log {
        server-name open-nti;
        export-name opennti;
        resource /junos/system/linecard/interface/logical/usage/;
    }
}

And get the following error message:

root@vqfx-re> show analytics status
error: peer_daemon: bad daemon: analyticsd

Version of RE/PFE ist 17.4R1.

 

Any ideas?

 

Greets

↧

Re: Large number of interfaces in an sflow configuration

February 13, 2019, 1:41 pm
$
0
0

Would the actual syntax be set groups sflo protocols sflow interfaces <ge-*> ?

↧

Sflow config for 4300s

February 13, 2019, 2:47 pm
$
0
0

Is there an easy way to include all the interfaces to send sflow data instead of doing set sflow interfaces ge-x/x/x.x for each interface ?

 

I already have the following

{master:0} [edit protocols]

username@vcname# show sflow

polling-interval 10;

sample-rate {

ingress 500;

egress500;

}

collector ip address of collector {

udp-port 6343;

}

interfaces ge-0/0/7.0;

interfaces xe-0/2/0.0;

interfaces xe-1/2/0.0;

{master:0}[edit protocols]

↧
Search

Re: Sflow config for 4300s

February 13, 2019, 5:53 pm
$
0
0
Hi Modus,

Please try this:

set groups sflow_group protocols sflow interfaces <*> sample-rate ingress 4096
set groups sflow_group protocols sflow interfaces <*> sample-rate egress 4096

You can refer to this documentation for the apply-groups usage: https://www.juniper.net/documentation/en_US/junos/topics/topic-map/configuration-groups-usage.html

To verify:
show protocols sflow | display inheritance | display set


Hope this helps.

Regards,
-r.

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

If this solves your problem, please mark this post as "Accepted Solution."
Kudos are always appreciated Smiley Happy.
↧
↧

Re: Large number of interfaces in an sflow configuration

February 13, 2019, 5:53 pm
$
0
0
Hi Modus,

Try this:

set groups sflow_group protocols sflow interfaces <*> sample-rate ingress 4096
set groups sflow_group protocols sflow interfaces <*> sample-rate egress 4096

You can refer to this documentation for the apply-groups usage: https://www.juniper.net/documentation/en_US/junos/topics/topic-map/configuration-groups-usage.html

To verify:
show protocols sflow | display inheritance | display set


Hope this helps.

Regards,
-r.

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

If this solves your problem, please mark this post as "Accepted Solution."
Kudos are always appreciated Smiley Happy.
↧

Re: Large number of interfaces in an sflow configuration

February 13, 2019, 7:43 pm
$
0
0

Hi Modus,

 

Since we cannot configure an interface-range under sflow, there is no other option but to configure each interface  individually.  We can only use apply-groups to add the same sample-rate to all interfaces.

 

Please refer this documentation for the apply-groups usage: https://www.juniper.net/documentation/en_US/junos/topics/topic-map/configuration-groups-usage.html

 

root@Juniper# show groups sflo | display set

set groups test protocols sflow interfaces <*> sample-rate ingress 4096

set groups test protocols sflow interfaces <*> sample-rate egress 4096

 

{master:0}[edit]

root@Juniper# show protocols sflow | display set

set protocols sflow agent-id 1.1.1.1

set protocols sflow sample-rate ingress 4096

set protocols sflow source-ip 1.1.1.1

set protocols sflow collector 2.2.2.2 udp-port 6343

set protocols sflow collector 3.3.3.3 udp-port 6343

set protocols sflow interfaces xe-0/0/0.0 apply-groups test

set protocols sflow interfaces xe-0/0/1.0 apply-groups test

 

{master:0}[edit]

root@Juniper# show protocols sflow | display inheritance

agent-id 1.1.1.1;

sample-rate ingress 4096;

source-ip 1.1.1.1;

collector 2.2.2.2 {

    udp-port 6343;

}

collector 3.3.3.3 {

    udp-port 6343;

}

interfaces xe-0/0/0.0 {

    ##

    ## 'sample-rate' was inherited from group 'test'

    ##

    sample-rate {

        ##

        ## '4096' was inherited from group 'test'

        ##

        ingress 4096;

        ##

        ## '4096' was inherited from group 'test'

        ##

        egress 4096;

    }

}

interfaces xe-0/0/1.0 {

    ##

    ## 'sample-rate' was inherited from group 'test'

    ##

    sample-rate {

        ##

        ## '4096' was inherited from group 'test'

        ##

        ingress 4096;

        ##

        ## '4096' was inherited from group 'test'

        ##

        egress 4096;

    }

}

 

{master:0}[edit]

root@Juniper# show protocols sflow | display inheritance | display set

set protocols sflow agent-id 1.1.1.1

set protocols sflow sample-rate ingress 4096

set protocols sflow source-ip 1.1.1.1

set protocols sflow collector 2.2.2.2 udp-port 6343

set protocols sflow collector 3.3.3.3 udp-port 6343

set protocols sflow interfaces xe-0/0/0.0 sample-rate ingress 4096

set protocols sflow interfaces xe-0/0/0.0 sample-rate egress 4096

set protocols sflow interfaces xe-0/0/1.0 sample-rate ingress 4096

set protocols sflow interfaces xe-0/0/1.0 sample-rate egress 4096

 

In this example, we have a config group for applying sample-rate to interfaces and we apply this to protocols sflow interfaces<interface-name> and the sample rate gets inherited from the group "test".

 

 

Hope this helps.

 

Regards,

-r.

 

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

 

If this solves your problem, please mark this post as "Accepted Solution."

Kudos are always appreciated Smiley Happy.

 

↧

Re: Sflow config for 4300s

February 13, 2019, 8:03 pm
$
0
0

Hi Modus,

 

Since we cannot configure an interface-range under sflow, there is no other option but to configure each interface  individually.  We can only use apply-groups to add the same sample-rate to all interfaces.

 

Please refer this documentation for the apply-groups usage: https://www.juniper.net/documentation/en_US/junos/topics/topic-map/configuration-groups-usage.html

 

root@Juniper# show groups sflo | display set

set groups test protocols sflow interfaces <*> sample-rate ingress 4096

set groups test protocols sflow interfaces <*> sample-rate egress 4096

 

{master:0}[edit]

root@Juniper# show protocols sflow | display set

set protocols sflow agent-id 1.1.1.1

set protocols sflow sample-rate ingress 4096

set protocols sflow source-ip 1.1.1.1

set protocols sflow collector 2.2.2.2 udp-port 6343

set protocols sflow collector 3.3.3.3 udp-port 6343

set protocols sflow interfaces xe-0/0/0.0 apply-groups test

set protocols sflow interfaces xe-0/0/1.0 apply-groups test

 

{master:0}[edit]

root@Juniper# show protocols sflow | display inheritance

agent-id 1.1.1.1;

sample-rate ingress 4096;

source-ip 1.1.1.1;

collector 2.2.2.2 {

    udp-port 6343;

}

collector 3.3.3.3 {

    udp-port 6343;

}

interfaces xe-0/0/0.0 {

    ##

    ## 'sample-rate' was inherited from group 'test'

    ##

    sample-rate {

        ##

        ## '4096' was inherited from group 'test'

        ##

        ingress 4096;

        ##

        ## '4096' was inherited from group 'test'

        ##

        egress 4096;

    }

}

interfaces xe-0/0/1.0 {

    ##

    ## 'sample-rate' was inherited from group 'test'

    ##

    sample-rate {

        ##

        ## '4096' was inherited from group 'test'

        ##

        ingress 4096;

        ##

        ## '4096' was inherited from group 'test'

        ##

        egress 4096;

    }

}

 

{master:0}[edit]

root@Juniper# show protocols sflow | display inheritance | display set

set protocols sflow agent-id 1.1.1.1

set protocols sflow sample-rate ingress 4096

set protocols sflow source-ip 1.1.1.1

set protocols sflow collector 2.2.2.2 udp-port 6343

set protocols sflow collector 3.3.3.3 udp-port 6343

set protocols sflow interfaces xe-0/0/0.0 sample-rate ingress 4096

set protocols sflow interfaces xe-0/0/0.0 sample-rate egress 4096

set protocols sflow interfaces xe-0/0/1.0 sample-rate ingress 4096

set protocols sflow interfaces xe-0/0/1.0 sample-rate egress 4096

 

In this example, we have a config group for applying sample-rate to interfaces and we apply this to protocols sflow interfaces<interface-name> and the sample rate gets inherited from the group "test".

 

 

Hope this helps.

 

Regards,

-r.

 

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

 

If this solves your problem, please mark this post as "Accepted Solution."

Kudos are always appreciated Smiley Happy.

↧

Re: QFX5100 - mixing families

February 14, 2019, 12:37 am
$
0
0
Hi Beelze,

You're welcome and thanks for confirming you were trying the different families on different units. That is exactly what is supported post Junos 16.1R6 on QFX5100s, with a caveat that family ethernet-switching should be configured only on unit 0.

Reference: https://www.juniper.net/documentation/en_US/junos/topics/topic-map/switches-interface-flexible.html

"On QFX5100 switches, you can combine encapsulations on the same physical interface for vlan-bridge and family ethernet switching. Starting with Junos OS Release 16.1R6, you can also combine encapsulations on the same physical interface for family inet and family ethernet-switching."

Your QFX should be fine and you can quote the above to explain the behavior. If this config is still desired, consider upgrading to the latest JTAC recommended Junos for QFX5100:
https://kb.juniper.net/InfoCenter/index?page=content&id=kb21476


Hope this helps.

Regards,
-r.

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

If this solves your problem, please mark this post as "Accepted Solution."
Kudos are always appreciated Smiley Happy.
↧
↧

Mirror port on Ex9214 not working

February 14, 2019, 1:08 am
$
0
0

I tried to setup a mirror port on my EX9214 but it fail, the state always show "Down"

I follow instruction given in this page https://kb.juniper.net/InfoCenter/index?page=content&id=KB28604

is there anything I misconfiged?  Thank you

 

RE1> show forwarding-options analyzer porttrace
Analyzer name : porttrace
Mirror rate : 1
Maximum packet length : 0
State : down
Ingress monitored interfaces : ge-0/0/3.0
Ingress monitored interfaces : ge-0/0/8.0
Ingress monitored interfaces : ge-0/1/1.0
Ingress monitored interfaces : ge-12/0/3.0
Ingress monitored interfaces : ge-0/1/2.0
Ingress monitored interfaces : ge-0/1/3.0
Ingress monitored interfaces : ge-0/1/5.0
Ingress monitored interfaces : ge-1/2/1.0
Ingress monitored interfaces : ge-13/2/1.0
Ingress monitored interfaces : ge-12/1/3.0
Ingress monitored interfaces : ge-12/1/5.0
Ingress monitored interfaces : ge-12/1/1.0
Ingress monitored interfaces : ge-12/1/2.0
Egress monitored interfaces : ge-0/0/3.0
Egress monitored interfaces : ge-0/0/8.0
Egress monitored interfaces : ge-0/1/1.0
Egress monitored interfaces : ge-12/0/3.0
Egress monitored interfaces : ge-0/1/2.0
Egress monitored interfaces : ge-0/1/3.0
Egress monitored interfaces : ge-0/1/5.0
Egress monitored interfaces : ge-1/2/1.0
Egress monitored interfaces : ge-13/2/1.0
Egress monitored interfaces : ge-12/1/3.0
Egress monitored interfaces : ge-12/1/5.0
Egress monitored interfaces : ge-12/1/1.0
Egress monitored interfaces : ge-12/1/2.0

↧

Re: Mirror port on Ex9214 not working

February 14, 2019, 3:03 am
$
0
0
Hi owenchen,

A few things to note to ensure the analyzer is up:

a) Ensure you added the dummy VLAN to the output interface.
b) Ensure that at least one of the ingress/egress ports configured is up and has a valid family inet/ethernet-switching configured.

That should do it. Else please share your Junos version and config.

Hope this helps.

Regards,
-r.

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

If this solves your problem, please mark this post as "Accepted Solution."
Kudos are always appreciated Smiley Happy.
↧
Search

Re: EX3400 - Recovery from failed SW upgrade fails

February 15, 2019, 4:06 am
$
0
0

Hi @rmaradia,

How long does this procedure takes? I followed your steps, but the switch seems to hang after the reboot (see attachement). Is this a normal behaviour?

 

thanks for your help.ex2300.png

↧

Re: Sflow config for 4300s

February 15, 2019, 6:40 am
$
0
0

That sucks that we have to list ever interfaces and we can't do a wildcard. I'll just enter the uplinks

↧
↧

What is the number of QSFP+ build in EX4300MP?

February 15, 2019, 8:40 am
$
0
0

Dear Juniper

What is the number of QSFP+ build in EX4300MP?.  Information in datasheet and 4300 hardware guide is not equal.

↧

Re: What is the number of QSFP+ build in EX4300MP?

February 15, 2019, 9:57 am
$
0
0

4, just like other EX4300 models, with exception being the EX4300-32F which only has 2 x 40GE QSFP built-in ports.

 

The datasheet shows 0 (2) as the 4 x 40GE built-in can ONLY be used for VC, so not true 40GE ports.  For true 40GE there is an optional 2 x 40GE uplink module that can be added in the front.

↧

Re: What is the number of QSFP+ build in EX4300MP?

February 15, 2019, 4:45 pm
$
0
0
Its 4 QSFP ports on EX4300 on PIC 1. But not sure which one was referred as "EX4300MP". Uplink modules are different based on model of course.

Example:

root@EX4300-48T> show chassis hardware | no-more
Hardware inventory:
Item Version Part number Serial number Description
Chassis PE3714100763 EX4300-48T
Routing Engine 0 REV 10 650-044931 PE3714100763 EX4300-48T
FPC 0 REV 10 650-044931 PE3714100763 EX4300-48T
CPU BUILTIN BUILTIN FPC CPU
PIC 0 REV 10 BUILTIN BUILTIN 48x 10/100/1000 Base-T
PIC 1 REV 10 BUILTIN BUILTIN 4x 40GE QSFP+
PIC 2 REV 05 611-044925 MY3715380329 4x 1G/10G SFP/SFP+


Hope this helps.

Regards,
-r.

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

If this solves your problem, please mark this post as "Accepted Solution."
Kudos are always appreciated Smiley Happy.
↧
Viewing all 10307 articles
Browse latest View live
Search