Use the following configuration statement to configure the policy server–to–CMTS interface (PKT-MM2) so that the policy server can communicate with CMTS devices:
- slot number jps cmts-interface {
- cmts-addresses [cmts-addresses...];
- keepalive-interval keepalive-interval;
- synch-despite-unreachable-pep;
- synch-despite-pre-i03-pep;
- use-ssq-ssc-with-pre-i03-pep;
- local-address local-address;
- message-max-length message-max-length;
- message-read-buffer-size message-read-buffer-size;
- message-write-buffer-size message-write-buffer-size;
- open-connection-timeout open-connection-timeout;
- connection-open-retry-interval connection-open-retry-interval;
- sent-message-timeout sent-message-timeout;
- validate-pcmm-objects;
- }
To configure the policy server–to–CMTS interface:
A value of 0 means that no keepalive messages will be exchanged between the CMTS device and the JPS.
If no value is specified and there is more than one local address, a random local address is used as the source address.
The connection is dropped when initial PCMM messages are not exchanged within this time period.
This value must be less than the held-decs-max-age and pending-rks-event-max-age values for the corresponding RKS interface.
[edit slot 0 jps cmts-interface] user@host# show cmts-addresses ; keepalive-interval 60; synch-despite-unreachable-pep; synch-despite-pre-i03-pep; local-address ; message-max-length 204800; message-read-buffer-size 1000000; message-write-buffer-size 1000000; open-connection-timeout 5; connection-open-retry-interval 60; sent-message-timeout 60; validate-pcmm-objects;