We ran into something interesting on the network today.
I just wanted to post this up as a heads up.
As most of you know, BCM 3.6 (200 and 400 chassis) comes with preconfigured UP addresses for the various interfaces.
LAN1
LAN2
WAN1
WAN2
DIALUP
But it has one additional UP address for a virtual interface (# 42) with default IP addy of 10.10.15.1
The only way to change this IP addy is through VNC, I cannot for the life of me find a way to see this thing in Unified Manager.
So if you have any subnets with 10.10.15.x on you network, and you use RIP2, you may loose connectivity during a RIP election (i.e REboot)
This discovery brought me down another path on 1000 chassis BCM's. The 1000 BCM's shipped with only one LAN interface, still has the virtual QOS interace enabled for LAN2. At IP addy 10.10.11.1. Again this interace cannot be changed through Unified manager but requires VNC.
Unfortunatley for us, we have 40 locations and our IP scheme on the WAN is 10.10.X.1 where X = locations 1 - 40. You can see our dilema with some routing issues. After turning these off, my locations at 10.10.15.1 and 10.10.11.1 work much better.
Consequently, there where issues on 3.0, 3.5 and 3.6 upgrades where DHCP would fail and actually corrupt the BCM. Nortel ITAS knew of this issue but could not pinpoint the cause. We had one such failure, on our BCM 10.10.11.1 (!). I wonder if this system failed the update of DHCP fucntions due to routing conflicts of just that ip address, resident, active and pingable. Yet not visable in Unified Manager !?!
Just a heads up incase any of you run with a 10.10.x.x scheme on your wan IP addys.
Gil
I just wanted to post this up as a heads up.
As most of you know, BCM 3.6 (200 and 400 chassis) comes with preconfigured UP addresses for the various interfaces.
LAN1
LAN2
WAN1
WAN2
DIALUP
But it has one additional UP address for a virtual interface (# 42) with default IP addy of 10.10.15.1
The only way to change this IP addy is through VNC, I cannot for the life of me find a way to see this thing in Unified Manager.
So if you have any subnets with 10.10.15.x on you network, and you use RIP2, you may loose connectivity during a RIP election (i.e REboot)
This discovery brought me down another path on 1000 chassis BCM's. The 1000 BCM's shipped with only one LAN interface, still has the virtual QOS interace enabled for LAN2. At IP addy 10.10.11.1. Again this interace cannot be changed through Unified manager but requires VNC.
Unfortunatley for us, we have 40 locations and our IP scheme on the WAN is 10.10.X.1 where X = locations 1 - 40. You can see our dilema with some routing issues. After turning these off, my locations at 10.10.15.1 and 10.10.11.1 work much better.
Consequently, there where issues on 3.0, 3.5 and 3.6 upgrades where DHCP would fail and actually corrupt the BCM. Nortel ITAS knew of this issue but could not pinpoint the cause. We had one such failure, on our BCM 10.10.11.1 (!). I wonder if this system failed the update of DHCP fucntions due to routing conflicts of just that ip address, resident, active and pingable. Yet not visable in Unified Manager !?!
Just a heads up incase any of you run with a 10.10.x.x scheme on your wan IP addys.
Gil
