I have had a little trouble with the routing instance of a virtual switch. The trouble is that it does something I've never seen my srx300 do. It gets stuck in dhcp apipa and is not accessible. I did not send it to rescue. I had to roll it back, which if I had chosen to do(rescue), is dangerous. But still perhaps it would be fine given a full reset. So a word to the wise. Make sure apipa is a policy before this. Does anyone actually have this working.
Can someone explain if other parts can work in this statement? It seems skimpy. My symptoms are:
-
Srx not accessible through web.
-
DHCP only gives apipa addresses.
-
Can only rollback history.
As with the web accessibility the srx seems to choke inherently and this shows to be true with virtual switch. But other problems arise. Can anyone give any advice?
srx300-c xfinity model
does not have stp, mstp, etc.
15.1X49-D60.7
MyVRSwitch {
instance-type virtual-switch;
access {
address-assignment {
neighbor-discovery-router-advertisement p4;
pool p1 {
family inet {
network 192.168.1.0/24;
}
}
pool p2 {
family inet6 {
prefix 2001:558::0/64;
}
}
pool p3 {
family inet6 {
prefix 2601:204::0/64;
}
}
pool p4 {
family inet6 {
prefix fe80::0/64;
}
}
}
}
vrf-advertise-selective {
family {
inet-mvpn;
inet6-mvpn;
}
}
forwarding-options {
load-balance {
per-prefix {
hash-seed 24051;
}
}
}
}
}
------------------------------
Adrian Aguinaga
B.S.C.M. I.T.T. Tech
(Construction Management)
A.A.S. I.T.T. Tech
(Drafting & Design)
------------------------------