Switching

Hi all,

I'm new to Juniper switch and I'm having trouble changing hte default Vlan (0) IP address (192.168.1.3) on a EX4200-F through the CLI.

I've tried "set interface vlan unit 0 family inet address 10.100.0.215/24" but it returns the error "incompatible with interface assigned with address".

Thanks in advance I guess I'm just usind the wrong syntax.

Louise

Can you send the output of the vlan and interfaces configuration?

=====

If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.

Hi,

I like to use the following CLI command to change IP address:

replace pattern <old-ip-address> with <new-ip-adddress>

--
Click the star for kudos if you think I earned it.
If this post solves your problem, please mark this post as "Accepted Solution".

Cheers I'll keep that tip for future use. I tried it and it did change the IP but still didn't asign to the default Vlan.

Louise

What do you mean it's not assigned?

Can you send the relavant  'show interface vlan.UNIT' and 'show vlan <VLAN>'?

=====

If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.

In case you didn't fix it until now, this is what you need to do:

{master:0}[edit]
root@EX# delete interfaces vlan.0 family inet dhcp                   

{master:0}[edit]
root@EX# set interfaces vlan.0 family inet address 10.100.0.215/24    

{master:0}[edit]
root@EX#commit

=====

If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.

Thanks. Worked a treat, however I still can't ping the 10.100.0.215 ip addrees. 

I can however ping all the other Vlans 10.100.1.215, 10.100.2.215 and 10.100.3.215

Would the vme and vme.0 have any effect?

{master:0}
root@EX4200_Level_1> show interfaces vlan terse
Interface Admin Link Proto Local Remote
vlan up up
vlan.0 up up inet 10.100.0.215/24
vlan.1 up up inet 10.100.1.215/24
vlan.2 up up inet 10.100.2.215/24
vlan.3 up up inet 10.100.3.215/24

{master:0}

root@EX4200_Level_1> show interfaces terse
Interface Admin Link Proto Local Remote
ge-0/0/0 up up
ge-0/0/0.0 up up eth-switch
ge-0/0/1 up up
ge-0/0/1.0 up up eth-switch
ge-0/0/2 up up
ge-0/0/2.0 up up eth-switch
ge-0/0/3 up up
ge-0/0/3.0 up up eth-switch
ge-0/0/4 up up
ge-0/0/4.0 up up eth-switch
ge-0/0/5 up up
ge-0/0/5.0 up up eth-switch
ge-0/0/6 up up
ge-0/0/6.0 up up eth-switch
ge-0/0/7 up up
ge-0/0/7.0 up up eth-switch
ge-0/0/8 up up
ge-0/0/8.0 up up eth-switch
ge-0/0/9 up up
ge-0/0/9.0 up up eth-switch
ge-0/0/10 up up
ge-0/0/10.0 up up eth-switch
ge-0/0/22 up up
ge-0/0/22.0 up up eth-switch
ge-0/0/23 up up
ge-0/0/23.0 up up eth-switch
vcp-0 up down
vcp-0.32768 up down
vcp-1 up down
vcp-1.32768 up down
bme0 up up
bme0.32768 up up inet 128.0.0.1/2
128.0.0.16/2
128.0.0.32/2
tnp 0x10
dsc up up
gre up up
ipip up up
lo0 up up
lo0.16384 up up inet 127.0.0.1 --> 0/0
lsi up up
me0 up down
me0.0 up down eth-switch
mtun up up
pimd up up
pime up up
tap up up
vlan up up
vlan.0 up up inet 10.100.0.215/24
vlan.1 up up inet 10.100.1.215/24
vlan.2 up up inet 10.100.2.215/24
vlan.3 up up inet 10.100.3.215/24
vme up down
vme.0 up down inet

There is no relation between vme interface being down and not being able to ping your own IP address from RVI.

Can you do 'show route 10.100.0.215' and 'ping 10.100.0.215' and send us the output?

=====

If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.

Ok. Just dosen't make any sense! The EX4200 can ping all of its own interface IP's but the 10.100.0.215 can't be pinged from other switches in the network, but all the other Vlans 10.100.1.215, 10.100.2.215 & 10.100.3.215 can be pinged.

Show route ouput from the EX4200 fibre switch in question

root@EX4200_Level_1> show route 10.100.0.215

inet.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.100.0.215/32 *[Local/0] 23:12:25
Local via vlan.0

{master:0}
root@EX4200_Level_1> show route 10.100.1.215

