Juniper Enterprise Routing and Switching Support, Professional (JNCSP-ENT) : JN0-694

-- Exhibit -user@router# show class-of-service
classifiers {
inet-precedence ipp-test {
import default;
forwarding-class best-effort {
loss-priority low code-points be;
}
forwarding-class expedited-forwarding {
loss-priority low code-points af21;
}
forwarding-class assured-forwarding {
loss-priority low code-points af11;
}
forwarding-class network-control {
loss-priority low code-points nc1;
}
}
}
interfaces {
ge-* {
scheduler-map map-test;
unit * {
classifiers {
inet-precedence ipp-test;
}
rewrite-rules {
inet-precedence ipp-rw-test;
inet-precedence default;
}
}
}
}
...
rewrite-rules {
inet-precedence ipp-rw-test {
forwarding-class best-effort {
loss-priority low code-point be;
loss-priority high code-point af21;
}
forwarding-class expedited-forwarding {
loss-priority high code-point af21;
loss-priority low code-point be;
}
forwarding-class assured-forwarding {
loss-priority low code-point af11;
loss-priority high code-point af11;
}
forwarding-class network-control {
loss-priority low code-point nc1;
loss-priority high code-point nc1;
}
}
}
user@router> show class-of-service ... Code point type: inet-precedence Alias Bit pattern af11 001 af21 010 af31 011 af41 100 be 000 cs6 110 cs7 111 ef 101 nc1 110 nc2 111 -- Exhibit -
Click the Exhibit button.
Traffic with the IP precedence value af21 ingresses the router and should be rewritten with the same value as it egresses; however, this traffic is rewritten to a different value.
Referring to the exhibit, what is the source of this problem?

• A. The BA classifier is assigning the traffic to the best-effort queue with a high loss priority.
• B. The BA classifier is assigning the traffic to the expedited forwarding queue with a high loss priority.
• C. The BA classifier is assigning the traffic to the best-effort queue with a low loss priority.
• D. The BA classifier is assigning the traffic to the expedited forwarding queue with a low loss priority.

The exhibit shows the BGP configuration for a router. The router should be receiving an identical set of prefixes over its two peering sessions. You want to ensure the router is using both routes for forwarding. Which command will show this information?

• A. show route protocol bgp
• B. show route receive-protocol bgp <neighbor address>
• C. show route forwarding-table
• D. show bgp neighbor

You are implementing Q-in-Q tunneling on an EX Series switch. You want the tunnel to
support all C-VLANs; however, only some VLANs are able to send traffic across the tunnel. Switch-1 has the following configuration:
[edit vlans]
user@Switch-1# show
v100 {
vlan-id 100;
interface {
ge-0/0/0.10;
ge-0/0/1.20;
}
dot1q-tunneling {
customer-vlans [ ];
}
}
What would solve this problem?

• A. Implement RSTP.
• B. Add family ethernet-switching to the tunnel-side interface on Switch-1.
• C. Q-in-Q tunneling will not work in this scenario; use a Layer 2 VPN instead.
• D. Remove the customer-vlans statement.

