Because your PC works when connecting to the C877 directly, then it would appear that the issue would be between the Procurve uplink to the CPE and the access-port you attach you PC into.  Make sure that your Procurve uplink is configured to send/receive non-tagged packets and that your access-port to the PC is configured the same (and in the same access-VLAN1).    Make sure you get link stable between C877 and Procurve and that there is no link-flapping which could result in your STP never converging on the switch.    Check the console logs on both C877 and Procurve when you connect them to see if there are any clues. On the C877 console use the command "show vlan-switch" or "show spanning-tree vlan 1" to make sure the connectivity to your switch show the correct ports mapping the the Procurve when the connectivity is made.   Rgds, Jim.W. ... View more

Note. The ISR800 and ISR G2 which run the IOS release 15M/T is integrated with the DSL Firmware 35J for DSL Annex(es) A/M and 35J for Annex B/J. With the IOS release 15.6(3)M, we plan to change the embedded BRCM Firmware in IOS to 39Tfor Annex A/M and 38r1 for Annex B/J. This change will affect only the 880/890 and ISR G2+EHWIC SKUs which carry the BRCM6368 chip-set. More importantly, we also plan to change the current SDK version used for bootloader and embedded linux. This is the SDK used to compile the currently available FW. This SDK being a very old version,. Hence we plan to upgrade the SDK for the bootloader and embedded linux to the latest version 4.14L.04A . This will need customers to us either the embedded 39T FW version or later, compiled with the newer SDK if they plan to migrate IOS 15.6(3)M version or later. Customers who are on the existing IOS release 15.6(2)T version or earlier ( for ex. 15.4(3)M) can continue to use the earlier FW version(s) available. The Firmware release notes are available at the link below Release Notes for VDSL CPE PHY Release A2pv6C039t - Cisco Previous version release notes Release Notes for VDSL CPE PHY Release A2pv6C039m - Cisco Q) Will this change impact Annex B/J systems like (C886VA-K9 or C896VA-K9)? A) Yes. This change will be effective for both Annex A/M and Annex B/J based systems. Q) Will this change impact ADSL/VDSL NIM for ISR4000 series A) No. This change is only effective for the BRCM6368 based ADSL/VDSL interface or EHWIC on the 800 series/ISR G2. The ADSL/VDSL NIM has BCM63168 chipset Q) Is it possible to run the existing FW that we use in customer environment with the IOS 15.6(3)M release? A) No. The existing FW available on CCO has been compiled with the older SDK version 4.02L.03. For the FW to work with 15.6(3)M IOS release we will need to release a newer FW image on CCO compiled with the current SDK 4.14L.04A . Q) Is it possible to use the 39T FW with the older IOS releases like 15.5(3)M release? A) Yes. This FW is posted on CCO and available as an selectable option on CCW ordering tool. ... View more

Chaps, the new C867VAE devices will be tested via the BT-OpenReach MCT process which are the cut-price lower spec variants of our CPE. ... View more

Note:- Cisco IOS 15.6(3)M and later requires Firmware version A2pv6C039t as a minimum to work properly due to some changes in the interfaces between IOS and the Modem Firmware. The wording in the release notes at the link below are not clear on this point (blind copied from earlier Firmware versions) and so I have requested the tech-writers to clarify that in the docs. Release Notes for VDSL CPE PHY Release A2pv6C039t - Cisco The 39t Firmware version is progressing through testing in BT OpenReach conformance labs and should exit by end of September so I will update the support matrix assuming we get a green-light off the test teams. ... View more

I think you may be missing part of the header, I am using the following to obtain ticket via REST API and it's working fine. apic_controller = ' https://10.52.145.13 ' apic_uri = '/api/v1/ticket' header = {'content-type': 'application/json'} body = '{"username":"restapi_user","password":"restapi_Password123"}' resp = requests.post(apic_controller + apic_uri, data=body, headers=header,verify=False) or from browser REST client ... View more

draft version of config document has been posted at the link below, all comments / suggestions for changes welcome. Connecting Cisco ISR routers to BT GEA ... View more

Sorry Richard, my bad, I have been meaning to post something on here for a while now and never gotten around to it.  I will try to post the full config document this week if I get a moment. The most important is to reference the correct Firmware version under the DSL controller configuration if it is not included in the embedded image in IOS version.  Then a few tweaks to the default modem settings as shown below. controller VDSL 0    operating mode vdsl2    training log filename flash:897VA.log    firmware filename flash:VA_A_39m_B_38h3_24h.bin    modem disableV43          <-- be careful, this one is case-sensitive    sra Rgds, Jim.W. ... View more

Hi Gareth, I just replied to one of the other contributors (I'm not sure what view you have of all comments/replies so apologies for repetition) to say that based upon the requests for c867 then I will try to get the device through but it won't be at the expense of delaying the newer hardware SKU's which I have already pencilled in MCT dates for off OpenReach therefore I would be expecting 6months until I can get it scheduled into the front end of the process, assuming a pass first time.  If it's a lot of engineering work required to align the c867 with what we already have certified (c887, c897, etc) then we might need to think again. For the throughput, etc of the 6368 then the Broadcom chipset will have no issues pushing the required bandwidth (works fine on c887VA and c897VA with that chip installed), but the actual grunt of the processor of the c867 is where the bottle-neck would potentially lie if deploying with services layered on top of the basic DSL (IPsec, etc). Rgds, Jim.W. ... View more

Hi Tom, for the BT specific certifications then yes I am aiming to keep this site as the central point for updates when new kit undergoes certification or previous devices require changes such as Firmware updates. As for the c867 then seeing as there has been a couple of requests now for this to undergo testing then I will try to get this onto the schedule, though as I mentioned above my priority is with the newer hardware SKUs. The MCT test-slots from OpenReach are in pretty short supply therefore c867 will be submitted on a "best-efforts basis" if I am able to wrestle another testing window off OpenReach AND I don't have any backlog of other devices which need to go through the process. So in summary, I will try to get c867 through, but due to processes involved, don't hold you breath Rgds, Jim.W. ... View more