We see this issue quite often, we're staging an MSTP deployment of an NCS2006 M6 with dual TNC-Es, and we constantly lose connection to the shelf in CTC, making it difficult to setup some initial configuration parameters. This issue occurs on multiple shelves we have deployed, but not all of them. Some of the variables we've changed in order to rectify this issue: -Used multiple laptops -Used many different copper cables -Tried different switch platforms -Tried autonegotiate vs locked 100/full -Tried both EMS and CRAFT -Tried multishelf disabled and node controller modes -Tried with and without a protection unit (dual TNC) -Replaced TNCs, ECUs, and LCDs. -Tried versions 10.6, 10.8, and 11.0 All of which never rectified this issue. We never lose packets to the shelf itself, our CTC cache just loses and regains communication with it. TL1 never disconnects either. Currently, I have this in our lab and I'm trying to find the secret to getting this to stop. I'm wondering if anyone else with experience with these MSTP shelves encountered the same type of issue and know of a fix? Fielding for a response here before engaging TAC. Thanks!
... View more
Hi all, I'm sort of stumped with our PTP configuration and looking for some advice.
We're using a Microsemi TP5000 Time Server as our dedicated GM, which references GNSS for its time. It's configured to use the g8265.1 unicast profile on domain 10, and I have no issues pointing devices to it's ipv4 listening address as slaves.
Since the TP5K only supports 1000 direct clients, I'm tasked to scale this out to some of our 9Ks to act as master clocks so everything isn't pointed to the TP5K directly. Here's a basic topology:
Presently, the ASR9000 and ASR920 are direct slaves of the TP5000 and PHASE_LOCKED. However, in this case, I only want the ASR9000 peered directly with the TP5000 and distributing PTP downward to the ASR920 and other devices.
Here's what my current configuration looks like:
TP5000 - 10.99.1.1
ASR9000 - 10.88.1.1
ASR920 - 10.77.1.1
Listening on IPv4 10.99.1.1, g8265.1, domain 10
ptp clock domain 10 profile g.8265.1 time-source PTP !
profile ptp-gm-slave transport ipv4 master ipv4 10.99.1.1 !
interface TenGigE0/0/0/0 ptp profile ptp-gm-slave ! ipv4 address 10.88.1.1/24 !
RP/0/RSP0/CPU0:ASR9000#show frequency synchronization selection Node 0/RSP0/CPU0: ============== Selection point: T0-SEL-B (2 inputs, 1 selected) Last programmed 21:28:29 ago, and selection made 21:28:25 ago Next selection points SPA scoped : None Node scoped : T4-SEL-C CHASSIS-TOD-SEL Chassis scoped: LC_TX_SELECT Router scoped : None Uses frequency selection Used for local line interface output S Input Last Selection Point QL Pri Status == ======================== ======================== ===== === =========== 1 PTP [0/RSP0/CPU0] n/a PRC 254 Locked Internal0 [0/RSP0/CPU0] n/a SEC 255 Available
ptp clock ordinary domain 10 tod R0 cisco clock-port slave slave profile g8265.1 transport ipv4 unicast interface Lo0 negotiation clock source 10.99.1.1
ASR920#show ptp clock running PTP Ordinary Clock [Domain 10] State Ports Pkts sent Pkts rcvd Redundancy Mode PHASE_ALIGNED 1 43651 132319 Hot standby PORT SUMMARY PTP Master Name Tx Mode Role Transport State Sessions Port Addr slave unicast slave Lo0 Slave 1 10.99.1.1
How do I configure 10.88.1.1 to be a master to 10.77.1.1?
... View more