-- Exhibit -user@router# run show log ospf-test ... Jun 10 22:35:38.598494 OSPF sent Hello 10.100.0.1 -> 224.0.0.5 (ge-1/0/3.1000 IFL 77
area 0.0.0.0) Jun 10 22:35:38.598520 Version 2, length 44, ID 10.100.1.2, area 0.0.0.0 Jun 10 22:35:38.598543 mask 255.255.255.252, hello_ivl 10, opts 0x2, prio 128 Jun 10 22:35:38.598564 dead_ivl 32, DR 10.100.0.1, BDR 0.0.0.0 Jun 10 22:35:41.522956 OSPF periodic xmit from 10.200.26.1 to 224.0.0.5 (IFL
2684276196 area 0.0.0.1)
Jun 10 22:35:42.798220 OSPF rcvd Hello 10.100.0.2 -> 224.0.0.5 (ge-1/0/3.1000 IFL 77
area 0.0.0.0)
Jun 10 22:35:42.798311 Version 2, length 48, ID 10.100.1.1, area 0.0.0.0
Jun 10 22:35:42.798334 checksum 0x0, authtype 0
Jun 10 22:35:42.798356 mask 255.255.255.252, hello_ivl 10, opts 0x2, prio 128
Jun 10 22:35:42.798377 dead_ivl 40, DR 10.100.0.2, BDR 10.100.0.1
Jun 10 22:35:45.189034 OSPF rcvd Hello 10.100.0.2 -> 224.0.0.5 (ge-1/0/3.1000 IFL 77 area 0.0.0.0) Jun 10 22:35:45.189097 Version 2, length 44, ID 10.100.1.1, area 0.0.0.0 Jun 10 22:35:45.189118 checksum 0x0, authtype 0 Jun 10 22:35:45.189140 mask 255.255.255.252, hello_ivl 10, opts 0x2, prio 128 Jun 10 22:35:45.189162 dead_ivl 40, DR 10.100.0.2, BDR 0.0.0.0
Jun 10 22:35:45.196969 OSPF DR is 10.100.1.2, BDR is 0.0.0.0 Jun 10 22:35:45.197050 OSPF sent Hello 10.200.26.1 -> 224.0.0.5 (ge-1/0/0.0 IFL 69 area 0.0.0.1)
Jun 10 22:35:45.197076 Version 2, length 44, ID 10.100.1.2, area 0.0.0.1 Jun 10 22:35:45.197098 mask 255.255.255.252, hello_ivl 10, opts 0x2, prio 128 Jun 10 22:35:45.197119 dead_ivl 40, DR 10.200.26.1, BDR 0.0.0.0 Jun 10 22:35:46.746900 OSPF periodic xmit from 10.100.0.1 to 224.0.0.5 (IFL 2684276196
area 0.0.0.0) -- Exhibit -
Click the Exhibit button.
Referring to the exhibit, what is preventing the OSPF neighborship with two directly connected routers using interface ge-1/0/3 from reaching the full state?

• A. authentication type mismatch
• B. dead interval mismatch
• C. subnet mismatch
• D. hello interval mismatch

-- Exhibit --
{master:0}[edit ethernet-switching-options secure-access-port]
user@switch# show
interface ge-0/0/1.0 {
static-ip 172.27.0.2 vlan v11 mac 00:0c:29:b5:89:7c;
no-dhcp-trusted;
}
vlan v11 {
arp-inspection;
}
interface ge-0/0/2.0 {
dhcp-trusted;
}
user@switch> show log messages | match arp
Feb 8 14:31:45 switch eswd[1280]: ESWD_DAI_FAILED. 3 ARP_REQUEST received, interface ge-0/0/1.0[index 73], vlan v11[index 5], sender ip/mac 172.27.0.2/00:0c:29:b5:89:7d, receiver ip/mac 172.27.0.1/00:00:00:00:00:00
Feb 8 14:34:05 switch eswd[1280]: ESWD_DAI_FAILED. 3 ARP_REQUEST received, interface ge-0/0/1.0[index 73], vlan v11[index 5], sender ip/mac 172.27.0.2/00:0c:29:b5:89:7d, receiver ip/mac 172.27.0.1/00:00:00:00:00:00
Feb 8 14:36:05 switch eswd[1280]: ESWD_DAI_FAILED. 3 ARP_REQUEST received, interface ge-0/0/1.0[index 73], vlan v11[index 5], sender ip/mac 172.27.0.2/00:0c:29:b5:89:7d, receiver ip/mac 172.27.0.1/00:00:00:00:00:00
-- Exhibit -
Click the Exhibit button.
You have been asked to troubleshoot a problem where a user is not able to send traffic through your switch. While troubleshooting, you see the log messages shown in the exhibit.
What is causing the problem?

• A. The static IP address is misconfigured.
• B. The eswd process has been corrupted.
• C. The receiver MAC in the packets is undefined.
• D. The defined MAC address is misconfigured.