Cisco ATM assistance needed

[rainman]

Hello,

I am working on converting an older ATM network (Alcatel OmniStack) to Cisco. The OmniStack's current ATM config is basically taking VC's and mapping them to specific IP addresses. (i.e., 0/200 = 192.168.x.x). What would be the best method to migrate this to a Cisco ATM environment? Bridge groups?

Currently the devices on the are all layer 2, until they hit the OmniStack where it applies the layer 3 IP to the VPI/VCI. I need to do something similar with Cisco ATM. Any ideas?


Thanks,

Rainman

 

[rainman]

Ok -

Has anybody ever seen a BVI interface start bouncing? Right now, I have a few VC's as members of a specific BVI, but the BVI keeps bouncing. When I look at the spanning-tree it's telling me it's looped, then blocking, then listening, then looped. I am doing IEEE span tree, and I did a debug of the ATM packet and I see that I'm sending the IEEE span tree, and my ATM switch is also sending IEEE (they both match). In order to get the BVI to stay up, I had to do the following cmd:

int ATM1/0.1
atm pvc 1 0 100 aal5snap
atm pvc 2 0 101 aal5snap
atm pvc 3 0 102 aal5snap
atm pvc 4 0 103 aal5snap
bridge-group 1
bridge-group 1 spanning disabled

Without the spanning disabled, my BVI keeps bouncing. Anybody ever see this? Should I even be disabling the span tree on my BVI? I've used BVI's in other situations before and the only time they bounce is when there are no members of the BVI but in this case, I have a sub-interface with about 4 pvc's as members. Any thoughts?


-Rainman