OCOM Mediation Engine on Different Sub-nets

The OCOM Mediation Engine simplifies the operation of software-based OCOM probes by enabling the transmission of Internet Protocol Flow Information Export (IPFIX) data to one or more OCOM Mediation Engines. When deployed on different sub-nets, the ACLI hierarchy is different because the network-interface parameter is removed from the comm-monitor configuration object and is transferred to the monitor-collector configuration object.

When migrating from the S-C[xz]6.3.9 release to the E-C[xz]6.4.0 release, probes anchored on media interfaces revert to the default network-interface value of wancom0:0.

Note:

The comm-monitor VQ reports do not support disabling latching for a stream because the SBC does not have access to the stream source IP address. Latching may be globally disabled via the media-manager object or, dynamically disabled even when globally enabled in media-manager, for example, when a media for a session has been successfully negotiated but the source of the media flow changes.

The following illustration shows an S-C(xz)6.3.9 configuration.

comm-monitor
	state	enabled
	qos-enable	disabled
	sbc-grp-id	0
	tls-profile
	network-interface	M10:0
	monitor-collector
			address	172.16.29.102
			port	4739

The following illustration shows the upgraded E-C[xz]6.4.0 configuration.

comm-monitor
	state		enabled
	qos-enable		disabled
	sbc-grp-id		0
	tls-profile
	monitor-collector
		address	172.16.29.102
		port	4739
		network-interface	wancom0:0

Note:

To restore prior service, update the network-interface parameter to its original value of M10:0.