There is a major change on layer 2 configuration in this upgrade from the old ethernet switching model to the new ELS (enhanced layer 2 services) method.
You can run your existing configuration through the conversion tool.
https://www.juniper.net/customers/support/configtools/elstranslator/index.jsp
And see the overview of the ELS system here.
http://www.juniper.net/techpubs/en_US/junos/topics/task/configuration/getting-started-els.html
I'm a little confused now over the exact nature of the current problem.
I assume this switch was a member of a VC and now is not.
You are trying to use the old XE VC port as a normal XE port.
What seems to be confusing is which port we are talking about your title has xe-2/3 which I assume is xe-0/2/3
your command in first post has xe-0/1/3
But in any case the VC command do show that no interface is currently setup as a VC port.
So I think the next step is to verify that your interface is seen:
Does the interface show up using
show interfaces terse xe-#/#/#
this will verify that the device sees your hardware on the expected port
Is the optics module recognized:
port xe-0/2/3
show chassis pic fpc-slot 0 pic-slot 2
or make pic slot 1 if the interface is xe-0/1/3
are there optics data
show interface diagnostics optics xe-0/2/3
Hello,
Most likely the reason in "incompatibility configuration"
Try to use command "commit full" and you will get the answer where is the problem , correct configuration and make "commit full" again.
spuluka wrote:I'm a little confused now over the exact nature of the current problem.
I assume this switch was a member of a VC and now is not.
You are trying to use the old XE VC port as a normal XE port.
What seems to be confusing is which port we are talking about your title has xe-2/3 which I assume is xe-0/2/3
your command in first post has xe-0/1/3
But in any case the VC command do show that no interface is currently setup as a VC port.
So I think the next step is to verify that your interface is seen:
Does the interface show up using
show interfaces terse xe-#/#/#
this will verify that the device sees your hardware on the expected port
Is the optics module recognized:
port xe-0/2/3
show chassis pic fpc-slot 0 pic-slot 2
or make pic slot 1 if the interface is xe-0/1/3
are there optics data
show interface diagnostics optics xe-0/2/3
Hi, spuluka.
I assume the main problem is my poor english. sorry.
No, this switch had never been member of VC -it's standalone switch.
ports xe-0/1/0 and xe-0/1/1 are in use from the first day and xe-0/1/2 and xe-0/1/3 was empty until now.
and I'm talking about those ports and here is no any xe-0/2/x ports.
here is output:
show chassis hardware
Hardware inventory:
Item Version Part number Serial number Description
Chassis GD0213446061 EX3300-24T
Routing Engine 0 REV 14 750-034299 GD0213446061 EX3300 24-Port
FPC 0 REV 14 750-034299 GD0213446061 EX3300 24-Port
CPU BUILTIN BUILTIN FPC CPU
PIC 0 BUILTIN BUILTIN 24x 10/100/1000 Base-T
PIC 1 REV 14 750-034299 GD0213446061 4x GE/XE SFP+
Xcvr 0 REV 01 740-031838 APF13400061JH0 SFP+-10G-CU5M
Xcvr 1 REV 01 740-031838 APF1337006976L SFP+-10G-CU5M
Xcvr 3 REV 01 740-030077 APF13360028MY0 SFP+-10G-CU3M
Power Supply 0 PS 100W AC
Fan Tray Fan Traythis is problem port
Xcvr 3 REV 01 740-030077 APF13360028MY0 SFP+-10G-CU3M
today I've rebooted the switch, but no luck.
show interfaces terse xe-0/1/3 Interface Admin Link Proto Local Remote xe-0/1/3 up down xe-0/1/3.0 up down eth-switch
show chassis pic fpc-slot 0 pic-slot 1
FPC slot 0, PIC slot 1 information:
Type 4x GE/XE SFP+ Builtin
State Online
Uptime 13 hours, 50 minutes, 47 seconds
PIC port information:
Fiber Xcvr vendor Wave- Xcvr
Port Cable type type Xcvr vendor part number length Firmware
0 10GBASE CU 5M n/a Amphenol 584990006 n/a 0.0
1 10GBASE CU 5M n/a Amphenol 584990006 n/a 0.0
3 10GBASE CU 3M n/a Amphenol 584990002 n/a 0.0
show interfaces diagnostics optics xe-0/1/3
Physical interface: xe-0/1/3
Optical diagnostics : N/A
Thanks for the update. You appear to have a hardware problem. This could be either the optic (DAC cable in your case) or the expansion module.
Try disconnecting the DAC if it is still inserted and running the port tests again. If the port shows up the cable is defective.
If this is still down, try removing the expansion module. Keep it out for 2 minutes and insert it again. Now look for the interface again before inserting the DAC cable.
If this is still missing then the module is defective.
DAC is fine - I have another ex3300 and tested DAC there - it's fine.
also I've tested this DAC at xe-0/1/1 of this ex3300 - it's working.
which expasion module your are talking about? ex3300 has four 10gbe builtin ports - there is no expansion modules.
This seems likely to be a hardware issue with the switch then.
One last check, are these combo ports that can go either ge or xe?
See if you have a configuration or a recognized port in the ge version.
show interfaces terse ge-0/1/2
show configuration interfaces ge-0/1/2
Assuming these are also not present then your hardware has failed. You will need to open a JTAC ticket on the support site to verify and get an RMA replacement.
You are right - there was config for ge-0/1/2 and ge-0/1/3 ports.
but after deleting this xe-0/1/3 is still down.
will try to reconnect DAC a little later.
biraj wrote:
You can configure an access-port group for all the edge ports on the access switch. Then the group as a whole can be configured for bpdu-block-on-edge.
I figured out how to configure the group. It should be something like this:
protocols {
rstp {
bpdu-block-on-edge;
}
}
ethernet-switching-options {
bpdu-block {
disable-timeout 10;
}
}
I tought to put there also the "edge" setting but I cannot figure out how to do this.
Shoudl I set any port one by one when I put them in the group?
[edit interfaces ge-0/0/1]
user@router# show
unit100 {
vlan-id 100;
familyinet {
address /24;
}
}
[edit interfaces ge-0/0/1]
user@router# commit check
[edit interfaces ge-0/0/1]
'unit 100'
Only unit0 is valid for this encapsulation
error: configuration check-out failed
Referring to the above, you are unable to commit the configuration for the ge-0/0/1 interface.
What must you do to commit the configuration?
A. You must set the vlan-tagging parameter under the [edit interfaces ge-0/0/1] hierarchy.In the example above, the answer says we need to be in the edit interfaces ge-0/0/1 hierarchy.
I was under the impression we are in that hierarchey, from the edample.
Any help on this.
What the answer is saying is to enable vlan-tagging on the ge-0/0/1 interface. To enable vlan-tagging you need to navigate to the [edit interfaces ge-0/0/1] hierachy or you can do this from the top level as well i.e. set interfaces ge-0/0/1 unit vlan-tagging
OK, but I thought it was already at the hierarchy.
I have two more ex3300.
I'd deleted VC ports 0/1/2 and 0/1/3 at each of it.
and the same issue there.
only xe-0/1/0 and xe-0/1/1 are working as Network Ports.
I think that is not hardware malfunction.
it's software bug or something like that.
You can use configuration groups for this purpose, however I would suggest that using configuration groups is an advanced configuration feature that if you plan on using it, you must understand how it will be displayed or not, and use it consistently accros the network so as to avoid confusion.
set protocols rstp interface all edge
set protocols rstp interface ge-0/0/0.0 disable (any interface that you wish to disable rstp on)
Yes you are under the heirarchy, but the option vlan-tagging was not configured. So this opotion is configured at the physical interface heirarchy as shown
You must set the vlan-tagging parameter under the [edit interfaces ge-0/0/1]
any configuration under the unit numbers would represent logical properties
Without eabling vlan-tagging, the only logical unit number you can configure is unit 0. Enabling vlan-tagging allows you to configure unit 0-4095 if the switch allows it.
set interfaces ge-0/0/1 vlan-tagging
BTW you will also get this error if you try to configure family ethernet-switching under any unit number other than 0
I am using ports 2 and 3. The defaults.
show virtual-chassis vc-port all-members
root> show virtual-chassis vc-port all-members
fpc0:
--------------------------------------------------------------------------
Interface Type Trunk Status Speed Neighbor
or ID (mbps) ID Interface
PIC / Port
1/2 Configured 5 Up 40000 1 vcp-255/1/2
1/3 Configured 5 Up 40000 1 vcp-255/1/3
fpc1:
--------------------------------------------------------------------------
Interface Type Trunk Status Speed Neighbor
or ID (mbps) ID Interface
PIC / Port
1/2 Configured 5 Up 40000 0 vcp-255/1/2
1/3 Configured 5 Up 40000 0 vcp-255/1/3
{master:0}
Hello,
I am adding an IDS solution to our EX4400 swithing network. We would like to set up the IDS unit on a mirror Port as Listening to activity on the network. We have approximate 15 VLANs, but only need to collect information from 2 VLANS.
What is the recommendation on Port Mirroring. VLAN, Ingress port , Egress port? I am looking at the VLAN mirror, will that be too much for one port to mirror?
Thanks
I've searched but cannot find it... What is the earliest Junos a EX4200-48T Rev F will run? This is the later revision of the 4200 that requires the new boot loader.
For a customer who is locked on 10.2R2.11 (don't ask...), we're attempting to add these switches to their VC but I cannot seem to get the 10.2R2.11 code to work. It crashes with a Panic: Found Unsupported PCI Device and then dumps the usual hardware loader- stopped at kdb_enter+0x1a4:
10.4.r6 loads fine, but is there possibly a trick to getting this old version to load? Is it just not going to work?
TIA
What Junos Version? What does show virtual chassis output?