I am trying to implement BPI+ with a DOCSIS 1.1 CM file for the first time. Everything seems to sync up fine and I get a good lock and I can surf through the modem but I keep getting this error message poping up. This is on a Cisco uBR7114. Any Ideas???
Sep 2 15:03:30.069: %UBR7100-3-MAP_REJECT_DS_TRAFFIC_FLOW_NOT_MAPPED: <132>CMTS[DOCSIS]:<
66060510> Map Reject - Downstream traffic flow not mapped to BPI+SAID. CM Mac Addr <0011.
e3cf.2ab3>
Did anyone try to make fax and pos terminal working on cm's?
We are using thg520 and thg540 cm's. As i expirienced, some fax
machines are working properly. We are using docsis 1.1 standard.
Any ideas? What about other cm's?
I've been working with normal DOCSIS cable modems ( without VOIP ) for some time now .. well .. didn't get too much problems .. they just worked .. create the simple conf file .. 'compile' it .. put it in dhcp .. made a simple php script to generate dhcp entries based on sql .. anyhow .. everything worked well ..
now .. voip .. thg540 .. I noticed I had to add something new to it in order to make the usb usable for example ..
VendorSpecific
{
VendorIdentifier 0x001095;
I am migrating my network to DOCSIS 1.1 and have been a little lost about what the "Cable Service Class" commands in the Cisco uBR. I have looked through Cisco's site but have not had much luck. I have a DOCSIS 1.1 CM file I have created and have been able to successfully provision it to a modem and the modem operate but all my research shows the "Cable Service Class" set on the CMTS its self.
Hello everyone!
I'm currently having issues getting The Motorola SBV5222 to activate the MTA portion of the Cable modem. The cable modem it's self comes up just fine with BPI+ Enabled. We currently having Arris TM502G's working perfectly. We received a the demo SBV5222 last week and I just started writing configs for it any playing around.
We're unable to ping modems directly from the CMTS to the modem private IPs. As a result we're seeing a number of modems unable to get past init(d) during initialization because the CMTS cant communicate with them.
Also DHCP does not see the DHCP request.
What makes this issue more complicated is that we're able to ping to these modems private IPs from other locations within the network.
Tracing to the non-routable modem IP shows the CMTS as the hop just before the modem as one would expect.