Bound path configuration fails in N3EAS2 board due to VC4 and VCTRUNK bonding limitation. Publication Date: 2012-07-25 Views: 0 Downloads: 0 References: 0 Issue Description In an N3EAS2 board installed in OSN 8800 NE of version...
More
Bound path configuration fails in N3EAS2 board due to VC4 and VCTRUNK bonding limitation. Publication Date: 2012-07-25 Views: 0 Downloads: 0 References: 0 Issue Description In an N3EAS2 board installed in OSN 8800 NE of version V100R006C01SPC100(5.51.07.33), the VCTRUNK 1 was bounded to 12 VC4s (VC4: 1-12) and used in creating an Ethernet link service with PORT1 on the board. The customer tried to create another Ethernet line service with 16 VC4s bandwidth using PORT2 of the board. According to the documents and the Technical Specifications of the board, the customer had to use VCTRUNK 18 to bound it with 16 VC4s. In the VCTRUNK Specifications in the document of the board, the following two points are mentioned for Configuration principles: * VCTRUNKs 1 and 18 can be bound with a maximum of 64 VC-4 paths. The other VCTRUNKs can be bound with a maximum of eight VC-4 paths.VCTRUNKs 1 and 18 can be bound with a maximum of 64 VC-4 paths. The other VCTRUNKs can be bound with a maximum of ei
Less