Fixed multiplex of timeslots on V5 interface?

Retronetworking EWSD
1

On the IRC channel we were wondering if it is possible for the EWSD to [de]multiplex fixed timeslots of the DLU handling V5 interfaces to some other interface.

Specifically, this would be usefule with the EKSOS access networks. On them, you can transport the Q3 management over timeslos of a E1 link used for V5. For example, you could remove one timeslot from V5 usage and use that timeslot for Q3 management traffic.

If such a V5 interface ends up at an EWSD, the EWSD would have to take that timeslot and statically multiplex it to some other E1 interface. This way, one could collect the Q3 timeslots from each of the V5 interfaces (connecting to each of the EKSOS AN) and concentrate them on one other dedicated E1 interface, where then each timeslot corresponds to the Q3 TS of a diffent AN.

That concentrated E1 could then be fed into some Linux box (e.g. via icE1usb) which converts it back into an ethernet representation (e.g. tap device) that one could assign to the VM running the EKSOS Node Manager software to remotely manage the access networks.

If anyone knows how to do that on the EWSD, it would be rather useful to know for future C3ISDN (or other event deployments). This way we could avoid the need to separately back-haul the Q3 ethernet interface.

2

@NT2MKU wrote:

21:24 < NT2MKU> LaF0rge: nailed up connection on the EWSD for V5: CR 
                NUC:NUC=<name>,TYPE=PERM,EQNIC=<V5IF>-0-0-<Channel>,EQNOG=0-<LTG>-<LTU>-<Channel>
21:24 < NT2MKU> untested, you'll need an outgoing 2M LTU on the EWSD where you connect the management 
                equipment to
21:26 < NT2MKU> this could enable you to trunk all management timeslots of the ANs into one single 2M 
                link to your management console
3

If the create command was successful, the activation command is:

ACT NUC:NUC=<name>;

Delete with DACT NUC and CAN NUC.

1 Like