[j-nsp] Setting PE-4FE-TX port to 10m gives 'Illegal media change: invalid speed'

I've just tried to set a port on an PE-4FE-TX to 10m (set interfaces fe-0/0/1 speed 10m). This works fine on our PE-12FE-TX and the 'commit check' says all is well, but when I commit I get: /kernel: %KERN-2: fe-0/0/1: Illegal media change: invalid speed Are these 100m only ports? If not, what

Re: [j-nsp] Setting PE-4FE-TX port to 10m gives 'Illegal media change: invalid speed'

Hi Ras I believe this kind of card is able to run only at 100Mbps full or half. see: http://www.juniper.net/techpubs/hardware/m7i/m7i-pic/frameset.html Saying that the PE-12FE-TX is the only able to run at 10M or 100M I have already had the same problem as you. If you have some M7i with

Re: [j-nsp] Setting PE-4FE-TX port to 10m gives 'Illegal media change:invalid speed'

Hi Ras, Unfortunately the Px-4FE-TX is 100M only - see http://www.juniper.net/techpubs/software/junos/junos84/swconfig84-networ k-interfaces/id-12154979.html Note: The statement speed (10m | 100m) applies only to the management Ethernet interface (fxp0) and to the Fast Ethernet 12-port and

Re: [j-nsp] Setting PE-4FE-TX port to 10m gives 'Illegal media change: invalid speed'

Hi, http://www.juniper.net/techpubs/software/junos/junos83/swconfig83-network-interfaces/html/interfaces-ethernet-config2.html The statement speed (10m | 100m) applies only to the management Ethernet interface (fxp0) and to the Fast Ethernet 12-port and 48-port Physical Interface Cards (PICs).

Re: [j-nsp] monitor

This command monitor only traffic originated or terminated on local routing engine. You do not see packet which transit through the router (received on one interface and send via other) 2007/9/5, M.Mihailidis [EMAIL PROTECTED]: hello guys i want to monitor a interface to see what source

Re: [j-nsp] monitor

and how can i see traffic transit the router??? - Original Message - From: Rafał Szarecki To: M.Mihailidis Cc: juniper-nsp@puck.nether.net Sent: Wednesday, September 05, 2007 1:22 PM Subject: Re: [j-nsp] monitor This command monitor only traffic originated or terminated

[j-nsp] VPLS using targeted ldp

Hi everyone, Does Juniper router (M series, J series) support VPLS using targeted LDP for signaling? In the documentation, only BGP signaling are covered. Thanks, ~Erwin ___ juniper-nsp mailing list juniper-nsp@puck.nether.net

Re: [j-nsp] VPLS using targeted ldp

JUNOS 8.4 release Erwin D wrote: Hi everyone, Does Juniper router (M series, J series) support VPLS using targeted LDP for signaling? In the documentation, only BGP signaling are covered. Thanks, ~Erwin ___ juniper-nsp mailing list

Re: [j-nsp] monitor

Well. In sens of packet sniff you can't. What you can do, you can write firewall filter with action sample or log. and apply them on interface. 2007/9/5, M.Mihailidis [EMAIL PROTECTED]: and how can i see traffic transit the router??? - Original Message - *From:* Rafał Szarecki

Re: [j-nsp] monitor

Hi, You can not see the traffic transiting the router using the monitor command. IMHO, the workaround is implement some sort of port mirroring, etc. Thanks, ~Erwin On 9/5/07, M.Mihailidis [EMAIL PROTECTED] wrote: and how can i see traffic transit the router???

Re: [j-nsp] JUNOSe Cross-LM LACP?

Hi Rafał, so in essence there is no way to use a 2GBps LAG on an ERX700 or 1400? Thanks again, sven03 Mit freundlichen Gruessen i. A. Sven Juergensen Fachbereich Informationstechnologie KielNET GmbH Gesellschaft fuer Kommunikation Preusserstr. 1-9, 24105 Kiel Telefon : 0431 / 2219-053

Re: [j-nsp] Class of Service help on T-series w/8.2R1.7

Still having issues with CoS, specifically my classifier. If I explicitly force all traffic on a given logical unit to forwarding-class ef-high-fc (at [edit class-of-service interface] heirarchy), it works as expected. All traffic on that interface ends up in the right forwarding class.

Re: [j-nsp] Class of Service help on T-series w/8.2R1.7

What kind of tester are you using? If your tester is capable of doing pings I can suggest following - reconfigure one of vlans to be normal interface (not part of VPLS instance) and assing IP address to it; configure IP address in your test device from same subnet; try pinging router's IP

Re: [j-nsp] Class of Service help on T-series w/8.2R1.7

What you observe is absolutly correct. For incoming packtes L2 header is strip on ingress PIC, then forwarder to RE in private encapsulation (this is also Eth, but used internaly, so this is totaly new independent header). I understand Angel suggestion as way to verify recived traffic - if they

Re: [j-nsp] Class of Service help on T-series w/8.2R1.7

Moved all code-points to af-low-fc forwarding class in classifier, and am seeing same bad behaviour. Suspecting p-bit recognition again...will test against another platform to see if they're being honoured there. classifiers { ieee-802.1 trial { inactive: forwarding-class