[Xorp-users] PIM SM and VLAN
Eric S. Johnson
esj at cs.fiu.edu
Thu Feb 4 14:56:39 PST 2010
chicho.mancho at gmail.com said:
> This configuration is working the protocol goes up. PIM neighbor
> says the same thing - UP.
> Then I made a configuration without configuring PIM, but with VLAN
> vif:
Interesting. I hit this just the other day...
interface eth0 {
vif "eth0.xx" {
disable: false
vlan {
vlan-id: xx
}
address x.x.x.x {
prefix-length: xx
disable: false
}
}
vif "eth0.yy" {
disable: false
vlan {
vlan-id: yy
}
address yy.yy.yy.yy {
prefix-length: yy
disable: false
}
}
style declarations would not work with plumbing config like this
plumbing {
mfea4 {
interface eth0 {
vif "eth0.xx" {
disable: false
}
vif "eth0.yy" {
disable: false
}
}
interface register_vif {
vif register_vif {
disable: false
}
}
}
}
It wouldn't let me commit it.
But if your interface configs are like this
interfaces {
interface "eth0.xx" {
description: ""
disable: false
discard: false
unreachable: false
management: false
vif "eth0.xx" {
disable: false
address xx.xx.xx.xx {
prefix-length: xx
disable: false
}
}
}
interface "eth0.yy" {
description: ""
disable: false
discard: false
unreachable: false
management: false
vif "eth0.yy" {
disable: false
address yy.yy.yy.yy {
prefix-length: yy
disable: false
}
}
}
}
and your plumbing is
plumbing {
mfea4 {
disable: false
interface "eth0.xx" {
vif "eth0.xx" {
disable: false
}
}
interface "eth0.yy" {
vif "eth0.yy" {
disable: false
}
}
interface "register_vif" {
vif "register_vif" {
disable: false
}
}
}
}
It takes it fine and works.
This is on CentOS linux 5.4 with kernel 2.6.18-164.6.1.el5
Odd eh? In either case I had let CentOS create the vlans (but not
assign layer 3 addresses) before starting xorp.
A post to this list last year from Pavlin Radoslavov was what made me think
to try that.
http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2009-February/003032.html
So I guess it is a known bug.
E
More information about the Xorp-users
mailing list