Microwave backhaul service management— considerations/limitations
Wavence-specific service provisioning considerations/limitations
Table 15-5: Microwave backhaul service management — considerations/limitations
Functions |
Limitations |
---|---|
Path search |
Path search does not work beyond the Wavence realm (that is, IP/MPLS region). Path search does not work when you configure a single site service. Path search through a ring assigns a random radio ring instance if multiple options are available. If you want to use a specific ring instance, it must be done manually. It is the responsibility of the user to check and not to exceed the bandwidth provided by any interface (radio/Ethernet/LAG) involved in the subsequent creation of VLL services. |
Ring with L1 radio LAG on CAHD boards |
Cross-board CAHD LAG is not supported as a radio ring component TDM cross-connections are not supported. You cannot configure a cross-connection between an ERPS instance with a CAHD L1 LAG as a ring port and any other supported port. EFM OAM or LOC can only be configured as an ERPS switching criteria if the topology includes an optical user EAC port as a ring port. The switching criteria are only active on that EAC port’s ring direction. |
Ring with L1 radio LAG on electrical interfaces of EAS and EASv2 |
NFM-P accepts an L1 radio LAG that has radio interfaces configured either as static or adaptive modulation, as a ring port. NFM-P accepts only an active L1 radio LAG as a ring port . NFM-P does not accept an L1 radio LAG as a ring port when MPT-HC, MPT-HLv1, MPT-HLS, MPT-HLC, and MPT-HQAM radio interfaces are provisioned on the same EAS and EASv2 peripheral. NFM-P does not accept an L1 radio LAG as a ring port when electrical user Ethernet interfaces are enabled on the same EAS and EASv2 peripheral. NFM-P does not accept an L1 radio LAG as a ring port when optical user Ethernet interfaces are enabled on the same EAS and EASv2 peripheral. NFM-P does not accept an L1 radio LAG as a ring port when optical user Ethernet interfaces that have SFP provisioned are disabled on the same EAS and EASv2 peripheral. NFM-P does not accept an L1 radio LAG as a ring port when the L1 radio LAG is segregated with: |
Support for MPTs in the same LAG |
NFM-P does not support a mix of MPTs (MPT-HL and MPT-HQAM) in the same LAG on anEASv1 card. |
EPS protection |
NFM-P supports EPS protection on UBT-S node configured on the EAC card and UBT-T node configured on the Core-EVO and EAC cards. |
GUI label in Network Policy window |
"Network Policy type for 7705" label is displayed for all node types including Wavence. |
ECFM configuration |
Wavence ECFM configuration supports L2 Backhaul VLAN service with UBT-SA nodes used as a pass thru node. However, once the UBT-SA nodes are unmanaged and re-managed, the Connect Service operation must be performed to discover the nodes. See Connect service. |