[j-nsp] ex-series and RSPAN ?

[Thomas Burnett]

I have in configured remote span to work across a lag (junos 9.3)
The important thing to remember is the output vlan can only egress the switch on one logical port.
If you allow all vlan on a trunk, the span vlan is now trying to egress on two logical ports.



    ae5 {
        description "SW1 ae5 LAG--> SW5 ae0 LAG";
        unit 0 {
            family ethernet-switching {
                port-mode trunk;
                vlan {
                    members [ VLAN-LAN VLAN-DEV VLAN-QA remote-analyzer ];
                }
            }
        }
    }

ethernet-switching-options {
    analyzer traffic-monitor {
        loss-priority high;
        input {
            ingress {
                interface ge-1/0/6.0;
                interface ge-3/0/6.0;
                interface ge-1/0/1.0;
                interface ge-3/0/1.0;
            }
            egress {
                interface ge-1/0/6.0;
                interface ge-3/0/6.0;
                interface ge-1/0/1.0;
                interface ge-3/0/1.0;
            }
        }
        output {
            vlan {
                remote-analyzer;
            }
        }
    }
}

Thomas Burnett

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Alexandre Snarskii
Sent: Thursday, April 29, 2010 6:04 AM
To: Cyrill Malevanov
Cc: Juniper-NSP Mailing list
Subject: Re: [j-nsp] ex-series and RSPAN ?

On Fri, Feb 12, 2010 at 04:29:30PM +0300, Alexandre Snarskii wrote:
> 
> In my case, i'm trying to configure remote span, with output set to vlan: 
> 
> snar at us-smf-csw02> show configuration ethernet-switching-options analyzer Analyzer2 
> loss-priority high;
> input {
>     ingress {
>         interface ge-0/0/12.0;
>         interface ge-0/0/13.0;
>         interface ge-0/0/14.0;
>         interface ge-0/0/16.0;
>         interface ge-0/0/17.0;
>         interface ge-0/0/19.0;
>     }
> }
> output {
>     vlan {
>         Analyzer2;
>     }
> }
> 
> And it seems that my problem may be related to the fact that
> this vlan exits this switch and enters next one via aggregated 
> ethernet: 

Just to confirm this idea: 10.0R3 refuses this configuration with 
the following error: 

snar at us-smf-csw02# commit check 
[edit ethernet-switching-options]
  'analyzer'
    Aggregated interface <ae2.0> cannot be configured as a member of Analyzer output VLAN <Analyzer2>
error: configuration check-out failed

> 
> snar at us-smf-csw02> show vlans Analyzer2 extensive 
> VLAN: Analyzer2, Created at: Fri Feb 12 02:46:45 2010
> 802.1Q Tag: 999, Internal index: 18, Admin State: Enabled, Origin: Static
> Protocol: Port Mode
> Number of interfaces: Tagged 1 (Active = 1), Untagged  0 (Active = 0)
>       ae2.0*, tagged, trunk
> 
> Will check next week.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp