JN0-643 無料問題集「Juniper Enterprise Routing and Switching, Professional (JNCIP-ENT)」
-- Exhibit --
[edit]
user@switch# commit
error: Trunk interface <ge-0/0/10.0> can not be member of both dot1q-tunneling enabled vlan <cust-1>, and a non dot1q-tunneled vlan <v11> when dot1q-tunneling ethernet-type is not <0x8100> error: configuration check-out failed
-- Exhibit --
Click the Exhibit button.
When you try to commit your 802.1Q tunneling configuration, you receive the error shown in the exhibit.
Which configuration statement will allow the configuration to commit?
[edit]
user@switch# commit
error: Trunk interface <ge-0/0/10.0> can not be member of both dot1q-tunneling enabled vlan <cust-1>, and a non dot1q-tunneled vlan <v11> when dot1q-tunneling ethernet-type is not <0x8100> error: configuration check-out failed
-- Exhibit --
Click the Exhibit button.
When you try to commit your 802.1Q tunneling configuration, you receive the error shown in the exhibit.
Which configuration statement will allow the configuration to commit?
正解:B
解答を投票する
-- Exhibit --
Mar 16 17:48:06.145257 OSPF periodic xmit from 172.14.10.1 to 224.0.0.5 (IFL 69 area
0 .0.0.1)
Mar 16 17:48:12.404986 ospf_trigger_build_telink_lsas : No peer found
Mar 16 17:48:13.013420 ospf_trigger_build_telink_lsas : No peer found
Mar 16 17:48:13.013555 ospf_set_lsdb_statE. Router LSA 192.168.2.1 adv-rtr 192.168.2.1 state QUIET->GEN_PENDING
Mar 16 17:48:13.013661 OSPF trigger router LSA 0x156d0f0 build for area 0.0.0.1 lsa-id
192.168.2.1
Mar 16 17:48:13.017494 ospf_set_lsdb_statE. Router LSA 192.168.2.1 adv-rtr 192.168.2.1 state GEN_PENDING->QUIET
Mar 16 17:48:13.017636 OSPF built router LSA, area 0.0.0.1, link count 2
Mar 16 17:48:13.017954 OSPF sent Hello 172.14.10.1 -> 224.0.0.5 (ge-0/0/1.0 IFL 69 area
0.0.0.1)
Mar 16 17:48:13.018023 Version 2, length 44, ID 192.168.2.1, area 0.0.0.1
Mar 16 17:48:13.018111 mask 255.255.255.0, hello_ivl 10, opts 0x2, prio 128
Mar 16 17:48:13.018162 dead_ivl 40, DR 172.14.10.1, BDR 0.0.0.0
Mar 16 17:48:13.018613 OSPF DR is 192.168.2.1, BDR is 0.0.0.0
Mar 16 17:48:13.018900 OSPF sent Hello 172.14.10.1 -> 224.0.0.5 (ge-0/0/1.0 IFL 69 area
0.0.0.1)
Mar 16 17:48:13.018968 Version 2, length 44, ID 192.168.2.1, area 0.0.0.1
Mar 16 17:48:13.019032 mask 255.255.255.0, hello_ivl 10, opts 0x2, prio 128
Mar 16 17:48:13.019118 dead_ivl 40, DR 172.14.10.1, BDR 0.0.0.0
Mar 16 17:48:13.028426 OSPF DR is 192.168.2.1, BDR is 0.0.0.0
Mar 16 17:48:13.432025 OSPF packet ignoreD. area mismatch (0.0.0.0) from 172.14.10.2 on intf ge-0/0/1.0 area 0.0.0.1
Mar 16 17:48:13.432135 OSPF rcvd Hello 172.14.10.2 -> 224.0.0.5 (ge-0/0/1.0 IFL 69 area
0.0.0.1)
Mar 16 17:48:13.432189 Version 2, length 44, ID 192.168.5.1, area 0.0.0.0
Mar 16 17:48:13.432274 checksum 0x8065, authtype 0
Mar 16 17:48:13.432346 mask 255.255.255.0, hello_ivl 10, opts 0x2, prio 128
Mar 16 17:48:13.432398 dead_ivl 40, DR 172.14.10.2, BDR 0.0.0.0
commit complete
-- Exhibit --
Click the Exhibit button.
Looking at the traceoptions output in the exhibit, why are the OSPF routers stuck in Init state?
Mar 16 17:48:06.145257 OSPF periodic xmit from 172.14.10.1 to 224.0.0.5 (IFL 69 area
0 .0.0.1)
Mar 16 17:48:12.404986 ospf_trigger_build_telink_lsas : No peer found
Mar 16 17:48:13.013420 ospf_trigger_build_telink_lsas : No peer found
Mar 16 17:48:13.013555 ospf_set_lsdb_statE. Router LSA 192.168.2.1 adv-rtr 192.168.2.1 state QUIET->GEN_PENDING
Mar 16 17:48:13.013661 OSPF trigger router LSA 0x156d0f0 build for area 0.0.0.1 lsa-id
192.168.2.1
Mar 16 17:48:13.017494 ospf_set_lsdb_statE. Router LSA 192.168.2.1 adv-rtr 192.168.2.1 state GEN_PENDING->QUIET
Mar 16 17:48:13.017636 OSPF built router LSA, area 0.0.0.1, link count 2
Mar 16 17:48:13.017954 OSPF sent Hello 172.14.10.1 -> 224.0.0.5 (ge-0/0/1.0 IFL 69 area
0.0.0.1)
Mar 16 17:48:13.018023 Version 2, length 44, ID 192.168.2.1, area 0.0.0.1
Mar 16 17:48:13.018111 mask 255.255.255.0, hello_ivl 10, opts 0x2, prio 128
Mar 16 17:48:13.018162 dead_ivl 40, DR 172.14.10.1, BDR 0.0.0.0
Mar 16 17:48:13.018613 OSPF DR is 192.168.2.1, BDR is 0.0.0.0
Mar 16 17:48:13.018900 OSPF sent Hello 172.14.10.1 -> 224.0.0.5 (ge-0/0/1.0 IFL 69 area
0.0.0.1)
Mar 16 17:48:13.018968 Version 2, length 44, ID 192.168.2.1, area 0.0.0.1
Mar 16 17:48:13.019032 mask 255.255.255.0, hello_ivl 10, opts 0x2, prio 128
Mar 16 17:48:13.019118 dead_ivl 40, DR 172.14.10.1, BDR 0.0.0.0
Mar 16 17:48:13.028426 OSPF DR is 192.168.2.1, BDR is 0.0.0.0
Mar 16 17:48:13.432025 OSPF packet ignoreD. area mismatch (0.0.0.0) from 172.14.10.2 on intf ge-0/0/1.0 area 0.0.0.1
Mar 16 17:48:13.432135 OSPF rcvd Hello 172.14.10.2 -> 224.0.0.5 (ge-0/0/1.0 IFL 69 area
0.0.0.1)
Mar 16 17:48:13.432189 Version 2, length 44, ID 192.168.5.1, area 0.0.0.0
Mar 16 17:48:13.432274 checksum 0x8065, authtype 0
Mar 16 17:48:13.432346 mask 255.255.255.0, hello_ivl 10, opts 0x2, prio 128
Mar 16 17:48:13.432398 dead_ivl 40, DR 172.14.10.2, BDR 0.0.0.0
commit complete
-- Exhibit --
Click the Exhibit button.
Looking at the traceoptions output in the exhibit, why are the OSPF routers stuck in Init state?
正解:B
解答を投票する
-- Exhibit --
user@switch-1> show spanning-tree bridge
STP bridge parameters
Context ID : 0
Enabled protocol : MSTP
STP bridge parameters for CIST
...
STP bridge parameters for MSTI 1
MSTI regional root : 4097.b0:c6:9a:73:27:90
Hello time : 2 seconds
Maximum age : 20 seconds
Forward delay : 15 seconds
Number of topology changes : 4
Time since last topology change : 42 seconds
Topology change initiator : ge-0/0/10.0
Topology change last recvd. from : 00:19:e2:55:24:8c
Local parameters
Bridge ID : 4097.b0:c6:9a:73:27:90
Extended system ID : 0
Internal instance ID : 1
STP bridge parameters for MSTI 2
MSTI regional root : 8194.b0:c6:9a:73:27:90
Hello time : 2 seconds
Maximum age : 20 seconds
Forward delay : 15 seconds
Number of topology changes : 4
Time since last topology change : 42 seconds
Topology change initiator : ge-0/0/10.0
Topology change last recvd. from : 00:19:e2:55:24:8c
Local parameters
Bridge ID : 8194.b0:c6:9a:73:27:90
Extended system ID : 0
Internal instance ID : 2
user@switch-1> show spanning-tree mstp configuration
MSTP information
Context identifier : 0
Region name : my-mstp-config
Revision : 1
Configuration digest : 0x91ee8012e6851d931adae71da4060690
MSTI Member VLANs
0 0,400-4094
1 1-199
2 200-399
user@switch-2> show spanning-tree bridge
STP bridge parameters
Context ID : 0
Enabled protocol : MSTP
STP bridge parameters for CIST
...
STP bridge parameters for MSTI 1
MSTI regional root : 8193.b0:c6:9a:73:39:90
Hello time : 2 seconds
Maximum age : 20 seconds
Forward delay : 15 seconds
Number of topology changes : 3
Time since last topology change : 320 seconds
Topology change initiator : ge-0/0/9.0
Topology change last recvd. from : b0:c6:9a:73:27:81
Local parameters
Bridge ID : 8193.b0:c6:9a:73:39:90
Extended system ID : 0
Internal instance ID : 1
STP bridge parameters for MSTI 2
MSTI regional root : 4098.b0:c6:9a:73:39:90
Hello time : 2 seconds
Maximum age : 20 seconds
Forward delay : 15 seconds
Number of topology changes : 3
Time since last topology change : 320 seconds
Topology change initiator : ge-0/0/9.0
Topology change last recvd. from : 00:19:e2:55:24:8d
Local parameters
Bridge ID : 4098.b0:c6:9a:73:39:90
Extended system ID : 0
Internal instance ID : 2
user@switch-2> show spanning-tree mstp configuration
MSTP information
Context identifier : 0
Region name : my-mstp-config
Revision : 10
Configuration digest : 0x91ee8012e6851d931adae71da4060690
MSTI Member VLANs
0 0,400-4094
1 1-199
2 200-399
-- Exhibit --
Click the Exhibit button.
A colleague recently implemented MSTP in your Layer 2 network and is having trouble determining why it is not working properly. You are asked to review the outputs provided in the exhibit to determine the cause.
Referring to the exhibit, what is causing the issue?
user@switch-1> show spanning-tree bridge
STP bridge parameters
Context ID : 0
Enabled protocol : MSTP
STP bridge parameters for CIST
...
STP bridge parameters for MSTI 1
MSTI regional root : 4097.b0:c6:9a:73:27:90
Hello time : 2 seconds
Maximum age : 20 seconds
Forward delay : 15 seconds
Number of topology changes : 4
Time since last topology change : 42 seconds
Topology change initiator : ge-0/0/10.0
Topology change last recvd. from : 00:19:e2:55:24:8c
Local parameters
Bridge ID : 4097.b0:c6:9a:73:27:90
Extended system ID : 0
Internal instance ID : 1
STP bridge parameters for MSTI 2
MSTI regional root : 8194.b0:c6:9a:73:27:90
Hello time : 2 seconds
Maximum age : 20 seconds
Forward delay : 15 seconds
Number of topology changes : 4
Time since last topology change : 42 seconds
Topology change initiator : ge-0/0/10.0
Topology change last recvd. from : 00:19:e2:55:24:8c
Local parameters
Bridge ID : 8194.b0:c6:9a:73:27:90
Extended system ID : 0
Internal instance ID : 2
user@switch-1> show spanning-tree mstp configuration
MSTP information
Context identifier : 0
Region name : my-mstp-config
Revision : 1
Configuration digest : 0x91ee8012e6851d931adae71da4060690
MSTI Member VLANs
0 0,400-4094
1 1-199
2 200-399
user@switch-2> show spanning-tree bridge
STP bridge parameters
Context ID : 0
Enabled protocol : MSTP
STP bridge parameters for CIST
...
STP bridge parameters for MSTI 1
MSTI regional root : 8193.b0:c6:9a:73:39:90
Hello time : 2 seconds
Maximum age : 20 seconds
Forward delay : 15 seconds
Number of topology changes : 3
Time since last topology change : 320 seconds
Topology change initiator : ge-0/0/9.0
Topology change last recvd. from : b0:c6:9a:73:27:81
Local parameters
Bridge ID : 8193.b0:c6:9a:73:39:90
Extended system ID : 0
Internal instance ID : 1
STP bridge parameters for MSTI 2
MSTI regional root : 4098.b0:c6:9a:73:39:90
Hello time : 2 seconds
Maximum age : 20 seconds
Forward delay : 15 seconds
Number of topology changes : 3
Time since last topology change : 320 seconds
Topology change initiator : ge-0/0/9.0
Topology change last recvd. from : 00:19:e2:55:24:8d
Local parameters
Bridge ID : 4098.b0:c6:9a:73:39:90
Extended system ID : 0
Internal instance ID : 2
user@switch-2> show spanning-tree mstp configuration
MSTP information
Context identifier : 0
Region name : my-mstp-config
Revision : 10
Configuration digest : 0x91ee8012e6851d931adae71da4060690
MSTI Member VLANs
0 0,400-4094
1 1-199
2 200-399
-- Exhibit --
Click the Exhibit button.
A colleague recently implemented MSTP in your Layer 2 network and is having trouble determining why it is not working properly. You are asked to review the outputs provided in the exhibit to determine the cause.
Referring to the exhibit, what is causing the issue?
正解:C
解答を投票する
-- Exhibit -

-- Exhibit --
Click the Exhibit button.
Referring to the exhibit, your AS is connected to ISP-A and ISP-B using BGP. R1 and R2 are advertising your AS's 172.25/16 prefix upstream to both ISPs, and both ISPs are providing a full BGP route table. You want to influence traffic flow so that traffic towards your network enters through R1.
Which action would meet the requirement?
Apply the following as an export policy towards ISP-B:

-- Exhibit --
Click the Exhibit button.
Referring to the exhibit, your AS is connected to ISP-A and ISP-B using BGP. R1 and R2 are advertising your AS's 172.25/16 prefix upstream to both ISPs, and both ISPs are providing a full BGP route table. You want to influence traffic flow so that traffic towards your network enters through R1.
Which action would meet the requirement?
Apply the following as an export policy towards ISP-B:
正解:A
解答を投票する
Referring to the exhibit, traffic is being sent from user1 to server 1 .The traffic is being classified using IP presentence into the default forwarding class expedited forwarding on
R1 R2 and R4 .however R3 has no class service configuration. What are two potential actions R3 will take on the traffic? (Choose two)

R1 R2 and R4 .however R3 has no class service configuration. What are two potential actions R3 will take on the traffic? (Choose two)

正解:B、C
解答を投票する
-- Exhibit --
[edit]
user@R1# show routing-options router-id
router-id 1.1.1.1;
[edit]
user@R1# show protocols ospf
area 0.0.0.0 {
interface ge-0/0/7.0;
}
[edit]
user@R2# show routing-options router-id
router-id 2.2.2.2;
[edit]
user@R2# show protocols ospf
area 0.0.0.0 {
interface ge-0/0/8.0 {
priority 200;
}
}
[edit]
user@R3# show routing-options router-id
router-id 222.255.255.255;
[edit]
user@R3# show protocols ospf
area 0.0.0.0 {
interface ge-0/0/8.0;
}
[edit]
user@R4# show routing-options router-id
router-id 239.255.255.255;
[edit]
user@R4# show protocols ospf
area 0.0.0.0 {
interface ge-0/0/6.0 {
priority 0;
}
}
-- Exhibit --
Click the Exhibit button.
All four routers in the exhibit are in the same broadcast domain. The routers were powered on at the same time.
Based on the configurations, which devices are the DR and the BDR
[edit]
user@R1# show routing-options router-id
router-id 1.1.1.1;
[edit]
user@R1# show protocols ospf
area 0.0.0.0 {
interface ge-0/0/7.0;
}
[edit]
user@R2# show routing-options router-id
router-id 2.2.2.2;
[edit]
user@R2# show protocols ospf
area 0.0.0.0 {
interface ge-0/0/8.0 {
priority 200;
}
}
[edit]
user@R3# show routing-options router-id
router-id 222.255.255.255;
[edit]
user@R3# show protocols ospf
area 0.0.0.0 {
interface ge-0/0/8.0;
}
[edit]
user@R4# show routing-options router-id
router-id 239.255.255.255;
[edit]
user@R4# show protocols ospf
area 0.0.0.0 {
interface ge-0/0/6.0 {
priority 0;
}
}
-- Exhibit --
Click the Exhibit button.
All four routers in the exhibit are in the same broadcast domain. The routers were powered on at the same time.
Based on the configurations, which devices are the DR and the BDR
正解:B
解答を投票する