inet.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.100.1.215/32 *[Local/0] 1d 04:29:54
Local via vlan.1

{master:0}
root@EX4200_Level_1> show route 10.100.2.215

inet.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.100.2.215/32 *[Local/0] 1d 04:30:22
Local via vlan.2

{master:0}
root@EX4200_Level_1> show route 10.100.3.215

inet.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.100.3.215/32 *[Local/0] 1d 04:30:32
Local via vlan.3

This is the show route from one of the other EX2200 switches in the network

root@EX2200_GND_A> show route 10.100.0.215

inet.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.100.0.0/24 *[Direct/0] 2d 02:42:05
> via vlan.0

{master:0}

inet.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.100.1.0/24 *[Direct/0] 1d 06:41:29
> via vlan.1

{master:0}
root@EX2200_GND_A> show route 10.100.2.215

inet.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.100.2.0/24 *[Direct/0] 1d 06:09:58
> via vlan.2

{master:0}
root@EX2200_GND_A> show route 10.100.3.215

inet.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.100.3.0/24 *[Direct/0] 1d 06:10:01
> via vlan.3

This is the ping from the EX4200 fibre switch in question to 10.100.0.215 and 10.100.1.215 

root@EX4200_Level_1> ping 10.100.0.215
PING 10.100.0.215 (10.100.0.215): 56 data bytes
64 bytes from 10.100.0.215: icmp_seq=0 ttl=64 time=2.301 ms
64 bytes from 10.100.0.215: icmp_seq=1 ttl=64 time=0.125 ms
64 bytes from 10.100.0.215: icmp_seq=2 ttl=64 time=0.230 ms
64 bytes from 10.100.0.215: icmp_seq=3 ttl=64 time=0.175 ms
64 bytes from 10.100.0.215: icmp_seq=4 ttl=64 time=0.169 ms
64 bytes from 10.100.0.215: icmp_seq=5 ttl=64 time=0.174 ms
64 bytes from 10.100.0.215: icmp_seq=6 ttl=64 time=0.286 ms
64 bytes from 10.100.0.215: icmp_seq=7 ttl=64 time=0.179 ms
^C
--- 10.100.0.215 ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.125/0.455/2.301/0.699 ms

{master:0}
root@EX4200_Level_1> ping 10.100.1.215
PING 10.100.1.215 (10.100.1.215): 56 data bytes
64 bytes from 10.100.1.215: icmp_seq=0 ttl=64 time=1.968 ms
64 bytes from 10.100.1.215: icmp_seq=1 ttl=64 time=0.184 ms
64 bytes from 10.100.1.215: icmp_seq=2 ttl=64 time=0.129 ms
64 bytes from 10.100.1.215: icmp_seq=3 ttl=64 time=0.177 ms
64 bytes from 10.100.1.215: icmp_seq=4 ttl=64 time=0.128 ms
^C
--- 10.100.1.215 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.128/0.517/1.968/0.726 ms

This is the ping from one of the other EX2200 switches in the network to 10.100.0.215 and 10.100.1.215 

root@EX2200_GND_A> ping 10.100.0.215
PING 10.100.0.215 (10.100.0.215): 56 data bytes
^C
--- 10.100.0.215 ping statistics ---
159 packets transmitted, 0 packets received, 100% packet loss

{master:0}
root@EX2200_GND_A> ping 10.100.1.215
PING 10.100.1.215 (10.100.1.215): 56 data bytes
64 bytes from 10.100.1.215: icmp_seq=0 ttl=64 time=5.210 ms
64 bytes from 10.100.1.215: icmp_seq=1 ttl=64 time=3.603 ms
64 bytes from 10.100.1.215: icmp_seq=2 ttl=64 time=3.452 ms
64 bytes from 10.100.1.215: icmp_seq=3 ttl=64 time=4.623 ms
64 bytes from 10.100.1.215: icmp_seq=4 ttl=64 time=3.606 ms
64 bytes from 10.100.1.215: icmp_seq=5 ttl=64 time=3.389 ms
64 bytes from 10.100.1.215: icmp_seq=6 ttl=64 time=3.241 ms
64 bytes from 10.100.1.215: icmp_seq=7 ttl=64 time=3.283 ms
64 bytes from 10.100.1.215: icmp_seq=8 ttl=64 time=3.294 ms
64 bytes from 10.100.1.215: icmp_seq=9 ttl=64 time=3.296 ms
64 bytes from 10.100.1.215: icmp_seq=10 ttl=64 time=3.385 ms
64 bytes from 10.100.1.215: icmp_seq=11 ttl=64 time=4.481 ms
64 bytes from 10.100.1.215: icmp_seq=12 ttl=64 time=3.702 ms
64 bytes from 10.100.1.215: icmp_seq=13 ttl=64 time=4.253 ms
^C
--- 10.100.1.215 ping statistics ---
14 packets transmitted, 14 packets received, 0% packet loss
round-trip min/avg/max/stddev = 3.241/3.773/5.210/0.595 ms

