Here are some previous power supply only replacements
2016-0908-0698
2016-0822-0406
2016-0105-0402
ok thanks
Hi,
To have a proper web management working you have to follow below steps :
> copy both packages under /var/tmp
> request system software add no-validate /var/tmp/jweb-15.1R5.5-signed.tgz (required by jweb-ex-app-15.1A3-signed.tgz)
> request system software add no-validate /var/tmp/jweb-ex-app-15.1A3-signed.tgz
# set system servies web-management http (it's a hidden CLI , just copy/paste)
Here we go :
http://1.1.1.1 (Loopback Address)
Make sure there is no firewall filter blocking your http traffic towards the EX RE.
I's working fine for me on EX8208. very nice web interface.
I hope it helps. good luck.
BR/
Zakour
Hi,
Here is the link to official documentation from Juniper Portal :
J-Web Application Package for EX Series
Good Lecture.
BR/
Zakour
HI Velu
Are you saying you are just configuring MF without any COS profile?
Did you check this example
Thanks
Partha
Multified classifier only classifies the traffic it does not manipulate the packet header You should check to see if it is being classified. You have not aded the following:
Hi,
We have been trying to get this setup working properly:
Customer(cisco) <-> EX4300 <-> MX960 <-> MX80 <-> Cusomer(cisco)
Between the MX routers there is a l2circuit.
EX config:
# show interfaces ge-0/0/4
description "customer interface";
flexible-vlan-tagging;
native-vlan-id 400;
encapsulation extended-vlan-bridge;
unit 400 {
vlan-id-list 1-4094;
input-vlan-map push;
output-vlan-map pop;
}
# show interfaces xe-0/0/32
description "Uplink to MX960";
flexible-vlan-tagging;
encapsulation extended-vlan-bridge;
unit 100 {
description "ge-0/0/0 QinQ";
vlan-id 100;
}
unit 200 {
description "ae0 QinQ";
vlan-id 200;
}
unit 300 {
description "ge-0/0/3 QinQ";
vlan-id 300;
}
unit 400 {
description "ge-0/0/4 QinQ";
vlan-id 400;
}
unit 500 {
description "ge-0/0/5 QinQ";
vlan-id 500;
}
unit 4094 {
description mgmt;
vlan-id 4094;
}
# show vlans
MGMT {
vlan-id 4094;
interface xe-0/0/32.4094;
l3-interface irb.4094;
}
default {
vlan-id 1;
l3-interface irb.0;
}
v100 {
interface xe-0/0/32.100;
interface ge-0/0/0.100;
}
v200 {
interface xe-0/0/32.200;
interface ae0.200;
}
v300 {
interface xe-0/0/32.300;
interface ge-0/0/3.300;
interface ge-0/0/6.300;
}
v400 {
interface xe-0/0/32.400;
interface ge-0/0/4.400;
switch-options {
no-mac-learning;
}
}
v500 {
interface ge-0/0/5.500;
interface xe-0/0/32.500;
}
# show protocols layer2-control mac-rewrite
interface ge-0/0/4 {
protocol {
vtp;
cdp;
ieee8023ah;
lacp;
lldp;
mvrp;
gvrp;
vstp;
}
}
MX960 config:
# show interfaces xe-0/0/5
flexible-vlan-tagging;
mtu 9192;
encapsulation flexible-ethernet-services;
unit 400 {
description "to cust";
encapsulation vlan-ccc;
vlan-tags outer 400;
family ccc {
mtu 1526;
}
}
# show protocols l2circuit
neighbor 10.10.1.1 {
interface xe-0/0/5.400 {
virtual-circuit-id 1;
description test;
encapsulation-type ethernet;
}
}MX80 config:
# show protocols l2circuit
neighbor 10.10.1.100 {
interface ge-1/0/8.0 {
virtual-circuit-id 1;
description test;
encapsulation-type ethernet;
}
}
# show interfaces ge-1/0/8
description "customer interface";
mtu 1518;
encapsulation ethernet-ccc;
unit 0 {
family ccc;
}We recently replaced a MX80 with the MX960 and EX4300 to provide 1G ports. So the idea here was to run q-in-q on the trunk to the EX4300 and tunnel any l2 protocols that the customer is using since the switch itself is not as transparent as the old MX80 solution. The customer interface is configured as a trunk with CDP and LACP but none of the protocols are working for them. Any ideas? Thanks!
Trying to setup OSPF for the three links to the MPLS cloud.
Would the code below work.?
protocols {
ospf {
area 0.0.0.0 {
interface lo0.0 passive;
interface ge-0/0/21.0;
interface ge-0/0/22.0;
interface ge-0/0/23.0;
}
}
policy-statement ospf {
term ospf {
from {
protocol ospf;
interface [ ge-0/0/21.0 ge-0/0/22.0 ge-0/0/23.0 ];
}
}
then accept;
}
I have added the forwarding class and loss priority on the MF and could see the packets being classified. so the purpose of setting dscp action modifier on the firewall filter is only used for the classification ?
so, if we need to mark the packets header then it has to be done using the re-write dscp at the egress interface.
The fix - send them a picture of the power supply with p/n and s/n showing (thanks to my support guy for thinking of that). Support updates the database so that shows as a serial number, and then passes it to the RMA people to provide an RMA. Makes me wonder - something that could almost be automated takes multiple people at Juniper to touch it, send a dozen or more emails, requires me to keep asking, making phone calls, bugging my local rep, etc. Hopefully this is an exception, not a sign of the way things are from now on.
Hello,
Bit by bit:
starlog wrote:
Trying to setup OSPF for the three links to the MPLS cloud.
Would the code below work.?
protocols { ospf { area 0.0.0.0 { interface lo0.0 passive; interface ge-0/0/21.0; interface ge-0/0/22.0; interface ge-0/0/23.0; } }
This code should work UNLESS Level3 uses OSPF p2p links. In that case (OSPF broadcast links on Your side and OSPF p2p links on Level3 side) this code won't work.
starlog wrote:
policy-statement ospf { term ospf { from { protocol ospf; interface [ ge-0/0/21.0 ge-0/0/22.0 ge-0/0/23.0 ]; } } then accept; }
You did not show us where & how this policy is applied so no opinion.
HTH
Thx
Alex
HI
Can you send us the config from both sides?
Thanks
Partha
HI
I can give you an example , hope this helps.
QinQ ELS Configs
+------------------+ +------------------+ +--------------------+ +--------------------+
| EX2200 +---------+ QFX-5100 +---------+ EX3300 +---------+ EX2200 |
| | | | | | | |
+----------------0/1/0 0/0/0-------------0/0/23 0/1/0-----------------0/0/0 0/1/0-----------------+
+
EX2200
root@2200-Left> show configuration vlans
v200 {
vlan-id 200;
interface {
ge-0/1/0.0;
}
l3-interface vlan.200;
}
vlans {
vlan-id 100;
interface {
ge-0/0/0.0;
ge-0/1/0.0;
}
}
{master:0}
root@2200-Left> show configuration interfaces vlan.200
family inet {
address 20.20.20.1/24;
}
QFX5100
root@5100# show interfaces ge-0/0/0
flexible-vlan-tagging;
encapsulation extended-vlan-bridge;
unit 4000 {
vlan-id-list 100-200;
input-vlan-map push;
output-vlan-map pop;
}
{master:0}[edit]
root@5100# show interfaces ge-0/0/23
flexible-vlan-tagging;
encapsulation extended-vlan-bridge;
unit 4000 {
vlan-id 4000;
}
{master:0}[edit]
root@5100# show vlans
Svlan {
interface ge-0/0/23.4000;
interface ge-0/0/0.4000;
}
EX3300
"root@3300# show interfaces ge-0/1/0
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members 4000;
}
}
}
{master:0}[edit]
root@3300# show interfaces ge-0/0/0
unit 0 {
family ethernet-switching {
port-mode access;
vlan {
members 4000;
}
}
}
{master:0}[edit]
root@3300# show vlans
Svlan {
vlan-id 4000;
##
## Warning: requires 'dot1q-tunneling' license
##
dot1q-tunneling {
customer-vlans 100 200;
layer2-protocol-tunneling {
all;
}
}
}
{master:0}[edit]
root@3300# show ethernet-switching-options
dot1q-tunneling {
ether-type 0x8100;
}
storm-control {
interface all;
}
EX2200
root@2200-Right# show interfaces ge-0/1/0
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members all;
}
}
}
[edit]
root@2200-Right# show vlans
v200 {
vlan-id 200;
l3-interface vlan.200;
}
[edit]
root@2200-Right# show interfaces vlan.200
family inet {
address 20.20.20.2/24;
}
Thanks
Partha
I will request the config from Level-3.
Alex,
You did not show us where & how this policy is applied so no opinion.
What are you meaning "applied" .?
thanks
Hello, there,
You showed us only the "ospf" policy definition under [edit policy-options].
For this policy definition to take effect, it has to be referenced under
[edit protocols ospf export]
or
[edit protocols bgp group BLAH export]
or
[edit protocols isis export]
or
[edit protocols rip export]
or
[edit routing-instances BLAH routing-options instance-import]
etc etc
You did not show us where else Your policy "ospf" is referenced so if it is not referenced anywhere then it is not applied.
If it is not applied, then it is not doing anything/having no effect.
HTH
Thx
Alex
Alex,
OK, lets see if I can share it.
protocols {
ospf {
traceoptions {
file OSPF_Troubleshooting;
inactive: flag error;
inactive: flag general;
inactive: flag hello;
inactive: flag event;
flag all;
}
export test;
area 0.0.0.0 {
inactive: area-range 10.11.9.0/24;
network-summary-export EXPORT-POLICY;
interface vlan.109;
inactive: interface vlan.102 {
passive;
}
inactive: interface vlan.103 {
passive;
}
interface lo0.0 passive;
interface xe-2/0/14.0;
interface ge-0/0/1.0;
interface ge-1/0/39.0;
}
}policy-options {
policy-statement EXPORT-POLICY {
term one {
from {
protocol static;
route-filter 10.1.0.0/16 orlonger;
route-filter 10.2.0.0/16 orlonger;
route-filter 10.3.0.0/16 orlonger;
route-filter 10.4.0.0/16 orlonger;
route-filter 10.5.0.0/16 orlonger;
route-filter 10.6.0.0/16 orlonger;
route-filter 10.7.0.0/16 orlonger;
route-filter 10.8.0.0/16 orlonger;
route-filter 10.9.0.0/16 orlonger;
route-filter 10.10.0.0/16 orlonger;
route-filter 10.11.0.0/16 orlonger;
}
then accept;
}
} policy-statement test {
term one {
from protocol direct;
then accept;
}
}
}
policy-statement ospf {
term ospf {
from {
protocol ospf;
interface [ ge-1/0/39.0 ge-0/0/1.0 xe-2/0/14.0 ];
}
}
then accept;
}
policy-statement test {
term one {
from protocol direct;
then accept;
}
}
}
Also this is what is in the Level-3 MPLS
! router ospf 100 router-id 100.100.9.2 log-adjacency-changes redistribute connected subnets redistribute static subnets redistribute bgp 65001 subnets route-map BGP2OSPF network 10.11.9.0 0.0.0.255 area 0 default-information originate distribute-list DENY-MGMT out !
! route-map OSPF2BGP permit 20 match ip address PERMIT-ALL !
I have an EX2200 switch that I have configured 4 vlans on - 203, 204, 209 and 215. I used the JWeb to configure it since I am not very familiar with the Junos CLI language.
I assigned vlan 209 to port 0, 204 to port 1, 203 to port 2 and 215 to port 3. My trunk port is port 47 and all vlans are get an ip address and can see the network on vlans 203 and 204 with no issue. I cannot get an ip address for vlans 209 and 215. They are all configured the same way.
You might want to post your whole config, after removing any sensitive items such as passwords.
Using the CLI Viewer in the J-Web Interface to View Configuration Text
## Last changed: 2015-02-18 07:30:27 EST
version 12.3R9.4;
system {
host-name BLAWS1005A;
time-zone EST5EDT;
root-authentication {
encrypted-password "$1$XNW1Nffa$4Nd34O1k83PLd7POKjF6A1";
}
services {
ssh {
protocol-version v2;
}
telnet;
netconf {
ssh;
}
web-management {
http;
}
dhcp {
traceoptions {
file dhcp_logfile;
level all;
flag all;
}
}
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;
}
}
}
chassis {
auto-image-upgrade;
}
interfaces {
ge-0/0/0 {
unit 0 {
family ethernet-switching {
port-mode access;
vlan {
members v209;
}
}
}
}
ge-0/0/1 {
unit 0 {
family ethernet-switching {
port-mode access;
vlan {
members v204;
}
}
}
}
ge-0/0/2 {
unit 0 {
family ethernet-switching {
port-mode access;
vlan {
members v203;
}
}
}
}
ge-0/0/3 {
unit 0 {
family ethernet-switching {
port-mode access;
vlan {
members v215;
}
}
}
}
ge-0/0/4 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/5 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/6 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/7 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/8 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/9 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/10 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/11 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/12 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/13 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/14 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/15 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/16 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/17 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/18 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/19 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/20 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/21 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/22 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/23 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/24 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/25 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/26 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/27 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/28 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/29 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/30 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/31 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/32 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/33 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/34 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/35 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/36 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/37 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/38 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/39 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/40 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/41 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/42 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/43 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/44 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/45 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/46 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/47 {
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members [ default v203 v204 v215 ];
}
}
}
}
ge-0/1/0 {
unit 0 {
family ethernet-switching;
}
}
ge-0/1/1 {
unit 0 {
family ethernet-switching;
}
}
ge-0/1/2 {
unit 0 {
family ethernet-switching;
}
}
ge-0/1/3 {
unit 0 {
family ethernet-switching;
}
}
me0 {
unit 0 {
family inet {
address 192.168.215.10/24;
}
}
}
vlan {
unit 0 {
family inet {
address 192.168.203.10/24;
}
}
}
}
snmp {
location Box5A;
contact BlairsIT;
community public {
authorization read-only;
}
}
routing-options {
static {
route 0.0.0.0/0 next-hop 192.168.203.2;
}
}
protocols {
igmp-snooping {
vlan all;
}
rstp;
lldp {
interface all;
}
lldp-med {
interface all;
}
}
ethernet-switching-options {
voip;
storm-control {
interface all;
}
}
vlans {
default {
vlan-id 1;
}
v203 {
vlan-id 203;
l3-interface vlan.0;
}
v204 {
vlan-id 204;
}
v209 {
vlan-id 209;
interface {
ge-0/0/47.0;
}
}
v215 {
vlan-id 215;
}
}
poe {
interface all;
}