I see that the trunk interface from EX4200_Level_1 is configured like this:

ge-0/0/0 {
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members all;

Is the interface from EX2200_GND_A configured in the same way?

Make sure that the trunk interfaces are configured in the same way. Also the configuration of default vlan. Seems to be some sort of tagging problem of the default vlan.

=====

If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.

I think I know whats wrong. All the other 15 switches have had the trunk ports set with the default vlan as Native but the fibre switch hasn't.

Do you know the command/s to set the default vlan as Native on all ports?

Yes, I was suspecting that this was the problem.

You are looking for this command:

set interfaces ge-0/0/1 unit 0 family ethernet-switching native-vlan-id 1

Also, you can apply a group for all interfaces:

{master:0}[edit]
root@EX# show groups
NATIVE {
    interfaces {
        <ge-0/*/*> {
            unit 0 {
                family ethernet-switching {
                    native-vlan-id 1;
                }
            }
        }
    }
}

{master:0}[edit]
root@EX# show interfaces ge-0/0/0  
disable;
unit 0 {
    bandwidth 10m;
    family ethernet-switching;
}

{master:0}[edit]
root@EX# show interfaces ge-0/0/0 | display inheritance
disable;
unit 0 {
    bandwidth 10m;
    family ethernet-switching;
}

{master:0}[edit]
root@EX# set apply-groups NATIVE

{master:0}[edit]
root@EX# show interfaces ge-0/0/0 | display inheritance     
disable;
unit 0 {
    bandwidth 10m;
    family ethernet-switching {
        ##
        ## '1' was inherited from group 'NATIVE'
        ##
        native-vlan-id 1;
    }
}

{master:0}[edit]
root@EX#

=====

If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.

Thanks, I'll try that in the morning, but shouldn't the native-vlan-id be 0 the match the default vlan?

Louise

Not sure what it should be. You have to configure it as it is on other devices. You can specify straight away the 'default' keyword. 0 is not a valid value for native vlan id. Just make sure that the port is trunk:

{master:0}[edit]
root@EX# show interfaces ge-0/0/1  
unit 0 {
    family ethernet-switching {
        port-mode trunk;
        native-vlan-id default;
    }
}

{master:0}[edit]
root@EX# commit check                                                
warning: Could not connect to fpc-1 : Can't assign requested address
warning: Cannot connect to other RE, ignoring it
configuration check succeeds

{master:0}[edit]
root@EX#

=====

If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.

I couldn't wait so I just RDP into the site and tried it, all looking good now with full connectivity on all ports 0/0/0 through to 0/0/12.

Thanks so much for your help.

set interfaces ge-0/0/0 unit 0 family ethernet-switching native-vlan-id default

Louise 

Hi is this what you mean?

It appears the DHCP comment is causing me an issue.

I'm trying to set the default Vlan to 10.100.0.215/24 by using this syntax:

{master:0}[edit interfaces]

root@EX4200_Level_1# set vlan unit 0 family inet address 10.100.0.215/24

but I get this error when i do a commit check

root@EX4200_Level_1# commit check
[edit interfaces vlan unit 0 family inet]
'dhcp'
Incompatible with interface assigned with address
error: configuration check-out failed: (statements constraint check failed)

root@EX4200_Level_1# show vlans
Vlan-1 {
vlan-id 1;
l3-interface vlan.1;
}
Vlan-2 {
vlan-id 2;
l3-interface vlan.2;
}
Vlan-3 {
vlan-id 3;
l3-interface vlan.3;
}
default {
l3-interface vlan.0;
}

root@EX4200_Level_1# show interfaces vlan
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ex4200-24f;
}
}
}
unit 1 {
family inet {
address 10.100.1.215/24;
}
}sh
unit 2 {
family inet {
address 10.100.2.215/24;
}
}
unit 3 {
family inet {
address 10.100.3.215/24;
}
}

root@EX4200_Level_1# show interfaces
ge-0/0/0 {
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members all;
}
}
}
}
ge-0/0/1 {
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members all;
}
}
}
}